Vasiliy Ulyanov

Yeah, this request was raised quite a while ago. We will probably need to re-evaluate our current hw requirements to potentially also include SNP. Will close this for now.

@alicefr, `pull-kubevirt-e2e-kind-sriov` has failed several times in a row with the same set of tests. This probably needs a closer look. Adding a hold. Feel free to remove if it...

This looks similar to https://github.com/kubevirt/kubevirt/issues/10555. @mansoncui, I see that you use `v1.1.0-alpha.0`. Could you try with `v1.0.0`? Also, could you please share more info about your environment? What Kubernetes distro...

Is it Minikube / Kind or some other Kubernetes distro?

Please attach full `virt-handler` and `virt-launcher` logs.

Previously, the error in the log was `Unable to open /dev/kvm: No such file or directory`: ```json {"component":"virt-launcher","level":"error","msg":"Unable to open /dev/kvm: No such file or directory","pos":"virHostCPUGetCPUID:1422","subcomponent":"libvirt","thread":"46","timestamp":"2023-10-22T07:05:51.373000Z"} ``` Now it is...

@vsundarraj-px, please provide some details about your environment and issue: - your host OS - do you have apparmor/selinux enabled? - bare-metal or nested? - check the comment https://github.com/kubevirt/kubevirt/issues/10605#issuecomment-1777346409 -...

> Host OS: CentOS Linux release 7.9.2009 (Core)Apparmor enabled Nested > virt-host-validate setlocale: No such file or directory QEMU: Checking for hardware virtualization : FAIL (Only emulated CPUs are available,...

@vsundarraj-px, could you add the bellow metadata to your VM and collect virt-launcher logs? ```yaml metadata: labels: debugLogs: "true" logVerbosity: "6" annotations: kubevirt.io/keep-launcher-alive-after-failure: "true" ``` That should increase the verbosity....

@vsundarraj-px, I personally cannot reproduce the issue on my setup. Regarding the message: > Message: failed to configure vmi network: setup failed, err: open /proc/sys/net/ipv6/conf/all/forwarding: no such file or directory...