Xen users - Oct 2009 - How do you give USB to a Windows domU?

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

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

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

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

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

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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore

On Mon, Nov 2, 2009 at 11:35 PM, James Pifer <jep@obrien-pifer.com> 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@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

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

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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore

On Tue, Nov 3, 2009 at 12:01 AM, Nick Couchman
<Nick.Couchman@seakr.com>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@gmail.com> 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@lists.xensource.com
http://lists.xensource.com/xen-users

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

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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore

On Tue, Nov 3, 2009 at 12:12 AM, James Pifer <jep@obrien-pifer.com> 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@lists.xensource.com
http://lists.xensource.com/xen-users

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

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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore

On Tue, Nov 3, 2009 at 12:29 AM, Nick Couchman
<Nick.Couchman@seakr.com>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@gmail.com> 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@lists.xensource.com
http://lists.xensource.com/xen-users

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

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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore

On Tue, Nov 3, 2009 at 12:53 AM, James Pifer <jep@obrien-pifer.com> 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@lists.xensource.com
http://lists.xensource.com/xen-users

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

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

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

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

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

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

On Mon, Nov 02, 2009 at 07:49:30PM -0700, Nick Couchman
wrote:
> "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.
>
"xm info" has the Xen version in xen_major.xen_minor.xen_extra fields.

-- Pasi
> -Nick
> 
> >>> On 2009/11/02 at 19:47, James Pifer
<jep@obrien-pifer.com> 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@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, 2009-11-02 at 19:49 -0700, Nick Couchman wrote:
> "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
> 
After a reboot I''m up and running on xen 3.4.x. I''m having a
helluva
time trying to get virt-manager installed so I can install run
virt-manager. I keep hitting what is apparently a bug in
dev_mapper_devel. It''s installed, but when I try to configure libvirt
it
doesn''t think it is. 

So I installed libvirt from rpms. I told it to ignore the deps for xen
and it installed. virt-manager will not run though. 



In the mean time I tried to start my domU from the command line and I
get this:
# xm start Vista
Error: Device 0 not connected
Usage: xm start <DomainName>

Start a Xend managed domain
  -p, --paused                   Do not unpause domain after starting
it    
  -c, --console_autoconnect      Connect to the console after the
domain    
                                 is created
  --vncviewer                    Connect to display via VNC after
the       
                                 domain is created
  --vncviewer-autopass           Pass VNC password to viewer via stdin
and  
                                 -autopass


Thanks
James


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

Shouldn''t it be "xm create Vista"?

-- 
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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore

On Tue, Nov 3, 2009 at 10:54 PM, James Pifer <jep@obrien-pifer.com> wrote:
> On Mon, 2009-11-02 at 19:49 -0700, Nick Couchman wrote:
> > "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
> >
>
> After a reboot I''m up and running on xen 3.4.x. I''m
having a helluva
> time trying to get virt-manager installed so I can install run
> virt-manager. I keep hitting what is apparently a bug in
> dev_mapper_devel. It''s installed, but when I try to configure
libvirt it
> doesn''t think it is.
>
> So I installed libvirt from rpms. I told it to ignore the deps for xen
> and it installed. virt-manager will not run though.
>
>
>
> In the mean time I tried to start my domU from the command line and I
> get this:
> # xm start Vista
> Error: Device 0 not connected
> Usage: xm start <DomainName>
>
> Start a Xend managed domain
>  -p, --paused                   Do not unpause domain after starting
> it
>  -c, --console_autoconnect      Connect to the console after the
> domain
>                                 is created
>  --vncviewer                    Connect to display via VNC after
> the
>                                 domain is created
>  --vncviewer-autopass           Pass VNC password to viewer via stdin
> and
>                                 -autopass
>
>
> Thanks
> James
>
>

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

No, Xen keeps records of your Virtual Machines via xenstore and once
you've done either "xm new" or "xm create" you can start
it subsequently
using "xm start".

James, look at "xm log" and "xm dmesg" to see what's
causing this -
usually a network or storage device not connecting correctly.

-Nick
>>> On 2009/11/03 at 07:56, "Mr. Teo En Ming (Zhang Enming)"
<space.time.universe@gmail.com> wrote: 
> Shouldn't it be "xm create Vista"?
> 
> -- 
> 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@gmail.com
> Mobile Phone (Starhub Prepaid): +65-8369-2618
> Street: Bedok Reservoir Road
> Country: Singapore
> 
> On Tue, Nov 3, 2009 at 10:54 PM, James Pifer <jep@obrien-pifer.com>
wrote:
> 
>> On Mon, 2009-11-02 at 19:49 -0700, Nick Couchman wrote:
>> > "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
>> >
>>
>> After a reboot I'm up and running on xen 3.4.x. I'm having a
helluva
>> time trying to get virt-manager installed so I can install run
>> virt-manager. I keep hitting what is apparently a bug in
>> dev_mapper_devel. It's installed, but when I try to configure
libvirt it
>> doesn't think it is.
>>
>> So I installed libvirt from rpms. I told it to ignore the deps for
xen
>> and it installed. virt-manager will not run though.
>>
>>
>>
>> In the mean time I tried to start my domU from the command line and
I
>> get this:
>> # xm start Vista
>> Error: Device 0 not connected
>> Usage: xm start <DomainName>
>>
>> Start a Xend managed domain
>>  -p, --paused                   Do not unpause domain after
starting
>> it
>>  -c, --console_autoconnect      Connect to the console after the
>> domain
>>                                 is created
>>  --vncviewer                    Connect to display via VNC after
>> the
>>                                 domain is created
>>  --vncviewer-autopass           Pass VNC password to viewer via
stdin
>> and
>>                                 -autopass
>>
>>
>> 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@lists.xensource.com
http://lists.xensource.com/xen-users

On Tue, 2009-11-03 at 22:56 +0800, Mr. Teo En Ming (Zhang Enming)
wrote:
> Shouldn''t it be "xm create Vista"?
> 
It already exists:

# xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  1024    16     r-----    610.7
Vista                                        1024     1                 0.0

James


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

I''ve never used "xm new" or "xm start", only
"xm create".

-- 
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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore

On Tue, Nov 3, 2009 at 10:58 PM, Nick Couchman
<Nick.Couchman@seakr.com>wrote:
> No, Xen keeps records of your Virtual Machines via xenstore and once
> you''ve done either "xm new" or "xm create" you
can start it subsequently
> using "xm start".
>
> James, look at "xm log" and "xm dmesg" to see
what''s causing this -
> usually a network or storage device not connecting correctly.
>
> -Nick
>
> >>> On 2009/11/03 at 07:56, "Mr. Teo En Ming (Zhang
Enming)"
> <space.time.universe@gmail.com> wrote:
> > Shouldn''t it be "xm create Vista"?
> >
> > --
> > 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@gmail.com
> > Mobile Phone (Starhub Prepaid): +65-8369-2618
> > Street: Bedok Reservoir Road
> > Country: Singapore
> >
> > On Tue, Nov 3, 2009 at 10:54 PM, James Pifer
<jep@obrien-pifer.com>
> wrote:
> >
> >> On Mon, 2009-11-02 at 19:49 -0700, Nick Couchman wrote:
> >> > "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
> >> >
> >>
> >> After a reboot I''m up and running on xen 3.4.x.
I''m having a
> helluva
> >> time trying to get virt-manager installed so I can install run
> >> virt-manager. I keep hitting what is apparently a bug in
> >> dev_mapper_devel. It''s installed, but when I try to
configure
> libvirt it
> >> doesn''t think it is.
> >>
> >> So I installed libvirt from rpms. I told it to ignore the deps for
> xen
> >> and it installed. virt-manager will not run though.
> >>
> >>
> >>
> >> In the mean time I tried to start my domU from the command line
and
> I
> >> get this:
> >> # xm start Vista
> >> Error: Device 0 not connected
> >> Usage: xm start <DomainName>
> >>
> >> Start a Xend managed domain
> >>  -p, --paused                   Do not unpause domain after
> starting
> >> it
> >>  -c, --console_autoconnect      Connect to the console after the
> >> domain
> >>                                 is created
> >>  --vncviewer                    Connect to display via VNC after
> >> the
> >>                                 domain is created
> >>  --vncviewer-autopass           Pass VNC password to viewer via
> stdin
> >> and
> >>                                 -autopass
> >>
> >>
> >> 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@lists.xensource.com
http://lists.xensource.com/xen-users

On Tue, 2009-11-03 at 07:58 -0700, Nick Couchman wrote:
> No, Xen keeps records of your Virtual Machines via xenstore and once
> you''ve done either "xm new" or "xm create" you
can start it subsequently
> using "xm start".
> 
> James, look at "xm log" and "xm dmesg" to see
what''s causing this -
> usually a network or storage device not connecting correctly.
> 
> -Nick
Here''s what I get in xm log when I try to start the domU.


[2009-11-03 09:13:30 5603] DEBUG (XendDomainInfo:2304)
XendDomainInfo.constructDomain
[2009-11-03 09:13:30 5603] DEBUG (balloon:166) Balloon: 32122132 KiB free; need
4096; done.
[2009-11-03 09:13:30 5603] DEBUG (XendDomain:453) Adding Domain: 6
[2009-11-03 09:13:30 5603] DEBUG (XendDomainInfo:2505)
XendDomainInfo.initDomain: 6 256
[2009-11-03 09:13:30 5603] DEBUG (image:322) No VNC passwd configured for vfb
access
[2009-11-03 09:13:30 5603] DEBUG (image:813) args: boot, val: c
[2009-11-03 09:13:30 5603] DEBUG (image:813) args: fda, val: None
[2009-11-03 09:13:30 5603] DEBUG (image:813) args: fdb, val: None
[2009-11-03 09:13:30 5603] DEBUG (image:813) args: soundhw, val: None
[2009-11-03 09:13:30 5603] DEBUG (image:813) args: localtime, val: 1
[2009-11-03 09:13:30 5603] DEBUG (image:813) args: serial, val:
[''pty'']
[2009-11-03 09:13:30 5603] DEBUG (image:813) args: std-vga, val: 0
[2009-11-03 09:13:30 5603] DEBUG (image:813) args: isa, val: 0
[2009-11-03 09:13:30 5603] DEBUG (image:813) args: acpi, val: 1
[2009-11-03 09:13:30 5603] DEBUG (image:813) args: usb, val: 1
[2009-11-03 09:13:30 5603] DEBUG (image:813) args: usbdevice, val:
host:0951:1607
[2009-11-03 09:13:30 5603] INFO (image:749) Need to create platform
device.[domid:6]
[2009-11-03 09:13:30 5603] DEBUG (XendDomainInfo:2529)
_initDomain:shadow_memory=0xa, memory_static_max=0x40000000,
memory_static_min=0x0.
[2009-11-03 09:13:30 5603] DEBUG (balloon:166) Balloon: 32120700 KiB free; need
1067008; done.
[2009-11-03 09:13:30 5603] INFO (image:173) buildDomain os=hvm dom=6 vcpus=2
[2009-11-03 09:13:30 5603] DEBUG (image:866) domid          = 6
[2009-11-03 09:13:30 5603] DEBUG (image:867) image          =
/usr/lib/xen/boot/hvmloader
[2009-11-03 09:13:30 5603] DEBUG (image:868) store_evtchn   = 3
[2009-11-03 09:13:30 5603] DEBUG (image:869) memsize        = 1024
[2009-11-03 09:13:30 5603] DEBUG (image:870) target         = 1024
[2009-11-03 09:13:30 5603] DEBUG (image:871) vcpus          = 2
[2009-11-03 09:13:30 5603] DEBUG (image:872) acpi           = 1
[2009-11-03 09:13:30 5603] DEBUG (image:873) apic           = 1
[2009-11-03 09:13:30 5603] INFO (XendDomainInfo:2168) createDevice: vfb :
{''vncunused'': 1, ''devid'': 0,
''vnc'': ''1'', ''uuid'':
''5605afb8-d54d-54dc-b983-8140b5436558'',
''other_config'': {''vncunused'': 1,
''vnc'': ''1''}}
[2009-11-03 09:13:30 5603] DEBUG (DevController:95) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vfb/6/0''} to
/local/domain/6/device/vfb/0.
[2009-11-03 09:13:30 5603] DEBUG (DevController:97) DevController: writing
{''vncunused'': ''1'',
''domain'': ''Vista'',
''frontend'': ''/local/domain/6/device/vfb/0'',
''uuid'':
''5605afb8-d54d-54dc-b983-8140b5436558'',
''frontend-id'': ''6'',
''state'': ''1'', ''online'':
''1'', ''vnc'': ''1''} to
/local/domain/0/backend/vfb/6/0.
[2009-11-03 09:13:30 5603] INFO (XendDomainInfo:2168) createDevice: vbd :
{''uuid'':
''e5b28c95-296b-b34d-ca26-d64fb31d46c3'',
''bootable'': 1, ''devid'': 768,
''driver'': ''paravirtualised'',
''dev'': ''hda'', ''uname'':
''file:/xendata2/images/Vista/disk0'', ''mode'':
''w''}
[2009-11-03 09:13:30 5603] DEBUG (DevController:95) DevController: writing
{''backend-id'': ''0'',
''virtual-device'': ''768'',
''device-type'': ''disk'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/6/768''} to
/local/domain/6/device/vbd/768.
[2009-11-03 09:13:30 5603] DEBUG (DevController:97) DevController: writing
{''domain'': ''Vista'',
''frontend'':
''/local/domain/6/device/vbd/768'', ''uuid'':
''e5b28c95-296b-b34d-ca26-d64fb31d46c3'',
''bootable'': ''1'', ''dev'':
''hda'', ''state'': ''1'',
''params'': ''/xendata2/images/Vista/disk0'',
''mode'': ''w'', ''online'':
''1'', ''frontend-id'': ''6'',
''type'': ''file''} to
/local/domain/0/backend/vbd/6/768.
[2009-11-03 09:13:31 5603] INFO (XendDomainInfo:2168) createDevice: vif :
{''mac'': ''00:16:3e:1a:45:41'',
''devid'': 0, ''type'':
''ioemu'', ''model'':
''rtl8139'', ''uuid'':
''ace7ea85-4d3a-da5b-2a6c-2294f86de6b4''}
[2009-11-03 09:13:31 5603] DEBUG (DevController:95) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vif/6/0''} to
/local/domain/6/device/vif/0.
[2009-11-03 09:13:31 5603] DEBUG (DevController:97) DevController: writing
{''domain'': ''Vista'',
''frontend'': ''/local/domain/6/device/vif/0'',
''uuid'':
''ace7ea85-4d3a-da5b-2a6c-2294f86de6b4'',
''script'': ''/etc/xen/scripts/vif-bridge'',
''mac'': ''00:16:3e:1a:45:41'',
''frontend-id'': ''6'',
''state'': ''1'', ''online'':
''1'', ''handle'': ''0'',
''model'': ''rtl8139'',
''type'': ''ioemu''} to
/local/domain/0/backend/vif/6/0.
[2009-11-03 09:13:31 5603] INFO (image:394) spawning device models:
/usr/lib/xen/bin/qemu-dm [''/usr/lib/xen/bin/qemu-dm'',
''-d'', ''6'', ''-domain-name'',
''Vista'', ''-videoram'', ''4'',
''-vnc'', ''127.0.0.1:0'',
''-vncunused'', ''-vcpus'',
''2'', ''-boot'', ''c'',
''-localtime'', ''-serial'',
''pty'', ''-acpi'', ''-usb'',
''-usbdevice'', ''host:0951:1607'',
''-net'',
''nic,vlan=1,macaddr=00:16:3e:1a:45:41,model=rtl8139'',
''-net'',
''tap,vlan=1,ifname=tap6.0,bridge=xenbr0'',
''-M'', ''xenfv'']
[2009-11-03 09:13:31 5603] INFO (image:443) device model pid: 17985
[2009-11-03 09:13:31 5603] INFO (image:531) waiting for sentinel_fifo
[2009-11-03 09:13:31 5603] WARNING (image:493) domain Vista: device model
failure: pid 17985: exited with nonzero status 126; see
/var/log/xen/qemu-dm-Vista.log
[2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:3060) Storing VM details:
{''on_xend_stop'': ''ignore'',
''shadow_memory'': ''10'',
''uuid'':
''abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
''on_reboot'': ''restart'',
''start_time'': ''1257261211.05'',
''on_poweroff'': ''destroy'',
''bootloader_args'': '''',
''on_xend_start'': ''ignore'',
''on_crash'': ''destroy'',
''xend/restart_count'': ''0'',
''vcpus'': ''2'',
''vcpu_avail'': ''3'',
''bootloader'': '''', ''image'':
''(hvm (kernel ) (videoram 4) (hpet 0) (stdvga 0) (loader
/usr/lib/xen/boot/hvmloader) (serial pty) (vncunused 1) (xen_platform_pci 1)
(boot c) (rtc_timeoffset 0) (pci ()) (pae 1) (vpt_align 1) (hap 1) (viridian 0)
(acpi 1) (localtime 1) (timer_mode 1) (vnc 1) (nographic 0) (guest_os_type
default) (pci_msitranslate 1) (apic 1) (monitor 0) (usbdevice host:0951:1607)
(device_model /usr/lib/xen/bin/qemu-dm) (pci_power_mgmt 0) (usb 1) (xauthority
/root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL 1)))'',
''name'': ''Vista''}
[2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:1622) Storing domain details:
{''console/port'': ''4'',
''name'': ''Vista'',
''console/limit'': ''1048576'',
''store/port'': ''3'', ''vm'':
''/vm/abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
''domid'': ''6'',
''image/suspend-cancel'': ''1'',
''cpu/0/availability'': ''online'',
''memory/target'': ''1048576'',
''control/platform-feature-multiprocessor-suspend'':
''1'', ''store/ring-ref'':
''1044476'', ''cpu/1/availability'':
''online'', ''console/type'':
''ioemu''}
[2009-11-03 09:13:31 5603] WARNING (XendDomainInfo:1886) Domain has crashed:
name=Vista id=6.
[2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:2732) XendDomainInfo.destroy:
domid=6
[2009-11-03 09:13:31 5603] DEBUG (DevController:139) Waiting for devices vif.
[2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:2207) Destroying device model
[2009-11-03 09:13:31 5603] DEBUG (DevController:144) Waiting for 0.
[2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:2214) Releasing devices
[2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:2227) Removing vif/0
[2009-11-03 09:13:31 5603] DEBUG (DevController:629) hotplugStatusCallback
/local/domain/0/backend/vif/6/0/hotplug-status.
[2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:2227) Removing vbd/768
[2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:2227) Removing vfb/0
[2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2009-11-03 09:15:11 5603] WARNING (XendDomain:1048) Failed to setup devices for
<domain id=None name=Vista memory=1073741824 state=halted>: Device 0 not
connected



Here''s what I have in xm dmesg:

# xm dmesg
 __  __            _____ _  _    ____              _____                   
 \ \/ /___ _ __   |___ /| || |  |___ \    _ __ ___|___ /    _ __  _ __ ___ 
  \  // _ \ ''_ \    |_ \| || |_   __) |__| ''__/ __| |_ \ __|
