Re: [Xen-users] How do you give USB to a Windows domU?

[James Pifer <jep@xxxxxxxxxxxxxxxx>]

On Wed, 2009-11-11 at 08:15 +0100, Jeroen Groenewegen van der Weyden
wrote:
>         "tablet" then adding the usb drive, as well as the hub devices
>         themselves. Nothing gets added to the domU though, ie it doesn't show 
> up
>         in the list on the left side of the "Details".
> Please notice that there can be only 1 usb device attached, the tablet
> also counts as one.
> 

Right, I removed the "tablet" then added the usb drive.

> Furtermore your qemu log confuses me, my experience is when the usb is
> not working there are warnings of some sort in the qemu log. If not
> the usb is either not configured or it is working properly. please
> capture the /var/log/messages during the time of the domain startup
> and the vm config file.
> 

If I stop and start xend I get this in /var/log/messages
Nov 11 08:09:03 pcalakxen03 BLKTAPCTRL[26657]: blktapctrl.c:789: blktapctrl: 
v1.0.0
Nov 11 08:09:03 pcalakxen03 BLKTAPCTRL[26657]: blktapctrl.c:791: Found driver: 
[raw image (aio)]
Nov 11 08:09:03 pcalakxen03 BLKTAPCTRL[26657]: blktapctrl.c:791: Found driver: 
[raw image (sync)]
Nov 11 08:09:03 pcalakxen03 BLKTAPCTRL[26657]: blktapctrl.c:791: Found driver: 
[vmware image (vmdk)]
Nov 11 08:09:03 pcalakxen03 BLKTAPCTRL[26657]: blktapctrl.c:791: Found driver: 
[ramdisk image (ram)]
Nov 11 08:09:03 pcalakxen03 BLKTAPCTRL[26657]: blktapctrl.c:791: Found driver: 
[qcow disk (qcow)]
Nov 11 08:09:03 pcalakxen03 BLKTAPCTRL[26657]: blktapctrl.c:791: Found driver: 
[qcow2 disk (qcow2)]
Nov 11 08:09:03 pcalakxen03 BLKTAPCTRL[26657]: blktapctrl.c:791: Found driver: 
[raw image (cdrom)]
Nov 11 08:09:03 pcalakxen03 BLKTAPCTRL[26657]: blktapctrl_linux.c:23: 
/dev/xen/blktap0 device already exists


When I start the domU I get this in /var/log/messages
Nov 11 08:10:46 pcalakxen03 logger: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/2/768
Nov 11 08:10:46 pcalakxen03 kernel: device tap2.0 entered promiscuous mode
Nov 11 08:10:46 pcalakxen03 kernel: br0: topology change detected, propagating
Nov 11 08:10:46 pcalakxen03 kernel: br0: port 3(tap2.0) entering forwarding 
state
Nov 11 08:10:46 pcalakxen03 logger: /etc/xen/scripts/vif-bridge: online 
XENBUS_PATH=backend/vif/2/0
Nov 11 08:10:46 pcalakxen03 kernel: device vif2.0 entered promiscuous mode
Nov 11 08:10:46 pcalakxen03 kernel: br0: topology change detected, propagating
Nov 11 08:10:46 pcalakxen03 kernel: br0: port 4(vif2.0) entering forwarding 
state
Nov 11 08:10:46 pcalakxen03 kernel: physdev match: using --physdev-out in the 
OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported 
anymore.
Nov 11 08:10:46 pcalakxen03 logger: /etc/xen/scripts/vif-bridge: iptables setup 
failed. This may affect guest networking.
Nov 11 08:10:46 pcalakxen03 ifup:     vif2.0    
Nov 11 08:10:46 pcalakxen03 ifup:               No configuration found for 
vif2.0
Nov 11 08:10:46 pcalakxen03 logger: /etc/xen/scripts/vif-bridge: Successful 
vif-bridge online for vif2.0, bridge br0.
Nov 11 08:10:46 pcalakxen03 logger: /etc/xen/scripts/vif-bridge: Writing 
backend/vif/2/0/hotplug-status connected to xenstore.
Nov 11 08:10:46 pcalakxen03 logger: /etc/xen/scripts/block: Writing 
backend/vbd/2/768/node /dev/loop0 to xenstore.
Nov 11 08:10:46 pcalakxen03 logger: /etc/xen/scripts/block: Writing 
backend/vbd/2/768/physical-device 7:0 to xenstore.
Nov 11 08:10:46 pcalakxen03 kernel: (cdrom_add_media_watch() 
file=drivers/xen/blkback/cdrom.c, line=108) nodename:backend/vbd/2/768
Nov 11 08:10:46 pcalakxen03 kernel: (cdrom_is_type() 
file=drivers/xen/blkback/cdrom.c, line=95) type:0
Nov 11 08:10:46 pcalakxen03 logger: /etc/xen/scripts/block: Writing 
backend/vbd/2/768/hotplug-status connected to xenstore.

Nothing about usb in either case.

USB is working on dom0. I mean I can access the USB drive. I've tried
adding it to the domU using virt-manager while it is both mounted and
unmounted on dom0. 

Is there a way to run virt-manager in some kind of debug to see why it
can't add the usb device to the domU?

Thanks,
James


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