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

[Xen-users] Migration sometimes fails - domU hangs

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Migration sometimes fails - domU hangs
From: Marc A. Müller <Marc.Mueller@xxxxxxxxxxxxxxxx>
Date: Thu, 7 Jan 2010 16:04:53 +0100
Delivery-date: Thu, 07 Jan 2010 07:05:44 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqPqsRpMKOzmp6YThOQkq0Gfyc1KA==
Thread-topic: Migration sometimes fails - domU hangs
Hi,
 
I'm trying to set up xen using drbd as replication service on two servers.
The system is openSUSE 11.2-64bit (XEN 3.4.1, kernel 2.6.31.8, drbd 8.3.4) on Intel Core 2 machines.
 

Migration sometimes works, sometimes the domU hangs after migration: 'xm list' then shows the state 'r'-running (should be 'b'-blocked, because domU is idle) and the cpu time is running. The domU doesn't respond to any requests, not even 'xm shutdown' works. It happens on live and non-live migration.
 

The only error messages I could see are in /var/log/xen/qemu-dm-test1.log:
-----------------------------------------------------
domid: 2
Warning: vlan 0 is not connected to host network
Using xvda for guest's hda
qemu: type (image format) 'drbd' unknown for vbd '/local/domain/0/backend/vbd/2/51712/mode' or image 'd1'
Watching /local/domain/0/device-model/2/logdirty/next-active
Watching /local/domain/0/device-model/2/command
char device redirected to /dev/pts/3
/usr/src/packages/BUILD/xen-3.4.1-testing/tools/ioemu-dir/hw/xen_blktap.c:715: Init blktap pipes
Could not open /var/run/tap/qemu-read-2
xen be: console-0: connect() failed
xs_read(): vncpasswd get error. /vm/188d6f2c-910c-db01-9973-b662bd5fd357/vncpasswd.
xen be: console-0: connect() failed
xen be: console-0: connect() failed
xen be: console-0: connect() failed
----------------------------------------------------
The "connect() failed" messages only appear when the migration fails.
 
 
 
By the way, on boot of dom0, xend.log shows the warnings:
-----------------------------------------------------
[2010-01-07 14:47:43 3962] WARNING (XendAPI:701) API call: VBD.set_device not found
[2010-01-07 14:47:43 3962] WARNING (XendAPI:701) API call: VBD.set_type not found 
[2010-01-07 14:47:43 3962] WARNING (XendAPI:701) API call: session.get_all_records not found
[2010-01-07 14:47:43 3962] WARNING (XendAPI:701) API call: event.get_record not found
[2010-01-07 14:47:43 3962] WARNING (XendAPI:701) API call: event.get_all not found  
[2010-01-07 14:47:43 3962] WARNING (XendAPI:701) API call: VIF.get_network not found
[2010-01-07 14:47:43 3962] WARNING (XendAPI:701) API call: VIF.set_device not found
[2010-01-07 14:47:43 3962] WARNING (XendAPI:701) API call: VIF.set_MAC not found  
[2010-01-07 14:47:43 3962] WARNING (XendAPI:701) API call: VIF.set_MTU not found
[2010-01-07 14:47:43 3962] WARNING (XendAPI:701) API call: debug.get_all not found
-----------------------------------------------------
Should I worry about these?
 

Thank You,
Marc
 
 
 
 
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Migration sometimes fails - domU hangs, Marc A. Müller <=