''_ \| ''__/ _ \
  /  \  __/ | | |  ___) |__   _| / __/|__| | | (__ ___) |__| |_) | | |  __/
 /_/\_\___|_| |_| |____(_) |_|(_)_____|  |_|  \___|____/   | .__/|_|  \___|
                                                           |_|             
(XEN) Xen version 3.4.2-rc3-pre (root@pca.com) (gcc version 4.1.2 20070115 (SUSE
Linux)) Mon Nov  2 13:20:52 CST 2009
(XEN) Latest ChangeSet: Thu Oct 29 15:02:30 2009 +0000 19815:d626b239fed1
(XEN) Command line: dom0_mem=1024M
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 2 seconds
(XEN) Disc information:
(XEN)  Found 2 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009ec00 (usable)
(XEN)  000000000009ec00 - 00000000000a0000 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000df62f000 (usable)
(XEN)  00000000df62f000 - 00000000df63c000 (ACPI data)
(XEN)  00000000df63c000 - 00000000df63d000 (usable)
(XEN)  00000000df63d000 - 00000000e4000000 (reserved)
(XEN)  00000000fec00000 - 00000000fee10000 (reserved)
(XEN)  00000000ff800000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000081ffff000 (usable)
(XEN) System RAM: 32757MB (33543988kB)
(XEN) ACPI: RSDP 000F4F00, 0024 (r2 HP    )
(XEN) ACPI: XSDT DF62FDC0, 00B4 (r1 HP     ProLiant        2   �     162E)
(XEN) ACPI: FACP DF62FEC0, 00F4 (r3 HP     ProLiant        2   �     162E)
(XEN) ACPI: DSDT DF62FFC0, 1F95 (r1 HP         DSDT        1 INTL 20030228)
(XEN) ACPI: FACS DF62F100, 0040
(XEN) ACPI: SPCR DF62F140, 0050 (r1 HP     SPCRRBSU        1   �     162E)
(XEN) ACPI: MCFG DF62F1C0, 003C (r1 HP     ProLiant        1             0)
(XEN) ACPI: HPET DF62F200, 0038 (r1 HP     ProLiant        2   �     162E)
(XEN) ACPI: FFFF DF62F240, 0064 (r2 HP     ProLiant        2   �     162E)
(XEN) ACPI: SPMI DF62F2C0, 0040 (r5 HP     ProLiant        1   �     162E)
(XEN) ACPI: ERST DF62F300, 01D0 (r1 HP     ProLiant        1   �     162E)
(XEN) ACPI: APIC DF62F500, 00DE (r1 HP     ProLiant        2             0)
(XEN) ACPI: SRAT DF62F600, 0370 (r1 HP     Proliant        1   �     162E)
(XEN) ACPI: FFFF DF62F980, 0176 (r1 HP     ProLiant        1   �     162E)
(XEN) ACPI: BERT DF62FB00, 0030 (r1 HP     ProLiant        1   �     162E)
(XEN) ACPI: HEST DF62FB40, 00BC (r1 HP     ProLiant        1   �     162E)
(XEN) ACPI: DMAR DF62FC00, 012C (r1 HP     ProLiant        1   �     162E)
(XEN) ACPI: SSDT DF631F80, 0125 (r3     HP  CRSPCI0        2   HP        1)
(XEN) ACPI: SSDT DF6320C0, 01CF (r3     HP  riser1a        2 INTL 20061109)
(XEN) ACPI: SSDT DF6322C0, 021B (r1     HP      pcc        1 INTL 20090625)
(XEN) ACPI: SSDT DF632500, 0377 (r1     HP     pmab        1 INTL 20090625)
(XEN) ACPI: SSDT DF632880, 3094 (r1  INTEL PPM RCM         1 INTL 20061109)
(XEN) Domain heap initialised
(XEN) Processor #0 7:10 APIC version 21
(XEN) Processor #16 7:10 APIC version 21
(XEN) Processor #4 7:10 APIC version 21
(XEN) Processor #20 7:10 APIC version 21
(XEN) Processor #2 7:10 APIC version 21
(XEN) Processor #18 7:10 APIC version 21
(XEN) Processor #6 7:10 APIC version 21
(XEN) Processor #22 7:10 APIC version 21
(XEN) Processor #1 7:10 APIC version 21
(XEN) Processor #17 7:10 APIC version 21
(XEN) Processor #5 7:10 APIC version 21
(XEN) Processor #21 7:10 APIC version 21
(XEN) Processor #3 7:10 APIC version 21
(XEN) Processor #19 7:10 APIC version 21
(XEN) Processor #7 7:10 APIC version 21
(XEN) Processor #23 7:10 APIC version 21
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 0, version 32, address 0xfec80000, GSI 24-47
(XEN) Enabling APIC mode:  Phys.  Using 2 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2533.494 MHz processor.
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) VMX: EPT is available.
(XEN) VMX: VPID is available.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) CPU0: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 1/16 eip 8c000
(XEN) CPU1: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 2/4 eip 8c000
(XEN) CPU2: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 3/20 eip 8c000
(XEN) CPU3: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 4/2 eip 8c000
(XEN) CPU4: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 5/18 eip 8c000
(XEN) CPU5: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 6/6 eip 8c000
(XEN) CPU6: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 7/22 eip 8c000
(XEN) CPU7: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 8/1 eip 8c000
(XEN) CPU8: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 9/17 eip 8c000
(XEN) CPU9: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 10/5 eip 8c000
(XEN) CPU10: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 11/21 eip 8c000
(XEN) CPU11: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 12/3 eip 8c000
(XEN) CPU12: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 13/19 eip 8c000
(XEN) CPU13: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 14/7 eip 8c000
(XEN) CPU14: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Booting processor 15/23 eip 8c000
(XEN) CPU15: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping 05
(XEN) Total of 16 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) checking TSC synchronization across 16 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 16 CPUs
(XEN) I/O virtualisation disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, lsb, paddr 0x100000 -> 0x4a3bdc
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000808000000->0000000809000000 (258048 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80100000->ffffffff804a3bdc
(XEN)  Init. ramdisk: ffffffff804a4000->ffffffff80cb4000
(XEN)  Phys-Mach map: ffffffff80cb4000->ffffffff80eb4000
(XEN)  Start info:    ffffffff80eb4000->ffffffff80eb44b4
(XEN)  Page tables:   ffffffff80eb5000->ffffffff80ec0000
(XEN)  Boot stack:    ffffffff80ec0000->ffffffff80ec1000
(XEN)  TOTAL:         ffffffff80000000->ffffffff81000000
(XEN)  ENTRY ADDRESS: ffffffff80100000
(XEN) Dom0 has maximum 16 VCPUs
(XEN) Scrubbing Free RAM:
..........................................................................................................................................................................................................................................................................................................................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch input to Xen)
(XEN) Freed 128kB init memory.
(XEN) mm.c:806:d0 Error getting mfn 100 (pfn 2420) from L1 entry
0000000000100225 for l1e_owner=0, pg_owner=32753
(XEN) mm.c:806:d0 Error getting mfn 100 (pfn 2420) from L1 entry
0000000000100225 for l1e_owner=0, pg_owner=32753
(XEN) mm.c:806:d0 Error getting mfn 100 (pfn 2420) from L1 entry
0000000000100225 for l1e_owner=0, pg_owner=32753
(XEN) mm.c:806:d0 Error getting mfn 100 (pfn 2420) from L1 entry
0000000000100225 for l1e_owner=0, pg_owner=32753
(XEN) mm.c:806:d0 Error getting mfn 100 (pfn 2420) from L1 entry
0000000000100225 for l1e_owner=0, pg_owner=32753
(XEN) mm.c:806:d0 Error getting mfn 100 (pfn 2420) from L1 entry
0000000000100225 for l1e_owner=0, pg_owner=32753



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

Look at the log file referenced in this log:
/var/log/xen/qemu-dm-Vista.log.

-Nick
>>> On 2009/11/03 at 08:17, James Pifer <jep@obrien-pifer.com>
wrote:
> On Tue, 2009-11-03 at 07:58 -0700, Nick Couchman wrote:
>> No, Xen keeps records of your Virtual Machines via xenstore and
once
>> you've done either "xm new" or "xm create" you
can start it
subsequently
>> using "xm start".
>> 
>> James, look at "xm log" and "xm dmesg" to see
what's causing this -
>> usually a network or storage device not connecting correctly.
>> 
>> -Nick
> 
> Here's what I get in xm log when I try to start the domU.
> 
> 
> [2009-11-03 09:13:30 5603] DEBUG (XendDomainInfo:2304) 
> XendDomainInfo.constructDomain
> [2009-11-03 09:13:30 5603] DEBUG (balloon:166) Balloon: 32122132 KiB
free; 
> need 4096; done.
> [2009-11-03 09:13:30 5603] DEBUG (XendDomain:453) Adding Domain: 6
> [2009-11-03 09:13:30 5603] DEBUG (XendDomainInfo:2505) 
> XendDomainInfo.initDomain: 6 256
> [2009-11-03 09:13:30 5603] DEBUG (image:322) No VNC passwd configured
for 
> vfb access
> [2009-11-03 09:13:30 5603] DEBUG (image:813) args: boot, val: c
> [2009-11-03 09:13:30 5603] DEBUG (image:813) args: fda, val: None
> [2009-11-03 09:13:30 5603] DEBUG (image:813) args: fdb, val: None
> [2009-11-03 09:13:30 5603] DEBUG (image:813) args: soundhw, val:
None
> [2009-11-03 09:13:30 5603] DEBUG (image:813) args: localtime, val: 1
> [2009-11-03 09:13:30 5603] DEBUG (image:813) args: serial, val:
['pty']
> [2009-11-03 09:13:30 5603] DEBUG (image:813) args: std-vga, val: 0
> [2009-11-03 09:13:30 5603] DEBUG (image:813) args: isa, val: 0
> [2009-11-03 09:13:30 5603] DEBUG (image:813) args: acpi, val: 1
> [2009-11-03 09:13:30 5603] DEBUG (image:813) args: usb, val: 1
> [2009-11-03 09:13:30 5603] DEBUG (image:813) args: usbdevice, val: 
> host:0951:1607
> [2009-11-03 09:13:30 5603] INFO (image:749) Need to create platform 
> device.[domid:6]
> [2009-11-03 09:13:30 5603] DEBUG (XendDomainInfo:2529) 
> _initDomain:shadow_memory=0xa, memory_static_max=0x40000000, 
> memory_static_min=0x0.
> [2009-11-03 09:13:30 5603] DEBUG (balloon:166) Balloon: 32120700 KiB
free; 
> need 1067008; done.
> [2009-11-03 09:13:30 5603] INFO (image:173) buildDomain os=hvm dom=6
vcpus=2
> [2009-11-03 09:13:30 5603] DEBUG (image:866) domid          = 6
> [2009-11-03 09:13:30 5603] DEBUG (image:867) image          = 
> /usr/lib/xen/boot/hvmloader
> [2009-11-03 09:13:30 5603] DEBUG (image:868) store_evtchn   = 3
> [2009-11-03 09:13:30 5603] DEBUG (image:869) memsize        = 1024
> [2009-11-03 09:13:30 5603] DEBUG (image:870) target         = 1024
> [2009-11-03 09:13:30 5603] DEBUG (image:871) vcpus          = 2
> [2009-11-03 09:13:30 5603] DEBUG (image:872) acpi           = 1
> [2009-11-03 09:13:30 5603] DEBUG (image:873) apic           = 1
> [2009-11-03 09:13:30 5603] INFO (XendDomainInfo:2168) createDevice:
vfb : 
> {'vncunused': 1, 'devid': 0, 'vnc': '1',
'uuid':
> '5605afb8-d54d-54dc-b983-8140b5436558', 'other_config':
{'vncunused':
1, 
> 'vnc': '1'}}
> [2009-11-03 09:13:30 5603] DEBUG (DevController:95) DevController:
writing 
> {'state': '1', 'backend-id': '0',
'backend':
> '/local/domain/0/backend/vfb/6/0'} to /local/domain/6/device/vfb/0.
> [2009-11-03 09:13:30 5603] DEBUG (DevController:97) DevController:
writing 
> {'vncunused': '1', 'domain': 'Vista',
'frontend':
> '/local/domain/6/device/vfb/0', 'uuid': 
> '5605afb8-d54d-54dc-b983-8140b5436558', 'frontend-id':
'6', 'state':
'1', 
> 'online': '1', 'vnc': '1'} to
/local/domain/0/backend/vfb/6/0.
> [2009-11-03 09:13:30 5603] INFO (XendDomainInfo:2168) createDevice:
vbd : 
> {'uuid': 'e5b28c95-296b-b34d-ca26-d64fb31d46c3',
'bootable': 1,
'devid': 
> 768, 'driver': 'paravirtualised', 'dev':
'hda', 'uname':
> 'file:/xendata2/images/Vista/disk0', 'mode': 'w'}
> [2009-11-03 09:13:30 5603] DEBUG (DevController:95) DevController:
writing 
> {'backend-id': '0', 'virtual-device':
'768', 'device-type': 'disk',
'state': 
> '1', 'backend':
'/local/domain/0/backend/vbd/6/768'} to
> /local/domain/6/device/vbd/768.
> [2009-11-03 09:13:30 5603] DEBUG (DevController:97) DevController:
writing 
> {'domain': 'Vista', 'frontend':
'/local/domain/6/device/vbd/768',
'uuid': 
> 'e5b28c95-296b-b34d-ca26-d64fb31d46c3', 'bootable':
'1', 'dev':
'hda', 
> 'state': '1', 'params':
'/xendata2/images/Vista/disk0', 'mode': 'w',
> 'online': '1', 'frontend-id': '6',
'type': 'file'} to
> /local/domain/0/backend/vbd/6/768.
> [2009-11-03 09:13:31 5603] INFO (XendDomainInfo:2168) createDevice:
vif : 
> {'mac': '00:16:3e:1a:45:41', 'devid': 0,
'type': 'ioemu', 'model':
> 'rtl8139', 'uuid':
'ace7ea85-4d3a-da5b-2a6c-2294f86de6b4'}
> [2009-11-03 09:13:31 5603] DEBUG (DevController:95) DevController:
writing 
> {'state': '1', 'backend-id': '0',
'backend':
> '/local/domain/0/backend/vif/6/0'} to /local/domain/6/device/vif/0.
> [2009-11-03 09:13:31 5603] DEBUG (DevController:97) DevController:
writing 
> {'domain': 'Vista', 'frontend':
'/local/domain/6/device/vif/0',
'uuid': 
> 'ace7ea85-4d3a-da5b-2a6c-2294f86de6b4', 'script': 
> '/etc/xen/scripts/vif-bridge', 'mac':
'00:16:3e:1a:45:41',
'frontend-id': 
> '6', 'state': '1', 'online': '1',
'handle': '0', 'model': 'rtl8139',
'type': 
> 'ioemu'} to /local/domain/0/backend/vif/6/0.
> [2009-11-03 09:13:31 5603] INFO (image:394) spawning device models: 
> /usr/lib/xen/bin/qemu-dm ['/usr/lib/xen/bin/qemu-dm', '-d',
'6',
> '-domain-name', 'Vista', '-videoram', '4',
'-vnc', '127.0.0.1:0',
> '-vncunused', '-vcpus', '2', '-boot',
'c', '-localtime', '-serial',
'pty', 
> '-acpi', '-usb', '-usbdevice',
'host:0951:1607', '-net',
> 'nic,vlan=1,macaddr=00:16:3e:1a:45:41,model=rtl8139',
'-net',
> 'tap,vlan=1,ifname=tap6.0,bridge=xenbr0', '-M',
'xenfv']
> [2009-11-03 09:13:31 5603] INFO (image:443) device model pid: 17985
> [2009-11-03 09:13:31 5603] INFO (image:531) waiting for
sentinel_fifo
> [2009-11-03 09:13:31 5603] WARNING (image:493) domain Vista: device
model 
> failure: pid 17985: exited with nonzero status 126; see 
> /var/log/xen/qemu-dm-Vista.log 
> [2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:3060) Storing VM
details: 
> {'on_xend_stop': 'ignore', 'shadow_memory':
'10', 'uuid':
> 'abf38e32-96d7-dcdd-ac1c-76a0c62adc1b', 'on_reboot':
'restart',
'start_time': 
> '1257261211.05', 'on_poweroff': 'destroy',
'bootloader_args': '',
> 'on_xend_start': 'ignore', 'on_crash':
'destroy',
'xend/restart_count': '0', 
> 'vcpus': '2', 'vcpu_avail': '3',
'bootloader': '', 'image': '(hvm
(kernel ) 
> (videoram 4) (hpet 0) (stdvga 0) (loader /usr/lib/xen/boot/hvmloader)
(serial 
> pty) (vncunused 1) (xen_platform_pci 1) (boot c) (rtc_timeoffset 0)
(pci ()) 
> (pae 1) (vpt_align 1) (hap 1) (viridian 0) (acpi 1) (localtime 1)
(timer_mode 
> 1) (vnc 1) (nographic 0) (guest_os_type default) (pci_msitranslate 1)
(apic 
> 1) (monitor 0) (usbdevice host:0951:1607) (device_model 
> /usr/lib/xen/bin/qemu-dm) (pci_power_mgmt 0) (usb 1) (xauthority 
> /root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL 1)))',
'name':
'Vista'}
> [2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:1622) Storing domain
> details: {'console/port': '4', 'name':
'Vista', 'console/limit':
'1048576', 
> 'store/port': '3', 'vm':
'/vm/abf38e32-96d7-dcdd-ac1c-76a0c62adc1b',
'domid': 
> '6', 'image/suspend-cancel': '1',
'cpu/0/availability': 'online',
> 'memory/target': '1048576', 
> 'control/platform-feature-multiprocessor-suspend': '1',
'store/ring-ref': 
> '1044476', 'cpu/1/availability': 'online',
'console/type': 'ioemu'}
> [2009-11-03 09:13:31 5603] WARNING (XendDomainInfo:1886) Domain has
crashed: 
> name=Vista id=6.
> [2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:2732) 
> XendDomainInfo.destroy: domid=6
> [2009-11-03 09:13:31 5603] DEBUG (DevController:139) Waiting for
devices 
> vif.
> [2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:2207) Destroying
device 
> model
> [2009-11-03 09:13:31 5603] DEBUG (DevController:144) Waiting for 0.
> [2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:2214) Releasing
devices
> [2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:2227) Removing
vif/0
> [2009-11-03 09:13:31 5603] DEBUG (DevController:629)
hotplugStatusCallback 
> /local/domain/0/backend/vif/6/0/hotplug-status.
> [2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:1134) 
> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
> [2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:2227) Removing
vbd/768
> [2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:1134) 
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
> [2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:2227) Removing
vfb/0
> [2009-11-03 09:13:31 5603] DEBUG (XendDomainInfo:1134) 
> XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
> [2009-11-03 09:15:11 5603] WARNING (XendDomain:1048) Failed to setup
devices 
> for <domain id=None name=Vista memory=1073741824 state=halted>:
Device 0 not 
> connected
> 
> 
> 
> Here's what I have in xm dmesg:
> 
> # xm dmesg
>  __  __            _____ _  _    ____              _____             
     
