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


Re: [Xen-users] Problem with Xen and OCFS2

To: "Gonçalo Borges" <goncalo@xxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Problem with Xen and OCFS2
From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Date: Fri, 21 Aug 2009 10:38:30 -0600
Delivery-date: Fri, 21 Aug 2009 09:39:51 -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

I have exactly the same issue and have posted a couple of times on this list without any response.  I'm guessing there's something about file locking on OCFS2 that doesn't work quite right for the xm save process, but I could be wrong.  I'm interested to see if you get any hits on this thread that help to track down the problem...


>>> On 2009/08/21 at 08:42, Gonçalo Borges<goncalo@xxxxxx> wrote:

Hi All...

I'm testing a Xen solution on an OCFS2 SAN to store VM images.

If I try to save a VM asking to store the file in any Dom0 local dir
(ex: /tmp) everything works fine, and I can properly restore the VM
afterwards. Nevertheless, It I try to save a VM asking to store the
saved file inside the OCFS2 SAN, it fails with the following messages in


[2009-08-21 14:45:25 xend 9720] DEBUG (XendCheckpoint:89) [xc_save]:
/usr/lib64/xen/bin/xc_save 26 9 0 0 0
[2009-08-21 14:45:25 xend 9720] DEBUG (XendCheckpoint:322) suspend
[2009-08-21 14:45:25 xend 9720] DEBUG (XendCheckpoint:92) In
saveInputHandler suspend
[2009-08-21 14:45:25 xend 9720] DEBUG (XendCheckpoint:94) Suspending 9 ...
[2009-08-21 14:45:25 xend.XendDomainInfo 9720] DEBUG
(XendDomainInfo:1036) XendDomainInfo.handleShutdownWatch
[2009-08-21 14:45:25 xend.XendDomainInfo 9720] DEBUG
(XendDomainInfo:1036) XendDomainInfo.handleShutdownWatch
[2009-08-21 14:45:25 xend.XendDomainInfo 9720] INFO (XendDomainInfo:994)
Domain has shutdown: name=migrating-one-0 id=9 reason=suspend.
[2009-08-21 14:45:25 xend 9720] INFO (XendCheckpoint:99) Domain 9 suspended.
[2009-08-21 14:45:25 xend 9720] DEBUG (XendCheckpoint:108) Written done
[2009-08-21 14:45:25 xend 9720] INFO (XendCheckpoint:351) Had 0
unexplained entries in p2m table
[2009-08-21 14:45:25 xend 9720] INFO (XendCheckpoint:351) Saving memory
pages: iter 1   0%ERROR Internal error: Error when writing to state file
(5) (errno 14)
[2009-08-21 14:45:25 xend 9720] INFO (XendCheckpoint:351) Save exit rc=1
[2009-08-21 14:45:25 xend 9720] ERROR (XendCheckpoint:133) Save failed
on domain one-0 (9).
Traceback (most recent call last):
   File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
line 110, in save
     forkHelper(cmd, fd, saveInputHandler, False)
   File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py",
line 339, in forkHelper
     raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_save 26 9 0 0 0 failed


It seems I'm not the only one complaining about this issue, according to
the following threads:


I wonder is there is some workaround for the problem?


This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>