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] live migration with xen 2.0.7 with fibre channel on Debian -

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] live migration with xen 2.0.7 with fibre channel on Debian - help needed
From: Michael Mey <michael.mey@xxxxxx>
Date: Wed, 7 Dec 2005 16:00:11 +0100
Delivery-date: Wed, 07 Dec 2005 15:00:59 +0000
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Thinking Objects Software GmbH
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9

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

- 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)

- 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:
[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: 
     xfrd.log on both dom0s says migration was successful

   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.



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

Attachment: pgpRz6yQnAuJO.pgp
Description: PGP signature

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] live migration with xen 2.0.7 with fibre channel on Debian - help needed, Michael Mey <=