All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gordan Bobic <gordan@bobich.net>
To: Steven Haigh <netwiz@crc.id.au>
Cc: xen-devel <xen-devel@lists.xen.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: EL6 initscript feedback.
Date: Tue, 21 May 2013 12:47:55 +0100	[thread overview]
Message-ID: <d43030808f263b467f60fd52e4d16df5@mail.shatteredsilicon.net> (raw)
In-Reply-To: <519B5AD3.9050007@crc.id.au>

 On Tue, 21 May 2013 21:30:27 +1000, Steven Haigh <netwiz@crc.id.au> 
 wrote:
> On 05/21/2013 09:20 PM, Stefano Stabellini wrote:
>> On Tue, 21 May 2013, Steven Haigh wrote:
>>> Hi all,
>>>
>>> I'm throwing in my initscript here that I've been pushing to 
>>> autostart xen
>>> domains on system boot.
>>>
>>> There are at least one issue right now that I'm not 100% sure how 
>>> to handle -
>>> and that is domains created by libvirt. These continue to show in 
>>> an xm/xl
>>> list output even when they are not paused / running / blocked - 
>>> causing my
>>> initscript to think they are still running.
>>>
>>> The ways I can think of detecting this are *very* hacky and I 
>>> wouldn't feel
>>> comfortable to including them in widely used packages.
>>>
>>> I'm wondering if people have some spare time that they review the 
>>> logic in
>>> this initscript and provide feedback / suggestions / fixes / 
>>> improvements that
>>> I can roll into the scripts to enhance them for all.
>>
>> Is it actually a good idea to mix and match different toolstacks on 
>> the
>> same host? If somebody intends to use libvirt, surely she would want 
>> to
>> use it for everything?
>
> This is the interesting question... which probably leads into a more
> important question... What is the best practices for config 
> management
> and defining configuration for DomU's?
>
> While I recommend that people use a plain text config file in
> /etc/xen (although really the files can be just about anywhere) and
> then links to various auto-start DomU's in /etc/xen/auto as a general
> rule.
>
> Am I correct in thinking that libvirt only keeps details of domains
> in the xenstore? Is this recommended? Although more a libvirt 
> question
> - can libvirt be configured to use config files in /etc/xen or
> similar?

 I think this is largely distribution dependant. In the case of 
 EL/Fedora,
 libvirt seems to be the distro's intended way of managing VMs, at least 
 for
 their primary supported virtualization method (KVM).

 In the interest of clarity and maintainability I have seen the light
 and converted my VMs to simple text files in /etc/xen/ (there seems to 
 be
 no documentation on how to edit most of the settings in xenstore). Some
 consensus on the best way would be good, though.

 Gordan

  reply	other threads:[~2013-05-21 11:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21  3:01 EL6 initscript feedback Steven Haigh
2013-05-21 11:20 ` Stefano Stabellini
2013-05-21 11:30   ` Steven Haigh
2013-05-21 11:47     ` Gordan Bobic [this message]
2013-05-21 12:02       ` Stefano Stabellini
2013-05-21 17:00         ` Pasi Kärkkäinen
2013-05-21 18:25           ` Gordan Bobic
2013-05-21 18:46             ` Pasi Kärkkäinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d43030808f263b467f60fd52e4d16df5@mail.shatteredsilicon.net \
    --to=gordan@bobich.net \
    --cc=netwiz@crc.id.au \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.