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

["Nick Couchman" <Nick.Couchman@xxxxxxxxx>]

The configuration file for the domU is under /etc/xen/vm/ with the name the 
same as the domU.  You can update the config file, then do "xm delete <domU>" 
and then "xm new <domU>" and this should refresh the configuration.  You only 
need to worry about pciback if you want to forward the entire PCI-based USB 
controller through to the domU - this will make the USB controller unavailable 
to dom0, which on most modern machines isn't a great idea as USB is generally 
used for keyboards and mice these days.

-Nick

>>> On 2009/10/30 at 13:49, James Pifer <jep@xxxxxxxxxxxxxxxx> wrote:
> On Fri, 2009-10-30 at 13:31 -0600, Nick Couchman wrote:
>> On Windows HVMs, the "usbdevice=tablet" takes up the one USB device
>> that  you can forward through to the domU.  So, you have to disable
>> that, then you can forward through a usb device.  You can use
>> "usbdevice=host:xxx.yyy" or "usbdevice=host:aaaa:bbbb" - in the first
>> case, it's the bus location where the device is plugged in; in the
>> second case it's the vendor ID and device ID of the USB device.
>> 
>> -Nick
>> 
> 
> 
> So do I need to worry about pciback stuff? Looking at the Running Xen
> book I tried what they suggested by adding the pciback.permissive and
> pciback.hide commands. Got this in dmesg:
> 
> # dmesg | grep pciback
> Bootdata ok (command line is 
> root=/dev/disk/by-id/scsi-200d0b29d2d004400-part2 
> vga=0x317 resume=/dev/sda1 splash=silent showopts pciback.permissive 
> pciback.hide=(00:1d.0)(0000:00:1d.0))
> Kernel command line: root=/dev/disk/by-id/scsi-200d0b29d2d004400-part2 
> vga=0x317 resume=/dev/sda1 splash=silent showopts pciback.permissive 
> pciback.hide=(00:1d.0)(0000:00:1d.0)
> Unknown boot option `pciback.permissive': ignoring
> Unknown boot option `pciback.hide=(00:1d.0)(0000:00:1d.0)': ignoring
> 
> 
> How do I disable usbdevice=tablet and where do you put the
> usbdevice=host:xxx.yyy?
> 
> Here's what the config looks like:
> 
> # xm list -l Vista
> (domain
>     (on_crash destroy)
>     (uuid abf38e32-96d7-dcdd-ac1c-76a0c62adc1b)
>     (bootloader_args )
>     (vcpus 2)
>     (name Vista)
>     (on_poweroff destroy)
>     (on_reboot restart)
>     (bootloader )
>     (maxmem 1024)
>     (memory 1024)
>     (shadow_memory 10)
>     (features )
>     (on_xend_start ignore)
>     (on_xend_stop ignore)
>     (start_time 1256911200.21)
>     (cpu_time 84.60747841)
>     (image
>         (hvm
>             (kernel /usr/lib/xen/boot/hvmloader)
>             (hpet 0)
>             (boot c)
>             (rtc_timeoffset -18000)
>             (pae 1)
>             (acpi 1)
>             (localtime 1)
>             (timer_mode 0)
>             (apic 1)
>             (device_model /usr/lib/xen/bin/qemu-dm)
>             (usb 1)
>             (notes (SUSPEND_CANCEL 1))
>         )
>     )
>     (status 0)
>     (device
>         (vif
>             (bridge eth4)
>             (mac 00:16:3e:29:52:0c)
>             (backend 0)
>             (uuid 9fdd461a-4636-4e6b-432b-91dfd2f75a07)
>             (script vif-bridge)
>         )
>     )
>     (device
>         (vbd
>             (uuid cf9d7942-f200-0b99-a4ba-fcdd17494aee)
>             (bootable 1)
>             (driver paravirtualised)
>             (dev hda:disk)
>             (uname file:/xendata2/images/Vista/disk0)
>             (mode w)
>             (backend 0)
>         )
>     )
>     (device (vkbd (uuid 08076ab7-815d-c9a6-8ee2-5d04d215a643) (backend
> 0)))
>     (device
>         (vfb
>             (vncunused 1)
>             (type vnc)
>             (uuid 2af45cb8-5722-6419-4840-1820d6c44b36)
>             (location 127.0.0.1:5900)
>         )
>     )
>     (device
>         (console
>             (protocol vt100)
>             (location 4)
>             (uuid 58e633ec-843e-5eee-3fdf-0ffa0647bcde)
>         )
>     )
> )



--------
This e-mail may contain confidential and privileged material for the sole use 
of the intended recipient.  If this email is not intended for you, or you are 
not responsible for the delivery of this message to the intended recipient, 
please note that this message may contain SEAKR Engineering (SEAKR) 
Privileged/Proprietary Information.  In such a case, you are strictly 
prohibited from downloading, photocopying, distributing or otherwise using this 
message, its contents or attachments in any way.  If you have received this 
message in error, please notify us immediately by replying to this e-mail and 
delete the message from your mailbox.  Information contained in this message 
that does not relate to the business of SEAKR is neither endorsed by nor 
attributable to SEAKR.

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