How do you give USB to a Windows domU?

[James Pifer]

I have xen 3.2.x running on sles10sp2 dom0. I have a domU that I need to
give access to a usb port for a usb hardware key. I'd also like to
restrict it to only this domU having that usb port.

So I have a test Vista domU. When I look at Device Manager under
Universal Serial Bus Controllers it has:
-Intel 82371SB PCI to USB Universal Host Controller
-USB Root Hub

In the config for the domU usb=1.
    (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))
        )
    )
Above is pulled from the xenstore using xm list -l <domname>


Tried plugging a flash drive into all the usb ports, but it's not seen
by the domU.


How do I enable usb in this domU?

And, how do I restrict it only to this domU?

Any assistance is appreciated.

Thanks,
James


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

[Nick Couchman]

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

>>> On 2009/10/30 at 11:26, James Pifer <jep@...> wrote:
> I have xen 3.2.x running on sles10sp2 dom0. I have a domU that I need to
> give access to a usb port for a usb hardware key. I'd also like to
> restrict it to only this domU having that usb port.
>
> So I have a test Vista domU. When I look at Device Manager under
> Universal Serial Bus Controllers it has:
> -Intel 82371SB PCI to USB Universal Host Controller
> -USB Root Hub
>
> In the config for the domU usb=1.
>     (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))
>         )
>     )
> Above is pulled from the xenstore using xm list -l <domname>
>
>
> Tried plugging a flash drive into all the usb ports, but it's not seen
> by the domU.
>
>
> How do I enable usb in this domU?
>
> And, how do I restrict it only to this domU?
>
> Any assistance is appreciated.
>
> Thanks,
> James

--------
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@...
http://lists.xensource.com/xen-users

[James Pifer]

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



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

[Nick Couchman]

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@...> 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@...
http://lists.xensource.com/xen-users

[James Pifer]

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

I tried to do this and the Vista domU still doesn't see it. Can you tell
what I'm doing wrong? Thanks for all the help.

James


#lsusb
Bus 006 Device 002: ID 03f0:1027 Hewlett-Packard
Bus 006 Device 003: ID 03f0:1327 Hewlett-Packard
Bus 006 Device 001: ID 0000:0000  
Bus 005 Device 001: ID 0000:0000  
Bus 004 Device 001: ID 0000:0000  
Bus 003 Device 001: ID 0000:0000  
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 002: ID 0951:1607 Kingston Technology
Bus 001 Device 001: ID 0000:0000  

                             
                             
                             
# xm delete Vista;xm new Vista
Using config file "./Vista".                            
xen03:/etc/xen/vm # 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=[ 'mac=00:16:3e:1a:45:41,model=rtl8139,type=ioemu', ]  
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 2)                                          
    (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 1257175085.02)                          
    (cpu_time 68.597921547)                            
    (online_vcpus 2)                                    
    (image                                              
        (hvm                                            
            (kernel /usr/lib/xen/boot/hvmloader)        
            (hpet 0)                                    
            (stdvga 0)                                  
            (extid 0)                                  
            (serial pty)                                
            (vncunused 1)                              
            (boot c)                                    
            (rtc_timeoffset -21600)                    
            (pci ())                                    
            (pae 1)                                    
            (hap 1)                                    
            (acpi 1)                                    
            (localtime 1)                              
            (timer_mode 0)                              
            (vnc 1)                                    
            (nographic 0)                              
            (guest_os_type default)                    
            (apic 1)                                    
            (monitor 0)                                
            (usbdevice host:0951:1607)                  
            (device_model /usr/lib/xen/bin/qemu-dm)    
            (usb 1)                                    
            (xauthority /root/.Xauthority)              
            (isa 0)                                    
            (notes (SUSPEND_CANCEL 1))                  
        )                                              
    )                                                  
    (status 2)                                          
    (state -b----)                                      
    (store_mfn 262142)                                  
    (device                                            
        (vif                                            
            (uuid 64a31e5a-120c-d316-3334-c59ec7eb86c6)
            (script vif-bridge)                        
            (mac 00:16:3e:1a:45:41)                    
            (model rtl8139)                            
            (type ioemu)                                
            (backend 0)                                
        )                                              
    )                                                  
    (device                                            
        (vbd                                            
            (uname file:/xendata2/images/Vista/disk0)
            (uuid 683331e3-5705-0468-6e8d-0a3fa28a24ad)
            (mode w)                                    
            (dev hda:disk)                              
            (backend 0)                                
            (bootable 1)                                
        )                                              
    )                                                  
    (device                                            
        (vfb                                            
            (vncunused 1)                              
            (type vnc)                                  
            (uuid 391189b0-7e08-1c0a-7388-139af4ecf5a1)
            (location 127.0.0.1:5900)                  
        )                                              
    )                                                  
    (device                                            
        (console                                        
            (protocol vt100)                            
            (location 4)                                
            (uuid dbd942ab-e7dd-eebf-c092-b434c1acc64b)
        )                                              
    )                                                  
)                                                      
                                             


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

