Xen users - Jul 2008 - Unable to hot-add disk to Win2K3 HVM with GPLPV drivers

I''m using xen 3.1.2 with fedora8 in dom0 and Win2K3 SP2 with 0.9.10.4 
pre-release drivers in domU.

The domain is defined with virsh, and has a single hard disc on LVM phy: 
and a cdrom from an iso file: the machine boots properly with and 
without /gplpv

I wanted to add another LVM based partition for IOmeter testing, so I did

	virsh attach-disk wintest2 /dev/vgr5/junk xvdc --driver phy

Within Windows, I saw an event logged

	source: XenVbd
	eventid: 4
	descr: 	Driver detected an internal error in its data structures
		for \Device\Scsi\XenVbd3

In Device Manager the exising block devices show as

	Xen Block Device Driver

but the hot-added one shows as

	Xen vbd device #51744

it has the same drivers xen/config/hide/vbd.sys loaded as the 
functioning disks.

If I do a

	virsh detach-disk wintest2 xvdc

I get no error, but the disk doesn''t disappear inside Windows.

I then rebooted the domain and tried

	virsh attach-disk wintest2 /dev/vgr5/junk hdb --driver phy

this time no event was logged, but no new disc showed up in device 
manager, or under disk management

Am I doing something wrong?

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 03/07/2008 09:14, Andy Burns wrote:
> no new disc showed up in device 
> manager, or under disk management
I thought if hot-add wasn''t working I''d be able to just add it
to my
.xml file and redefine the domain with virsh, relevent sections

     <disk type=''block'' device=''disk''>
       <driver name=''phy''/>
       <source dev=''/dev/vgr1/wintest2''/>
       <target dev=''hda''/>
     </disk>
     <disk type=''block'' device=''disk''>
       <driver name=''phy''/>
       <source dev=''/dev/vgr5/junk''/>
       <target dev=''hdb'' bus=''ide''/>
     </disk>
     <disk type=''file'' device=''cdrom''>
       <driver name=''file''/>
       <source file=''/mnt/repo/iso/w2k3_32.iso''/>
       <target dev=''hdc''/>
       <readonly/>
     </disk>

But the new "hdb" device still doesn''t show up in Disk
Management, it
does show in Device Manager, but only named as "xen vbd device #832"

http://adslpipe.co.uk/pics/xendisks.png




_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 03/07/2008 09:44, Andy Burns wrote:
> But the new "hdb" device still doesn''t show up in Disk
Management, it
> does show in Device Manager, but only named as "xen vbd device
#832"
I just upgraded to pre-5

The upgrade went smoothly, didn''t need to switch to non /gplpv mode, 
didn''t get unsigned driver warnings (I imported cert when I installed 
pre-4) obviously do still get non-WHQL driver warnings.

Even before rebooting, the driver had picked up my second hard disc.

After rebooting I was also able to hot-add a third hard disc, it came 
straight up with the device wizard.

Also the delay I was experiencing at startup is gone.

So all in all, pre-5 looks like a good candidate for 0.9.11 proper :-)


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 03/07/2008 09:14, Andy Burns wrote:
> I wanted to add another LVM based partition for IOmeter testing
With 1MB blocks, all reads or all writes, either random or sequential, 
performance always seems to be about 50MB/s, with a 50:50 mix of 
read/write it drops to 30MB/s.

With 4KB blocks, all reads, either random or sequential, performance is 
20MB/s, this doesn''t seem too bad considering the difference in block 
size, but with all writes the performance plummets to under 1MB/s.

One surprising good result, using 2 separate disks, with two worker 
threads, and 1MB blocks, all reads or all writes, either random or 
sequential, the total performance is 180MB/s.



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 04/07/2008 02:18, James Harper wrote:
>> So all in all, pre-5 looks like a good candidate for 0.9.11 proper :-)
>>
> 
> It would have been, except that save/restore doesn''t work now.
Hmm, hot adding a disk worked when I upgraded to 0.9.11-pre5 but now 
seems to fail again with 0.9.11-pre9

Existing domU has LVM for hard disk as hda and iso for cdrom as hdc, I 
created a new LV

