xm save / restore with xen-unstable not working ?

xm save / restore with xen-unstable not working ?

[sven.kretzschmar]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1457 bytes --]


I have downloaded, compiled and installed xen-unstable
from bitkeeper yesterday evening (UTC).
Everything works fine so far.
When starting xend and creating a new unprivileged
domain via "xm create..." and connecting via "xm console..."
this also works correctly.
Also nearly every other xm command that I tried (like info,
consoles, pause, destroy, etc.).
However when I try "xm save" on a domain this always
generates an error message on the screen like 
"...connection refused on the other side...111:connection
refused..." and does not work.
Xend is running in Dom0 at this time and all other xm commands
work fine at the same time.
Is xm save / restore broken or disabled with xen-unstable ?

Also I could not find a possibility to tell the xm tool
on which port xend is listening. So when I change the
port Xend is listening on in the xend-config file, no
xm command works any more. Where can I configure the
port the xm tool is trying to contact the xend daemon ?

Thanks and keep up the good work, xen-unstable is already
a very impressive software... :)


-- 
NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler!
GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

Re: xm save / restore with xen-unstable not working ?

[Ian Pratt]

> However when I try "xm save" on a domain this always
> generates an error message on the screen like 
> "...connection refused on the other side...111:connection
> refused..." and does not work.
> Xend is running in Dom0 at this time and all other xm commands
> work fine at the same time.
> Is xm save / restore broken or disabled with xen-unstable ?

Yep -- there was a small interface change that broke
save/restore/migrate, and I promised to fix it, but I just
haven't had a chance with OLS and admin etc.

I'll work on it over the weekend, if not before.

> Also I could not find a possibility to tell the xm tool
> on which port xend is listening. So when I change the
> port Xend is listening on in the xend-config file, no
> xm command works any more. Where can I configure the
> port the xm tool is trying to contact the xend daemon ?

At one point, we talked about xm having a "-U" option where a URL
was used to specify the xend to talk to. I don't think it's there
in the current version, but it should be trivial to add. You'd
then be able to control and query multiple xen nodes from a
single host. Anyone want to have a go to add this?

Cheers,
Ian


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

Re: xm save / restore with xen-unstable not working ?

[Tom Wilkie]

The simplest way to achieve this is to alter the XendClient.py file.  
In  this file is the class that xm used to communicate with xend.  If 
you change this, it would also change the sv web interface, which would 
(perhaps) be useful too, so you can manage multiple nodes form one 
interface

Tom

On 29 Jul 2004, at 14:56, Ian Pratt wrote:

>
>> However when I try "xm save" on a domain this always
>> generates an error message on the screen like
>> "...connection refused on the other side...111:connection
>> refused..." and does not work.
>> Xend is running in Dom0 at this time and all other xm commands
>> work fine at the same time.
>> Is xm save / restore broken or disabled with xen-unstable ?
>
> Yep -- there was a small interface change that broke
> save/restore/migrate, and I promised to fix it, but I just
> haven't had a chance with OLS and admin etc.
>
> I'll work on it over the weekend, if not before.
>
>> Also I could not find a possibility to tell the xm tool
>> on which port xend is listening. So when I change the
>> port Xend is listening on in the xend-config file, no
>> xm command works any more. Where can I configure the
>> port the xm tool is trying to contact the xend daemon ?
>
> At one point, we talked about xm having a "-U" option where a URL
> was used to specify the xend to talk to. I don't think it's there
> in the current version, but it should be trivial to add. You'd
> then be able to control and query multiple xen nodes from a
> single host. Anyone want to have a go to add this?
>
> Cheers,
> Ian
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

Re: xm save / restore with xen-unstable not working ?

[Sven Kretzschmar]

I also forgot to start the xfrd daemon, it's also necessary if one only want's
to save but not migrate a domain.
I haven't seen this in the docu, only realized it by digging through the xend,
xm and xfrd sources.
Now the error points more to the "small interface change" Ian has mentioned:
"Invalid state record -- pfn count out of range: <big number goes here...>"
I am quite interested in testing the save/migrate feature. If it's really only
a small interface change, can you shortly point me to the places / files
of the source where I should look in order to correct it, or does
it need very deep knowledge of xen internals ?

