WARNING - OLD ARCHIVES

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

xen-users

Re: [Xen-users] 2.6.18.8 xen.org dom0 kernel w/RHEL 5 PV on HVM guests

On Mon, Mar 22, 2010 at 12:41:14PM -0700, Andrew Evans wrote:
> >>     
> > Do you have a bridge called 'eth0' for real? Try "brctl show" to verify.
> > RHEL5 as a default creates 'xenbr0', not 'eth0'.
> >   
> 
> Well spotted! I don't have such a bridge, and I can't create one because
> eth0 is already an existing network interface name. I've changed my
> libvirt domU config to use xenbr0 instead of eth0. Not sure why this
> works with Xen 3.4.2 though.
>

Xen 3.4.x with the default configuration creates a bridge called 'eth0',
and renames the physical network adapter to peth0.

Xen 3.0.x and 3.1.x with the default configuration creates a bridge called 
'xenbr0',
and renames the physical network adapter to peth0, and also creates a separate
dom0 management only virtual interface called 'eth0'.

So it's just different defaults.
 
> My domU *still* isn't starting, though. xend-debug.log shows this traceback:
> 

Are you sure you got the earlier xen 3.4.x stuff completely removed? 

Did you also make sure virt-manager, libvirt, virsh etc were downgraded 
to the RHEL5 default versions?

Dunno if the xml configuration created with newer libvirt is still compatible 
with the older libvirt/xen..

-- Pasi

> Traceback (most recent call last):
>   File "/usr/lib64/python2.4/SocketServer.py", line 463, in
> process_request_thread
>     self.finish_request(request, client_address)
>   File "/usr/lib64/python2.4/SocketServer.py", line 254, in finish_request
>     self.RequestHandlerClass(request, client_address, self)
>   File "/usr/lib64/python2.4/SocketServer.py", line 521, in __init__
>     self.handle()
>   File "/usr/lib64/python2.4/BaseHTTPServer.py", line 316, in handle
>     self.handle_one_request()
>   File "/usr/lib64/python2.4/BaseHTTPServer.py", line 310, in
> handle_one_request
>     method()
>   File "/usr/lib64/python2.4/site-packages/xen/util/xmlrpclib2.py", line
> 66, in do_POST
>     self.send_response(200)
>   File "/usr/lib64/python2.4/BaseHTTPServer.py", line 367, in send_response
>     self.wfile.write("%s %d %s\r\n" %
>   File "/usr/lib64/python2.4/socket.py", line 256, in write
>     self.flush()
>   File "/usr/lib64/python2.4/socket.py", line 243, in flush
>     self._sock.sendall(buffer)
> error: (32, 'Broken pipe')
> 
> No idea if it's relevant or not. Certainly doesn't look good though.
> 
> xend.log contains everyone's favorite, "Hotplug scripts not working":
> 
> [2010-03-22 19:28:38 xend 4863] ERROR (SrvBase:88) Request
> wait_for_devices failed.
> Traceback (most recent call last):
>   File "/usr/lib64/python2.4/site-packages/xen/web/SrvBase.py", line 85,
> in perform
>     return op_method(op, req)
>   File
> "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDomain.py", line
> 72, in op_wait_for_devices
>     return self.dom.waitForDevices()
>   File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
> line 2330, in waitForDevices
>     self.waitForDevices_(c)
>   File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
> line 1422, in waitForDevices_
>     return self.getDeviceController(deviceClass).waitForDevices()
>   File
> "/usr/lib64/python2.4/site-packages/xen/xend/server/DevController.py",
> line 160, in waitForDevices
>     return map(self.waitForDevice, self.deviceIDs())
>   File
> "/usr/lib64/python2.4/site-packages/xen/xend/server/DevController.py",
> line 170, in waitForDevice
>     raise VmError("Device %s (%s) could not be connected. "
> VmError: Device 0 (vif) could not be connected. Hotplug scripts not working.
> 
> Device model log:
> 
> $ cat qemu-dm.16544.log
> domid: 4
> qemu: the number of cpus is 7
> Change xvda to look like hda
> Change xvdb to look like hdb
> Change xvdc to look like hdc
> Watching /local/domain/4/logdirty/next-active
> Watching /local/domain/0/device-model/4/command
> xs_read(): vncpasswd get error.
> /vm/51711672-9512-4bd8-91ea-a1d542bbda92/vncpasswd.
> char device redirected to /dev/pts/1
> qemu_map_cache_init nr_buckets = 10000
> shared page at pfn effff
> buffered io page at pfn efffd
> xs_read(/vm/51711672-9512-4bd8-91ea-a1d542bbda92/rtc/timeoffset): read error
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> Triggered log-dirty buffer switch
> 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
> 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
> 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
> 
> Current domU config (libvirt XML):
> 
> <domain type='xen'>
>   <name>foo</name>
>   <memory>7340032</memory>
>   <currentMemory>7340032</currentMemory>
>   <vcpu>7</vcpu>
>   <os>
>     <type arch='x86_64' machine='xenfv'>hvm</type>
>     <loader>/usr/lib/xen/boot/hvmloader</loader>
>     <boot dev='hd'/>
>   </os>
>   <features>
>     <acpi/>
>     <apic/>
>     <pae/>
>   </features>
>   <clock offset='utc'/>
>   <on_poweroff>destroy</on_poweroff>
>   <on_reboot>restart</on_reboot>
>   <on_crash>restart</on_crash>
>   <devices>
>     <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
>     <disk type='block' device='disk'>
>       <driver name='phy'/>
>       <source dev='/dev/sys/lv0'/>
>       <target dev='xvda' bus='xen'/>
>     </disk>
>     <disk type='block' device='disk'>
>       <driver name='phy'/>
>       <source dev='/dev/sys/lv1'/>
>       <target dev='xvdb' bus='xen'/>
>     </disk>
>     <disk type='block' device='disk'>
>       <driver name='phy'/>
>       <source dev='/dev/sys/lv2'/>
>       <target dev='xvdc' bus='xen'/>
>     </disk>
>     <interface type='bridge'>
>       <mac address='00:50:56:0f:dd:02'/>
>       <source bridge='xenbr0'/>
>       <script path='vif-bridge'/>
>     </interface>
>     <serial type='pty'>
>       <target port='0'/>
>     </serial>
>     <console type='pty'>
>       <target port='0'/>
>     </console>
>     <input type='mouse' bus='ps2'/>
>     <graphics type='vnc' port='-1' autoport='yes'/>
>   </devices>
> </domain>
> 
> thanks,
> 
> -Andrew
> 

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