[Mr. Teo En Ming (Zhang Enming)-2]

Your Vista configuration looks correct.

Can you add the following lines to your Vista config?

vnclisten=127.0.0.1
vncdisplay=0
vncconsole=1

And then restart your Vista VM?

You should then see a vncviewer.

Then press CTRL+ALT+2 on your keyboard simultaneously to go into QEMU monitor/console.

Then execute the following command in the QEMU console.

(qemu) usb_add host:0951:1607

See if it helps.

--
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering)
Alma Maters:
(1) Singapore Polytechnic
(2) National University of Singapore
My Primary Blog: http://teo-en-ming-aka-zhang-enming.blogspot.com
My Secondary Blog: http://enmingteo.wordpress.com
My Youtube videos: http://www.youtube.com/user/enmingteo
Email: space.time.universe@...
Mobile Phone (Starhub Prepaid): [phone]
Street: Bedok Reservoir Road
Country: Singapore

On Mon, Nov 2, 2009 at 11:35 PM, James Pifer <jep@...> 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

I tried to do this and the Vista domU still doesn't see it. Can you tell
what I'm doing wrong? Thanks for all the help.

James


#lsusb
Bus 006 Device 002: ID 03f0:1027 Hewlett-Packard
Bus 006 Device 003: ID 03f0:1327 Hewlett-Packard
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 0951:1607 Kingston Technology
Bus 001 Device 001: ID 0000:0000




# xm delete Vista;xm new Vista
Using config file "./Vista".
xen03:/etc/xen/vm # 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=[ 'mac=00:16:3e:1a:45:41,model=rtl8139,type=ioemu', ]
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 2)

   (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 1257175085.02)
   (cpu_time 68.597921547)
   (online_vcpus 2)

   (image
       (hvm
           (kernel /usr/lib/xen/boot/hvmloader)
           (hpet 0)

           (stdvga 0)
           (extid 0)
           (serial pty)
           (vncunused 1)
           (boot c)
           (rtc_timeoffset -21600)
           (pci ())
           (pae 1)
           (hap 1)

           (acpi 1)
           (localtime 1)
           (timer_mode 0)

           (vnc 1)
           (nographic 0)
           (guest_os_type default)
           (apic 1)
           (monitor 0)
           (usbdevice host:0951:1607)

           (device_model /usr/lib/xen/bin/qemu-dm)
           (usb 1)

           (xauthority /root/.Xauthority)
           (isa 0)
           (notes (SUSPEND_CANCEL 1))
       )
   )
   (status 2)
   (state -b----)
   (store_mfn 262142)
   (device
       (vif
           (uuid 64a31e5a-120c-d316-3334-c59ec7eb86c6)
           (script vif-bridge)
           (mac 00:16:3e:1a:45:41)
           (model rtl8139)
           (type ioemu)
           (backend 0)
       )
   )
   (device
       (vbd

           (uname file:/xendata2/images/Vista/disk0)

           (uuid 683331e3-5705-0468-6e8d-0a3fa28a24ad)
           (mode w)
           (dev hda:disk)
           (backend 0)
           (bootable 1)
       )
   )

   (device
       (vfb
           (vncunused 1)
           (type vnc)

           (uuid 391189b0-7e08-1c0a-7388-139af4ecf5a1)

           (location 127.0.0.1:5900)
       )
   )
   (device
       (console
           (protocol vt100)
           (location 4)

           (uuid dbd942ab-e7dd-eebf-c092-b434c1acc64b)
       )
   )
)

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

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

