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

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

Can you look at the /var/log/xem/qemu-dm-<domU>.log file for this domU
and see if there are any messages in there relating to the USB device?

-Nick

>>> On 2009/11/09 at 13:55, James Pifer <jep@xxxxxxxxxxxxxxxx> wrote: 
> On Tue, 2009-11-03 at 00:06 +0800, Mr. Teo En Ming (Zhang Enming)
wrote:
>> James is running Xen 3.2.x. I am running Xen 3.5-unstable now. So
far
>> I only have experience with Xen 3.4-testing and Xen 3.5-unstable. I
am
>> not sure about 3.2.x. But I thought usb_add command for QEMU is
>> universal?
>> 
>> -- 
> 
> So I've made some progress here. I have a sles11 server running xen
> 3.4.1. I've loaded my Vista domU using the same config file as
before.
> The usb drive is in the same spot. Unfortunately, it's still not
loaded
> in the domU. Interesting that nothing is listed in the xenstore
except
> usb 1. Shouldn't the device I'm trying to pass through be listed
> somewhere?
> 
> Info below.
> Thanks,
> James
> 
> 
> 
> 
> # xm info
> host                   : xen03
> release                : 2.6.27.19-5-xen
> version                : #1 SMP 2009-02-28 04:40:21 +0100
> machine                : x86_64
> nr_cpus                : 16
> nr_nodes               : 1
> cores_per_socket       : 4
> threads_per_core       : 2
> cpu_mhz                : 2533
> hw_caps                : 
>
bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000
> virt_caps              : hvm
> total_memory           : 32757
> free_memory            : 30328
> max_free_memory        : 30838
> max_para_memory        : 30834
> max_hvm_memory         : 30753
> node_to_cpu            : node0:0-15
> node_to_memory         : node0:30328
> xen_major              : 3
> xen_minor              : 4
> xen_extra              : .1_19718_04-26.
> xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p
hvm-3.0-x86_32 
> hvm-3.0-x86_32p hvm-3.0-x86_64 
> xen_scheduler          : credit
> xen_pagesize           : 4096
> platform_params        : virt_start=0xffff800000000000
> xen_changeset          : 19718
> cc_compiler            : gcc version 4.3.2 [gcc-4_3-branch revision
141291] 
> (SUSE Linux)
> cc_compile_by          : abuild
> cc_compile_domain      : 
> cc_compile_date        : Wed Oct 14 00:02:21 UTC 2009
> xend_config_format     : 4
> 
> 
> 
> # cat Vista
> name="Vista"
> uuid="abf38e32-96d7-dcdd-ac1c-76a0c62adc1b"
> memory=1024
> maxmem=1024
> vcpus=2
> on_poweroff="destroy"
> on_reboot="restart"
> on_crash="destroy"
> localtime=1
> 
> builder="hvm"
> extid=0
> device_model="/usr/lib/xen/bin/qemu-dm"
> kernel="/usr/lib/xen/boot/hvmloader"
> boot="c"
> disk=[ 'file:/xendata2/images/Vista/disk0,hda,w', ]
> vif=[ 'bridge=br0,mac=00:16:3e:0a:ff:3b', ]
> stdvga=0
> vnc=1
> vncunused=1
> apic=1
> acpi=1
> pae=1
> 
> usb=1
> usbdevice='host:0951:1607'
> 
> serial="pty"
> 
> 
> 
> # xm list -l Vista
> (domain
>     (domid 3)
>     (bootloader )
>     (on_crash destroy)
>     (uuid abf38e32-96d7-dcdd-ac1c-76a0c62adc1b)
>     (bootloader_args )
>     (vcpus 2)
>     (name Vista)
>     (cpus (() ()))
>     (on_reboot restart)
>     (on_poweroff destroy)
>     (maxmem 1024)
>     (memory 1024)
>     (shadow_memory 10)
>     (features )
>     (on_xend_start ignore)
>     (on_xend_stop ignore)
>     (start_time 1257799109.32)
>     (cpu_time 134.032194576)
>     (online_vcpus 2)
>     (image
>         (hvm
>             (kernel )
>             (timer_mode 0)
>             (hpet 0)
>             (rtc_timeoffset -21600)
>             (loader /usr/lib/xen/boot/hvmloader)
>             (apic 1)
>             (serial pty)
>             (device_model /usr/lib/xen/bin/qemu-dm)
>             (boot c)
>             (pae 1)
>             (usb 1)
>             (acpi 1)
>             (localtime 1)
>             (notes (SUSPEND_CANCEL 1))
>         )
>     )
>     (status 2)
>     (state -b----)
>     (store_mfn 262141)
>     (device
>         (vif
>             (bridge br0)
>             (mac 00:16:3e:0a:ff:3b)
>             (script /etc/xen/scripts/vif-bridge)
>             (uuid 725b2236-b798-0587-87db-e5252da319d3)
>             (backend 0)
>         )
>     )
>     (device (vkbd (backend 0)))
>     (device
>         (console
>             (protocol vt100)
>             (location 4)
>             (uuid 1bf9cb91-c15c-99be-5bb5-e18fab9ee105)
>         )
>     )
>     (device
>         (vbd
>             (uname file:/xendata2/images/Vista/disk0)
>             (uuid 1c1ad8d2-cdf9-e278-9c0d-51d615b60b58)
>             (mode w)
>             (dev hda:disk)
>             (backend 0)
>             (bootable 1)
>             (VDI )
>         )
>     )
>     (device
>         (vfb
>             (vncunused 1)
>             (type vnc)
>             (uuid 928789a3-2c86-b8ed-0abe-d9e792dfc584)
>             (location localhost:5900)
>         )
>     )
> )
> 
> 
> 
> 
> # lsusb
> Bus 005 Device 003: ID 03f0:1327 Hewlett-Packard 
> Bus 005 Device 002: ID 03f0:1027 Hewlett-Packard 
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 002: ID 0951:1607 Kingston Technology Data Traveler
2.0
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub



--------
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