pimox7 icon indicating copy to clipboard operation
pimox7 copied to clipboard

TASK ERROR: start failed: QEMU exited with code 1

Open svn-matterize opened this issue 4 years ago • 18 comments

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.

svn-matterize avatar Sep 30 '21 12:09 svn-matterize

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.

TuxfeatMac avatar Oct 02 '21 18:10 TuxfeatMac

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 avatar Oct 03 '21 05:10 svn-matterize

@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?

svn-matterize avatar Oct 03 '21 12:10 svn-matterize

I think you have to adjust te boot order.

TuxfeatMac avatar Oct 03 '21 13:10 TuxfeatMac

Like,

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

Right?

svn-matterize avatar Oct 03 '21 14:10 svn-matterize

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

soxrok2212 avatar Oct 08 '21 17:10 soxrok2212

Same here, console does not work.

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

metronidazole avatar Oct 10 '21 03:10 metronidazole

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

metronidazole avatar Oct 10 '21 06:10 metronidazole

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

svn-matterize avatar Oct 11 '21 11:10 svn-matterize

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/

metronidazole avatar Oct 11 '21 12:10 metronidazole

Unfortunately, it take me to here.

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

svn-matterize avatar Oct 11 '21 12:10 svn-matterize

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

metronidazole avatar Oct 20 '21 13:10 metronidazole

maybe this helps ? https://github.com/pimox/pimox7/issues/14#issuecomment-968082718

TuxfeatMac avatar Nov 13 '21 15:11 TuxfeatMac

maybe this helps ? #14 (comment)

This worked for me. Cheers!

soxrok2212 avatar Nov 30 '21 23:11 soxrok2212

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 avatar Feb 19 '22 23:02 andras-szuecs

nvm, found a YouTube video for us n00bs:

https://youtu.be/nulmOjaAnAM

andras-szuecs avatar Feb 20 '22 21:02 andras-szuecs

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

Im-clutch avatar Mar 15 '22 23:03 Im-clutch

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)

tarkantula avatar Apr 01 '22 07:04 tarkantula