Proxmox5.0 / VM will not boot from CDROM

[Spiros Pap]

Hi all,

I am creating a VM with a centos iso installed as a CDROM (ide2) and the VM will not boot from cdrom. The seaBIOS sits there doing nothing.

I am doing the same thing on proxmox4.4 and the VM boots just fine from the same iso.

The VM options look the same on both proxmox 4.4 and 5.0.

Any ideas?

Thanx,
Spiros

 

[Spiros Pap]

Hi all,

I am creating a VM with a centos iso installed as a CDROM (ide2) and the VM will not boot from cdrom. The seaBIOS sits there doing nothing.

I am doing the same thing on proxmox4.4 and the VM boots just fine from the same iso.

The VM options look the same on both proxmox 4.4 and 5.0.

Any ideas?

Thanx,
Spiros

I just noticed that proxmox 4.4 uses SeaBios 1.9, while proxmox5.0 has SeaBIOS1.10. When SeaBIOS1.9 boots, I can see it tries to boot from harddisk and fails (becuase there is no OS) and then it goes to cdrom and network and I can see all these tries. When SeaBIOS 1.10 (proxmox5.0) boots, it does not try anything. It just prints the name of the BIOS and stays there doing nothing....

Later info: I tried to use SeaBIOS1.9 on proxmox5 but the same thing happened: SeaBIOS1.9 printed the BIOS string and froze when the VM booted. So I guess it is not a BIOS issue.


Spiros

 

[Spiros Pap]

I just noticed that proxmox 4.4 uses SeaBios 1.9, while proxmox5.0 has SeaBIOS1.10. When SeaBIOS1.9 boots, I can see it tries to boot from harddisk and fails (becuase there is no OS) and then it goes to cdrom and network and I can see all these tries. When SeaBIOS 1.10 (proxmox5.0) boots, it does not try anything. It just prints the name of the BIOS and stays there doing nothing....


Spiros

Proxmox5.0 is a test setup on a vmware hypervisor with nested virt enabled. Is it possible that this is the culprit?

Sp

 

[tom]

Proxmox5.0 is a test setup on a vmware hypervisor with nested virt enabled. Is it possible that this is the culprit?

Sp

you should mention such "small details" in the beginning.

see https://bugzilla.proxmox.com/show_bug.cgi?id=1181
=> qm set VMID -machine pc-i440fx-2.6

 

[Spiros Pap]

you should mention such "small details" in the beginning.

see https://bugzilla.proxmox.com/show_bug.cgi?id=1181
=> qm set VMID -machine pc-i440fx-2.6

Well, it took me a day or so to realize the relevance of such a small detail
It works now!

thank you very much,
Sp