>  \ \/ /___ _ __   |___ /| || |  |___ \    _ __ ___|___ /    _ __  _
__ ___ 
>   \  // _ \ '_ \    |_ \| || |_   __) |__| '__/ __| |_ \ __| '_
\|
'__/ _ \
>   /  \  __/ | | |  ___) |__   _| / __/|__| | | (__ ___) |__| |_) | |
|  __/
>  /_/\_\___|_| |_| |____(_) |_|(_)_____|  |_|  \___|____/   | .__/|_| 
\___|
>                                                            |_|       
     
> (XEN) Xen version 3.4.2-rc3-pre (root@pca.com) (gcc version 4.1.2
20070115 
> (SUSE Linux)) Mon Nov  2 13:20:52 CST 2009
> (XEN) Latest ChangeSet: Thu Oct 29 15:02:30 2009 +0000
19815:d626b239fed1
> (XEN) Command line: dom0_mem=1024M
> (XEN) Video information:
> (XEN)  VGA is text mode 80x25, font 8x16
> (XEN)  VBE/DDC methods: V2; EDID transfer time: 2 seconds
> (XEN) Disc information:
> (XEN)  Found 2 MBR signatures
> (XEN)  Found 2 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 000000000009ec00 (usable)
> (XEN)  000000000009ec00 - 00000000000a0000 (reserved)
> (XEN)  00000000000f0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 00000000df62f000 (usable)
> (XEN)  00000000df62f000 - 00000000df63c000 (ACPI data)
> (XEN)  00000000df63c000 - 00000000df63d000 (usable)
> (XEN)  00000000df63d000 - 00000000e4000000 (reserved)
> (XEN)  00000000fec00000 - 00000000fee10000 (reserved)
> (XEN)  00000000ff800000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 000000081ffff000 (usable)
> (XEN) System RAM: 32757MB (33543988kB)
> (XEN) ACPI: RSDP 000F4F00, 0024 (r2 HP    )
> (XEN) ACPI: XSDT DF62FDC0, 00B4 (r1 HP     ProLiant        2   �    
162E)
> (XEN) ACPI: FACP DF62FEC0, 00F4 (r3 HP     ProLiant        2   �    
162E)
> (XEN) ACPI: DSDT DF62FFC0, 1F95 (r1 HP         DSDT        1 INTL
20030228)
> (XEN) ACPI: FACS DF62F100, 0040
> (XEN) ACPI: SPCR DF62F140, 0050 (r1 HP     SPCRRBSU        1   �    
162E)
> (XEN) ACPI: MCFG DF62F1C0, 003C (r1 HP     ProLiant        1         
   0)
> (XEN) ACPI: HPET DF62F200, 0038 (r1 HP     ProLiant        2   �    
162E)
> (XEN) ACPI: FFFF DF62F240, 0064 (r2 HP     ProLiant        2   �    
162E)
> (XEN) ACPI: SPMI DF62F2C0, 0040 (r5 HP     ProLiant        1   �    
162E)
> (XEN) ACPI: ERST DF62F300, 01D0 (r1 HP     ProLiant        1   �    
162E)
> (XEN) ACPI: APIC DF62F500, 00DE (r1 HP     ProLiant        2         
   0)
> (XEN) ACPI: SRAT DF62F600, 0370 (r1 HP     Proliant        1   �    
162E)
> (XEN) ACPI: FFFF DF62F980, 0176 (r1 HP     ProLiant        1   �    
162E)
> (XEN) ACPI: BERT DF62FB00, 0030 (r1 HP     ProLiant        1   �    
162E)
> (XEN) ACPI: HEST DF62FB40, 00BC (r1 HP     ProLiant        1   �    
162E)
> (XEN) ACPI: DMAR DF62FC00, 012C (r1 HP     ProLiant        1   �    
162E)
> (XEN) ACPI: SSDT DF631F80, 0125 (r3     HP  CRSPCI0        2   HP    
   1)
> (XEN) ACPI: SSDT DF6320C0, 01CF (r3     HP  riser1a        2 INTL
20061109)
> (XEN) ACPI: SSDT DF6322C0, 021B (r1     HP      pcc        1 INTL
20090625)
> (XEN) ACPI: SSDT DF632500, 0377 (r1     HP     pmab        1 INTL
20090625)
> (XEN) ACPI: SSDT DF632880, 3094 (r1  INTEL PPM RCM         1 INTL
20061109)
> (XEN) Domain heap initialised
> (XEN) Processor #0 7:10 APIC version 21
> (XEN) Processor #16 7:10 APIC version 21
> (XEN) Processor #4 7:10 APIC version 21
> (XEN) Processor #20 7:10 APIC version 21
> (XEN) Processor #2 7:10 APIC version 21
> (XEN) Processor #18 7:10 APIC version 21
> (XEN) Processor #6 7:10 APIC version 21
> (XEN) Processor #22 7:10 APIC version 21
> (XEN) Processor #1 7:10 APIC version 21
> (XEN) Processor #17 7:10 APIC version 21
> (XEN) Processor #5 7:10 APIC version 21
> (XEN) Processor #21 7:10 APIC version 21
> (XEN) Processor #3 7:10 APIC version 21
> (XEN) Processor #19 7:10 APIC version 21
> (XEN) Processor #7 7:10 APIC version 21
> (XEN) Processor #23 7:10 APIC version 21
> (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
> (XEN) IOAPIC[1]: apic_id 0, version 32, address 0xfec80000, GSI
24-47
> (XEN) Enabling APIC mode:  Phys.  Using 2 I/O APICs
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Detected 2533.494 MHz processor.
> (XEN) VMX: Supported advanced features:
> (XEN)  - APIC MMIO access virtualisation
> (XEN)  - APIC TPR shadow
> (XEN)  - Extended Page Tables (EPT)
> (XEN)  - Virtual-Processor Identifiers (VPID)
> (XEN)  - Virtual NMI
> (XEN)  - MSR direct-access bitmap
> (XEN) VMX: EPT is available.
> (XEN) VMX: VPID is available.
> (XEN) HVM: VMX enabled
> (XEN) HVM: Hardware Assisted Paging detected.
> (XEN) CPU0: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 1/16 eip 8c000
> (XEN) CPU1: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 2/4 eip 8c000
> (XEN) CPU2: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 3/20 eip 8c000
> (XEN) CPU3: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 4/2 eip 8c000
> (XEN) CPU4: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 5/18 eip 8c000
> (XEN) CPU5: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 6/6 eip 8c000
> (XEN) CPU6: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 7/22 eip 8c000
> (XEN) CPU7: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 8/1 eip 8c000
> (XEN) CPU8: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 9/17 eip 8c000
> (XEN) CPU9: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 10/5 eip 8c000
> (XEN) CPU10: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 11/21 eip 8c000
> (XEN) CPU11: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 12/3 eip 8c000
> (XEN) CPU12: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 13/19 eip 8c000
> (XEN) CPU13: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 14/7 eip 8c000
> (XEN) CPU14: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Booting processor 15/23 eip 8c000
> (XEN) CPU15: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz stepping
05
> (XEN) Total of 16 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  -> Using new ACK method
> (XEN) checking TSC synchronization across 16 CPUs: passed.
> (XEN) Platform timer is 14.318MHz HPET
> (XEN) Brought up 16 CPUs
> (XEN) I/O virtualisation disabled
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN)  Xen  kernel: 64-bit, lsb, compat32
> (XEN)  Dom0 kernel: 64-bit, lsb, paddr 0x100000 -> 0x4a3bdc
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   0000000808000000->0000000809000000 (258048
pages to be 
> allocated)
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff80100000->ffffffff804a3bdc
> (XEN)  Init. ramdisk: ffffffff804a4000->ffffffff80cb4000
> (XEN)  Phys-Mach map: ffffffff80cb4000->ffffffff80eb4000
> (XEN)  Start info:    ffffffff80eb4000->ffffffff80eb44b4
> (XEN)  Page tables:   ffffffff80eb5000->ffffffff80ec0000
> (XEN)  Boot stack:    ffffffff80ec0000->ffffffff80ec1000
> (XEN)  TOTAL:         ffffffff80000000->ffffffff81000000
> (XEN)  ENTRY ADDRESS: ffffffff80100000
> (XEN) Dom0 has maximum 16 VCPUs
> (XEN) Scrubbing Free RAM: 
>
.............................................................................
>
.............................................................................
>
.............................................................................
>
.............................................................................
> ......done.
> (XEN) Xen trace buffers: disabled
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> (XEN) Xen is relinquishing VGA console.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to
switch
input to 
> Xen)
> (XEN) Freed 128kB init memory.
> (XEN) mm.c:806:d0 Error getting mfn 100 (pfn 2420) from L1 entry 
> 0000000000100225 for l1e_owner=0, pg_owner=32753
> (XEN) mm.c:806:d0 Error getting mfn 100 (pfn 2420) from L1 entry 
> 0000000000100225 for l1e_owner=0, pg_owner=32753
> (XEN) mm.c:806:d0 Error getting mfn 100 (pfn 2420) from L1 entry 
> 0000000000100225 for l1e_owner=0, pg_owner=32753
> (XEN) mm.c:806:d0 Error getting mfn 100 (pfn 2420) from L1 entry 
> 0000000000100225 for l1e_owner=0, pg_owner=32753
> (XEN) mm.c:806:d0 Error getting mfn 100 (pfn 2420) from L1 entry 
> 0000000000100225 for l1e_owner=0, pg_owner=32753
> (XEN) mm.c:806:d0 Error getting mfn 100 (pfn 2420) from L1 entry 
> 0000000000100225 for l1e_owner=0, pg_owner=32753


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

On Tue, 2009-11-03 at 08:27 -0700, Nick Couchman wrote:
> Look at the log file referenced in this log:
> /var/log/xen/qemu-dm-Vista.log.
> 
> -Nick
> 
It says:

# cat qemu-dm-Vista.log
failed to set up fds or execute dm /usr/lib/xen/bin/qemu-dm: [''OSError:
[Errno 2] No such file or directory\n'']


This file is actually located here:
/usr/lib64/xen/bin/qemu-dm

James


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

Yeah...some of the locations may change when you use the vanilla source vs. the
SLES packages - the package builders (not just SLES - RH/Fedora/etc.) tend to
move things around a bit, and that causes problems.  You can create a symlink in
/usr/lib/xen/bin to the /usr/lib64/xen/bin binary and that will probably also
solve your problem.  Or you can just remember to change the location of the
device model in your Xen configs.

-Nick
>>> On 2009/11/03 at 08:43, James Pifer <jep@obrien-pifer.com>
wrote:
> On Tue, 2009-11-03 at 08:27 -0700, Nick Couchman wrote:
>> Look at the log file referenced in this log:
>> /var/log/xen/qemu-dm-Vista.log.
>> 
>> -Nick
>> 
> 
> It says:
> 
> # cat qemu-dm-Vista.log
> failed to set up fds or execute dm /usr/lib/xen/bin/qemu-dm:
[''OSError:
> [Errno 2] No such file or directory\n'']
> 
> 
> This file is actually located here:
> /usr/lib64/xen/bin/qemu-dm
> 
> 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@lists.xensource.com
http://lists.xensource.com/xen-users

On Tue, 2009-11-03 at 08:59 -0700, Nick Couchman wrote:
> You might need to specify "bridge=<bridgename>" on the
"vif=" line in your config file and point it at a specific bridge.
> 
> -Nick
How can I tell what the bridge is called? Is it eth4 or peth4?

brctl show gives me:
bridge name     bridge id               STP enabled     interfaces
eth4            8000.002655827dd4       no              peth4


# ifconfig
eth4      Link encap:Ethernet  HWaddr 00:26:55:82:7D:D4  
          inet addr:172.16.4.153  Bcast:10.96.5.255  Mask:255.255.254.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:147511 errors:0 dropped:0 overruns:0 frame:0
          TX packets:121841 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:30694748 (29.2 Mb)  TX bytes:36280012 (34.5 Mb)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:114 errors:0 dropped:0 overruns:0 frame:0
          TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:6850 (6.6 Kb)  TX bytes:6850 (6.6 Kb)

peth4     Link encap:Ethernet  HWaddr 00:26:55:82:7D:D4  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:147623 errors:0 dropped:0 overruns:0 frame:0
          TX packets:124186 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:33415763 (31.8 Mb)  TX bytes:36952614 (35.2 Mb)
          Interrupt:20 Memory:f8000000-f8012100 


I tied this these didn''t work:
vif=[
''bridge=peth4,mac=00:16:3e:1a:45:41,model=rtl8139,type=ioemu'',
]
vif=[
''bridge=eth4,mac=00:16:3e:1a:45:41,model=rtl8139,type=ioemu'',
]

I''d still like to get virt-manager working too, but not sure to go
about
that. 

Thanks,
James


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

eth4 - The xen startup script renames eth4 to peth4, then creates a
bridge called eth4.  You can also use the command "brctl show" to show
the currently configured bridges.

-Nick
>>> On 2009/11/03 at 09:49, James Pifer <jep@obrien-pifer.com>
wrote:
> On Tue, 2009-11-03 at 08:59 -0700, Nick Couchman wrote:
>> You might need to specify "bridge=<bridgename>" on the
"vif=" line
in your 
> config file and point it at a specific bridge.
>> 
>> -Nick
> 
> How can I tell what the bridge is called? Is it eth4 or peth4?
> 
> brctl show gives me:
> bridge name     bridge id               STP enabled     interfaces
> eth4            8000.002655827dd4       no              peth4
> 
> 
> # ifconfig
> eth4      Link encap:Ethernet  HWaddr 00:26:55:82:7D:D4  
>           inet addr:172.16.4.153  Bcast:10.96.5.255 
Mask:255.255.254.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:147511 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:121841 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:30694748 (29.2 Mb)  TX bytes:36280012 (34.5 Mb)
> 
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:114 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:6850 (6.6 Kb)  TX bytes:6850 (6.6 Kb)
> 
> peth4     Link encap:Ethernet  HWaddr 00:26:55:82:7D:D4  
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:147623 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:124186 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:33415763 (31.8 Mb)  TX bytes:36952614 (35.2 Mb)
>           Interrupt:20 Memory:f8000000-f8012100 
> 
> 
> I tied this these didn't work:
> vif=[
'bridge=peth4,mac=00:16:3e:1a:45:41,model=rtl8139,type=ioemu',
]
> vif=[
'bridge=eth4,mac=00:16:3e:1a:45:41,model=rtl8139,type=ioemu',
]
> 
> I'd still like to get virt-manager working too, but not sure to go
about
> that. 
> 
> 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@lists.xensource.com
http://lists.xensource.com/xen-users

According to brctl show, your ethernet bride is eth4 and not peth4.

Try this:

vif=[ ''mac=00:16:3e:1a:45:41,bridge=eth4'' ]

-- 
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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore

On Wed, Nov 4, 2009 at 12:49 AM, James Pifer <jep@obrien-pifer.com> wrote:
> On Tue, 2009-11-03 at 08:59 -0700, Nick Couchman wrote:
> > You might need to specify "bridge=<bridgename>" on the
"vif=" line in
> your config file and point it at a specific bridge.
> >
> > -Nick
>
> How can I tell what the bridge is called? Is it eth4 or peth4?
>
> brctl show gives me:
> bridge name     bridge id               STP enabled     interfaces
> eth4            8000.002655827dd4       no              peth4
>
>
> # ifconfig
> eth4      Link encap:Ethernet  HWaddr 00:26:55:82:7D:D4
>          inet addr:172.16.4.153  Bcast:10.96.5.255  Mask:255.255.254.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:147511 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:121841 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:30694748 (29.2 Mb)  TX bytes:36280012 (34.5 Mb)
>
> lo        Link encap:Local Loopback
>          inet addr:127.0.0.1  Mask:255.0.0.0
>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>          RX packets:114 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:6850 (6.6 Kb)  TX bytes:6850 (6.6 Kb)
>
> peth4     Link encap:Ethernet  HWaddr 00:26:55:82:7D:D4
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:147623 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:124186 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:33415763 (31.8 Mb)  TX bytes:36952614 (35.2 Mb)
>          Interrupt:20 Memory:f8000000-f8012100
>
>
> I tied this these didn''t work:
> vif=[
''bridge=peth4,mac=00:16:3e:1a:45:41,model=rtl8139,type=ioemu'',
]
> vif=[
''bridge=eth4,mac=00:16:3e:1a:45:41,model=rtl8139,type=ioemu'',
]
>
> I''d still like to get virt-manager working too, but not sure to go
about
> that.
>
> Thanks,
> James
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

On Wed, 2009-11-04 at 01:14 +0800, Mr. Teo En Ming (Zhang Enming)
wrote:
> According to brctl show, your ethernet bride is eth4 and not peth4.
> 
> Try this:
> 
> vif=[ ''mac=00:16:3e:1a:45:41,bridge=eth4'' ]
> 
> -- 

I''m wondering if I should try centos. I can get newer packages for xen
on centos I believe.

I tried what you suggested and still got the same thing. Still no go. 