[Nick Couchman]

Note that this only works in 3.4 and later versions of Xen (I think) - 3.2 and 3.3 do not have the version of Qemu that supports the usb_add command.  IIRC, in the OP James stated that he was running SLES11 (??), which uses Xen 3.3.x.

-Nick

>>> On 2009/11/02 at 08:53, "Mr. Teo En Ming (Zhang Enming)"
<space.time.universe@...> wrote:

> Your Vista configuration looks correct.
>
> Can you add the following lines to your Vista config?
>
> vnclisten=127.0.0.1
> vncdisplay=0
> vncconsole=1
>
> And then restart your Vista VM?
>
> You should then see a vncviewer.
>
> Then press CTRL+ALT+2 on your keyboard simultaneously to go into QEMU
> monitor/console.
>
> Then execute the following command in the QEMU console.
>
> (qemu) usb_add host:0951:1607
>
> See if it helps.

--------
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@...
http://lists.xensource.com/xen-users

[Mr. Teo En Ming (Zhang Enming)-2]

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?

--
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering)
Alma Maters:
(1) Singapore Polytechnic
(2) National University of Singapore
My Primary Blog: http://teo-en-ming-aka-zhang-enming.blogspot.com
My Secondary Blog: http://enmingteo.wordpress.com
My Youtube videos: http://www.youtube.com/user/enmingteo
Email: space.time.universe@...
Mobile Phone (Starhub Prepaid): [phone]
Street: Bedok Reservoir Road
Country: Singapore

On Tue, Nov 3, 2009 at 12:01 AM, Nick Couchman <Nick.Couchman@...> wrote:

Note that this only works in 3.4 and later versions of Xen (I think) - 3.2 and 3.3 do not have the version of Qemu that supports the usb_add command.  IIRC, in the OP James stated that he was running SLES11 (??), which uses Xen 3.3.x.

-Nick

>>> On 2009/11/02 at 08:53, "Mr. Teo En Ming (Zhang Enming)"

<space.time.universe@...> wrote:
> Your Vista configuration looks correct.
>
> Can you add the following lines to your Vista config?
>
> vnclisten=127.0.0.1
> vncdisplay=0
> vncconsole=1
>
> And then restart your Vista VM?
>
> You should then see a vncviewer.
>
> Then press CTRL+ALT+2 on your keyboard simultaneously to go into QEMU
> monitor/console.
>
> Then execute the following command in the QEMU console.
>
> (qemu) usb_add host:0951:1607
>
> See if it helps.

--------
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@...
http://lists.xensource.com/xen-users

[James Pifer]

On Mon, 2009-11-02 at 09:01 -0700, Nick Couchman wrote:
> Note that this only works in 3.4 and later versions of Xen (I think) -
> 3.2 and 3.3 do not have the version of Qemu that supports the usb_add
> command.  IIRC, in the OP James stated that he was running SLES11
> (??), which uses Xen 3.3.x.
>
> -Nick

Crap, xen is 3.2. So can you pass usb with 3.2 another way?

James


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

[Mr. Teo En Ming (Zhang Enming)-2]

