I want to use MaaS to manage some VMs.
(My justification is that I have a project which should use 6 machines, but I only have 4, so for now I want to deploy my workload across 2 VMs, and 4 bare metal.)
I discovered MAAS pods, which are designed for exactly this situation.
I want the VMs to be located on the same machine as the MAAS controller (which is running on bare metal).
I added a pod through the MAAS GUI, with address
qemu+ssh://falsePockets@localhost/system and the password I use to log in to user
falsePockets on the MAAS controller.
The pod was added successfully. Through the MAAS GUI I can successfully add and commission new 'machines' through virsh. ( pods > my pod > Take Action > Compose).
When I manually run
virsh list --all, or open Virt Manager, I see the VM which MAAS just created. So MAAS is definitely able to talk to virsh, and has sufficient permissions to create a VM.
Then when it try to deploy (to actually install Ubuntu to the VM), MAAS gets stuck on "Deploying Ubuntu 18.04 LTS", and eventually "Failed deployment". When I open up that VM in Virt Manager and look at the screen, I see that it has failed to PXE boot, and found no bootable installation on the hard drive, so it just sits because it has nothing to boot too.
I have also tried manually creating a VM and PXE booting, to trick MAAS into thinking that a VM is a bare metal machine. That doesn't work. The PXE boot fails. No boot image found.
sudo su - maasto become the
groupsshows that my
maasuser is in the
virsh -c qemu+ssh://opentelco@localhost/system list --allshows the VMs which exist. So MAAS can definitely talk to virsh.
- I have successfully commissioned and deployed bare metal machines.
After the deployment attempt times out, the logs for that (virtual) machine just say "Installation was aborted."
I have enabled DHCP by MAAS on the relevant subnet
I have disabled DHCP by Virsh with
virsh net-edit default, and deleting the
<dhcp>element. ( I tried before and after this)
- I have tried manually rebooting the VMs with virt manager, to trigger a PXE boot. That didn't work. No PXE boot source found.
- this may be a duplicate question. However that question is a bit unclear. There's insufficient detail and it's unclear what 'enlist' means.
- the VM's network connection is a NAT to the default virsh network. (That's what MAAS configured it to be)