[2009-11-03 11:23:22 5603] DEBUG (XendDomain:1006) Creating new managed domain:
Vista
[2009-11-03 11:23:26 5603] DEBUG (XendDomainInfo:2304)
XendDomainInfo.constructDomain
[2009-11-03 11:23:26 5603] DEBUG (balloon:166) Balloon: 32122132 KiB free; need
4096; done.
[2009-11-03 11:23:26 5603] DEBUG (XendDomain:453) Adding Domain: 12
[2009-11-03 11:23:26 5603] DEBUG (XendDomainInfo:2505)
XendDomainInfo.initDomain: 12 256
[2009-11-03 11:23:26 5603] DEBUG (image:322) No VNC passwd configured for vfb
access
[2009-11-03 11:23:26 5603] DEBUG (image:813) args: boot, val: c
[2009-11-03 11:23:26 5603] DEBUG (image:813) args: fda, val: None
[2009-11-03 11:23:26 5603] DEBUG (image:813) args: fdb, val: None
[2009-11-03 11:23:26 5603] DEBUG (image:813) args: soundhw, val: None
[2009-11-03 11:23:26 5603] DEBUG (image:813) args: localtime, val: 1
[2009-11-03 11:23:26 5603] DEBUG (image:813) args: serial, val:
[''pty'']
[2009-11-03 11:23:26 5603] DEBUG (image:813) args: std-vga, val: 0
[2009-11-03 11:23:26 5603] DEBUG (image:813) args: isa, val: 0
[2009-11-03 11:23:26 5603] DEBUG (image:813) args: acpi, val: 1
[2009-11-03 11:23:26 5603] DEBUG (image:813) args: usb, val: 1
[2009-11-03 11:23:26 5603] DEBUG (image:813) args: usbdevice, val:
host:0951:1607
[2009-11-03 11:23:26 5603] INFO (image:749) Need to create platform
device.[domid:12]
[2009-11-03 11:23:26 5603] DEBUG (XendDomainInfo:2529)
_initDomain:shadow_memory=0x0, memory_static_max=0x40000000,
memory_static_min=0x0.
[2009-11-03 11:23:26 5603] DEBUG (balloon:166) Balloon: 32120700 KiB free; need
1067008; done.
[2009-11-03 11:23:26 5603] INFO (image:173) buildDomain os=hvm dom=12 vcpus=2
[2009-11-03 11:23:26 5603] DEBUG (image:866) domid          = 12
[2009-11-03 11:23:26 5603] DEBUG (image:867) image          =
/usr/lib/xen/boot/hvmloader
[2009-11-03 11:23:26 5603] DEBUG (image:868) store_evtchn   = 3
[2009-11-03 11:23:26 5603] DEBUG (image:869) memsize        = 1024
[2009-11-03 11:23:26 5603] DEBUG (image:870) target         = 1024
[2009-11-03 11:23:26 5603] DEBUG (image:871) vcpus          = 2
[2009-11-03 11:23:26 5603] DEBUG (image:872) acpi           = 1
[2009-11-03 11:23:26 5603] DEBUG (image:873) apic           = 1
[2009-11-03 11:23:26 5603] INFO (XendDomainInfo:2168) createDevice: vfb :
{''vncunused'': 1, ''other_config'':
{''vncunused'': 1, ''vnc'':
''1''}, ''vnc'': ''1'',
''uuid'':
''ecf80d39-153a-f383-f43b-85c6cb4fe3d0''}
[2009-11-03 11:23:26 5603] DEBUG (DevController:95) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vfb/12/0''} to
/local/domain/12/device/vfb/0.
[2009-11-03 11:23:26 5603] DEBUG (DevController:97) DevController: writing
{''vncunused'': ''1'',
''domain'': ''Vista'',
''frontend'': ''/local/domain/12/device/vfb/0'',
''uuid'':
''ecf80d39-153a-f383-f43b-85c6cb4fe3d0'',
''frontend-id'': ''12'',
''state'': ''1'', ''online'':
''1'', ''vnc'': ''1''} to
/local/domain/0/backend/vfb/12/0.
[2009-11-03 11:23:26 5603] INFO (XendDomainInfo:2168) createDevice: vbd :
{''uuid'':
''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': 1, ''driver'':
''paravirtualised'', ''dev'':
''hda'', ''uname'':
''file:/xendata2/images/Vista/disk0'', ''mode'':
''w''}
[2009-11-03 11:23:26 5603] DEBUG (DevController:95) DevController: writing
{''backend-id'': ''0'',
''virtual-device'': ''768'',
''device-type'': ''disk'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/12/768''} to
/local/domain/12/device/vbd/768.
[2009-11-03 11:23:26 5603] DEBUG (DevController:97) DevController: writing
{''domain'': ''Vista'',
''frontend'':
''/local/domain/12/device/vbd/768'', ''uuid'':
''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': ''1'', ''dev'':
''hda'', ''state'': ''1'',
''params'': ''/xendata2/images/Vista/disk0'',
''mode'': ''w'', ''online'':
''1'', ''frontend-id'': ''12'',
''type'': ''file''} to
/local/domain/0/backend/vbd/12/768.
[2009-11-03 11:23:26 5603] INFO (XendDomainInfo:2168) createDevice: vif :
{''bridge'': ''eth4'', ''mac'':
''00:16:3e:1a:45:41'', ''uuid'':
''10b23fcd-acbe-c507-3593-640c6131f533''}
[2009-11-03 11:23:26 5603] DEBUG (DevController:95) DevController: writing
{''backend-id'': ''0'', ''mac'':
''00:16:3e:1a:45:41'', ''handle'':
''0'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vif/12/0''} to
/local/domain/12/device/vif/0.
[2009-11-03 11:23:26 5603] DEBUG (DevController:97) DevController: writing
{''bridge'': ''eth4'',
''domain'': ''Vista'',
''handle'': ''0'', ''uuid'':
''10b23fcd-acbe-c507-3593-640c6131f533'',
''script'': ''/etc/xen/scripts/vif-bridge'',
''mac'': ''00:16:3e:1a:45:41'',
''frontend-id'': ''12'',
''state'': ''1'', ''online'':
''1'', ''frontend'':
''/local/domain/12/device/vif/0''} to
/local/domain/0/backend/vif/12/0.
[2009-11-03 11:23:26 5603] INFO (image:394) spawning device models:
/usr/lib/xen/bin/qemu-dm [''/usr/lib/xen/bin/qemu-dm'',
''-d'', ''12'',
''-domain-name'', ''Vista'',
''-videoram'', ''4'', ''-vnc'',
''127.0.0.1:0'', ''-vncunused'',
''-vcpus'', ''2'', ''-boot'',
''c'', ''-localtime'',
''-serial'', ''pty'', ''-acpi'',
''-usb'', ''-usbdevice'',
''host:0951:1607'', ''-net'',
''nic,vlan=1,macaddr=00:16:3e:1a:45:41,model=rtl8139'',
''-net'',
''tap,vlan=1,ifname=tap12.0,bridge=eth4'',
''-M'', ''xenfv'']
[2009-11-03 11:23:26 5603] INFO (image:443) device model pid: 23382
[2009-11-03 11:23:26 5603] INFO (image:531) waiting for sentinel_fifo
[2009-11-03 11:23:26 5603] DEBUG (XendDomainInfo:3060) Storing VM details:
{''on_xend_stop'': ''ignore'',
''shadow_memory'': ''10'',
''uuid'':
''abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
''on_reboot'': ''restart'',
''start_time'': ''1257269006.36'',
''on_poweroff'': ''destroy'',
''bootloader_args'': '''',
''on_xend_start'': ''ignore'',
''on_crash'': ''destroy'',
''xend/restart_count'': ''0'',
''vcpus'': ''2'',
''vcpu_avail'': ''3'',
''bootloader'': '''', ''image'':
''(hvm (kernel ) (videoram 4) (hpet 0) (stdvga 0) (loader
/usr/lib/xen/boot/hvmloader) (serial pty) (vncunused 1) (xen_platform_pci 1)
(boot c) (rtc_timeoffset 0) (pci ()) (pae 1) (vpt_align 1) (hap 1) (viridian 0)
(acpi 1) (localtime 1) (timer_mode 1) (vnc 1) (nographic 0) (guest_os_type
default) (pci_msitranslate 1) (apic 1) (monitor 0) (usbdevice host:0951:1607)
(device_model /usr/lib/xen/bin/qemu-dm) (pci_power_mgmt 0) (usb 1) (xauthority
/root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL 1)))'',
''name'': ''Vista''}
[2009-11-03 11:23:26 5603] DEBUG (XendDomainInfo:1622) Storing domain details:
{''console/port'': ''4'',
''name'': ''Vista'',
''console/limit'': ''1048576'',
''store/port'': ''3'', ''vm'':
''/vm/abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
''domid'': ''12'',
''image/suspend-cancel'': ''1'',
''cpu/0/availability'': ''online'',
''memory/target'': ''1048576'',
''control/platform-feature-multiprocessor-suspend'':
''1'', ''store/ring-ref'':
''1044476'', ''cpu/1/availability'':
''online'', ''console/type'':
''ioemu''}
[2009-11-03 11:23:26 5603] DEBUG (DevController:139) Waiting for devices vif.
[2009-11-03 11:23:26 5603] DEBUG (DevController:95) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/console/12/0''} to
/local/domain/12/device/console/0.
[2009-11-03 11:23:26 5603] DEBUG (DevController:144) Waiting for 0.
[2009-11-03 11:23:26 5603] DEBUG (DevController:97) DevController: writing
{''domain'': ''Vista'',
''frontend'':
''/local/domain/12/device/console/0'', ''uuid'':
''12f0151f-6f80-887e-ff47-f98302e69222'',
''frontend-id'': ''12'',
''state'': ''1'', ''location'':
''4'', ''online'': ''1'',
''protocol'': ''vt100''} to
/local/domain/0/backend/console/12/0.
[2009-11-03 11:23:26 5603] DEBUG (XendDomainInfo:1709)
XendDomainInfo.handleShutdownWatch
[2009-11-03 11:23:26 5603] DEBUG (DevController:629) hotplugStatusCallback
/local/domain/0/backend/vif/12/0/hotplug-status.
[2009-11-03 11:25:06 5603] WARNING (XendDomain:1048) Failed to setup devices for
<domain id=12 name=Vista memory=1073741824 state=paused>: Device 0 (vif)
could not be connected. Hotplug scripts not working.
[2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2732) XendDomainInfo.destroy:
domid=12
[2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2207) Destroying device model
[2009-11-03 11:25:06 5603] INFO (image:556) Vista device model terminated
[2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2214) Releasing devices
[2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2227) Removing vif/0
[2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2227) Removing vbd/768
[2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2227) Removing vfb/0
[2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2227) Removing console/0
[2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2212) No device model
[2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2214) Releasing devices




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

After you have started Vista virtual machine, can you post your "brctl
show"
output and contents of /var/log/xen/qemu-dm-Vista.log again.

You might want to try Fedora 11 64-bit with Xen 3.4-testing and latest
pv-ops dom0 kernel 2.6.31.5 like me.

-- 
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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore

