This issue can be reproduced with KVM nodes on our BareMetal MAAS
Step to reproduce:
1. Deploy a KVM node with Xenial / Bionic
2. sudo apt install gcc build-essential cpu-checker qemu-kvm git
3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/kvm-unit-tests/ -b disco
4. cd kvm-unit-tests
5. ./configure
6. make standalone
7. cd tests
8. sudo ./vmx_nm_test
BUILD_HEAD=4671e4ba
timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.wHvN1CDAeZ -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.J5VNtXChPd
enabling ap
(Test interrupted here)
When this happens, the node will stop responding, nothing special can be found in syslog. The virsh on the host will show it's been paused:
$ virsh list
Id Name State
----------------------------------------------------
533 curly paused
This issue can be reproduced with KVM nodes on our BareMetal MAAS
Step to reproduce: ubuntu. com/ubuntu/ kvm-unit- tests/ -b disco qemu-system- x86_64 -nodefaults -device pc-testdev -device isa-debug- exit,iobase= 0xf4,iosize= 0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.wHvN1CDAeZ -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.J5VNtXChPd
1. Deploy a KVM node with Xenial / Bionic
2. sudo apt install gcc build-essential cpu-checker qemu-kvm git
3. git clone --depth=1 git://kernel.
4. cd kvm-unit-tests
5. ./configure
6. make standalone
7. cd tests
8. sudo ./vmx_nm_test
BUILD_HEAD=4671e4ba
timeout -k 1s --foreground 30 /usr/bin/
enabling ap
(Test interrupted here)
When this happens, the node will stop responding, nothing special can be found in syslog. The virsh on the host will show it's been paused: ------- ------- ------- ------- ------- ------- ---
$ virsh list
Id Name State
-------
533 curly paused