internal-error on PXE Boot - issue with recent iPXE version?

Kaeltis

New Member
Jul 22, 2016
6
0
1
33
Hey,

I'm currently trying to network boot the FOG client via PXE, however after some initial loading, the VM goes into a "internal-error" state, where it's stuck forever.

firefox_2016_07_21_13_22_59.png


I already tried updating the iPXE ROM following this guide https://gist.github.com/papamoose/e0b18d002f8686aaf767, but that didn't change anything (is it the right location for the files?)

Any clues on how to fix this?
 
Try the iPXE cd image and boot from them. It helped me.

Locations are:

Code:
root@pve4-test ~ > dpkg -L pve-qemu-kvm | grep rom
/usr/share/kvm/pxe-virtio.rom
/usr/share/kvm/pxe-pcnet.rom
/usr/share/kvm/efi-pcnet.rom
/usr/share/kvm/pxe-ne2k_pci.rom
/usr/share/kvm/efi-rtl8139.rom
/usr/share/kvm/pxe-rtl8139.rom
/usr/share/kvm/efi-ne2k_pci.rom
/usr/share/kvm/efi-eepro100.rom
/usr/share/kvm/efi-virtio.rom
/usr/share/kvm/pxe-eepro100.rom
/usr/share/kvm/efi-e1000.rom
/usr/share/kvm/pxe-e1000.rom
 
Strange.. I tried booting the iPXE .iso and it's also causing an internal-error, is there an incompatibility between iPXE and KVM or something?

firefox_2016_07_22_23_08_21.png
 
Code:
proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
pve-manager: 4.2-2 (running version: 4.2-2/725d76f0)
pve-kernel-4.4.6-1-pve: 4.4.6-48
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-39
qemu-server: 4.0-72
pve-firmware: 1.1-8
libpve-common-perl: 4.0-59
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-14
pve-container: 1.0-62
pve-firewall: 2.0-25
pve-ha-manager: 1.0-28
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie
openvswitch-switch: not correctly installed
 
Even tried it on different hardware now, still no luck. Any ideas? Or at least a way to get some debug output?
 
I tried updating iPXE and then SeaBIOS first from sources and then from qemu's repo, now it get's stuck at an earlier stage. Is there an incompatibility between proxmox and recent iPXE versions?

firefox_2016_07_26_15_51_26.png
 
Okay, it's a hardware problem. It's working fine on a proxmox server with a Xeon L5640 but not on one with a L5420.
No clue what do do now, since the working one is in use for something different.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!