On Wed, Nov 4, 2009 at 1:30 AM, James Pifer <jep@obrien-pifer.com> wrote:
> On Wed, 2009-11-04 at 01:14 +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> > According to brctl show, your ethernet bride is eth4 and not peth4.
> >
> > Try this:
> >
> > vif=[ ''mac=00:16:3e:1a:45:41,bridge=eth4'' ]
> >
> > --
>
> 
> I''m wondering if I should try centos. I can get newer packages for
xen
> on centos I believe.
>
> I tried what you suggested and still got the same thing. Still no go.
>
> [2009-11-03 11:23:22 5603] DEBUG (XendDomain:1006) Creating new managed
> domain: Vista
> [2009-11-03 11:23:26 5603] DEBUG (XendDomainInfo:2304)
> XendDomainInfo.constructDomain
> [2009-11-03 11:23:26 5603] DEBUG (balloon:166) Balloon: 32122132 KiB free;
> need 4096; done.
> [2009-11-03 11:23:26 5603] DEBUG (XendDomain:453) Adding Domain: 12
> [2009-11-03 11:23:26 5603] DEBUG (XendDomainInfo:2505)
> XendDomainInfo.initDomain: 12 256
> [2009-11-03 11:23:26 5603] DEBUG (image:322) No VNC passwd configured for
> vfb access
> [2009-11-03 11:23:26 5603] DEBUG (image:813) args: boot, val: c
> [2009-11-03 11:23:26 5603] DEBUG (image:813) args: fda, val: None
> [2009-11-03 11:23:26 5603] DEBUG (image:813) args: fdb, val: None
> [2009-11-03 11:23:26 5603] DEBUG (image:813) args: soundhw, val: None
> [2009-11-03 11:23:26 5603] DEBUG (image:813) args: localtime, val: 1
> [2009-11-03 11:23:26 5603] DEBUG (image:813) args: serial, val:
[''pty'']
> [2009-11-03 11:23:26 5603] DEBUG (image:813) args: std-vga, val: 0
> [2009-11-03 11:23:26 5603] DEBUG (image:813) args: isa, val: 0
> [2009-11-03 11:23:26 5603] DEBUG (image:813) args: acpi, val: 1
> [2009-11-03 11:23:26 5603] DEBUG (image:813) args: usb, val: 1
> [2009-11-03 11:23:26 5603] DEBUG (image:813) args: usbdevice, val:
> host:0951:1607
> [2009-11-03 11:23:26 5603] INFO (image:749) Need to create platform
> device.[domid:12]
> [2009-11-03 11:23:26 5603] DEBUG (XendDomainInfo:2529)
> _initDomain:shadow_memory=0x0, memory_static_max=0x40000000,
> memory_static_min=0x0.
> [2009-11-03 11:23:26 5603] DEBUG (balloon:166) Balloon: 32120700 KiB free;
> need 1067008; done.
> [2009-11-03 11:23:26 5603] INFO (image:173) buildDomain os=hvm dom=12
> vcpus=2
> [2009-11-03 11:23:26 5603] DEBUG (image:866) domid          = 12
> [2009-11-03 11:23:26 5603] DEBUG (image:867) image          >
/usr/lib/xen/boot/hvmloader
> [2009-11-03 11:23:26 5603] DEBUG (image:868) store_evtchn   = 3
> [2009-11-03 11:23:26 5603] DEBUG (image:869) memsize        = 1024
> [2009-11-03 11:23:26 5603] DEBUG (image:870) target         = 1024
> [2009-11-03 11:23:26 5603] DEBUG (image:871) vcpus          = 2
> [2009-11-03 11:23:26 5603] DEBUG (image:872) acpi           = 1
> [2009-11-03 11:23:26 5603] DEBUG (image:873) apic           = 1
> [2009-11-03 11:23:26 5603] INFO (XendDomainInfo:2168) createDevice: vfb :
> {''vncunused'': 1, ''other_config'':
{''vncunused'': 1, ''vnc'':
''1''}, ''vnc'': ''1'',
> ''uuid'':
''ecf80d39-153a-f383-f43b-85c6cb4fe3d0''}
> [2009-11-03 11:23:26 5603] DEBUG (DevController:95) DevController: writing
> {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
> ''/local/domain/0/backend/vfb/12/0''} to
/local/domain/12/device/vfb/0.
> [2009-11-03 11:23:26 5603] DEBUG (DevController:97) DevController: writing
> {''vncunused'': ''1'',
''domain'': ''Vista'',
''frontend'':
> ''/local/domain/12/device/vfb/0'',
''uuid'':
> ''ecf80d39-153a-f383-f43b-85c6cb4fe3d0'',
''frontend-id'': ''12'',
''state'': ''1'',
> ''online'': ''1'', ''vnc'':
''1''} to /local/domain/0/backend/vfb/12/0.
> [2009-11-03 11:23:26 5603] INFO (XendDomainInfo:2168) createDevice: vbd :
> {''uuid'':
''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': 1, ''driver'':
> ''paravirtualised'', ''dev'':
''hda'', ''uname'':
> ''file:/xendata2/images/Vista/disk0'',
''mode'': ''w''}
> [2009-11-03 11:23:26 5603] DEBUG (DevController:95) DevController: writing
> {''backend-id'': ''0'',
''virtual-device'': ''768'',
''device-type'': ''disk'',
''state'':
> ''1'', ''backend'':
''/local/domain/0/backend/vbd/12/768''} to
> /local/domain/12/device/vbd/768.
> [2009-11-03 11:23:26 5603] DEBUG (DevController:97) DevController: writing
> {''domain'': ''Vista'',
''frontend'':
''/local/domain/12/device/vbd/768'', ''uuid'':
> ''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': ''1'', ''dev'':
''hda'',
> ''state'': ''1'',
''params'': ''/xendata2/images/Vista/disk0'',
''mode'': ''w'',
> ''online'': ''1'',
''frontend-id'': ''12'',
''type'': ''file''} to
> /local/domain/0/backend/vbd/12/768.
> [2009-11-03 11:23:26 5603] INFO (XendDomainInfo:2168) createDevice: vif :
> {''bridge'': ''eth4'',
''mac'': ''00:16:3e:1a:45:41'',
''uuid'':
> ''10b23fcd-acbe-c507-3593-640c6131f533''}
> [2009-11-03 11:23:26 5603] DEBUG (DevController:95) DevController: writing
> {''backend-id'': ''0'',
''mac'': ''00:16:3e:1a:45:41'',
''handle'': ''0'', ''state'':
''1'',
> ''backend'':
''/local/domain/0/backend/vif/12/0''} to
> /local/domain/12/device/vif/0.
> [2009-11-03 11:23:26 5603] DEBUG (DevController:97) DevController: writing
> {''bridge'': ''eth4'',
''domain'': ''Vista'',
''handle'': ''0'', ''uuid'':
> ''10b23fcd-acbe-c507-3593-640c6131f533'',
''script'':
> ''/etc/xen/scripts/vif-bridge'', ''mac'':
''00:16:3e:1a:45:41'', ''frontend-id'':
> ''12'', ''state'': ''1'',
''online'': ''1'', ''frontend'':
> ''/local/domain/12/device/vif/0''} to
/local/domain/0/backend/vif/12/0.
> [2009-11-03 11:23:26 5603] INFO (image:394) spawning device models:
> /usr/lib/xen/bin/qemu-dm [''/usr/lib/xen/bin/qemu-dm'',
''-d'', ''12'',
> ''-domain-name'', ''Vista'',
''-videoram'', ''4'', ''-vnc'',
''127.0.0.1:0'',
> ''-vncunused'', ''-vcpus'',
''2'', ''-boot'', ''c'',
''-localtime'', ''-serial'',
''pty'',
> ''-acpi'', ''-usb'',
''-usbdevice'', ''host:0951:1607'',
''-net'',
> ''nic,vlan=1,macaddr=00:16:3e:1a:45:41,model=rtl8139'',
''-net'',
> ''tap,vlan=1,ifname=tap12.0,bridge=eth4'',
''-M'', ''xenfv'']
> [2009-11-03 11:23:26 5603] INFO (image:443) device model pid: 23382
> [2009-11-03 11:23:26 5603] INFO (image:531) waiting for sentinel_fifo
> [2009-11-03 11:23:26 5603] DEBUG (XendDomainInfo:3060) Storing VM details:
> {''on_xend_stop'': ''ignore'',
''shadow_memory'': ''10'',
''uuid'':
> ''abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
''on_reboot'': ''restart'',
> ''start_time'': ''1257269006.36'',
''on_poweroff'': ''destroy'',
''bootloader_args'':
> '''', ''on_xend_start'':
''ignore'', ''on_crash'':
''destroy'', ''xend/restart_count'':
> ''0'', ''vcpus'': ''2'',
''vcpu_avail'': ''3'',
''bootloader'': '''', ''image'':
''(hvm
> (kernel ) (videoram 4) (hpet 0) (stdvga 0) (loader
> /usr/lib/xen/boot/hvmloader) (serial pty) (vncunused 1) (xen_platform_pci
1)
> (boot c) (rtc_timeoffset 0) (pci ()) (pae 1) (vpt_align 1) (hap 1)
(viridian
> 0) (acpi 1) (localtime 1) (timer_mode 1) (vnc 1) (nographic 0)
> (guest_os_type default) (pci_msitranslate 1) (apic 1) (monitor 0)
(usbdevice
> host:0951:1607) (device_model /usr/lib/xen/bin/qemu-dm) (pci_power_mgmt 0)
> (usb 1) (xauthority /root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL
1)))'',
> ''name'': ''Vista''}
> [2009-11-03 11:23:26 5603] DEBUG (XendDomainInfo:1622) Storing domain
> details: {''console/port'': ''4'',
''name'': ''Vista'',
''console/limit'': ''1048576'',
> ''store/port'': ''3'',
''vm'':
''/vm/abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
> ''domid'': ''12'',
''image/suspend-cancel'': ''1'',
''cpu/0/availability'': ''online'',
> ''memory/target'': ''1048576'',
> ''control/platform-feature-multiprocessor-suspend'':
''1'', ''store/ring-ref'':
> ''1044476'', ''cpu/1/availability'':
''online'', ''console/type'':
''ioemu''}
> [2009-11-03 11:23:26 5603] DEBUG (DevController:139) Waiting for devices
> vif.
> [2009-11-03 11:23:26 5603] DEBUG (DevController:95) DevController: writing
> {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
> ''/local/domain/0/backend/console/12/0''} to
> /local/domain/12/device/console/0.
> [2009-11-03 11:23:26 5603] DEBUG (DevController:144) Waiting for 0.
> [2009-11-03 11:23:26 5603] DEBUG (DevController:97) DevController: writing
> {''domain'': ''Vista'',
''frontend'':
''/local/domain/12/device/console/0'', ''uuid'':
> ''12f0151f-6f80-887e-ff47-f98302e69222'',
''frontend-id'': ''12'',
''state'': ''1'',
> ''location'': ''4'',
''online'': ''1'', ''protocol'':
''vt100''} to
> /local/domain/0/backend/console/12/0.
> [2009-11-03 11:23:26 5603] DEBUG (XendDomainInfo:1709)
> XendDomainInfo.handleShutdownWatch
> [2009-11-03 11:23:26 5603] DEBUG (DevController:629) hotplugStatusCallback
> /local/domain/0/backend/vif/12/0/hotplug-status.
> [2009-11-03 11:25:06 5603] WARNING (XendDomain:1048) Failed to setup
> devices for <domain id=12 name=Vista memory=1073741824 state=paused>:
Device
> 0 (vif) could not be connected. Hotplug scripts not working.
> [2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2732)
> XendDomainInfo.destroy: domid=12
> [2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2207) Destroying device
> model
> [2009-11-03 11:25:06 5603] INFO (image:556) Vista device model terminated
> [2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2214) Releasing devices
> [2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2227) Removing vif/0
> [2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
> [2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2227) Removing vbd/768
> [2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
> [2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2227) Removing vfb/0
> [2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
> [2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2227) Removing console/0
> [2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
> [2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2212) No device model
> [2009-11-03 11:25:06 5603] DEBUG (XendDomainInfo:2214) Releasing devices
>
>
>
>

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

On Wed, 2009-11-04 at 01:42 +0800, Mr. Teo En Ming (Zhang Enming)
wrote:
> brctl show

You mean while it''s attempting to start? See below.

I could probably get away with centos in a production environment, but
definitely not fedora. SLES10 is our current "standard". Unfortunately
I
need usb functionality for a production server, whether that is or is
not recommended. 

Thanks,
James


# xm start Vista
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Usage: xm start <DomainName>

Start a Xend managed domain
  -p, --paused                   Do not unpause domain after starting it    
  -c, --console_autoconnect      Connect to the console after the domain    
                                 is created
  --vncviewer                    Connect to display via VNC after the       
                                 domain is created
  --vncviewer-autopass           Pass VNC password to viewer via stdin and  
                                 -autopass



# brctl show
bridge name     bridge id               STP enabled     interfaces
eth4            8000.002655827dd4       no              peth4
                                                        tap13.0




[2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2304)
XendDomainInfo.constructDomain
[2009-11-03 11:47:41 5603] DEBUG (balloon:166) Balloon: 32122132 KiB free; need
4096; done.
[2009-11-03 11:47:41 5603] DEBUG (XendDomain:453) Adding Domain: 13
[2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2505)
XendDomainInfo.initDomain: 13 256
[2009-11-03 11:47:41 5603] DEBUG (image:322) No VNC passwd configured for vfb
access
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: boot, val: c
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: fda, val: None
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: fdb, val: None
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: soundhw, val: None
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: localtime, val: 1
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: serial, val:
[''pty'']
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: std-vga, val: 0
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: isa, val: 0
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: acpi, val: 1
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: usb, val: 1
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: usbdevice, val:
host:0951:1607
[2009-11-03 11:47:41 5603] INFO (image:749) Need to create platform
device.[domid:13]
[2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2529)
_initDomain:shadow_memory=0xa, memory_static_max=0x40000000,
memory_static_min=0x0.
[2009-11-03 11:47:41 5603] DEBUG (balloon:166) Balloon: 32120700 KiB free; need
1067008; done.
[2009-11-03 11:47:41 5603] INFO (image:173) buildDomain os=hvm dom=13 vcpus=2
[2009-11-03 11:47:41 5603] DEBUG (image:866) domid          = 13
[2009-11-03 11:47:41 5603] DEBUG (image:867) image          =
/usr/lib/xen/boot/hvmloader
[2009-11-03 11:47:41 5603] DEBUG (image:868) store_evtchn   = 3
[2009-11-03 11:47:41 5603] DEBUG (image:869) memsize        = 1024
[2009-11-03 11:47:41 5603] DEBUG (image:870) target         = 1024
[2009-11-03 11:47:41 5603] DEBUG (image:871) vcpus          = 2
[2009-11-03 11:47:41 5603] DEBUG (image:872) acpi           = 1
[2009-11-03 11:47:41 5603] DEBUG (image:873) apic           = 1
[2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vfb :
{''vncunused'': 1, ''other_config'':
{''vncunused'': 1, ''vnc'':
''1''}, ''vnc'': ''1'',
''uuid'':
''ecf80d39-153a-f383-f43b-85c6cb4fe3d0'',
''devid'': 0, ''location'':
''127.0.0.1:5900''}
[2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vfb/13/0''} to
/local/domain/13/device/vfb/0.
[2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
{''vncunused'': ''1'',
''domain'': ''Vista'',
''frontend'': ''/local/domain/13/device/vfb/0'',
''uuid'':
''ecf80d39-153a-f383-f43b-85c6cb4fe3d0'',
''frontend-id'': ''13'',
''state'': ''1'', ''location'':
''127.0.0.1:5900'', ''online'':
''1'', ''vnc'': ''1''} to
/local/domain/0/backend/vfb/13/0.
[2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: console :
{''other_config'': {}, ''protocol'':
''vt100'', ''uuid'':
''12f0151f-6f80-887e-ff47-f98302e69222'',
''location'': ''4''}
[2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/console/13/0''} to
/local/domain/13/device/console/0.
[2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
{''domain'': ''Vista'',
''frontend'':
''/local/domain/13/device/console/0'', ''uuid'':
''12f0151f-6f80-887e-ff47-f98302e69222'',
''frontend-id'': ''13'',
''state'': ''1'', ''location'':
''4'', ''online'': ''1'',
''protocol'': ''vt100''} to
/local/domain/0/backend/console/13/0.
[2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vbd :
{''uuid'':
''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': 1, ''devid'': 768,
''driver'': ''paravirtualised'',
''dev'': ''hda'', ''uname'':
''file:/xendata2/images/Vista/disk0'', ''mode'':
''w''}
[2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
{''backend-id'': ''0'',
''virtual-device'': ''768'',
''device-type'': ''disk'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/13/768''} to
/local/domain/13/device/vbd/768.
[2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
{''domain'': ''Vista'',
''frontend'':
''/local/domain/13/device/vbd/768'', ''uuid'':
''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': ''1'', ''dev'':
''hda'', ''state'': ''1'',
''params'': ''/xendata2/images/Vista/disk0'',
''mode'': ''w'', ''online'':
''1'', ''frontend-id'': ''13'',
''type'': ''file''} to
/local/domain/0/backend/vbd/13/768.
[2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vif :
{''bridge'': ''eth4'', ''mac'':
''00:16:3e:1a:45:41'', ''devid'': 0,
''uuid'':
''10b23fcd-acbe-c507-3593-640c6131f533''}
[2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
{''backend-id'': ''0'', ''mac'':
''00:16:3e:1a:45:41'', ''handle'':
''0'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vif/13/0''} to
/local/domain/13/device/vif/0.
[2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
{''bridge'': ''eth4'',
''domain'': ''Vista'',
''handle'': ''0'', ''uuid'':
''10b23fcd-acbe-c507-3593-640c6131f533'',
''script'': ''/etc/xen/scripts/vif-bridge'',
''mac'': ''00:16:3e:1a:45:41'',
''frontend-id'': ''13'',
''state'': ''1'', ''online'':
''1'', ''frontend'':
''/local/domain/13/device/vif/0''} to
/local/domain/0/backend/vif/13/0.
[2009-11-03 11:47:41 5603] INFO (image:394) spawning device models:
/usr/lib/xen/bin/qemu-dm [''/usr/lib/xen/bin/qemu-dm'',
''-d'', ''13'',
''-domain-name'', ''Vista'',
''-videoram'', ''4'', ''-vnc'',
''127.0.0.1:0'', ''-vncunused'',
''-vcpus'', ''2'', ''-boot'',
''c'', ''-localtime'',
''-serial'', ''pty'', ''-acpi'',
''-usb'', ''-usbdevice'',
''host:0951:1607'', ''-net'',
''nic,vlan=1,macaddr=00:16:3e:1a:45:41,model=rtl8139'',
''-net'',
''tap,vlan=1,ifname=tap13.0,bridge=eth4'',
''-M'', ''xenfv'']
[2009-11-03 11:47:41 5603] INFO (image:443) device model pid: 24518
[2009-11-03 11:47:41 5603] INFO (image:531) waiting for sentinel_fifo
[2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:3060) Storing VM details:
{''on_xend_stop'': ''ignore'',
''shadow_memory'': ''10'',
''uuid'':
''abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
''on_reboot'': ''restart'',
''start_time'': ''1257270461.49'',
''on_poweroff'': ''destroy'',
''bootloader_args'': '''',
''on_xend_start'': ''ignore'',
''on_crash'': ''destroy'',
''xend/restart_count'': ''0'',
''vcpus'': ''2'',
''vcpu_avail'': ''3'',
''bootloader'': '''', ''image'':
''(hvm (kernel ) (videoram 4) (hpet 0) (stdvga 0) (loader
/usr/lib/xen/boot/hvmloader) (serial pty) (vncunused 1) (xen_platform_pci 1)
(boot c) (rtc_timeoffset 0) (pci ()) (pae 1) (vpt_align 1) (hap 1) (viridian 0)
(acpi 1) (localtime 1) (timer_mode 1) (vnc 1) (nographic 0) (guest_os_type
default) (pci_msitranslate 1) (apic 1) (monitor 0) (usbdevice host:0951:1607)
(device_model /usr/lib/xen/bin/qemu-dm) (pci_power_mgmt 0) (usb 1) (xauthority
/root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL 1)))'',
''name'': ''Vista''}
[2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:1622) Storing domain details:
{''console/port'': ''4'',
''name'': ''Vista'',
''console/limit'': ''1048576'',
''store/port'': ''3'', ''vm'':
''/vm/abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
''domid'': ''13'',
''image/suspend-cancel'': ''1'',
''cpu/0/availability'': ''online'',
''memory/target'': ''1048576'',
''control/platform-feature-multiprocessor-suspend'':
''1'', ''store/ring-ref'':
''1044476'', ''cpu/1/availability'':
''online'', ''console/type'':
''ioemu''}
[2009-11-03 11:47:41 5603] DEBUG (DevController:139) Waiting for devices vif.
[2009-11-03 11:47:41 5603] DEBUG (DevController:144) Waiting for 0.
[2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:1709)
XendDomainInfo.handleShutdownWatch
[2009-11-03 11:47:41 5603] DEBUG (DevController:629) hotplugStatusCallback
/local/domain/0/backend/vif/13/0/hotplug-status.
[2009-11-03 11:49:21 5603] WARNING (XendDomain:1048) Failed to setup devices for
<domain id=13 name=Vista memory=1073741824 state=paused>: Device 0 (vif)
could not be connected. Hotplug scripts not working.
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2732) XendDomainInfo.destroy:
domid=13
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2207) Destroying device model
[2009-11-03 11:49:21 5603] INFO (image:556) Vista device model terminated
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2214) Releasing devices
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2227) Removing vif/0
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2227) Removing vbd/768
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2227) Removing vfb/0
[2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2227) Removing console/0
[2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2212) No device model
[2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2214) Releasing devices



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

I''m a bit late in this discussion, so sorry if this idea has already
been axed, but could you buy a PCI card with USB ports and pass it through to
the domU instead of trying to pass through a USB device?
	Dustin

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of James Pifer
Sent: Tuesday, November 03, 2009 12:53
To: xen-users@lists.xensource.com
Cc: space.time.universe@gmail.com; Nick Couchman
Subject: Re: [Xen-users] How do you give USB to a Windows domU?

On Wed, 2009-11-04 at 01:42 +0800, Mr. Teo En Ming (Zhang Enming)
wrote:
> brctl show

You mean while it''s attempting to start? See below.

I could probably get away with centos in a production environment, but
definitely not fedora. SLES10 is our current "standard". Unfortunately
I need usb functionality for a production server, whether that is or is not
recommended.

Thanks,
James


# xm start Vista
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Usage: xm start <DomainName>

Start a Xend managed domain
  -p, --paused                   Do not unpause domain after starting it    
  -c, --console_autoconnect      Connect to the console after the domain    
                                 is created
  --vncviewer                    Connect to display via VNC after the       
                                 domain is created
  --vncviewer-autopass           Pass VNC password to viewer via stdin and  
                                 -autopass



# brctl show
bridge name     bridge id               STP enabled     interfaces
eth4            8000.002655827dd4       no              peth4
                                                        tap13.0




[2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2304)
XendDomainInfo.constructDomain
[2009-11-03 11:47:41 5603] DEBUG (balloon:166) Balloon: 32122132 KiB free; need
4096; done.
[2009-11-03 11:47:41 5603] DEBUG (XendDomain:453) Adding Domain: 13
[2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2505)
XendDomainInfo.initDomain: 13 256
[2009-11-03 11:47:41 5603] DEBUG (image:322) No VNC passwd configured for vfb
access
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: boot, val: c
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: fda, val: None
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: fdb, val: None
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: soundhw, val: None
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: localtime, val: 1
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: serial, val:
[''pty'']
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: std-vga, val: 0
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: isa, val: 0
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: acpi, val: 1
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: usb, val: 1
[2009-11-03 11:47:41 5603] DEBUG (image:813) args: usbdevice, val:
host:0951:1607
[2009-11-03 11:47:41 5603] INFO (image:749) Need to create platform
device.[domid:13]
[2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2529)
_initDomain:shadow_memory=0xa, memory_static_max=0x40000000,
memory_static_min=0x0.
[2009-11-03 11:47:41 5603] DEBUG (balloon:166) Balloon: 32120700 KiB free; need
1067008; done.
[2009-11-03 11:47:41 5603] INFO (image:173) buildDomain os=hvm dom=13 vcpus=2
[2009-11-03 11:47:41 5603] DEBUG (image:866) domid          = 13
[2009-11-03 11:47:41 5603] DEBUG (image:867) image          =
/usr/lib/xen/boot/hvmloader
[2009-11-03 11:47:41 5603] DEBUG (image:868) store_evtchn   = 3
[2009-11-03 11:47:41 5603] DEBUG (image:869) memsize        = 1024
[2009-11-03 11:47:41 5603] DEBUG (image:870) target         = 1024
[2009-11-03 11:47:41 5603] DEBUG (image:871) vcpus          = 2
[2009-11-03 11:47:41 5603] DEBUG (image:872) acpi           = 1
[2009-11-03 11:47:41 5603] DEBUG (image:873) apic           = 1
[2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vfb :
{''vncunused'': 1, ''other_config'':
{''vncunused'': 1, ''vnc'':
''1''}, ''vnc'': ''1'',
''uuid'':
''ecf80d39-153a-f383-f43b-85c6cb4fe3d0'',
''devid'': 0, ''location'':
''127.0.0.1:5900''}
[2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vfb/13/0''} to
/local/domain/13/device/vfb/0.
[2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
{''vncunused'': ''1'',
''domain'': ''Vista'',
''frontend'': ''/local/domain/13/device/vfb/0'',
''uuid'':
''ecf80d39-153a-f383-f43b-85c6cb4fe3d0'',
''frontend-id'': ''13'',
''state'': ''1'', ''location'':
''127.0.0.1:5900'', ''online'':
''1'', ''vnc'': ''1''} to
/local/domain/0/backend/vfb/13/0.
[2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: console :
{''other_config'': {}, ''protocol'':
''vt100'', ''uuid'':
''12f0151f-6f80-887e-ff47-f98302e69222'',
''location'': ''4''}
[2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/console/13/0''} to
/local/domain/13/device/console/0.
[2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
{''domain'': ''Vista'',
''frontend'':
''/local/domain/13/device/console/0'', ''uuid'':
''12f0151f-6f80-887e-ff47-f98302e69222'',
''frontend-id'': ''13'',
''state'': ''1'', ''location'':
''4'', ''online'': ''1'',
''protocol'': ''vt100''} to
/local/domain/0/backend/console/13/0.
[2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vbd :
{''uuid'':
''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': 1, ''devid'': 768,
''driver'': ''paravirtualised'',
''dev'': ''hda'', ''uname'':
''file:/xendata2/images/Vista/disk0'', ''mode'':
''w''}
[2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
{''backend-id'': ''0'',
''virtual-device'': ''768'',
''device-type'': ''disk'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/13/768''} to
/local/domain/13/device/vbd/768.
[2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
{''domain'': ''Vista'',
''frontend'':
''/local/domain/13/device/vbd/768'', ''uuid'':
''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': ''1'', ''dev'':
''hda'', ''state'': ''1'',
''params'': ''/xendata2/images/Vista/disk0'',
''mode'': ''w'', ''online'':
''1'', ''frontend-id'': ''13'',
''type'': ''file''} to
/local/domain/0/backend/vbd/13/768.
[2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vif :
{''bridge'': ''eth4'', ''mac'':
''00:16:3e:1a:45:41'', ''devid'': 0,
''uuid'':
''10b23fcd-acbe-c507-3593-640c6131f533''}
[2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
{''backend-id'': ''0'', ''mac'':
''00:16:3e:1a:45:41'', ''handle'':
''0'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vif/13/0''} to
/local/domain/13/device/vif/0.
[2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
{''bridge'': ''eth4'',
''domain'': ''Vista'',
''handle'': ''0'', ''uuid'':
''10b23fcd-acbe-c507-3593-640c6131f533'',
''script'': ''/etc/xen/scripts/vif-bridge'',
''mac'': ''00:16:3e:1a:45:41'',
''frontend-id'': ''13'',
''state'': ''1'', ''online'':
''1'', ''frontend'':
''/local/domain/13/device/vif/0''} to
/local/domain/0/backend/vif/13/0.
[2009-11-03 11:47:41 5603] INFO (image:394) spawning device models:
/usr/lib/xen/bin/qemu-dm [''/usr/lib/xen/bin/qemu-dm'',
''-d'', ''13'',
''-domain-name'', ''Vista'',
''-videoram'', ''4'', ''-vnc'',
''127.0.0.1:0'', ''-vncunused'',
''-vcpus'', ''2'', ''-boot'',
''c'', ''-localtime'',
''-serial'', ''pty'', ''-acpi'',
''-usb'', ''-usbdevice'',
''host:0951:1607'', ''-net'',
''nic,vlan=1,macaddr=00:16:3e:1a:45:41,model=rtl8139'',
''-net'',
''tap,vlan=1,ifname=tap13.0,bridge=eth4'',
''-M'', ''xenfv'']
[2009-11-03 11:47:41 5603] INFO (image:443) device model pid: 24518
[2009-11-03 11:47:41 5603] INFO (image:531) waiting for sentinel_fifo
[2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:3060) Storing VM details:
{''on_xend_stop'': ''ignore'',
''shadow_memory'': ''10'',
''uuid'':
''abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
''on_reboot'': ''restart'',
''start_time'': ''1257270461.49'',
''on_poweroff'': ''destroy'',
''bootloader_args'': '''',
''on_xend_start'': ''ignore'',
''on_crash'': ''destroy'',
''xend/restart_count'': ''0'',
''vcpus'': ''2'',
''vcpu_avail'': ''3'',
''bootloader'': '''', ''image'':
''(hvm (kernel ) (videoram 4) (hpet 0) (stdvga 0) (loader
/usr/lib/xen/boot/hvmloader) (serial pty) (vncunused 1) (xen_platform_pci 1)
(boot c) (rtc_timeoffset 0) (pci ()) (pae 1) (vpt_align 1) (hap 1) (viridian 0)
(acpi 1) (localtime 1) (timer_mode 1) (vnc 1) (nographic 0) (guest_os_type
default) (pci_msitranslate 1) (apic 1) (monitor 0) (usbdevice host:0951:1607)
(device_model /usr/lib/xen/bin/qemu-dm) (pci_power_mgmt 0) (usb 1) (xauthority
/root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL 1)))'',
''name'': ''Vista''}
[2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:1622) Storing domain details:
{''console/port'': ''4'',
''name'': ''Vista'',
''console/limit'': ''1048576'',
''store/port'': ''3'', ''vm'':
''/vm/abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
''domid'': ''13'',
''image/suspend-cancel'': ''1'',
''cpu/0/availability'': ''online'',
''memory/target'': ''1048576'',
''control/platform-feature-multiprocessor-suspend'':
''1'', ''store/ring-ref'':
''1044476'', ''cpu/1/availability'':
''online'', ''console/type'':
''ioemu''}
[2009-11-03 11:47:41 5603] DEBUG (DevController:139) Waiting for devices vif.
[2009-11-03 11:47:41 5603] DEBUG (DevController:144) Waiting for 0.
[2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:1709)
XendDomainInfo.handleShutdownWatch
[2009-11-03 11:47:41 5603] DEBUG (DevController:629) hotplugStatusCallback
/local/domain/0/backend/vif/13/0/hotplug-status.
[2009-11-03 11:49:21 5603] WARNING (XendDomain:1048) Failed to setup devices for
<domain id=13 name=Vista memory=1073741824 state=paused>: Device 0 (vif)
could not be connected. Hotplug scripts not working.
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2732) XendDomainInfo.destroy:
domid=13
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2207) Destroying device model
[2009-11-03 11:49:21 5603] INFO (image:556) Vista device model terminated
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2214) Releasing devices
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2227) Removing vif/0
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2227) Removing vbd/768
[2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2227) Removing vfb/0
[2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2227) Removing console/0
[2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:1134)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2212) No device model
[2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2214) Releasing devices



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



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

I think eth4 is correct anyway.  eth4 is listed under "bridge name" in
brctl show, I suspect the OP was just having trouble deciphering the output (or
the way the bridge script works).
	Dustin

From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Mr. Teo En Ming
(Zhang Enming)
Sent: Tuesday, November 03, 2009 12:14
To: James Pifer
Cc: space.time.universe@gmail.com; Xen List; Nick Couchman
Subject: Re: [Xen-users] How do you give USB to a Windows domU?

According to brctl show, your ethernet bride is eth4 and not peth4.

Try this:

vif=[ ''mac=00:16:3e:1a:45:41,bridge=eth4'' ]

-- 
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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore
On Wed, Nov 4, 2009 at 12:49 AM, James Pifer <jep@obrien-pifer.com> wrote:
On Tue, 2009-11-03 at 08:59 -0700, Nick Couchman wrote:
> You might need to specify "bridge=<bridgename>" on the
"vif=" line in your config file and point it at a specific bridge.
>
> -Nick
How can I tell what the bridge is called? Is it eth4 or peth4?

brctl show gives me:
bridge name     bridge id               STP enabled     interfaces
eth4            8000.002655827dd4       no              peth4


# ifconfig
eth4      Link encap:Ethernet  HWaddr 00:26:55:82:7D:D4
         inet addr:172.16.4.153  Bcast:10.96.5.255  Mask:255.255.254.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:147511 errors:0 dropped:0 overruns:0 frame:0
         TX packets:121841 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:30694748 (29.2 Mb)  TX bytes:36280012 (34.5 Mb)

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:114 errors:0 dropped:0 overruns:0 frame:0
         TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:6850 (6.6 Kb)  TX bytes:6850 (6.6 Kb)

peth4     Link encap:Ethernet  HWaddr 00:26:55:82:7D:D4
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:147623 errors:0 dropped:0 overruns:0 frame:0
         TX packets:124186 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:33415763 (31.8 Mb)  TX bytes:36952614 (35.2 Mb)
         Interrupt:20 Memory:f8000000-f8012100


I tied this these didn''t work:
vif=[
''bridge=peth4,mac=00:16:3e:1a:45:41,model=rtl8139,type=ioemu'',
]
vif=[
''bridge=eth4,mac=00:16:3e:1a:45:41,model=rtl8139,type=ioemu'',
]

I''d still like to get virt-manager working too, but not sure to go
about
that.

Thanks,
James


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






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

On Tue, 2009-11-03 at 12:55 -0500, Dustin Henning wrote:
> 	I''m a bit late in this discussion, so sorry if this idea has
already
> been axed, but could you buy a PCI card with USB ports and pass it through
> to the domU instead of trying to pass through a USB device?
> 	Dustin
Good idea, but it''s a 1U server with no slots available. 

Thanks,
James



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

Then he needs VT-d for his Windows Vista HVM domU.

-- 
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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore*

*
On Wed, Nov 4, 2009 at 1:56 AM, Dustin Henning
<Dustin.Henning@prd-inc.com>wrote:
>        I''m a bit late in this discussion, so sorry if this idea
has already
> been axed, but could you buy a PCI card with USB ports and pass it through
> to the domU instead of trying to pass through a USB device?
>        Dustin
>
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com [mailto:
> xen-users-bounces@lists.xensource.com] On Behalf Of James Pifer
> Sent: Tuesday, November 03, 2009 12:53
> To: xen-users@lists.xensource.com
> Cc: space.time.universe@gmail.com; Nick Couchman
> Subject: Re: [Xen-users] How do you give USB to a Windows domU?
>
> On Wed, 2009-11-04 at 01:42 +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> > brctl show
>
>
> You mean while it''s attempting to start? See below.
>
> I could probably get away with centos in a production environment, but
> definitely not fedora. SLES10 is our current "standard".
Unfortunately I
> need usb functionality for a production server, whether that is or is not
> recommended.
>
> Thanks,
> James
>
>
> # xm start Vista
> Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
> Usage: xm start <DomainName>
>
> Start a Xend managed domain
>  -p, --paused                   Do not unpause domain after starting it
>  -c, --console_autoconnect      Connect to the console after the domain
>                                 is created
>  --vncviewer                    Connect to display via VNC after the
>                                 domain is created
>  --vncviewer-autopass           Pass VNC password to viewer via stdin and
>                                 -autopass
>
>
>
> # brctl show
> bridge name     bridge id               STP enabled     interfaces
> eth4            8000.002655827dd4       no              peth4
>                                                         tap13.0
>
>
>
>
> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2304)
> XendDomainInfo.constructDomain
> [2009-11-03 11:47:41 5603] DEBUG (balloon:166) Balloon: 32122132 KiB free;
> need 4096; done.
> [2009-11-03 11:47:41 5603] DEBUG (XendDomain:453) Adding Domain: 13
> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2505)
> XendDomainInfo.initDomain: 13 256
> [2009-11-03 11:47:41 5603] DEBUG (image:322) No VNC passwd configured for
> vfb access
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: boot, val: c
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: fda, val: None
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: fdb, val: None
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: soundhw, val: None
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: localtime, val: 1
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: serial, val:
[''pty'']
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: std-vga, val: 0
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: isa, val: 0
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: acpi, val: 1
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: usb, val: 1
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: usbdevice, val:
> host:0951:1607
> [2009-11-03 11:47:41 5603] INFO (image:749) Need to create platform
> device.[domid:13]
> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2529)
> _initDomain:shadow_memory=0xa, memory_static_max=0x40000000,
> memory_static_min=0x0.
> [2009-11-03 11:47:41 5603] DEBUG (balloon:166) Balloon: 32120700 KiB free;
> need 1067008; done.
> [2009-11-03 11:47:41 5603] INFO (image:173) buildDomain os=hvm dom=13
> vcpus=2
> [2009-11-03 11:47:41 5603] DEBUG (image:866) domid          = 13
> [2009-11-03 11:47:41 5603] DEBUG (image:867) image          >
/usr/lib/xen/boot/hvmloader
> [2009-11-03 11:47:41 5603] DEBUG (image:868) store_evtchn   = 3
> [2009-11-03 11:47:41 5603] DEBUG (image:869) memsize        = 1024
> [2009-11-03 11:47:41 5603] DEBUG (image:870) target         = 1024
> [2009-11-03 11:47:41 5603] DEBUG (image:871) vcpus          = 2
> [2009-11-03 11:47:41 5603] DEBUG (image:872) acpi           = 1
> [2009-11-03 11:47:41 5603] DEBUG (image:873) apic           = 1
> [2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vfb :
> {''vncunused'': 1, ''other_config'':
{''vncunused'': 1, ''vnc'':
''1''}, ''vnc'': ''1'',
> ''uuid'':
''ecf80d39-153a-f383-f43b-85c6cb4fe3d0'',
''devid'': 0, ''location'': ''
> 127.0.0.1:5900''}
> [2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
> {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
> ''/local/domain/0/backend/vfb/13/0''} to
/local/domain/13/device/vfb/0.
> [2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
> {''vncunused'': ''1'',
''domain'': ''Vista'',
''frontend'':
> ''/local/domain/13/device/vfb/0'',
''uuid'':
> ''ecf80d39-153a-f383-f43b-85c6cb4fe3d0'',
''frontend-id'': ''13'',
''state'': ''1'',
> ''location'': ''127.0.0.1:5900'',
''online'': ''1'', ''vnc'':
''1''} to
> /local/domain/0/backend/vfb/13/0.
> [2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: console
> : {''other_config'': {}, ''protocol'':
''vt100'', ''uuid'':
> ''12f0151f-6f80-887e-ff47-f98302e69222'',
''location'': ''4''}
> [2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
> {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
> ''/local/domain/0/backend/console/13/0''} to
> /local/domain/13/device/console/0.
> [2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
> {''domain'': ''Vista'',
''frontend'':
''/local/domain/13/device/console/0'', ''uuid'':
> ''12f0151f-6f80-887e-ff47-f98302e69222'',
''frontend-id'': ''13'',
''state'': ''1'',
> ''location'': ''4'',
''online'': ''1'', ''protocol'':
''vt100''} to
> /local/domain/0/backend/console/13/0.
> [2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vbd :
> {''uuid'':
''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': 1, ''devid'':
> 768, ''driver'': ''paravirtualised'',
''dev'': ''hda'', ''uname'':
> ''file:/xendata2/images/Vista/disk0'',
''mode'': ''w''}
> [2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
> {''backend-id'': ''0'',
''virtual-device'': ''768'',
''device-type'': ''disk'',
''state'':
> ''1'', ''backend'':
''/local/domain/0/backend/vbd/13/768''} to
> /local/domain/13/device/vbd/768.
> [2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
> {''domain'': ''Vista'',
''frontend'':
''/local/domain/13/device/vbd/768'', ''uuid'':
> ''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': ''1'', ''dev'':
''hda'',
> ''state'': ''1'',
''params'': ''/xendata2/images/Vista/disk0'',
''mode'': ''w'',
> ''online'': ''1'',
''frontend-id'': ''13'',
''type'': ''file''} to
> /local/domain/0/backend/vbd/13/768.
> [2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vif :
> {''bridge'': ''eth4'',
''mac'': ''00:16:3e:1a:45:41'',
''devid'': 0, ''uuid'':
> ''10b23fcd-acbe-c507-3593-640c6131f533''}
> [2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
> {''backend-id'': ''0'',
''mac'': ''00:16:3e:1a:45:41'',
''handle'': ''0'', ''state'':
''1'',
> ''backend'':
''/local/domain/0/backend/vif/13/0''} to
> /local/domain/13/device/vif/0.
> [2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
> {''bridge'': ''eth4'',
''domain'': ''Vista'',
''handle'': ''0'', ''uuid'':
> ''10b23fcd-acbe-c507-3593-640c6131f533'',
''script'':
> ''/etc/xen/scripts/vif-bridge'', ''mac'':
''00:16:3e:1a:45:41'', ''frontend-id'':
> ''13'', ''state'': ''1'',
''online'': ''1'', ''frontend'':
> ''/local/domain/13/device/vif/0''} to
/local/domain/0/backend/vif/13/0.
> [2009-11-03 11:47:41 5603] INFO (image:394) spawning device models:
> /usr/lib/xen/bin/qemu-dm [''/usr/lib/xen/bin/qemu-dm'',
''-d'', ''13'',
> ''-domain-name'', ''Vista'',
''-videoram'', ''4'', ''-vnc'',
''127.0.0.1:0'',
> ''-vncunused'', ''-vcpus'',
''2'', ''-boot'', ''c'',
''-localtime'', ''-serial'',
''pty'',
> ''-acpi'', ''-usb'',
''-usbdevice'', ''host:0951:1607'',
''-net'',
> ''nic,vlan=1,macaddr=00:16:3e:1a:45:41,model=rtl8139'',
''-net'',
> ''tap,vlan=1,ifname=tap13.0,bridge=eth4'',
''-M'', ''xenfv'']
> [2009-11-03 11:47:41 5603] INFO (image:443) device model pid: 24518
> [2009-11-03 11:47:41 5603] INFO (image:531) waiting for sentinel_fifo
> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:3060) Storing VM details:
> {''on_xend_stop'': ''ignore'',
''shadow_memory'': ''10'',
''uuid'':
> ''abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
''on_reboot'': ''restart'',
> ''start_time'': ''1257270461.49'',
''on_poweroff'': ''destroy'',
''bootloader_args'':
> '''', ''on_xend_start'':
''ignore'', ''on_crash'':
''destroy'', ''xend/restart_count'':
> ''0'', ''vcpus'': ''2'',
''vcpu_avail'': ''3'',
''bootloader'': '''', ''image'':
''(hvm
> (kernel ) (videoram 4) (hpet 0) (stdvga 0) (loader
> /usr/lib/xen/boot/hvmloader) (serial pty) (vncunused 1) (xen_platform_pci
1)
> (boot c) (rtc_timeoffset 0) (pci ()) (pae 1) (vpt_align 1) (hap 1)
(viridian
> 0) (acpi 1) (localtime 1) (timer_mode 1) (vnc 1) (nographic 0)
> (guest_os_type default) (pci_msitranslate 1) (apic 1) (monitor 0)
(usbdevice
> host:0951:1607) (device_model /usr/lib/xen/bin/qemu-dm) (pci_power_mgmt 0)
> (usb 1) (xauthority /root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL
1)))'',
> ''name'': ''Vista''}
> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:1622) Storing domain
> details: {''console/port'': ''4'',
''name'': ''Vista'',
''console/limit'': ''1048576'',
> ''store/port'': ''3'',
''vm'':
''/vm/abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
> ''domid'': ''13'',
''image/suspend-cancel'': ''1'',
''cpu/0/availability'': ''online'',
> ''memory/target'': ''1048576'',
> ''control/platform-feature-multiprocessor-suspend'':
''1'', ''store/ring-ref'':
> ''1044476'', ''cpu/1/availability'':
''online'', ''console/type'':
''ioemu''}
> [2009-11-03 11:47:41 5603] DEBUG (DevController:139) Waiting for devices
> vif.
> [2009-11-03 11:47:41 5603] DEBUG (DevController:144) Waiting for 0.
> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:1709)
> XendDomainInfo.handleShutdownWatch
> [2009-11-03 11:47:41 5603] DEBUG (DevController:629) hotplugStatusCallback
> /local/domain/0/backend/vif/13/0/hotplug-status.
> [2009-11-03 11:49:21 5603] WARNING (XendDomain:1048) Failed to setup
> devices for <domain id=13 name=Vista memory=1073741824 state=paused>:
Device
> 0 (vif) could not be connected. Hotplug scripts not working.
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2732)
> XendDomainInfo.destroy: domid=13
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2207) Destroying device
> model
> [2009-11-03 11:49:21 5603] INFO (image:556) Vista device model terminated
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2214) Releasing devices
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2227) Removing vif/0
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2227) Removing vbd/768
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2227) Removing vfb/0
> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2227) Removing console/0
> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2212) No device model
> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2214) Releasing devices
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

There are no PCI-X or PCI Express riser slots?

-- 
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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore

On Wed, Nov 4, 2009 at 1:59 AM, James Pifer <jep@obrien-pifer.com> wrote:
> On Tue, 2009-11-03 at 12:55 -0500, Dustin Henning wrote:
> >       I''m a bit late in this discussion, so sorry if this
idea has
> already
> > been axed, but could you buy a PCI card with USB ports and pass it
> through
> > to the domU instead of trying to pass through a USB device?
> >       Dustin
>
> Good idea, but it''s a 1U server with no slots available.
>
> Thanks,
> James
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

On Wed, 2009-11-04 at 02:04 +0800, Mr. Teo En Ming (Zhang Enming)
wrote:
> There are no PCI-X or PCI Express riser slots?
> 
One slot being used for SAN connection.

James


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

In your brctl show output, you have tap13.0 added to the eth4 bridge, but
vif13.0 cannot be created and added to the same bridge. So I guess
there''s
something wrong with your Xen networking.

For production environments, you might want to try CentOS or Scientific
Linux.

-- 
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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore

On Wed, Nov 4, 2009 at 1:53 AM, James Pifer <jep@obrien-pifer.com> wrote:
> On Wed, 2009-11-04 at 01:42 +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> > brctl show
>
>
> You mean while it''s attempting to start? See below.
>
> I could probably get away with centos in a production environment, but
> definitely not fedora. SLES10 is our current "standard".
Unfortunately I
> need usb functionality for a production server, whether that is or is
> not recommended.
>
> Thanks,
> James
>
>
> # xm start Vista
> Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
> Usage: xm start <DomainName>
>
> Start a Xend managed domain
>  -p, --paused                   Do not unpause domain after starting it
>  -c, --console_autoconnect      Connect to the console after the domain
>                                 is created
>  --vncviewer                    Connect to display via VNC after the
>                                 domain is created
>  --vncviewer-autopass           Pass VNC password to viewer via stdin and
>                                 -autopass
>
>
>
> # brctl show
> bridge name     bridge id               STP enabled     interfaces
> eth4            8000.002655827dd4       no              peth4
>                                                         tap13.0
>
>
>
>
> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2304)
> XendDomainInfo.constructDomain
> [2009-11-03 11:47:41 5603] DEBUG (balloon:166) Balloon: 32122132 KiB free;
> need 4096; done.
> [2009-11-03 11:47:41 5603] DEBUG (XendDomain:453) Adding Domain: 13
> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2505)
> XendDomainInfo.initDomain: 13 256
> [2009-11-03 11:47:41 5603] DEBUG (image:322) No VNC passwd configured for
> vfb access
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: boot, val: c
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: fda, val: None
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: fdb, val: None
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: soundhw, val: None
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: localtime, val: 1
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: serial, val:
[''pty'']
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: std-vga, val: 0
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: isa, val: 0
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: acpi, val: 1
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: usb, val: 1
> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: usbdevice, val:
> host:0951:1607
> [2009-11-03 11:47:41 5603] INFO (image:749) Need to create platform
> device.[domid:13]
> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2529)
> _initDomain:shadow_memory=0xa, memory_static_max=0x40000000,
> memory_static_min=0x0.
> [2009-11-03 11:47:41 5603] DEBUG (balloon:166) Balloon: 32120700 KiB free;
> need 1067008; done.
> [2009-11-03 11:47:41 5603] INFO (image:173) buildDomain os=hvm dom=13
> vcpus=2
> [2009-11-03 11:47:41 5603] DEBUG (image:866) domid          = 13
> [2009-11-03 11:47:41 5603] DEBUG (image:867) image          >
/usr/lib/xen/boot/hvmloader
> [2009-11-03 11:47:41 5603] DEBUG (image:868) store_evtchn   = 3
> [2009-11-03 11:47:41 5603] DEBUG (image:869) memsize        = 1024
> [2009-11-03 11:47:41 5603] DEBUG (image:870) target         = 1024
> [2009-11-03 11:47:41 5603] DEBUG (image:871) vcpus          = 2
> [2009-11-03 11:47:41 5603] DEBUG (image:872) acpi           = 1
> [2009-11-03 11:47:41 5603] DEBUG (image:873) apic           = 1
> [2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vfb :
> {''vncunused'': 1, ''other_config'':
{''vncunused'': 1, ''vnc'':
''1''}, ''vnc'': ''1'',
> ''uuid'':
''ecf80d39-153a-f383-f43b-85c6cb4fe3d0'',
''devid'': 0, ''location'': ''
> 127.0.0.1:5900''}
> [2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
> {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
> ''/local/domain/0/backend/vfb/13/0''} to
/local/domain/13/device/vfb/0.
> [2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
> {''vncunused'': ''1'',
''domain'': ''Vista'',
''frontend'':
> ''/local/domain/13/device/vfb/0'',
''uuid'':
> ''ecf80d39-153a-f383-f43b-85c6cb4fe3d0'',
''frontend-id'': ''13'',
''state'': ''1'',
> ''location'': ''127.0.0.1:5900'',
''online'': ''1'', ''vnc'':
''1''} to
> /local/domain/0/backend/vfb/13/0.
> [2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: console
> : {''other_config'': {}, ''protocol'':
''vt100'', ''uuid'':
> ''12f0151f-6f80-887e-ff47-f98302e69222'',
''location'': ''4''}
> [2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
> {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
> ''/local/domain/0/backend/console/13/0''} to
> /local/domain/13/device/console/0.
> [2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
> {''domain'': ''Vista'',
''frontend'':
''/local/domain/13/device/console/0'', ''uuid'':
> ''12f0151f-6f80-887e-ff47-f98302e69222'',
''frontend-id'': ''13'',
''state'': ''1'',
> ''location'': ''4'',
''online'': ''1'', ''protocol'':
''vt100''} to
> /local/domain/0/backend/console/13/0.
> [2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vbd :
> {''uuid'':
''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': 1, ''devid'':
> 768, ''driver'': ''paravirtualised'',
''dev'': ''hda'', ''uname'':
> ''file:/xendata2/images/Vista/disk0'',
''mode'': ''w''}
> [2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
> {''backend-id'': ''0'',
''virtual-device'': ''768'',
''device-type'': ''disk'',
''state'':
> ''1'', ''backend'':
''/local/domain/0/backend/vbd/13/768''} to
> /local/domain/13/device/vbd/768.
> [2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
> {''domain'': ''Vista'',
''frontend'':
''/local/domain/13/device/vbd/768'', ''uuid'':
> ''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': ''1'', ''dev'':
''hda'',
> ''state'': ''1'',
''params'': ''/xendata2/images/Vista/disk0'',
''mode'': ''w'',
> ''online'': ''1'',
''frontend-id'': ''13'',
''type'': ''file''} to
> /local/domain/0/backend/vbd/13/768.
> [2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vif :
> {''bridge'': ''eth4'',
''mac'': ''00:16:3e:1a:45:41'',
''devid'': 0, ''uuid'':
> ''10b23fcd-acbe-c507-3593-640c6131f533''}
> [2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController: writing
> {''backend-id'': ''0'',
''mac'': ''00:16:3e:1a:45:41'',
''handle'': ''0'', ''state'':
''1'',
> ''backend'':
''/local/domain/0/backend/vif/13/0''} to
> /local/domain/13/device/vif/0.
> [2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController: writing
> {''bridge'': ''eth4'',
''domain'': ''Vista'',
''handle'': ''0'', ''uuid'':
> ''10b23fcd-acbe-c507-3593-640c6131f533'',
''script'':
> ''/etc/xen/scripts/vif-bridge'', ''mac'':
''00:16:3e:1a:45:41'', ''frontend-id'':
> ''13'', ''state'': ''1'',
''online'': ''1'', ''frontend'':
> ''/local/domain/13/device/vif/0''} to
/local/domain/0/backend/vif/13/0.
> [2009-11-03 11:47:41 5603] INFO (image:394) spawning device models:
> /usr/lib/xen/bin/qemu-dm [''/usr/lib/xen/bin/qemu-dm'',
''-d'', ''13'',
> ''-domain-name'', ''Vista'',
''-videoram'', ''4'', ''-vnc'',
''127.0.0.1:0'',
> ''-vncunused'', ''-vcpus'',
''2'', ''-boot'', ''c'',
''-localtime'', ''-serial'',
''pty'',
> ''-acpi'', ''-usb'',
''-usbdevice'', ''host:0951:1607'',
''-net'',
> ''nic,vlan=1,macaddr=00:16:3e:1a:45:41,model=rtl8139'',
''-net'',
> ''tap,vlan=1,ifname=tap13.0,bridge=eth4'',
''-M'', ''xenfv'']
> [2009-11-03 11:47:41 5603] INFO (image:443) device model pid: 24518
> [2009-11-03 11:47:41 5603] INFO (image:531) waiting for sentinel_fifo
> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:3060) Storing VM details:
> {''on_xend_stop'': ''ignore'',
''shadow_memory'': ''10'',
''uuid'':
> ''abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
''on_reboot'': ''restart'',
> ''start_time'': ''1257270461.49'',
''on_poweroff'': ''destroy'',
''bootloader_args'':
> '''', ''on_xend_start'':
''ignore'', ''on_crash'':
''destroy'', ''xend/restart_count'':
> ''0'', ''vcpus'': ''2'',
''vcpu_avail'': ''3'',
''bootloader'': '''', ''image'':
''(hvm
> (kernel ) (videoram 4) (hpet 0) (stdvga 0) (loader
> /usr/lib/xen/boot/hvmloader) (serial pty) (vncunused 1) (xen_platform_pci
1)
> (boot c) (rtc_timeoffset 0) (pci ()) (pae 1) (vpt_align 1) (hap 1)
(viridian
> 0) (acpi 1) (localtime 1) (timer_mode 1) (vnc 1) (nographic 0)
> (guest_os_type default) (pci_msitranslate 1) (apic 1) (monitor 0)
(usbdevice
> host:0951:1607) (device_model /usr/lib/xen/bin/qemu-dm) (pci_power_mgmt 0)
> (usb 1) (xauthority /root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL
1)))'',
> ''name'': ''Vista''}
> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:1622) Storing domain
> details: {''console/port'': ''4'',
''name'': ''Vista'',
''console/limit'': ''1048576'',
> ''store/port'': ''3'',
''vm'':
''/vm/abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
> ''domid'': ''13'',
''image/suspend-cancel'': ''1'',
''cpu/0/availability'': ''online'',
> ''memory/target'': ''1048576'',
> ''control/platform-feature-multiprocessor-suspend'':
''1'', ''store/ring-ref'':
> ''1044476'', ''cpu/1/availability'':
''online'', ''console/type'':
''ioemu''}
> [2009-11-03 11:47:41 5603] DEBUG (DevController:139) Waiting for devices
> vif.
> [2009-11-03 11:47:41 5603] DEBUG (DevController:144) Waiting for 0.
> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:1709)
> XendDomainInfo.handleShutdownWatch
> [2009-11-03 11:47:41 5603] DEBUG (DevController:629) hotplugStatusCallback
> /local/domain/0/backend/vif/13/0/hotplug-status.
> [2009-11-03 11:49:21 5603] WARNING (XendDomain:1048) Failed to setup
> devices for <domain id=13 name=Vista memory=1073741824 state=paused>:
Device
> 0 (vif) could not be connected. Hotplug scripts not working.
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2732)
> XendDomainInfo.destroy: domid=13
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2207) Destroying device
> model
> [2009-11-03 11:49:21 5603] INFO (image:556) Vista device model terminated
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2214) Releasing devices
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2227) Removing vif/0
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2227) Removing vbd/768
> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2227) Removing vfb/0
> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2227) Removing console/0
> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2212) No device model
> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2214) Releasing devices
>
>
>

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

On Wed, 2009-11-04 at 02:03 +0800, Mr. Teo En Ming (Zhang Enming)
wrote:
> Then he needs VT-d for his Windows Vista HVM domU.
> 
Not sure how you jumped to hear. VT-d is should already be enabled. 

James


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

If you start a virtual machine with only one virtual network card, you will
see tap<domID>.0 and vif<domID>.0 created and inserted into the xen
bridge
eth4. In your case, your Windows Vista is domain ID 13. So you should get
tap13.0 and vif13.0. But in your case, vif13.0 cannot be created.

-- 
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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore

On Wed, Nov 4, 2009 at 2:14 AM, Mr. Teo En Ming (Zhang Enming) <
space.time.universe@gmail.com> wrote:
> In your brctl show output, you have tap13.0 added to the eth4 bridge, but
> vif13.0 cannot be created and added to the same bridge. So I guess
there''s
> something wrong with your Xen networking.
>
> For production environments, you might want to try CentOS or Scientific
> Linux.
>
>
> --
> 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@gmail.com
> Mobile Phone (Starhub Prepaid): +65-8369-2618
> Street: Bedok Reservoir Road
> Country: Singapore
>
> On Wed, Nov 4, 2009 at 1:53 AM, James Pifer <jep@obrien-pifer.com>
wrote:
>
>> On Wed, 2009-11-04 at 01:42 +0800, Mr. Teo En Ming (Zhang Enming)
wrote:
>> > brctl show
>>
>>
>> You mean while it''s attempting to start? See below.
>>
>> I could probably get away with centos in a production environment, but
>> definitely not fedora. SLES10 is our current "standard".
Unfortunately I
>> need usb functionality for a production server, whether that is or is
>> not recommended.
>>
>> Thanks,
>> James
>>
>>
>> # xm start Vista
>> Error: Device 0 (vif) could not be connected. Hotplug scripts not
working.
>> Usage: xm start <DomainName>
>>
>> Start a Xend managed domain
>>  -p, --paused                   Do not unpause domain after starting it
>>  -c, --console_autoconnect      Connect to the console after the domain
>>                                 is created
>>  --vncviewer                    Connect to display via VNC after the
>>                                 domain is created
>>  --vncviewer-autopass           Pass VNC password to viewer via stdin
and
>>                                 -autopass
>>
>>
>>
>> # brctl show
>> bridge name     bridge id               STP enabled     interfaces
>> eth4            8000.002655827dd4       no              peth4
>>                                                         tap13.0
>>
>>
>>
>>
>> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2304)
>> XendDomainInfo.constructDomain
>> [2009-11-03 11:47:41 5603] DEBUG (balloon:166) Balloon: 32122132 KiB
free;
>> need 4096; done.
>> [2009-11-03 11:47:41 5603] DEBUG (XendDomain:453) Adding Domain: 13
>> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2505)
>> XendDomainInfo.initDomain: 13 256
>> [2009-11-03 11:47:41 5603] DEBUG (image:322) No VNC passwd configured
for
>> vfb access
>> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: boot, val: c
>> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: fda, val: None
>> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: fdb, val: None
>> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: soundhw, val: None
>> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: localtime, val: 1
>> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: serial, val:
[''pty'']
>> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: std-vga, val: 0
>> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: isa, val: 0
>> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: acpi, val: 1
>> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: usb, val: 1
>> [2009-11-03 11:47:41 5603] DEBUG (image:813) args: usbdevice, val:
>> host:0951:1607
>> [2009-11-03 11:47:41 5603] INFO (image:749) Need to create platform
>> device.[domid:13]
>> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:2529)
>> _initDomain:shadow_memory=0xa, memory_static_max=0x40000000,
>> memory_static_min=0x0.
>> [2009-11-03 11:47:41 5603] DEBUG (balloon:166) Balloon: 32120700 KiB
free;
>> need 1067008; done.
>> [2009-11-03 11:47:41 5603] INFO (image:173) buildDomain os=hvm dom=13
>> vcpus=2
>> [2009-11-03 11:47:41 5603] DEBUG (image:866) domid          = 13
>> [2009-11-03 11:47:41 5603] DEBUG (image:867) image          >>
/usr/lib/xen/boot/hvmloader
>> [2009-11-03 11:47:41 5603] DEBUG (image:868) store_evtchn   = 3
>> [2009-11-03 11:47:41 5603] DEBUG (image:869) memsize        = 1024
>> [2009-11-03 11:47:41 5603] DEBUG (image:870) target         = 1024
>> [2009-11-03 11:47:41 5603] DEBUG (image:871) vcpus          = 2
>> [2009-11-03 11:47:41 5603] DEBUG (image:872) acpi           = 1
>> [2009-11-03 11:47:41 5603] DEBUG (image:873) apic           = 1
>> [2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vfb
:
>> {''vncunused'': 1, ''other_config'':
{''vncunused'': 1, ''vnc'':
''1''}, ''vnc'': ''1'',
>> ''uuid'':
''ecf80d39-153a-f383-f43b-85c6cb4fe3d0'',
''devid'': 0, ''location'': ''
>> 127.0.0.1:5900''}
>> [2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController:
writing
>> {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
>> ''/local/domain/0/backend/vfb/13/0''} to
/local/domain/13/device/vfb/0.
>> [2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController:
writing
>> {''vncunused'': ''1'',
''domain'': ''Vista'',
''frontend'':
>> ''/local/domain/13/device/vfb/0'',
''uuid'':
>> ''ecf80d39-153a-f383-f43b-85c6cb4fe3d0'',
''frontend-id'': ''13'',
''state'': ''1'',
>> ''location'': ''127.0.0.1:5900'',
''online'': ''1'', ''vnc'':
''1''} to
>> /local/domain/0/backend/vfb/13/0.
>> [2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice:
>> console : {''other_config'': {},
''protocol'': ''vt100'',
''uuid'':
>> ''12f0151f-6f80-887e-ff47-f98302e69222'',
''location'': ''4''}
>> [2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController:
writing
>> {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
>> ''/local/domain/0/backend/console/13/0''} to
>> /local/domain/13/device/console/0.
>> [2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController:
writing
>> {''domain'': ''Vista'',
''frontend'':
''/local/domain/13/device/console/0'', ''uuid'':
>> ''12f0151f-6f80-887e-ff47-f98302e69222'',
''frontend-id'': ''13'',
''state'': ''1'',
>> ''location'': ''4'',
''online'': ''1'', ''protocol'':
''vt100''} to
>> /local/domain/0/backend/console/13/0.
>> [2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vbd
:
>> {''uuid'':
''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': 1, ''devid'':
>> 768, ''driver'': ''paravirtualised'',
''dev'': ''hda'', ''uname'':
>> ''file:/xendata2/images/Vista/disk0'',
''mode'': ''w''}
>> [2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController:
writing
>> {''backend-id'': ''0'',
''virtual-device'': ''768'',
''device-type'': ''disk'',
''state'':
>> ''1'', ''backend'':
''/local/domain/0/backend/vbd/13/768''} to
>> /local/domain/13/device/vbd/768.
>> [2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController:
writing
>> {''domain'': ''Vista'',
''frontend'':
''/local/domain/13/device/vbd/768'', ''uuid'':
>> ''bb26be09-2e6d-602a-9d6c-98f7aa8d1b5f'',
''bootable'': ''1'', ''dev'':
''hda'',
>> ''state'': ''1'',
''params'': ''/xendata2/images/Vista/disk0'',
''mode'': ''w'',
>> ''online'': ''1'',
''frontend-id'': ''13'',
''type'': ''file''} to
>> /local/domain/0/backend/vbd/13/768.
>> [2009-11-03 11:47:41 5603] INFO (XendDomainInfo:2168) createDevice: vif
:
>> {''bridge'': ''eth4'',
''mac'': ''00:16:3e:1a:45:41'',
''devid'': 0, ''uuid'':
>> ''10b23fcd-acbe-c507-3593-640c6131f533''}
>> [2009-11-03 11:47:41 5603] DEBUG (DevController:95) DevController:
writing
>> {''backend-id'': ''0'',
''mac'': ''00:16:3e:1a:45:41'',
''handle'': ''0'', ''state'':
''1'',
>> ''backend'':
''/local/domain/0/backend/vif/13/0''} to
>> /local/domain/13/device/vif/0.
>> [2009-11-03 11:47:41 5603] DEBUG (DevController:97) DevController:
writing
>> {''bridge'': ''eth4'',
''domain'': ''Vista'',
''handle'': ''0'', ''uuid'':
>> ''10b23fcd-acbe-c507-3593-640c6131f533'',
''script'':
>> ''/etc/xen/scripts/vif-bridge'',
''mac'': ''00:16:3e:1a:45:41'',
''frontend-id'':
>> ''13'', ''state'':
''1'', ''online'': ''1'',
''frontend'':
>> ''/local/domain/13/device/vif/0''} to
/local/domain/0/backend/vif/13/0.
>> [2009-11-03 11:47:41 5603] INFO (image:394) spawning device models:
>> /usr/lib/xen/bin/qemu-dm [''/usr/lib/xen/bin/qemu-dm'',
''-d'', ''13'',
>> ''-domain-name'', ''Vista'',
''-videoram'', ''4'', ''-vnc'',
''127.0.0.1:0'',
>> ''-vncunused'', ''-vcpus'',
''2'', ''-boot'', ''c'',
''-localtime'', ''-serial'',
''pty'',
>> ''-acpi'', ''-usb'',
''-usbdevice'', ''host:0951:1607'',
''-net'',
>> ''nic,vlan=1,macaddr=00:16:3e:1a:45:41,model=rtl8139'',
''-net'',
>> ''tap,vlan=1,ifname=tap13.0,bridge=eth4'',
''-M'', ''xenfv'']
>> [2009-11-03 11:47:41 5603] INFO (image:443) device model pid: 24518
>> [2009-11-03 11:47:41 5603] INFO (image:531) waiting for sentinel_fifo
>> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:3060) Storing VM
details:
>> {''on_xend_stop'': ''ignore'',
''shadow_memory'': ''10'',
''uuid'':
>> ''abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
''on_reboot'': ''restart'',
>> ''start_time'': ''1257270461.49'',
''on_poweroff'': ''destroy'',
''bootloader_args'':
>> '''', ''on_xend_start'':
''ignore'', ''on_crash'':
''destroy'', ''xend/restart_count'':
>> ''0'', ''vcpus'':
''2'', ''vcpu_avail'': ''3'',
''bootloader'': '''', ''image'':
''(hvm
>> (kernel ) (videoram 4) (hpet 0) (stdvga 0) (loader
>> /usr/lib/xen/boot/hvmloader) (serial pty) (vncunused 1)
(xen_platform_pci 1)
>> (boot c) (rtc_timeoffset 0) (pci ()) (pae 1) (vpt_align 1) (hap 1)
(viridian
>> 0) (acpi 1) (localtime 1) (timer_mode 1) (vnc 1) (nographic 0)
>> (guest_os_type default) (pci_msitranslate 1) (apic 1) (monitor 0)
(usbdevice
>> host:0951:1607) (device_model /usr/lib/xen/bin/qemu-dm) (pci_power_mgmt
0)
>> (usb 1) (xauthority /root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL
1)))'',
>> ''name'': ''Vista''}
>> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:1622) Storing domain
>> details: {''console/port'': ''4'',
''name'': ''Vista'',
''console/limit'': ''1048576'',
>> ''store/port'': ''3'',
''vm'':
''/vm/abf38e32-96d7-dcdd-ac1c-76a0c62adc1b'',
>> ''domid'': ''13'',
''image/suspend-cancel'': ''1'',
''cpu/0/availability'': ''online'',
>> ''memory/target'': ''1048576'',
>> ''control/platform-feature-multiprocessor-suspend'':
''1'', ''store/ring-ref'':
>> ''1044476'', ''cpu/1/availability'':
''online'', ''console/type'':
''ioemu''}
>> [2009-11-03 11:47:41 5603] DEBUG (DevController:139) Waiting for
devices
>> vif.
>> [2009-11-03 11:47:41 5603] DEBUG (DevController:144) Waiting for 0.
>> [2009-11-03 11:47:41 5603] DEBUG (XendDomainInfo:1709)
>> XendDomainInfo.handleShutdownWatch
>> [2009-11-03 11:47:41 5603] DEBUG (DevController:629)
hotplugStatusCallback
>> /local/domain/0/backend/vif/13/0/hotplug-status.
>> [2009-11-03 11:49:21 5603] WARNING (XendDomain:1048) Failed to setup
>> devices for <domain id=13 name=Vista memory=1073741824
state=paused>: Device
>> 0 (vif) could not be connected. Hotplug scripts not working.
>> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2732)
>> XendDomainInfo.destroy: domid=13
>> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2207) Destroying
device
>> model
>> [2009-11-03 11:49:21 5603] INFO (image:556) Vista device model
terminated
>> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2214) Releasing
devices
>> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2227) Removing vif/0
>> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:1134)
>> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
>> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:2227) Removing vbd/768
>> [2009-11-03 11:49:21 5603] DEBUG (XendDomainInfo:1134)
>> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
>> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2227) Removing vfb/0
>> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:1134)
>> XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
>> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2227) Removing
console/0
>> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:1134)
>> XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
>> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2212) No device model
>> [2009-11-03 11:49:22 5603] DEBUG (XendDomainInfo:2214) Releasing
devices
>>
>>
>>
>
>
>

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