If you try to passthrough other USB devices does it work? Like USB keyboard, USB mouse, etc.

--
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering)
Alma Maters:
(1) Singapore Polytechnic
(2) National University of Singapore
My Primary Blog: http://teo-en-ming-aka-zhang-enming.blogspot.com
My Secondary Blog: http://enmingteo.wordpress.com
My Youtube videos: http://www.youtube.com/user/enmingteo
Email: space.time.universe@...
Mobile Phone (Starhub Prepaid): [phone]
Street: Bedok Reservoir Road
Country: Singapore

On Tue, Nov 3, 2009 at 12:12 AM, James Pifer <jep@...> wrote:

On Mon, 2009-11-02 at 09:01 -0700, Nick Couchman wrote:
> Note that this only works in 3.4 and later versions of Xen (I think) -
> 3.2 and 3.3 do not have the version of Qemu that supports the usb_add
> command.  IIRC, in the OP James stated that he was running SLES11
> (??), which uses Xen 3.3.x.
>
> -Nick

Crap, xen is 3.2. So can you pass usb with 3.2 another way?

James

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

[Nick Couchman]

It was added in later versions of Qemu that are used in later versions of Xen.  Don't know the exact changeset where it was added, but it definitely doesn't exist in Xen 3.2.x.

-Nick

>>> On 2009/11/02 at 09:06, "Mr. Teo En Ming (Zhang Enming)"
<space.time.universe@...> 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?




--------
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@...
http://lists.xensource.com/xen-users

[Mr. Teo En Ming (Zhang Enming)-2]

Hi James,

I googled around and found there's a case very similar to yours posted by Sebastian more than one year back but it was not solved.

Please refer to following link.

http://lists.xensource.com/archives/html/xen-users/2008-08/msg00360.html

So I'd suggest you upgrade to Xen 3.4 or 3.5 (not for production).

--
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering)
Alma Maters:
(1) Singapore Polytechnic
(2) National University of Singapore
My Primary Blog: http://teo-en-ming-aka-zhang-enming.blogspot.com
My Secondary Blog: http://enmingteo.wordpress.com
My Youtube videos: http://www.youtube.com/user/enmingteo
Email: space.time.universe@...
Mobile Phone (Starhub Prepaid): [phone]
Street: Bedok Reservoir Road
Country: Singapore

On Tue, Nov 3, 2009 at 12:29 AM, Nick Couchman <Nick.Couchman@...> wrote:

It was added in later versions of Qemu that are used in later versions of Xen.  Don't know the exact changeset where it was added, but it definitely doesn't exist in Xen 3.2.x.

-Nick

>>> On 2009/11/02 at 09:06, "Mr. Teo En Ming (Zhang Enming)"

<space.time.universe@...> 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?

--------
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@...
http://lists.xensource.com/xen-users

[James Pifer]

On Tue, 2009-11-03 at 00:46 +0800, Mr. Teo En Ming (Zhang Enming) wrote:

> Hi James,
>
> I googled around and found there's a case very similar to yours posted
> by Sebastian more than one year back but it was not solved.
>
> Please refer to following link.
>
> http://lists.xensource.com/archives/html/xen-users/2008-08/msg00360.html
>
> So I'd suggest you upgrade to Xen 3.4 or 3.5 (not for production).

I actually attempted to update to 3.4 once before and it seemed to get
more and more complicated with every step and I did not get it updated.
I guess I will have to look at it again though.

I'm on SLES10SP2.

Thanks,
James


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

[Mr. Teo En Ming (Zhang Enming)-2]

It's not very difficult. You could refer to Boris Derzhavets' instructions.

Upgrading to 3.4 involves the following steps:

# hg clone http://xenbits.xensource.com/xen-3.4-testing.hg
# cd xen-3.4-testing.hg
# make xen
# make install-xen
# make tools
# make install-tools

