Hello!
Many thanks for your reply!
I have updated sanbootconf and change my virtual NIC to Intel e1000, but I
still have a problem.
See my log. After "iBFT requested" I have no nothing about detected NIC.
nt!DbgBreakPoint:
80527bd0 cc int 3
kd> g
SAN Boot Configuration Driver initialising
Found ACPI table "iBFT" at 9cb40 OEM ID "FENSYS" OEM table ID "gPXE"
Found iBFT Initiator 0:
Flags = 0x3, valid, boot selected
iSNS = 0.0.0.0
SLP = 0.0.0.0
Radius = 0.0.0.0, 0.0.0.0
Name = iqn.2000-09.org.etherboot:UNKNOWN
Found iBFT NIC 0:
Flags = 0x3, valid, boot selected
IP = 192.168.21.231/24
Origin = 0
Gateway = 192.168.21.138
DNS = 192.168.21.138, 0.0.0.0
DHCP = 0.0.0.0
VLAN = 0000
MAC = 00:0c:29:09:46:b7
PCI = 02:00.0
Hostname =
Found iBFT target 0:
Flags = 0x3, valid, boot selected
IP = 192.168.21.1
Port = 3260
LUN = 0000-0000-0000-0000
CHAP type = 0 (None)
NIC = 0
Name = iqn.2008-08.com.starwindsoftware:hohlov-pc-winxp
CHAP name =
CHAP secret =
Reverse CHAP name =
Reverse CHAP secret =
No sBFT found
Attempting SAN boot; will wait for system disk
iBFT requested
Waiting for SAN system disk (attempt 1)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034):
"\??\SCSI#Disk&Ven_VMware_&Prod_VMware_Virtual_S&Rev_1.0#4&5fcaafc&0&000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Waiting for SAN system disk (attempt 2)
System disk is <unknown>, boot disk is <unknown>
Disk unavailable (c0000034):
"\??\SCSI#Disk&Ven_VMware_&Prod_VMware_Virtual_S&Rev_1.0#4&5fcaafc&0&000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Waiting for SAN system disk (attempt 3)
[... and so on...]
--
Best regards,
Yuriy Khokhlov.
2010/6/29 Stefan Hajnoczi <stefa...@gmail.com>
> On Tue, Jun 29, 2010 at 5:13 AM, Sean Shoufu Luo <luosho...@gmail.com>
> wrote:
> > I have met similar problem in Bochs 4.2 some day before. And resolved
> with
> > Stefan's help. Maybe not the same problem as you, just paste the link for
> > you reference:
> > http://www.mail-archive.com/gpxe@etherboot.org/msg00179.html
>
> VirtualBox has a BIOS based on Bochs BIOS, so this could be the issue.
>
> On a related note, Andrei Faur has rewritten the pcnet32 driver for
> gPXE 1.0.1. The new driver performs better and I'd recommend running
> gPXE 1.0.1-rc1 under VirtualBox for now. gPXE 1.0.1 is close to being
> released and contains the new driver.
>
> Stefan
> _______________________________________________
> gPXE mailing list
> gPXE@etherboot.org
> http://etherboot.org/mailman/listinfo/gpxe
>
_______________________________________________
gPXE mailing list
gPXE@etherboot.org
http://etherboot.org/mailman/listinfo/gpxe
