Sorry I missed the initial mailing list link in all the initial text :-/ It was just too similar to another bug that was coming by last week that I short-cut the wrong way.
Thanks Shivaprasad for clarifications. Also thansk Nish to spot there is a new revision. With a new look I recreated the case. The essential addition to trigger is (independent to the actual values): <maxMemory slots='16' unit='KiB'>10485760</maxMemory> (nothing more of the xml needs to be special) Code Review: We can't link against qemu_domain.c, but a comment that the define is essentially taken from virQEMUDriverDomainDefParserConfig might be nice to later on follow any updates there. Also mentioning why you dropped VIR_DOMAIN_DEF_FEATURE_USER_ALIAS for the same reason. (I'll reply so to the list shortly) The error can also be triggered in an isolated way. Get the uuid of the guest and dump it to a test.xml file. Then run: /usr/lib/libvirt/virt-aa-helper --create --dryrun --uuid 'libvirt-e137cfac-8880-484a-95f5-205a9fd604e7' < test.xml virt-aa-helper: error: could not parse XML virt-aa-helper: error: could not get VM definition I built a test in a ppa at [1] with your patch. With that installed retesting the above it works well. [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3122 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746431 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start the guest from Ubuntu1804 KVM host machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746431/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