For Windows HVM guests, you only need VT. If you want to pass through a PCI
device to HVM guests, you need VT-d. I don''t think you need VT-d to
passthrough a usb device to Windows virtual machines.

-- 
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@gmail.com
Mobile Phone (Starhub Prepaid): +65-8369-2618
Street: Bedok Reservoir Road
Country: Singapore

On Wed, Nov 4, 2009 at 2:16 AM, James Pifer <jep@obrien-pifer.com> wrote:
> On Wed, 2009-11-04 at 02:03 +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> > Then he needs VT-d for his Windows Vista HVM domU.
> >
>
> Not sure how you jumped to hear. VT-d is should already be enabled.
>
> James
>
>

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

On 02/11/2009 19:01, 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.
>
Sorry to come a bit late in the story but I am running 3.2 and usb_add 
is working. I use it to enable the tablet on a W2K8 server as I need a 
usb dongle to be connected.
> -Nick
>
>>>> On 2009/11/02 at 08:53, "Mr. Teo En Ming (Zhang
Enming)"
> <space.time.universe@gmail.com>  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.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

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



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

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

On Mon, 2009-11-09 at 14:01 -0700, Nick Couchman wrote:
> 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
> 

Could it be one of these libraries that also need to be updated? Some are still
3.3.
sles-xen_en-pdf-11.1-16.1
xen-3.4.1_19718_04-26.2
xen-doc-html-3.3.1_18546_12-3.1
xen-tools-3.3.1_18546_12-3.1
ocfs2-kmp-xen-1.4_2.6.27.19_5-4.35
xen-doc-pdf-3.3.1_18546_12-3.1
kernel-xen-base-2.6.27.19-5.1
kernel-xen-2.6.27.19-5.1
xen-libs-3.3.1_18546_12-3.1



