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

["develop@xxxxxxxxxx" <develop@xxxxxxxxxx>]

Hello!

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  
Time(s)
Domain-0                                     0   510    16     r-----  
7899.4
machine1                                      4  4096     4     -b----  
2288.1
migrating-machine2                     2  4099     2     ---s--    565.6
machine3                                     5  4096     4     -b----  
1803.4

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!

Martin



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