WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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

To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] How do you give USB to a Windows domU?
From: James Pifer <jep@xxxxxxxxxxxxxxxx>
Date: Wed, 11 Nov 2009 09:18:42 -0500
Cc: Jeroen Groenewegen van der Weyden <groen692@xxxxxxxxx>
Delivery-date: Wed, 11 Nov 2009 06:19:29 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AFA6478.8030406@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4AEAEAC9020000990007323F@xxxxxxxxxxxxxxxxxxxxx> <1257176118.2711.15.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <f712b9cf0911020753p17ea9703o3401560bab19d0fb@xxxxxxxxxxxxxx> <4AEE9FD50200009900028FCE@xxxxxxxxxxxxxxxxxxxxx> <f712b9cf0911020806y731634bg866e3acc36ad98b7@xxxxxxxxxxxxxx> <1257800128.13896.23.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <4AF820AB020000990002AA3F@xxxxxxxxxxxxxxxxxxxxx> <1257801871.13896.28.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <1257809832.13896.34.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <4AF91C0A.3070409@xxxxxxxxx> <1257861898.13896.40.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <4AF97A63.6070107@xxxxxxxxx> <1257864520.13896.44.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <4AF98777.90604@xxxxxxxxx> <1257869128.13896.49.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <4AFA6478.8030406@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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

<Prev in Thread] Current Thread [Next in Thread>