Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TASK ERROR: start failed: QEMU exited with code 1 #18

Open
svn-matterize opened this issue Sep 30, 2021 · 18 comments
Open

TASK ERROR: start failed: QEMU exited with code 1 #18

svn-matterize opened this issue Sep 30, 2021 · 18 comments

Comments

@svn-matterize
Copy link

After the successful installation of Proxmox server on Raspberry Pi 4 B (4GB RAM), navigated to the web browser and pointed the host server with port 8006 and I was successful at the login as well.

But when I tried to create the VM I was hit by the following error.

kvm: -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=101: Bus 'ide.1' not found TASK ERROR: start failed: QEMU exited with code 1

Help me to fix this issue.

@TuxfeatMac
Copy link
Contributor

This is an easy fix IDE drivers are not avaivable on the pi so delete your ide-cdrom and readd it as scsi-cd, then it should start up. Hope I could help.

@svn-matterize
Copy link
Author

Hey @TuxfeatMac,

Thanks for writing-up. I need to do this while creating the VM or while installing the proxmox to Pi?

I'm pretty new to this, so a decent tutorial will help me.

@svn-matterize
Copy link
Author

@TuxfeatMac - Good news. Managed to run the VM successfully but when I navigate to console, it always says, guest has not initialized the display (yet)

Am I missing something?

@TuxfeatMac
Copy link
Contributor

I think you have to adjust te boot order.

@svn-matterize
Copy link
Author

Like,

  1. The CD/DVD
  2. Hard-disk
  3. Net

Right?

@soxrok2212
Copy link

I am also seeing this issue after adjusting the boot order.

@metronidazole
Copy link

Same here, console does not work.

@TuxfeatMac Does the console work for you? What OS are you visualizing?

@metronidazole
Copy link

I managed to get the console to work by using the OVMF bios (UEFI) instead of the default (seabios). However I couldn't get it to boot from an ISO / CD drive: failed to load boot0001 uefi qemu cd-rom

@svn-matterize
Copy link
Author

It's taking me to the interactive shell.
Screenshot from 2021-10-11 16-30-06

@metronidazole
Copy link

It's taking me to the interactive shell

You can type exit to get to the boot selection screen. I found this post by one of the devs who says this was a working config (in the pimox v6 build). I haven't tried it yet though: https://old.reddit.com/r/Proxmox/comments/n4d7ev/now_running_proxmox_on_a_raspberry_pi_4_cluster/gwzr4h4/

@svn-matterize
Copy link
Author

Unfortunately, it take me to here.

Screenshot from 2021-10-11 18-01-27

@metronidazole
Copy link

Following this working config https://old.reddit.com/r/Proxmox/comments/n4d7ev/now_running_proxmox_on_a_raspberry_pi_4_cluster/gwzr4h4/ I was able to get it to work.

I just needed to set the cpu to host. One way of doing this is to ssh into the machine and run
$ sudo qm set --cpu=host

@TuxfeatMac
Copy link
Contributor

TuxfeatMac commented Nov 13, 2021

maybe this helps ?
#14 (comment)

@soxrok2212
Copy link

maybe this helps ? #14 (comment)

This worked for me. Cheers!

@andras-szuecs
Copy link

Hey @TuxfeatMac,

Thanks for writing-up. I need to do this while creating the VM or while installing the proxmox to Pi?

I'm pretty new to this, so a decent tutorial will help me.

hey, I have the same issue, what did you do in the end?

@andras-szuecs
Copy link

nvm, found a YouTube video for us n00bs:

https://youtu.be/nulmOjaAnAM

@Im-clutch
Copy link

This is an easy fix IDE drivers are not avaivable on the pi so delete your ide-cdrom and readd it as scsi-cd, then it should start up. Hope I could help.

This worked for me. Thanks

@tarkantula
Copy link

tarkantula commented Apr 1, 2022

I had the same issue where QEMU exited with code 1.
My constellation is a proxmox cluster with 3 nodes, and 2 network bridges (vmbr1 on node 1, and vmbr0 on node2).

The fault was the wrong chosen LinuxBridge on the networkdevise of the VM.

After i migrated the VM which was well connected on vmbr1 from node 1 it couldn´t connect on node2 because the bridge vmbr0.
Therefore The bridgenames of the nodes has to match in the name.
If not, you have to change the network setting of the VM manually, otherwhise the VM won´t start.

I changed the bridge from vmbr1 (Bridge from the other node) to vmbr0 and the VM starts again :-)
Changing the settings of other Hardware like the cdrom bus or other changes were not nessecary.

Thank you all for this issue, your discussion helped me to find the right path to the solution (to change the vm settings)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants