Comment 13 for bug 2037752

Ah! So, initially, the request failed with:

jbm@lmf-storage-1:~$ maas jbm vm-host compose -k 3
Unable to compose KVM instance in 'kvm-1'. CPU overcommit ratio is 1.0 and there are -8 available resources; 1 requested.Memory overcommit ratio is 1.0 and there are -16384 available resources; 2048 requested.

However, to verify that maas could communicate with the KVM host, I initiated a 'Refresh' from the GUI. After that, both my CLI and Web-UI compose operations now succeed. I know I have 'Refreshed' the KVM host before (since I created my last VM in virt-manager and Refreshed to get MAAS to pick it up). But now the refresh seems to have solved all of my issues.

Not sure how my system got into this state twice (first with 3.4~rc and then with 3.3.latest). Both were installed from packages, after which I discovered/commissioned/deployed an Ubuntu 20 KVM host (same hardware on both installs). According to dpkg.log, no packages have been updated since my 3.3 install on the 6-October.

I'm happy to accept that this was "operator error" if someone has any clue what I might have done wrong. I initially only reported the bug against 3.4~rc as I felt I had found a simple issue in the ~rc2 virsh handling.

Thanks for your help.

-Josh