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/
Home Products Support Community News


[Xen-users] 4.0.1 and 4.0.0: resume not possible, machine stays in ---s-

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] 4.0.1 and 4.0.0: resume not possible, machine stays in ---s-- forever
From: "develop@xxxxxxxxxx" <develop@xxxxxxxxxx>
Date: Tue, 17 May 2011 10:05:29 +0200
Delivery-date: Tue, 17 May 2011 01:06:50 -0700
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
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8

I have a serious problem during a suspend-resume-cycle: Sometimes
(approx. 30% of the time) a HVM machine stays in the "---s--" state and
it ist not possible to resume, unpause, destroy or delete the machine. I
tried xen 4.0.0 and 4.0.1 and both versions show the same behaviour.

In my script I do the following:

xm pause machine1
xm pause machine2
xm pause machine3

xm unpause machine1
xm suspend machine1

xm unpause machine2
xm suspend machine2

xm unpause machine3
xm suspend machine3

xm resume machine1 -p
xm resume machine2 -p
xm resume machine3 -p

xm upause machine1
xm upause machine2
xm upause machine3

Sometimes the cycle results to

~# xm list
Name                                        ID   Mem VCPUs      State  
Domain-0                                     0   510    16     r-----  
machine1                                      4  4096     4     -b----  
migrating-machine2                     2  4099     2     ---s--    565.6
machine3                                     5  4096     4     -b----  

The state seems to be saved because the directory
/var/lib/xend/domains/1b719930-2c61-8da9-fe3f-e39c6882bdf6 contains the
memory-dump of machine2.

A restart is only possible after shutting down the other machines,
rebooting the host, removing the /var/lib/xend/domains/1b...-directory.
Then I can do a "xm delete" and a "xm new".

All three machines are HVM (32 and 64bit Windows), host is 64bit Lenny.

Do you have any Ideas? Thanks a lot!


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] 4.0.1 and 4.0.0: resume not possible, machine stays in ---s-- forever, develop@xxxxxxxxxx <=