From: "Daniel P. Berrange" <berrange@redhat.com>
To: Stefan de Konink <skinkie@xs4all.nl>
Cc: xen-devel@lists.xensource.com,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
John Levon <levon@movementarian.org>,
Gerd Hoffmann <kraxel@redhat.com>,
Samuel Thibault <samuel.thibault@eu.citrix.com>,
Kevin Wolf <kwolf@suse.de>
Subject: Re: Re: [PATCH] qemu-xen: Fix PV segfault
Date: Wed, 2 Jul 2008 16:39:45 +0100 [thread overview]
Message-ID: <20080702153945.GL9275@redhat.com> (raw)
In-Reply-To: <486B9EAD.4090009@xs4all.nl>
On Wed, Jul 02, 2008 at 05:28:45PM +0200, Stefan de Konink wrote:
> Ian Jackson schreef:
> >Stefan de Konink writes ("Re: [Xen-devel] Re: [PATCH] qemu-xen: Fix PV
> >segfault"):
> >>But this isn't the case now at all, is it? I name xenstored; is the move
> >>that Samuel with minios takes a way to solve this?
> >
> >xenstored is not critical to the run-time operation of PV domains.
> >Without it you can't boot, add devices, etc. etc. But you can (for
> >example) shut down a PV domain cleanly.
>
> So the actual 'problem' is the storage of the domain properties,
> preferably in a 'process' that is not running, but an API that can query
> it. I think Libvirtd fails on that point too, everything gets fubar,
> once a daemon breaks. The reason for a running daemon providing domain
> specific information is not clear for me, storing it on disk will always
> give better recovery possibilities.
That is just an artifact of libvirt being written to work with all QEMU
versions back to 0.8.1, which didn't have a good way to re-connect to
the monitor of a running VM. Its on the TODO list to automatically use
a UNIX socket for monitor communication when we detect QEMU >= 0.9.x
so there's no need for libvirt be the direct parent of the QEMU processes
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2008-07-02 15:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 18:37 [PATCH] qemu-xen: Fix PV segfault Kevin Wolf
2008-07-01 11:42 ` Kevin Wolf
2008-07-01 17:31 ` Ian Jackson
2008-07-02 7:54 ` Kevin Wolf
2008-07-02 8:38 ` Gerd Hoffmann
2008-07-02 14:19 ` John Levon
2008-07-02 14:32 ` Ian Jackson
2008-07-02 14:35 ` Stefan de Konink
2008-07-02 14:38 ` John Levon
2008-07-02 14:50 ` Ian Jackson
2008-07-02 14:55 ` Kevin Wolf
2008-07-02 14:59 ` Stefan de Konink
2008-07-02 15:14 ` Ian Jackson
2008-07-02 15:28 ` Stefan de Konink
2008-07-02 15:39 ` Daniel P. Berrange [this message]
2008-07-02 16:00 ` John Levon
2008-07-02 17:14 ` Ian Jackson
2008-07-02 15:00 ` Daniel P. Berrange
2008-07-02 15:05 ` Daniel P. Berrange
2008-07-02 15:08 ` John Levon
2008-07-02 14:46 ` Kevin Wolf
2008-07-02 14:52 ` Daniel P. Berrange
2008-07-02 15:59 ` Gerd Hoffmann
2008-07-03 8:01 ` Gerd Hoffmann
2008-07-03 8:16 ` Kevin Wolf
2008-07-03 10:55 ` Gerd Hoffmann
2008-07-03 11:05 ` Kevin Wolf
2008-07-03 11:17 ` Kevin Wolf
2008-07-03 11:18 ` Gerd Hoffmann
2008-07-03 9:32 ` Ian Jackson
2008-07-03 11:13 ` Gerd Hoffmann
2008-07-02 10:21 ` Ian Jackson
2008-07-02 11:30 ` Kevin Wolf
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=20080702153945.GL9275@redhat.com \
--to=berrange@redhat.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=kraxel@redhat.com \
--cc=kwolf@suse.de \
--cc=levon@movementarian.org \
--cc=samuel.thibault@eu.citrix.com \
--cc=skinkie@xs4all.nl \
--cc=xen-devel@lists.xensource.com \
/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.