Boot problem when starting a VM

fba said:
@leesteken
just an example: https://pimylifeup.com/raspberry-pi-proxmox/
Click to expand...
Sure, but that's not Proxmox VE, while it appears to still be using Proxmox branding (which might be an issue). Maybe pimyllifeup or jiangcuo can answer support questions?
fba said:
You might try, what is described here: https://forum.proxmox.com/threads/h...-uefi-qemu-dvd-rom-time-out.83521/post-435514
Click to expand...
I do appreciate that you are trying to help the OP (more that I did with my reply).
 
  • Like
Reactions: Johannes S
leesteken said:
Sure, but that's not Proxmox VE, while it appears to still be using Proxmox branding (which might be an issue). Maybe pimyllifeup or jiangcuo can answer support questions?
Click to expand...
Sorry that my answer was short and not providing my intentions. I just wanted to point out, that there are possibilities to get Proxmox VE running on a Rasberry Pi. By no means I wanted it to be recognised as officially supported, which it isn't of course.

The project page of jiangcuo states this also:
This is an unofficial community project where we ported Proxmox VE to non-x86 platforms.

ProxmoxVE acts as upstream and Port acts as downstream. If support is required, it is provided by Port, not Proxmox upstream.
Click to expand...
 
  • Like
Reactions: leesteken
Hi Zoom,

Can you please provide us with a screenshot of the "Options" tab for the VM this is effecting?
 
Hi Zoom,

Thankyou for that! I should have also asked for a screen shot of the "Hardware" tab also.

I see you have the QEMU agent enabled, have you managed to get the VM booted in the past and installed it (and the associated virtIO drivers?)
 
Here is the hardware tab:
1736331789202.png

I have never been able to start the VM, from the first execution I have this message
 
Hi Zoom,

Have a go with changing the SCSI controller. Change it to the Default LSi adapter, see if this makes any difference.

I have had issues on both windows and linux distros where i have tried to use the VirtIO stuff and it fails on first boot as it does not have the drivers.

Can you also open the CPU options and drop a screen shot of that please?
 
Hi Zoom,

I am afraid i am out of ideas currently.

My train of thought was that maybe you had used the VirtIO drivers without having them installed (thus the machine would not boot as it would not be able to see the HDD). But as you are only given the VitIO adapters as option in your install, then this might not be the case (or it might still be, but we don't have any other way of testing it).

Another thing to look at is the controller for the CD Drive. Can you change that from SCSI to SATA or IDE? if so try the following:
1. Change the CD Drive to SATA
2. Change the boot order on the options tab to SATA
3. Attempt to boot the machine
4. Change the CD Drive to IDE
5. Change the boot order on the options tab to IDE
6. Attempt to boot the machine

If all these options fail, then im not sure where to go :(
 
Change the CPU Type from Default(host) to something else, maybe start with kvm64 & then try some others. My thinking:

The CPU type setting will expose some features of the CPU to the VM. Type host will expose all features, however your physical CPU is actually a completely different architecture than what is expected in this environment.
 
  • Like
Reactions: matto
You must log in or register to reply here.
Top Bottom