If you encounter any problems during the build process, it could be some dependency related issue. Just install the relevant dependency which the build process complains about. The packages you need to install should be of the form packagename-DEVEL-version.rpm.

--
Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering)
Alma Maters:
(1) Singapore Polytechnic
(2) National University of Singapore
My Primary Blog: http://teo-en-ming-aka-zhang-enming.blogspot.com
My Secondary Blog: http://enmingteo.wordpress.com
My Youtube videos: http://www.youtube.com/user/enmingteo
Email: space.time.universe@...
Mobile Phone (Starhub Prepaid): [phone]
Street: Bedok Reservoir Road
Country: Singapore

On Tue, Nov 3, 2009 at 12:53 AM, James Pifer <jep@...> wrote:

On Tue, 2009-11-03 at 00:46 +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> Hi James,
>
> I googled around and found there's a case very similar to yours posted
> by Sebastian more than one year back but it was not solved.
>
> Please refer to following link.
>
> http://lists.xensource.com/archives/html/xen-users/2008-08/msg00360.html
>
> So I'd suggest you upgrade to Xen 3.4 or 3.5 (not for production).

I actually attempted to update to 3.4 once before and it seemed to get
more and more complicated with every step and I did not get it updated.
I guess I will have to look at it again though.

I'm on SLES10SP2.

Thanks,
James

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

[James Pifer]

On Tue, 2009-11-03 at 01:00 +0800, Mr. Teo En Ming (Zhang Enming) wrote:

> It's not very difficult. You could refer to Boris Derzhavets'
> instructions.
>
> Upgrading to 3.4 involves the following steps:
>
> # hg clone http://xenbits.xensource.com/xen-3.4-testing.hg
> # cd xen-3.4-testing.hg
> # make xen
> # make install-xen
> # make tools
> # make install-tools
>

I'm certainly willing to try it, but what is the first command? hg
clone? Where does that come from.

Also, isn't there a 3.4 stable release rather than testing?

Thanks,
James




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

[Pasi Kärkkäinen]

On Mon, Nov 02, 2009 at 12:27:56PM -0500, James Pifer wrote:

> On Tue, 2009-11-03 at 01:00 +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> > It's not very difficult. You could refer to Boris Derzhavets'
> > instructions.
> >
> > Upgrading to 3.4 involves the following steps:
> >
> > # hg clone http://xenbits.xensource.com/xen-3.4-testing.hg
> > # cd xen-3.4-testing.hg
> > # make xen
> > # make install-xen
> > # make tools
> > # make install-tools
> >
>
>
> I'm certainly willing to try it, but what is the first command? hg
> clone? Where does that come from.
>

hg is in a package called 'mercurial'.

> Also, isn't there a 3.4 stable release rather than testing?
>

Xen 3.4.x stable releases are made from xen-3.4-testing.hg repository.

Currently it's getting towards Xen 3.4.2 release, and has a lot of fixes
after 3.4.1.

Xen 3.4.1 tarball can be found from here:
http://www.xen.org/products/xen_source.html

-- Pasi


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

[James Pifer]

On Mon, 2009-11-02 at 19:46 +0200, Pasi Kärkkäinen wrote:

> On Mon, Nov 02, 2009 at 12:27:56PM -0500, James Pifer wrote:
> > On Tue, 2009-11-03 at 01:00 +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> > > It's not very difficult. You could refer to Boris Derzhavets'
> > > instructions.
> > >
> > > Upgrading to 3.4 involves the following steps:
> > >
> > > # hg clone http://xenbits.xensource.com/xen-3.4-testing.hg
> > > # cd xen-3.4-testing.hg
> > > # make xen
> > > # make install-xen
> > > # make tools
> > > # make install-tools
> > >
> >

I was able to spend a little time on this. I got mercurial installed and
ran the first few commands. Got stuck at make tools because of git. I
have all but one of the dependencies installed. I found subversion in
Novell's SLE10 SDK, but I can't find subversion-perl. I've been googling
but none that I've found work. I'm running sles10sp2. Anyone know where
I can get subversion-perl? Novell's SLE10 SDK installs
subversion-1.3.1-1.5.

