Xen users - Aug 2009 - Difference between xm create and xm new / xm start

Hi,

As far as I can see, there is something different between using ''xm
create'' and ''xm new'' followed by ''xm
start''. It''s something to do with data being stored in
XenStore. I couldn''t suspend the one started with ''xm
create''. Could someone please explain the effective difference between
the two and when ''create'' should be used instead of
''new'' and vice-versa.

Thanks in advance,

Ian.



      

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

On Tue, Aug 18, 2009 at 8:28 AM, Ian Murray<murrayie@yahoo.co.uk>
wrote:
> Hi,
>
> As far as I can see, there is something different between using
''xm create'' and ''xm new'' followed by
''xm start''. It''s something to do with data being
stored in XenStore. I couldn''t suspend the one started with
''xm create''. Could someone please explain the effective
difference between the two and when ''create'' should be used
instead of ''new'' and vice-versa.
xm create -> domU configuration is NOT managed by xend. Usually using
config files on /etc/xen. This is the easiest method to use for
beginners, as you have a config file that you can edit manually. The
default on RHEL5 (which uses Xen 3.1+).

"xm new" and "xm start" -> domU configuration is managed
by xend. You
change values using commands like "xm block-attach", which can modify
settings online. No config file to edit manually. The default on
current versions of Xen.

Personally I use config files and "xm create", even on Xen 3.4 boxes.
It''s easier to manage that way.

-- 
Fajar

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

> 
> "xm new" and "xm start" -> domU configuration is
managed by xend. You
> change values using commands like "xm block-attach", which can
modify
> settings online. No config file to edit manually. The default on
> current versions of Xen.
> 
> Personally I use config files and "xm create", even on Xen 3.4
boxes.
> It''s easier to manage that way.
Thanks for the response. I think I tried a block-attach against a dom I had
created with ''create''. AFAIR it failed, so maybe that is why.
I read the wiki entry against XenStore but it doesn''t really tell you
how to manipulate it non-programatically.

When you do an xm new, does it copy the values from the config file into
XenStore?

Thanks in advance,

Ian.


      

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

On Tue, Aug 18, 2009 at 10:50 PM, Ian Murray<murrayie@yahoo.co.uk>
wrote:
>> "xm new" and "xm start" -> domU configuration is
managed by xend. You
>> change values using commands like "xm block-attach", which
can modify
>> settings online. No config file to edit manually. The default on
>> current versions of Xen.
>>
>> Personally I use config files and "xm create", even on Xen
3.4 boxes.
>> It''s easier to manage that way.
>
> Thanks for the response. I think I tried a block-attach against a dom I had
created with ''create''. AFAIR it failed, so maybe that is why.
No, that shouldn''t be it. "xm block attach" should work for
all domUs,
whether it''s created with "xm new" or "xm create".
Something else is
causing the error.

What I meant was with "xm new", using "xm block attach" (or
the
equivalent virsh command) was pretty much the only way to add new
block device. With "xm create", you could either use that, or edit the
config file manually.
>
> When you do an xm new, does it copy the values from the config file into
XenStore?
I don''t think so. Sure, xenstore stores info about all domU, but not
the config file. Try looking at /var/lib/xend/domains (which, AFAIK,
is  not part of xenstore).

-- 
Fajar

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