Here''s the log:
# cat qemu-dm-Vista.log
domid: 3
qemu: the number of cpus is 2
config qemu network with xen bridge for  tap3.0 br0
Watching /local/domain/0/device-model/3/logdirty/next-active
Watching /local/domain/0/device-model/3/command
xs_read(): vncpasswd get error.
/vm/abf38e32-96d7-dcdd-ac1c-76a0c62adc1b/vncpasswd.
char device redirected to /dev/pts/2
qemu_map_cache_init nr_buckets = 10000 size 3145728
/usr/src/packages/BUILD/xen-3.3.1-testing/tools/ioemu-dir/hw/xen_blktap.c:713:
Init blktap pipes
shared page at pfn 3fffe
buffered io page at pfn 3fffc
Time offset set -21600
Register xen platform.
Done register platform.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
gpe_sts_write: addr=0x1f68, val=0x0.
gpe_sts_write: addr=0x1f69, val=0x0.
gpe_sts_write: addr=0x1f6a, val=0x0.
gpe_sts_write: addr=0x1f6b, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x0.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x0.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_sts_write: addr=0x1f68, val=0x0.
gpe_sts_write: addr=0x1f69, val=0x0.
gpe_sts_write: addr=0x1f6a, val=0x0.
gpe_sts_write: addr=0x1f6b, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x8.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.