Other suggestions? I'd prefer to stay with packages if possible.

Thanks,
James


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

[Nick Couchman]

Did you look for the "git" package?  I'm pretty sure SLES10 includes it.
 If not, you might try www.opensuse.org - you can go to the "Get It"
page and then click on the Package Search button and search for
packages.  You can select the product you'd like to look for packages
for - e.g. SLES10, SLES11, etc.

-Nick

>>> On 2009/11/02 at 18:51, James Pifer <jep@...> wrote:
> On Mon, 2009-11-02 at 19:46 +0200, Pasi Kärkkäinen wrote:
>> On Mon, Nov 02, 2009 at 12:27:56PM -0500, James Pifer wrote:
>> > On Tue, 2009-11-03 at 01:00 +0800, Mr. Teo En Ming (Zhang Enming)
wrote:

>> > > It's not very difficult. You could refer to Boris Derzhavets'
>> > > instructions.
>> > >
>> > > Upgrading to 3.4 involves the following steps:
>> > >
>> > > # hg clone http://xenbits.xensource.com/xen-3.4-testing.hg 
>> > > # cd xen-3.4-testing.hg
>> > > # make xen
>> > > # make install-xen
>> > > # make tools
>> > > # make install-tools
>> > >
>> >
>
> I was able to spend a little time on this. I got mercurial installed

and
> ran the first few commands. Got stuck at make tools because of git.

I
> have all but one of the dependencies installed. I found subversion
in
> Novell's SLE10 SDK, but I can't find subversion-perl. I've been
googling
> but none that I've found work. I'm running sles10sp2. Anyone know
where
> I can get subversion-perl? Novell's SLE10 SDK installs
> subversion-1.3.1-1.5.
>
> Other suggestions? I'd prefer to stay with packages if possible.
>
> Thanks,
> James


--------
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@...
http://lists.xensource.com/xen-users

[James Pifer]

On Mon, 2009-11-02 at 18:54 -0700, Nick Couchman wrote:
> Did you look for the "git" package?  I'm pretty sure SLES10 includes it.
>  If not, you might try www.opensuse.org - you can go to the "Get It"
> page and then click on the Package Search button and search for
> packages.  You can select the product you'd like to look for packages
> for - e.g. SLES10, SLES11, etc.
>
> -Nick

Thanks Nick. git is not on the sles10sp2 dvd or sle10 sdk, but I was
able to install git-core and git by following your suggestion from
opensuse.org.

I started xend service and I can do an xm list. How can I confirm the
version of xen?

Now if I want to use virt-manager, do I need to install that from
source?

Thanks for all the help!

James




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

[Nick Couchman]

"xm info" should list the Xen version, and the output of "xm dmesg" at the very top lists the version.  Also, when you look in /boot you should see xen-3.4.gz.

-Nick

>>> On 2009/11/02 at 19:47, James Pifer <jep@...> wrote:
> On Mon, 2009-11-02 at 18:54 -0700, Nick Couchman wrote:
>> Did you look for the "git" package?  I'm pretty sure SLES10 includes it.
>>  If not, you might try www.opensuse.org - you can go to the "Get It"
>> page and then click on the Package Search button and search for
>> packages.  You can select the product you'd like to look for packages
>> for - e.g. SLES10, SLES11, etc.
>>
>> -Nick
>
> Thanks Nick. git is not on the sles10sp2 dvd or sle10 sdk, but I was
> able to install git-core and git by following your suggestion from
> opensuse.org.
>
> I started xend service and I can do an xm list. How can I confirm the
> version of xen?
>
> Now if I want to use virt-manager, do I need to install that from
> source?
>
> Thanks for all the help!
>
> James

--------
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@...
http://lists.xensource.com/xen-users