kubevirt: [flaky ci][ipv6 lane] command SyncVMI failed: LibvirtError qemu unexpectedly closed the monitor KVM: Cannot allocate memory
Is this a BUG REPORT or FEATURE REQUEST?:
Uncomment only one, leave it on its own line:
/kind bug
/kind enhancement
What happened:
The error happened on this test, but seems to be unrelated to the test itself - Networking VirtualMachineInstance with masquerade binding mechanism [test_id:1780]should allow regular network connection without a specific port number
/root/go/src/kubevirt.io/kubevirt/vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:43 Unexpected Warning event received: testvmizbpbhgd8hfqfrkcm8gr2fkfmwzfbpprb9qhj4hcfhlrlvvxx,0a00e945-52d0-4798-817a-5e0190bbb75f: server error. command SyncVMI failed: “LibvirtError(Code=1, Domain=10, Message=‘internal error: qemu unexpectedly closed the monitor: ioctl(KVM_CREATE_VM) failed: 12 Cannot allocate memory\n2020-06-24T16:25:43.013045Z qemu-kvm: failed to initialize KVM: Cannot allocate memory’)” Expected <string>: Warning not to equal <string>: Warning /root/go/src/kubevirt.io/kubevirt/tests/utils.go:409
link to the failing job : https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/3502/pull-kubevirt-e2e-kind-k8s-1.17.0-ipv6/1275775060711313408
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
- KubeVirt version (use
virtctl version): - Kubernetes version (use
kubectl version): - VM or VMI specifications:
- Cloud provider or hardware configuration:
- OS (e.g. from /etc/os-release):
- Kernel (e.g.
uname -a): - Install tools:
- Others:
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15 (15 by maintainers)
An update on
this one seems to be resolved with some disk io cache changes on the nodes.
The issue regarding to
open /dev/null: operation not permittedappears to be unrelated./assign @qinqon
Thanks for investigating the /dev/null issue.