James




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

On Mon, 2009-11-09 at 16:24 -0500, James Pifer wrote:
> On Mon, 2009-11-09 at 14:01 -0700, Nick Couchman wrote:
> > 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
> > 
> 
> 
> Could it be one of these libraries that also need to be updated? Some are
still 3.3.
> sles-xen_en-pdf-11.1-16.1
> xen-3.4.1_19718_04-26.2
> xen-doc-html-3.3.1_18546_12-3.1
> xen-tools-3.3.1_18546_12-3.1
> ocfs2-kmp-xen-1.4_2.6.27.19_5-4.35
> xen-doc-pdf-3.3.1_18546_12-3.1
> kernel-xen-base-2.6.27.19-5.1
> kernel-xen-2.6.27.19-5.1
> xen-libs-3.3.1_18546_12-3.1
> 
I updated xen-tools and xen-libs to 3.4.1 and I seem to have taken a
step backward. When I try to do anything with the Vista domU from
virt-manager, virt-manager crashes. I ran virt-manager from a console
window and no messages come back. 

I also tried removing and re-adding the Vista domU through virt-manager
and I can add it, but it still bombs when I do anything. I''ll have to
see if there''s an update to virt-manager/virt-libs. 

The good news is that the domU does load. I can connect to it using xm
vncviewer domU and i can remote desktop to it. 

The bad news is the USB drive still doesn''t work. Nothing in the log
that I can see. 

Thanks,
James


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

James,

I had a similar problem on openSUSE 11.1 the solution was to adjust the 
below.

in /etc/fstab
#usbfs                /proc/bus/usb        usbfs      
noauto                0 0
/sys/bus/usb/drivers /proc/bus/usb        usbfs      
devgid=0,devmode=664  0 0

After this a "mount -a" and create en start you domain newly and see
if
there is any improvement.

mfg,
jeroen

James Pifer wrote:
> On Mon, 2009-11-09 at 16:24 -0500, James Pifer wrote:
>   
>> On Mon, 2009-11-09 at 14:01 -0700, Nick Couchman wrote:
>>     
>>> 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
>>>
>>>       
>> 
>> Could it be one of these libraries that also need to be updated? Some
are still 3.3.
>> sles-xen_en-pdf-11.1-16.1
>> xen-3.4.1_19718_04-26.2
>> xen-doc-html-3.3.1_18546_12-3.1
>> xen-tools-3.3.1_18546_12-3.1
>> ocfs2-kmp-xen-1.4_2.6.27.19_5-4.35
>> xen-doc-pdf-3.3.1_18546_12-3.1
>> kernel-xen-base-2.6.27.19-5.1
>> kernel-xen-2.6.27.19-5.1
>> xen-libs-3.3.1_18546_12-3.1
>>
>>     
>
> I updated xen-tools and xen-libs to 3.4.1 and I seem to have taken a
> step backward. When I try to do anything with the Vista domU from
> virt-manager, virt-manager crashes. I ran virt-manager from a console
> window and no messages come back. 
>
> I also tried removing and re-adding the Vista domU through virt-manager
> and I can add it, but it still bombs when I do anything. I''ll have
to
> see if there''s an update to virt-manager/virt-libs. 
>
> The good news is that the domU does load. I can connect to it using xm
> vncviewer domU and i can remote desktop to it. 
>
> The bad news is the USB drive still doesn''t work. Nothing in the
log
> that I can see. 
>
> Thanks,
> James
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>   


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

On Tue, 2009-11-10 at 08:53 +0100, Jeroen Groenewegen van der Weyden
wrote:
> James,
> 
> I had a similar problem on openSUSE 11.1 the solution was to adjust
> the below.
> 
> in /etc/fstab
> #usbfs                /proc/bus/usb        usbfs      noauto
> 0 0
> /sys/bus/usb/drivers /proc/bus/usb        usbfs
> devgid=0,devmode=664  0 0
> 
> After this a "mount -a" and create en start you domain newly and
see
> if there is any improvement.
> 
What does the "mount -a" do? Unfortunately this did not change
anything.
I still cannot see the usb device in the Vista domU. I restarted the
server, deleted and recreated the domU. 

Shouldn''t the usb device be listed in the xenstore? It''s not
currently.
See below. 

Thanks,
James

# xm list -l Vista
(domain
    (domid 2)
    (bootloader )
    (on_crash destroy)
    (uuid e966ca8a-de85-accf-d9c3-1a15c3de0a7e)
    (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 1257861152.96)
    (cpu_time 82.084100073)
    (online_vcpus 2)
    (image
        (hvm
            (kernel )
            (videoram 4)
            (hpet 0)
            (stdvga 0)
            (loader /usr/lib/xen/boot/hvmloader)
            (monitor 0)
            (rtc_timeoffset 0)
            (pci ())
            (hap 1)
            (localtime 1)
            (timer_mode 1)
            (pci_msitranslate 1)
            (apic 1)
            (usbdevice tablet)
            (vpt_align 1)
            (extid 0)
            (serial pty)
            (vncunused 1)
            (boot c)
            (xen_platform_pci 1)
            (pae 1)
            (viridian 0)
            (acpi 1)
            (vnc 1)
            (nographic 0)
            (usb 1)
            (guest_os_type default)
            (device_model /usr/lib/xen/bin/qemu-dm)
            (keymap en-us)
            (pci_power_mgmt 0)
            (xauthority /root/.Xauthority)
            (isa 0)
            (notes (SUSPEND_CANCEL 1))
        )
    )
    (status 2)
    (state -b----)
    (store_mfn 1044476)
    (device
        (vif
            (bridge br0)
            (uuid 42ec763c-c202-2b41-59c9-bf56ab53a719)
            (script /etc/xen/scripts/vif-bridge)
            (mac 00:16:3e:5b:bc:c3)
            (model rtl8139)
            (backend 0)
        )
    )
    (device
        (console
            (protocol vt100)
            (location 4)
            (uuid 4277ecac-3423-2e91-4833-fd50d5582d18)
        )
    )
    (device
        (vbd
            (uuid 1ebfa3f5-216c-65cf-c239-d6f8cf9b9846)
            (bootable 1)
            (dev hda:disk)
            (uname file:/xendata2/images/Vista/disk0)
            (mode w)
            (backend 0)
            (bootable 1)
            (VDI )
        )
    )
    (device
        (vfb
            (vncunused 1)
            (vnc 1)
            (uuid afc9fb25-26d9-b210-85e4-7d8dd1f1f5e9)
            (location 127.0.0.1:5900)
        )
    )
)



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

On Mon, 2009-11-09 at 16:24 -0500, James Pifer wrote:
> On Mon, 2009-11-09 at 14:01 -0700, Nick Couchman wrote:
> > 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
> > 
> 
> 
> Could it be one of these libraries that also need to be updated? Some are
still 3.3.
> sles-xen_en-pdf-11.1-16.1
> xen-3.4.1_19718_04-26.2
> xen-doc-html-3.3.1_18546_12-3.1
> xen-tools-3.3.1_18546_12-3.1
> ocfs2-kmp-xen-1.4_2.6.27.19_5-4.35
> xen-doc-pdf-3.3.1_18546_12-3.1
> kernel-xen-base-2.6.27.19-5.1
> kernel-xen-2.6.27.19-5.1
> xen-libs-3.3.1_18546_12-3.1
> 
I updated virt-manager and libvirt packages and now virt-manager seems
stable. 

James


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

On Tue, 2009-11-10 at 15:36 +0100, Jeroen Groenewegen van der Weyden
wrote:
> can you sent the output of "mount"
> 
> 
Here it is. 

 # mount
/dev/sda2 on / type ext3 (rw,acl,user_xattr)
/proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
securityfs on /sys/kernel/security type securityfs (rw)
configfs on /sys/kernel/config type configfs (rw)
ocfs2_dlmfs on /dlm type ocfs2_dlmfs (rw)
/dev/sdb on /xendata type ocfs2 (rw,_netdev,heartbeat=local)
/dev/sdc on /xendata2 type ocfs2 (rw,_netdev,heartbeat=local)
gvfs-fuse-daemon on /root/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev)
/dev/sdd1 on /media/KINGSTON type vfat
(rw,nosuid,nodev,shortname=lower,flush,utf8,uid=0)
/dev/sr0 on /media/SUSE_SLES-11-0-0.001 type iso9660 (ro,nosuid,nodev,uid=0)
/sys/bus/usb/drivers on /proc/bus/usb type usbfs (rw,devgid=0,devmode=664)



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

On Tue, 2009-11-10 at 16:32 +0100, Jeroen Groenewegen van der Weyden
wrote:
> ok, that looks the same as on my openSUSE 11.1
> 
> This change did it for me, creating a domain from this point made the
> usb device showup in the domU.
> an onther thing I noticed is that not als usb devices let them self
> being handle like this. most device usb stick etc work. but most usb
> dongle won''t work like this.
> can you sent the /var/log/xen/qemu<domain>.log there from a domain
> created from this point. don''t reboot the domain do xm
> delete /(new/create).
> 
Wouldn''t I need to reboot for changes to fstab to take affect?

Log is below. The new versions of virt-manager give you the option of
adding a physical hardware device in the domU. I''ve tried removing the
"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".

# cat qemu-dm-Vista.log
domid: 3
qemu: the number of cpus is 2
config qemu network with xen bridge for  tap3.0 br0
Watching /local/domain/0/device-model/3/logdirty/next-active
Watching /local/domain/0/device-model/3/command
char device redirected to /dev/pts/1
qemu_map_cache_init nr_buckets = 10000 size 4194304
/usr/src/packages/BUILD/xen-3.4.1-testing/tools/ioemu-dir/hw/xen_blktap.c:715:
Init blktap pipes
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = e966ca8a-de85-accf-d9c3-1a15c3de0a7e
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
xs_read(/vm/e966ca8a-de85-accf-d9c3-1a15c3de0a7e/log-throttling): read error
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/3/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error.
/vm/e966ca8a-de85-accf-d9c3-1a15c3de0a7e/vncpasswd.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.
gpe_sts_write: addr=0x1f68, val=0x0.
gpe_sts_write: addr=0x1f69, val=0x0.
gpe_sts_write: addr=0x1f6a, val=0x0.
gpe_sts_write: addr=0x1f6b, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x0.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x0.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_sts_write: addr=0x1f68, val=0x0.
gpe_sts_write: addr=0x1f69, val=0x0.
gpe_sts_write: addr=0x1f6a, val=0x0.
gpe_sts_write: addr=0x1f6b, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x8.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x8.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x8.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x0.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.

Thanks,
James


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

> Log is below. The new versions of virt-manager give you the option of
> adding a physical hardware device in the domU. I''ve tried removing
the
> "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".
> 
Anyone have any ideas? I''m stuck....

Thanks,
James


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

You did do "xm delete domU && xm new /path/to/config/file"
after upgrading to the newer version of Xen??
>>> On 2009/11/10 at 13:14, James Pifer <jep@obrien-pifer.com>
wrote:
>>  Log is below. The new versions of virt-manager give you the option of
>> adding a physical hardware device in the domU. I''ve tried
removing the
>> "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".
>> 
> 
> Anyone have any ideas? I''m stuck....
> 
> 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@lists.xensource.com
http://lists.xensource.com/xen-users

On Tue, 2009-11-10 at 15:36 -0700, Nick Couchman wrote:
> You did do "xm delete domU && xm new
/path/to/config/file" after upgrading to the newer version of Xen??
> 
Yep.

Thanks,
James



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

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

On Wed, 2009-11-11 at 18:23 +0100, Jeroen Groenewegen van der Weyden
wrote:
> The /var/log/messages should have somekind of a qemu entry, can you
> mail this to
> 
I grepped /var/log/messages and got nothing for qemu. I tailed messages
while deleting and adding the domU, as well as starting it, nothing for
qemu. 

James


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

On Wed, 2009-11-11 at 13:52 -0500, James Pifer wrote:
> On Wed, 2009-11-11 at 18:23 +0100, Jeroen Groenewegen van der Weyden
> wrote:
> > The /var/log/messages should have somekind of a qemu entry, can you
> > mail this to
> > 
> 
> I grepped /var/log/messages and got nothing for qemu. I tailed messages
> while deleting and adding the domU, as well as starting it, nothing for
> qemu. 
> 
No other ideas on usb? 

Thanks,
James


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

On Fri, 2009-11-13 at 15:42 +0100, Jeroen Groenewegen van der Weyden
wrote:
> can you please sent the output of "ps -ef | grep qemu" after the
> domain is started 
> 
Ok, that command helped a lot. Even though virt-manager didn''t show it,
it was still loading tablet. So I retraced my steps and now it''s
working!!!! I must have been loading an incorrect config file or doing
something else stupid. Tail is currently tucked...

Interesting that virt-manager does not reflect the attached usb device
and doesn''t let you add/delete it. 

Thanks for all the help, especially Jeroen, Nick, and Teo.

James


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