Opened 16 years ago
Closed 14 years ago
#2536 closed defect (fixed)
PXE Boot failure -> Fixed in SVN
| Reported by: | Owned by: | ||
|---|---|---|---|
| Component: | network/hostif | Version: | VirtualBox 3.2.4 |
| Keywords: | pxe amd-v | Cc: | |
| Guest type: | other | Host type: | Linux |
Description
PXE Boot from network fails. Transmission of the kernel from tftp server interrupts after a while. This problem only appears if VT-x/AMD-V activated.
See attached screenshot and logfile.
VirtualBox 2.0.4 r38406 running on debian linux amd64
Attachments (7)
Change History (32)
by , 16 years ago
| Attachment: | pxe-boot-failure.log added |
|---|
comment:1 by , 16 years ago
Networkadapter is PCnet-Fast III connected to hostinterface vbox1 (bridged)
comment:2 by , 16 years ago
Is somebody reading this? Problem persists with VirtualBox 2.1.0 (network bridged to hostinterface eth0)
comment:3 by , 16 years ago
Just to be sure: You don't experience this when AMD-V is disabled for that VM (are you 100% sure)?
comment:4 by , 16 years ago
I have never seen that problem with deactivated AMD-V. With deactivated AMD-V PXE boot fails sometimes because there is no DHCP-response. But if TFTP tranfer is once started it completes in every case. PXE-boot also seems to be about twice as fast with AMD-V deactivated. Failure rate with AMD-V activated is about 80%. Please ask me if you need more information.
comment:5 by , 16 years ago
Sorry, I have to correct my last posting.
AMD-V. With deactivated AMD-V PXE boot fails sometimes because there is no DHCP-response.
This only happens with Intel PRO/1000.
comment:6 by , 16 years ago
It seems that I have the same kind of problem.
I run virtualbox-ose 2.1.0 and I can't use PXE on any VM. Wether I chose PCnet-PCI II or PCnet-FAST III, when I try to do PXE boot the screen stays black, 100% CPU on host and that's all.
But on this VM, deactivating VT-x (I'm on a Core2Duo) fixes the problem.
I can't try Intel card as I run -ose, but it seems the problem is shared anyway.
Cheers, -- Yves-Alexis
comment:7 by , 16 years ago
Oh and BTW it seems RIS (Remote Installation Service) by MS is failing after the configuration part, on virtualbox while it works fine on vmware, for example.
comment:9 by , 16 years ago
I also confirm problem persists with VirtualBox 2.1.2-41885
In order for PXE boot to work, I had to:
- Set host interface (eth0) to promiscuous mode (otherwise, VBox guest's PXE agent wouldn't respond to ARP request from TFTP server): ifconfig eth0 promisc
- Disable Intel VT extensions (CPU Intel Q9300), or TFTP download would get stuck before end of download (never at the same point, though)
Hope this helps
comment:10 by , 16 years ago
| Component: | network → network/hostif |
|---|
comment:12 by , 16 years ago
| Keywords: | amd-v added |
|---|---|
| Summary: | PXE Boot failure → PXE Boot failure -> Fixed in SVN |
| Version: | VirtualBox 2.0.4 → VirtualBox 2.1.4 |
The fix will be included in a future VBox version.
comment:13 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:14 by , 15 years ago
This is now really fixed. PXE boot performance is significantly faster now. Will be part of the upcoming 3.0 release.
comment:15 by , 15 years ago
I've just tried with virtualbox-ose on Debian sid, and it still doesn't work. Same symptoms:
- if VT-x is enabled, as soon as the guest gets the startom.com executable from the TFTP server and tries to run it, it goes to “Guru Meditation” error.
- if VT-x is disabled, the startom.com / OSChooser part is run fine, but when bootstrapping to the selected installation, it only reboots without doing anything.
Maybe it's a different issue?
comment:16 by , 14 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
i've installed VirtualBox-3.2-3.2.4_62467_fedora12-1.i686 on my fedora-12 and it's still not working. ie. if i turn off VT-x/AMD-V support than it's working, but if turn it on than it's hang:-(
comment:17 by , 14 years ago
Do you realize it's not really useful to reopen tickets without providing any information? VBox.log of that session is the bare minimum...
comment:18 by , 14 years ago
you've got right.
- i attached the log when VT-x/AMD-V disabled and the pxe boot menu appeared than poweroff the guest.
- i attached the log when VT-x/AMD-V enabled and wait many second where it hang than poweroff the guest.
- i attached the screenshot of the guest where it's hang.
comment:20 by , 14 years ago
Unable to reproduce such problem with or w/o VT-x/AMD-V. Tried latest Debian netboot installation (http://ftp.debian.org/debian/dists/stable/main/installer-i386/current/images/netboot/) Unpacked netboot.tar.gz to tftpboot directory and configured DHCP to offer pxelinux.0 file. Boots and installs well.
Can you upload your images/configs (if it possible and legal) somewhere please?
comment:21 by , 14 years ago
fedora people suggest to update from pxeboot from 3.73 to 3.83 and it seems now both virtualbox and kvm are able to boot from net. thanks. ps. anyway it's be useful to add to the faq that older pxeboot can't work.
comment:22 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
comment:23 by , 14 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
This problem is back on 4.0. Only if VT-x/AMD-V support is disabled boot works.
comment:25 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
The problem was fixed in 4.0.2.
VM logfile