Can commission virsh VM with MaaS Pod, but deploy fails with timeout
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.
Additional info
I ran
sudo su - maasto become themaasuser.
groupsshows that mymaasuser is in thelibvirt group.
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)
server virtualization maas qemu
asked Mar 14 at 4:24
falsePocketsfalsePockets
21128
add a comment |
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.
Additional info
I ran
sudo su - maasto become themaasuser.
groupsshows that mymaasuser is in thelibvirt group.
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)
server virtualization maas qemu
asked Mar 14 at 4:24
falsePocketsfalsePockets
21128
add a comment |
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.
Additional info
I ran
sudo su - maasto become themaasuser.
groupsshows that mymaasuser is in thelibvirt group.
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)
server virtualization maas qemu
asked Mar 14 at 4:24
falsePocketsfalsePockets
21128
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.
Additional info
I ran
sudo su - maasto become themaasuser.
groupsshows that mymaasuser is in thelibvirt group.
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)
server virtualization maas qemu
server virtualization maas qemu
asked Mar 14 at 4:24
falsePocketsfalsePockets
21128
asked Mar 14 at 4:24
falsePocketsfalsePockets
21128
edited Mar 14 at 4:32
falsePockets
asked Mar 14 at 4:24
falsePocketsfalsePockets
21128
asked Mar 14 at 4:24
falsePocketsfalsePockets
21128
asked Mar 14 at 4:24
falsePocketsfalsePockets
21128
21128
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1125495%2fcan-commission-virsh-vm-with-maas-pod-but-deploy-fails-with-timeout%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1125495%2fcan-commission-virsh-vm-with-maas-pod-but-deploy-fails-with-timeout%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
