RE: [Xen-users] live migration with xen 2.0.7 with fibre channel onDebian - help needed

["Cole, Ray" <Ray_Cole@xxxxxxx>]

I had this exact same problem with 2.0.7.  I had done a little investigation 
and found scheduled_work gets called to schedule the shutdown in the user 
domain kernel, but the shutdown work that gets scheduled never actually gets 
called.  I'm glad someone else is seeing this same problem now :-)  Like you, 
it worked a number of times in a row, then would fail, and it didn't seem to 
matter if there was really any load going on or not.

-- Ray


-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of Michael Mey
Sent: Wednesday, December 07, 2005 9:00 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] live migration with xen 2.0.7 with fibre channel
onDebian - help needed


Hi,

I'd like to test the stability of live migration during heavy load of domU.

scenario:
- both dom0s and domU are running on Debian Sarge.
- script on dom0 triggers live-migration to the other dom0
- domU is running I/O tests, e.g. bonnie++
- domUs root- (ext3) and swap fs is stored on two partitions in a san
- san is connected using fibre channel cards to both dom0s
- san in dom0 works fine (tested with bonnie++ and own consistency test)

observation:
- migration works several times, usually something between 10 and 30 times
- then something strange happens:
  A) either domU has completely disappeared on both dom0s
      xend.log on the target host of the last migration says:
<snip> 
[2005-12-06 15:55:31 xend] INFO (XendRoot:113) EVENT> xend.console.create [14, 
14, 9614]
[2005-12-06 15:55:32 xend] INFO (XendRoot:113) EVENT> xend.domain.create 
['debian1', '14']
[2005-12-06 15:56:02 xend] DEBUG (blkif:203) Connecting blkif to event channel 
<BlkifBackendInterface 14 0> ports=16:4
[2005-12-06 15:56:02 xend] DEBUG (XendDomain:244) XendDomain>reap> domain died 
name=debian1 id=14
[2005-12-06 15:56:02 xend] INFO (XendDomain:568) Destroying domain: 
name=debian1
</snip>
     xfrd.log on both dom0s says migration was successful
 
   OR

   B) domU is in paused-state on the target machine after migration,
        xend.log and xfrd.log seem to be ok on both dom0s
        domU _cannot_ be unpaused nor directly accessed using xm console
        xm vbd-destroy is working
        the only thing that can be done is xm destroy.

The thing I am wondering about is why domU suddenly gets crashed after several
successful migrations.
Any help or ideas would be appreciated.

Regards,

Michael


-- 
----------------------------------------------------------------------------------------
Michael Mey                                  
Thinking Objects Software GmbH    |   mailto: michael.mey@xxxxxx 
Lilienthalstrasse 2/1                         |   phone: +49 711 88770-147
70825 Stuttgart-Korntal, Germany  |   fax: +49 711 88770-449
----------------------------------------------------------------------------------------

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