I ran into this problem when I cloned a VM that had ceph storage devices to another host. The clone was fine, however I couldn't remove the cloned VM as there were RBD devices mapped on the host where the VM was cloned from.
Running Ceph 0.94.7 and latest Proxmox (free) update.s
Alright, I finally got a chance to revert one of my hosts back to the 2.6.32-32 kernel and that seems to have resolved the issue. PXE booting is now working again. Is there a bug tracker that I can file a bug in for the 3.x kernel?
Thanks!
A couple of other things I've tried with no effect on the issue:
1) Deleted the VM and recreated it. I removed the VM completely from the web console and recreated it.
2) Tried the e1000 and realtek network devices - no change from virtio there, either.
Glad to hear somebody else is/was seeing the same issue. I tried changing my VM's disk from virtio to IDE, but that had no effect on the problem. PXE boot is still hanging on downloading the kernel image from the TFTP server.
Still seeing this issue. I've applied all of the available updates:
# pveversion -v
proxmox-ve-2.6.32: 3.2-136 (running kernel: 3.10.0-3-pve)
pve-manager: 3.2-30 (running version: 3.2-30/1d095287)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-3.10.0-3-pve: 3.10.0-11
pve-kernel-2.6.32-31-pve...
Tried both of those suggestions and the problem still exists, unfortunately. The VM did appear to download a bit more of the PXE boot files than before - it got through the vmlinuz download and this time hung at the initrd.img file. I'm not sure if that had anything to do with the suggested...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.