kubevirt: vm-cirros failed to start with error "KVM: entry failed, hardware error 0x0"

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind enhancement

What happened: vm-cirros failed to start when issuing following commands, kubectl create -f cluster/examples/vm-cirros.yaml out/cmd/virtctl/virtctl start vm-cirros

VM was created and VMI was successfully scheduled. However, vmi was failed to startup. root@filmy1:/mnt/data/gowork/src/github.com/yu2003w/kubevirt# kubectl get vm --all-namespaces NAMESPACE NAME AGE RUNNING VOLUME vmtest vm-cirros 2h true
root@filmy1:/mnt/data/gowork/src/github.com/yu2003w/kubevirt# kubectl get vmi --all-namespaces NAMESPACE NAME AGE PHASE IP NODENAME vmtest vm-cirros 2h Running 10.1.60.183 172.16.17.35

VM vm-cirros is always paused and couldn’t be started.

/var/log/libvirt/qemu/vmtest_vm-cirros.log indicated error “KVM: entry failed, hardware error 0x0”.

virt handler indicated error as below, {“component”:“virt-handler”,“kind”:“”,“level”:“error”,“msg”:“Synchronizing the VirtualMachineInstance failed.”,“name”:“vm-cirros”,“namespace”:“vmtest”,“pos”:“vm.go:871”,“reason”:“server error. command SyncVMI failed: "LibvirtError(Code=1, Domain=10, Message=‘internal error: unable to execute QEMU command ‘cont’: Resetting the Virtual Machine is required’)"”,“timestamp”:“2019-05-24T06:21:08.843458Z”,“uid”:“12a3cb05-7dd4-11e9-963e-0016ac101123”} {“component”:“virt-handler”,“level”:“info”,“msg”:“re-enqueuing VirtualMachineInstance vmtest/vm-cirros”,“pos”:“vm.go:547”,“reason”:“server error. command SyncVMI failed: "LibvirtError(Code=1, Domain=10, Message=‘internal error: unable to execute QEMU command ‘cont’: Resetting the Virtual Machine is required’)"”,“timestamp”:“2019-05-24T06:21:08.846499Z”}

vmtest_vm-cirros.log

What you expected to happen: vm-cirros could be started. How to reproduce it (as minimally and precisely as possible): 1, deploy kubevirt on k8s cluster installed on ubuntu 2, kubectl create -f cluster/examples/vm-cirros.yaml 3, _out/cmd/virtctl/virtctl start vm-cirros

Anything else we need to know?:

Environment:

  • KubeVirt version (use virtctl version): Client Version: version.Info{GitVersion:“v0.17.0-110+e115bd5bd1b381-dirty”, GitCommit:“e115bd5bd1b3816c92864a0c42048ad20f5b11cc”, GitTreeState:“dirty”, BuildDate:“2019-05-24T02:08:06Z”, GoVersion:“go1.11.5”, Compiler:“gc”, Platform:“linux/amd64”} Server Version: version.Info{GitVersion:“v0.17.0-110+e115bd5bd1b381-dirty”, GitCommit:“e115bd5bd1b3816c92864a0c42048ad20f5b11cc”, GitTreeState:“dirty”, BuildDate:“2019-05-24T02:12:37Z”, GoVersion:“go1.11.5”, Compiler:“gc”, Platform:“linux/amd64”}
  • Kubernetes version (use kubectl version): 1.12.4
  • VM or VMI specifications: cluster/examples/vm-cirros.yaml
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release): NAME=“Ubuntu” VERSION=“18.04.2 LTS (Bionic Beaver)” ID=ubuntu ID_LIKE=debian PRETTY_NAME=“Ubuntu 18.04.2 LTS” VERSION_ID=“18.04” HOME_URL=“https://www.ubuntu.com/” SUPPORT_URL=“https://help.ubuntu.com/” BUG_REPORT_URL=“https://bugs.launchpad.net/ubuntu/” PRIVACY_POLICY_URL=“https://www.ubuntu.com/legal/terms-and-policies/privacy-policy” VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic
  • Kernel (e.g. uname -a): Linux filmy1.fyre.ibm.com 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  • Install tools:
  • Others:

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 19 (8 by maintainers)

Most upvoted comments

@rmohr I will open bugzilla ticket. Now I closed this issue. Thanks all your guys for helping me a lot.

@cynepco3hahue I tried to disable cpu features in vmi-fedora.yaml as below,

cpu:
      features:
      - name: "mpx"
        policy: disable
      - name: "avx512f"
        policy: disable
      - name: "avx512cd"
        policy: disable

Then ran the test again, however, it still failed with following log,

-cpu Broadwell-IBRS,vme=on,ss=on,f16c=on,rdrand=on,hypervisor=on,arat=on,tsc_adjust=on,
mpx=off,avx512f=off,avx512cd=off,ssbd=on,xsaveopt=on,abm=on,invpcid=off \

Worked VMI log is as below,

-cpu Broadwell-IBRS,vme=on,ss=on,f16c=on,rdrand=on,hypervisor=on,arat=on,tsc_adjust=on,
ssbd=on,xsaveopt=on,abm=on,invpcid=off \

It looks like the problem is not caused by cpu flags. And now I don’t have any ideas about this issue.