# lvcreate --name win2k3data --size 4G vgmirror

Tried adding with

# virsh attach-disk win2k3 /dev/vgmirror/win2k3data hdb --driver phy

or

# virsh attach-disk win2k3 /dev/vgmirror/win2k3data xvdb --driver phy

In each case the XenVbd driver gave an event log entry

"Driver detected an internal error in its data structures for 
\Device\Scsi\XenVbd3"

So I shutdown the domain, added the extra disk to the .xml config, 
undefined and re-defined the domU and restarted it.

     <disk type=''block'' device=''disk''>
       <driver name=''phy''/>
       <source dev=''/dev/vgmirror/win2k3sys''/>
       <target dev=''hda''/>
     </disk>
     <disk type=''block'' device=''disk''>
       <driver name=''phy''/>
       <source dev=''/dev/vgmirror/win2k3data''/>
       <target dev=''hdb''/>
     </disk>
     <disk type=''file'' device=''cdrom''>
       <driver name=''file''/>
       <source file=''/root/w2k3r2_cd1.iso''/>
       <target dev=''hdc''/>
       <readonly/>
     </disk>

The XenVbd driver still gives the same error for the hdb device, it 
shows up differently in device manager, similar to before

http://adslpipe.co.uk/pics/xendisks.png


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> >
> > It would have been, except that save/restore doesn''t work
now.
> 
> Hmm, hot adding a disk worked when I upgraded to 0.9.11-pre5 but now
> seems to fail again with 0.9.11-pre9
> 
> Existing domU has LVM for hard disk as hda and iso for cdrom as hdc, I
> created a new LV
> 
This is a bit of a long shot, but Windows tends to remember the driver
it had attached to various devices, so if you had device #832 running
with 0.9.11-pre5 and that device wasn''t present when you upgraded to
-pre9, windows might still use the old driver.

Once you block-attach the device, can you right click and see what
version of the driver it has loaded? Even if it says -pre9, please try
upgrading the driver anyway.

James

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 21/07/2008 01:53, James Harper wrote:
> This is a bit of a long shot, but Windows tends to remember the driver
> it had attached to various devices, so if you had device #832 running
> with 0.9.11-pre5 and that device wasn''t present when you upgraded
to
> -pre9, windows might still use the old driver.
strange, under "driver details ..." it knew it was using the xen*.sys 
files, but it didn''t show any driver provider/date/version info, so a 
driver update did the trick.
> Once you block-attach the device, can you right click and see what
> version of the driver it has loaded? Even if it says -pre9, please try
> upgrading the driver anyway.
That disk was eventually added via the domU config, I''ll try another 
with block-attach later, as it did seem to work better in pre5.

p.s.

I tried to uninstall of the "wrong" disk in device manager and got
this
event, should the driver either support removal, or deny the request in 
a different way?

log #271 from PlugPlayManager

Driver is preventing the device from stopping. The name of the device 
driver is listed as the vetoing service name below.

  Vetoed device: XEN\VBD\4&32FE5319&1&832
  Vetoing device: Xen\vbd\4&32fe5319&1&832
  Vetoing service name: Driver\XenVbd
  Veto type 6: PNP_VetoDevice

When Windows attempts to install, upgrade, remove, or reconfigure a 
device, it queries the driver responsible for that device to confirm 
that the operation can be performed. If any of these drivers denies 
permission (query-removal veto), then the computer must be restarted in 
order to complete the operation.

  User Action
  Restart your computer.

p.p.s

I notice I get a "safely remove hardware" icon on the taksbar for the 
Xen Net driver, barely a niggle, but perhaps it shouldn''t do that.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> p.p.s
> 
> I notice I get a "safely remove hardware" icon on the taksbar for
the
> Xen Net driver, barely a niggle, but perhaps it shouldn''t do that.
> 
I don''t know how to hide that and also make ''xm
xxx-detach'' work. The
best I could do was refuse to allow the user to actually remove the
hardware from windows (try it - it won''t work). There is probably a
way,
it''s just not a high priority right now.

James

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users