Hi Christian, First, I tried to create a lvl2 VM using your suggestion with `uvtool-libvirt`. I have tried this on one of my lvl1 VM, which is an OpenStack compute node.
``` compute@L1: $ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 release=xenial label=daily compute@L1: $ uvt-kvm create --memory 4096 --disk 30 --cpu 4 --password ubuntu xenial-guest-lvl1 arch=amd64 release=xenial label=daily ``` And this way, it works ! However, if I use the OpenStack API to create a lvl2 VM on this same compute node, the OpenStack Nova VM fails. . . . . If we recap the 3 options tested here to create an lvl2 VM: 1. OpenStack API -> FAIL The lvl2 VM is stuck for example at: "Starting Update UTMP about System Boot/Shutdown..." 2. virt-install "By hand" -> FAIL If I do like in [1], VM generate the same error than in my 1st post. 3. uvtool-libvirt -> SUCCESS Your example works just fine. [1] https://youth2009.org/post/kvm-with-ubuntu-cloud-image/ . . . . You say: > That guest runs just fine and is happy. > So it has to be part of your guest configuration in some way. I agree: maybe I should look further into the options of `virt-install`. What I give in my first post (the virt-install script) is my way of creating lvl1 VM. NB: It seems that for the moment, --os-variant has no `ubuntu18.04` value. I keep this parameter to ubuntu16.04, even if I want to create a 18.04 VM. The difference between Ubuntu 16.04 and 18.04 regarding `virt-install`: * 16.04: virt-install --version is 1.3.2 * 18.04: virt-install --version is 1.5.1 So maybe the problem comes from `virt-install` and the way I configure a VM. . . . . However when looking at the OpenStack API, here I am not the one who provides the guest configuration. I provide the OpenStack API with the info it needs to create a new OpenStack instance (i.e. flavor, image type, cloud-init config, etc...) and then the API ~converts~ this description to instantiate this OpenStack instance on the compute node which is running qemu/KVM. I am not sure what the OpenStack API uses to do that. I assume it uses python-libvirt [2] but I may be wrong. [2] https://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Guest_Domains-Lifecycle_Control.html#libvirt_application_development_guide_using_python-Guest_Domains-Lifecycle-Provisioning_and_Starting . . . . You say: > I wonder if your way to setup the guests uses special CPU types [...] > > Waiting for your feedback on guest CPU definitions in your case. My CPU is a Intel Xeon Broadwell. On the lvl0, which have 48 cores: ``` baremetal@L0:cat /proc/cpuinfo | grep invpcid | wc -l 48 ``` On the lvl1, which is a VM with 20 vCPU: ``` compute@L1:$ cat /proc/cpuinfo | grep invpcid | wc -l 20 ``` . . . . Dumpxml of a working lvl1 VM "compute41": https://paste.ubuntu.com/p/KMrCKGgvRg/ Dumpxml of a failing lvl2 VM created by the OpenStack/Nova API on "compute41": https://paste.ubuntu.com/p/9FrhMWWgVk/ Dumpxml of a working lvl2 VM created by uvtool-libvirt: https://paste.ubuntu.com/p/4CztPDW7fM/ On difference I see with your Dumpxml is for os part: machine='pc-i440fx-bionic' for me machine='pc-i440fx-xenial' for you Maybe this is due to the way I install qemu with cloud-archive:queens [3]. [3] https://wiki.ubuntu.com/OpenStack/CloudArchive . . . . qemu logs for the lvl2 VM created by uvtool-libvirt: ``` compute@L1:$ cat /var/log/libvirt/qemu/xenial-guest-lvl2.log [...] 2018-10-12T14:28:03.317760Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2] ``` If I miss sth, let me know! -- Nicolas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797332 Title: qemu nested virtualization is not working with Ubuntu16.04 + Intel CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1797332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
