Rance Hall schrieb:
I have two main problems with virtualbox and need some advice on how
to get around what I'm finding...
1) gPXE can sanboot from iscsi:FQDN:::1:win7
where FQDN is the hostname of my server and 1 is the LUN that needs to boot
Virtualbox can't seem to figure this out.
I can VBoxManage addiscsidisk --server --lun --target
but all I get is an error that there was a VERR_PARSE_ERROR which if I
read the documentation correctly means that something is now wrong
with the xml configuration file.
It can also mean that it doesn't understand what the iSCSI server is
babbling. Can you provide a VBox.log file for such a failed boot attempt?
The syntax of the iscsi disk label shows the lun AFTER the target
name, but I cant tell if this is just a label problem or if its a real
problem.
2) when netbooting with pxe to gpxelinux.0 and using the gpxe prompt
to set keep-san 1
and set sanboot iscsi:FQDN:::1:win7 and getting the proper notice that
the sanboot setup was successful but that the disk could not be booted
as it has no OS, I should be able to type "exit" and the gPXE prompt
and the boot sequence should continue at the next device which is the
DVD/CD device.
Vbox hangs right after I type "exit" and does nothing,
Returning to the BIOS boot code is a known trouble area... in any BIOS ;)
Klaus
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
