Alan Romeril wrote: > The iscsi blue screen names xvmbus.sys, interestingly if you don't > load the PV disk driver the iscsi volume works fine with the XVMbus > and XVMnet drivers at about 50-60 MB/sec sequential read. Cheers, > Alan
We've found the cause of the iscsi problem. The disk driver goes to attach to it (because it is a disk in one sense), and can't find a device for it in the backend. This case isn't handled properly, so you get the blue screen. The workaround, as you have already discovered, is to remove the xVMBus.sys driver and run your real disks in emulated mode. The bug is tracking all of this: 6770912 Guest additions for Windows inhibit MSFT iscsi initiator and it will be fixed in January. To answer another question of yours that went unanswered: > I've downloaded the EA2 guest additions, what's the best way to > install them on a domain that already has the earlier versions > running? Best bet is to uninstall them the official Windows way (control panel -> add/remove programs), and then install the new ones (followed by a reboot, of course). Unofficially, you can just replace the .sys driver binaries in c:\windows\system32\drivers with the new versions and reboot. There are three: xVMBus.sys, xVMNet.sys, and xVMStorFlt.sys. - Russ _______________________________________________ xen-discuss mailing list [email protected]
