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