WARNING - OLD ARCHIVES

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

xen-users

RE: [Xen-users] Problems saving domain

To: "'Petersson, Mats'" <Mats.Petersson@xxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Problems saving domain
From: "Artur Linhart - Linux communication" <AL.LINUX@xxxxxxxxxxx>
Date: Thu, 8 Mar 2007 10:56:39 +0100
Delivery-date: Thu, 08 Mar 2007 01:56:01 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <907625E08839C4409CE5768403633E0B018E1A2F@xxxxxxxxxxxxxxxxx>
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>
References: <00f601c76155$97922400$1500a8c0@xxxxxxxxxxxxxxxxxxxxxxxxx> <907625E08839C4409CE5768403633E0B018E1A2F@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acdgpr1NRjt2kT9fQm215ZSXvjCYSQAAZTIwACq46gAABIuZEAAAo6SA

Hello,

        Ok, clear. Thank You for Your work and for Your engagement how You
help us using xen :-)

        Sincerelly, Archie

-----Original Message-----
From: Petersson, Mats [mailto:Mats.Petersson@xxxxxxx] 
Sent: Thursday, March 08, 2007 10:41 AM
To: Artur Linhart - Linux communication; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Problems saving domain

 

> -----Original Message-----
> From: Artur Linhart - Linux communication 
> [mailto:AL.LINUX@xxxxxxxxxxx] 
> Sent: 08 March 2007 07:44
> To: Petersson, Mats; xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] Problems saving domain
> 
> 
> Hi Mats,
> 
> Thank You for the answer. Yes, it is Windows on HVM. With 
> linux as domU it
> works OK. So it is clear.
> I have also the problem with the shutdown of such windows 
> domain - the VM is
> always "turned off", so Windows are not shut down correctly 
> (again, with
> Linux as domU it is no problem).
> 
> What would You recommend, is there any possibility to get this both
> functionalities working for windows (also not with HVM), 
> could You point me
> to some description how to configure it to get it working? Or 
> is the only
> chance to wait for xen 3.0.5 or maybe later?

Since Windows only works in HVM mode, it's not possible to get this
working "by configuration". The code needed to save/restore HVM domains
isn't there in 3.0.4, it's only present in the "unstable" version of
Xen. This version will become 3.0.5 in the next few weeks or so. I was
the one who wrote the code to save the AMD CPU context, so I should know
;-)

As to power-off in Windows, I thought that worked, but maybe there are
different variants of how this works, which work differently - or maybe
because I've been running unstable for several months, and it certainly
works in unstable (well, I've never really done anything other than
unstable, as I'm a Xen kernel developer when I'm not responding to posts
here - there's rarely much point in running the "released" version when
you want to add new code to Xen)

--
Mats
> 
> Thank You very much for response,
> 
>       Archie.
> 
> -----Original Message-----
> From: Petersson, Mats [mailto:Mats.Petersson@xxxxxxx] 
> Sent: Wednesday, March 07, 2007 12:11 PM
> To: Artur Linhart - Linux communication; xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] Problems saving domain
> 
> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> > Artur Linhart - Linux communication
> > Sent: 07 March 2007 10:55
> > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: [Xen-users] Problems saving domain
> > 
> > Hello,
> > 
> >  
> > 
> >             I have the problems if I want to save the running 
> > domU on Xen 3.0.4.1 - the save always fails. In the xen log 
> > there i found following debug info:
> > 
> >  
> > 
> > [2007-03-07 11:19:10 xend 3396] DEBUG (XendCheckpoint:80) 
> > [xc_save]: /usr/lib64/xen/bin/xc_save 18 5 0 0 0
> > 
> > [2007-03-07 11:19:10 xend.XendDomainInfo 3396] DEBUG 
> > (XendDomainInfo:731) Storing domain details: 
> > {\047console/port\047: \0473\047, \047name\047: 
> > \047migrating-vm_w2ksrv_01\047, \047console/limit\047: 
> > \0471048576\047, \047vm\047: 
> > \047/vm/8645c693-e2c4-0d28-c0dc-2a2ae3781546\047, 
> > \047domid\047: \0475\047, \047cpu/0/availability\047: 
> > \047online\047, \047memory/target\047: \047200704\047, 
> > \047store/ring-ref\047: \04750174\047, \047store/port\047: 
> \0472\047}
> 
> Does vm_w2ksrv_01 mean that this is a Windows guest -> a HVM guest? In
> that case it's not "supposed to work". The code to implement HVM
> save/restore was introduced into unstable a few weeks back. It works
> most of the time at present, but there are a few bugs to fix 
> still - in
> particular, fixing that a domain may be in the middle of a IO
> transaction when it gets stopped - the current code in xen-unstable
> isn't coping with this very well... There is work in progress to fix
> this... I think this is a "required" feature for 3.0.5, so 
> 3.0.5 should
> have working save/restore - Live migration may or may not be 
> included in
> that. 
> 
> --
> Mats
> 
> --
> Mats
> 
> 
> 
> __________ Informace od NOD32 2101 (20070307) __________
> 
> Tato zprava byla proverena antivirovym systemem NOD32.
> http://www.nod32.cz
> 
> 
> 
> 
> 



__________ Informace od NOD32 2102 (20070308) __________

Tato zprava byla proverena antivirovym systemem NOD32.
http://www.nod32.cz



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

<Prev in Thread] Current Thread [Next in Thread>