TIA,
  Sven

*********** REPLY SEPARATOR  ***********

On 29.07.2004 at 15:06 Tom Wilkie wrote:

>The simplest way to achieve this is to alter the XendClient.py file.
>In  this file is the class that xm used to communicate with xend.  If
>you change this, it would also change the sv web interface, which would
>(perhaps) be useful too, so you can manage multiple nodes form one
>interface
>
>Tom
>
>On 29 Jul 2004, at 14:56, Ian Pratt wrote:
>
>>
>>> However when I try "xm save" on a domain this always
>>> generates an error message on the screen like
>>> "...connection refused on the other side...111:connection
>>> refused..." and does not work.
>>> Xend is running in Dom0 at this time and all other xm commands
>>> work fine at the same time.
>>> Is xm save / restore broken or disabled with xen-unstable ?
>>
>> Yep -- there was a small interface change that broke
>> save/restore/migrate, and I promised to fix it, but I just
>> haven't had a chance with OLS and admin etc.
>>
>> I'll work on it over the weekend, if not before.
>>
>>> Also I could not find a possibility to tell the xm tool
>>> on which port xend is listening. So when I change the
>>> port Xend is listening on in the xend-config file, no
>>> xm command works any more. Where can I configure the
>>> port the xm tool is trying to contact the xend daemon ?
>>
>> At one point, we talked about xm having a "-U" option where a URL
>> was used to specify the xend to talk to. I don't think it's there
>> in the current version, but it should be trivial to add. You'd
>> then be able to control and query multiple xen nodes from a
>> single host. Anyone want to have a go to add this?
>>
>> Cheers,
>> Ian
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by BEA Weblogic Workshop
>> FREE Java Enterprise J2EE developer tools!
>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/xen-devel
>>





-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com

Re: xm save / restore with xen-unstable not working ?

[Mike Wray]

Sven Kretzschmar wrote:

> I also forgot to start the xfrd daemon, it's also necessary if one only want's
> to save but not migrate a domain.
> I haven't seen this in the docu, only realized it by digging through the xend,
> xm and xfrd sources.
> Now the error points more to the "small interface change" Ian has mentioned:
> "Invalid state record -- pfn count out of range: <big number goes here...>"
> I am quite interested in testing the save/migrate feature. If it's really only
> a small interface change, can you shortly point me to the places / files
> of the source where I should look in order to correct it, or does
> it need very deep knowledge of xen internals ? 
> 

The save/restore/migrate code is very much in progress at the minute.
In other words, it doesn't work at the moment. Ian plans to look
at the pfc count error, and when that's fixed we'll know if the rest
of it works.

Mike


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com

Re: xm save / restore with xen-unstable not working ?

[Mike Wray]

Tom Wilkie wrote:

> The simplest way to achieve this is to alter the XendClient.py file.  
> In  this file is the class that xm used to communicate with xend.  If 
> you change this, it would also change the sv web interface, which would 
> (perhaps) be useful too, so you can manage multiple nodes form one 
> interface
> 

To avoid having to edit the XendClient file I've just checked-in
support for using the environment variable XEND to set the host
and port for the xend server. For example:

XEND=host:8000 xm list

alternatively,

export XEND=host:8000

xm list

Mike


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com

Re: xm save / restore with xen-unstable not working ?

[Tom Wilkie]

Have you changed xm to do this, or the XendClient?  Will thee changes 
carry over to the SV web interface?

I would look, but I'm at home today ;-)

Tom

On 30 Jul 2004, at 09:57, Mike Wray wrote:

> Tom Wilkie wrote:
>
>> The simplest way to achieve this is to alter the XendClient.py file.  
>> In  this file is the class that xm used to communicate with xend.  If 
>> you change this, it would also change the sv web interface, which 
>> would (perhaps) be useful too, so you can manage multiple nodes form 
>> one interface
>
> To avoid having to edit the XendClient file I've just checked-in
> support for using the environment variable XEND to set the host
> and port for the xend server. For example:
>
> XEND=host:8000 xm list
>
> alternatively,
>
> export XEND=host:8000
>
> xm list
>
> Mike
>



-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com