Also verifying this on Azure Cloud. I enabled -proposed and installed qemu 4.2-3ubuntu6.3 on a Focal instance.
$ sudo apt-cache policy qemu-kvm | grep Installed Installed: 1:4.2-3ubuntu6.3 >From there I executed the following: $ sudo -s # apt install qemu-kvm bridge-utils # BR_NAME="br0" # BR_ADDR="192.168.1.10" # ip link add "$BR_NAME" type bridge # ip addr add "$BR_ADDR"/24 dev "$BR_NAME" # ip link set "$BR_NAME" up # tap_name="tap1" # br_name=$BR_NAME # ip tuntap add $tap_name mode tap user $(whoami) multi_queue # ip link set $tap_name up # ip link set $tap_name master $br_name Download a guest VM: # wget https://cloud-images.ubuntu.com/focal/current/focal-server- cloudimg-amd64-disk-kvm.img Launch the VM: # /usr/bin/qemu-system-x86_64 -cpu host -smp 2 -m 2048 -hda focal-server-cloudimg-amd64-disk-kvm.img -device virtio-net-pci,netdev=net0,mac=52:54:00:f5:be:83 -netdev user,id=net0,hostfwd=tcp::60022-:22 -device virtio-net-pci,netdev=net1,mac=52:54:00:c6:29:dc,mq=on,vectors=10 -netdev tap,id=net1,ifname=tap1,script=no,vhost=on,queues=4 -display none -enable-kvm -daemonize QEMU successfully starts without error, and checking ps and logs shows the QEMU VM is alive and well: 2500 ? Sl 0:31 /usr/bin/qemu-system-x86_64 -cpu host -smp 2 -m 2048 -hda focal-server-cloudimg-amd64-disk-kvm.img -device virtio- net-pci,netdev=net0,mac=52:54:00:f5:be:83 -netdev user,id= I can ping the VM and ssh in. I am happy to also say this bug is verified. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882774 Title: issues with secondary VMX execution controls To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1882774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
