------- Comment From [email protected] 2018-02-21 06:12 EDT------- Hi,
--> Able to start the guests from host system with max memory tag successfully with libvirt 4.0.0 version. Issue fixed with latest 4.0.0 version. # virsh version Compiled against library: libvirt 4.0.0 Using library: libvirt 4.0.0 Using API: QEMU 4.0.0 Running hypervisor: QEMU 2.11.0 root@boslcp3:/home# uname -a Linux boslcp3 4.15.0-041500rc9-generic #201801212130 SMP Mon Jan 22 03:36:42 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:/home# uname -r 4.15.0-041500rc9-generic root@boslcp3:/home# virsh dumpxml boslcp3g1 | grep max <maxMemory slots='16' unit='KiB'>16777216</maxMemory> root@boslcp3:/home# virsh start --console boslcp3g1 Domain boslcp3g1 started Connected to domain boslcp3g1 Escape character is ^] ***** QEMU Starting Build Date = Dec 13 2017 13:46:58 FW Version = buildd@ release 20170724 Press "s" to enter Open Firmware. Press F12 for boot menu. root@boslcp3g1:~# free -h total used free shared buff/cache available Mem: 6.0G 428M 4.4G 7.6M 1.1G 4.6G Swap: 2.0G 0B 2.0G -- 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: virt-aa-helper: do not fail with memory slots specified in guest xml 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
