#1568 closed defect (fixed)
vbox-OSE: pxegrub won't start after successful transfer via tftp
| Reported by: | Vladimir | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 1.6.0 |
| Keywords: | pxegrub SuSE OSE | Cc: | |
| Guest type: | other | Host type: | other |
Description
pxegrub won't start after successful transfer via tftp
from host in OSE (SuSE rpm) build,
while works fine with binary non-OSE (Sun xVM) VirtualBox
from suse-10.3 rpm package.
May be related: it seems OSE has single NIC driver linked in,
while configurator offers 3 various,
but ignores any selects, regards to last pxegrub message
before it hungs (see vbox-netconfig.png and vbox-pxeboot.png attached).
May be related: both PCnet LANCE NIC-s are pxe-booting in non-OSE vbox,
but, Intel 1Gbit card:
- won't boot via pxe [grub], reporting attempt of use PCnet NIC;
- won't show RX and TX packets counts, while ping and ssh to host work fine(!)
Attachments (2)
Change History (5)
by , 17 years ago
| Attachment: | vbox-pxeboot.png added |
|---|
comment:1 by , 17 years ago
| Component: | other → network |
|---|
comment:2 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Pleas retry with the upcoming release 2.2.0 and reopen if the problem persists.
comment:3 by , 16 years ago
Don't forget to attach the VBox.log file of such a VM session in that case.
Note:
See TracTickets
for help on using tickets.
pxegrub startup screenshot.