All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, Gerd Hoffmann <kraxel@redhat.com>,
	Kevin Wolf <kwolf@suse.de>, John Levon <levon@movementarian.org>
Subject: Re: Re: [PATCH] qemu-xen: Fix PV segfault
Date: Wed, 2 Jul 2008 16:00:59 +0100	[thread overview]
Message-ID: <20080702150059.GJ9275@redhat.com> (raw)
In-Reply-To: <18539.38311.54023.618715@mariner.uk.xensource.com>

On Wed, Jul 02, 2008 at 03:50:15PM +0100, Ian Jackson wrote:
> John Levon writes ("Re: [Xen-devel] Re: [PATCH] qemu-xen: Fix PV segfault"):
> > Oh, if it's just the PV bits, then it's probably part of the work to
> > drop the need for the Xen daemons altogether and move to a domain ==
> > running qemu implementation as Dan Berrange presented at the summit some
> > time ago.
> 
> I wasn't around for that summit presentation but for the record my
> personal view is that this is a bad idea.  dom0 host processes are
> much more fragile (much more vulnerable to failures induced both
> inside that process and from the rest of dom0) than a Xen domain.
> Ideally the proper functioning of guests would not depend on that kind
> of complexity.
> 
> Indeed currently even if dom0 entirely stops running user code for
> some reason, it is still possible to have PV guests keep running and
> cleanly shut themselves down (although management functions like
> migration, device hotplug, and requesting shutdown from dom0 are of
> course unavailable).
> 
> So guests should continue to be regarded as owned and parented by the
> hypervisor, not by some dom0 userland process.

My work didn't change who owned the VM's at all. I literally just took
the the domain setup code from the constructDomain() method in XenDomainInfo.py
and replicated it in QEMU. So instead of having XenD construct the domain,
QEMU did it directly. The split of responsibilities between HV vs Dom0
remained the same - it was just shuffling responsibilities within Dom0.

The original patches (no longer working against current xen-unstable)
are here

   http://hg.berrange.com/tools/xenite--devel

The main problem I didn't solve was correct cleanup in the event that
QEMU crashed - something XenD would ordinarily do - but would have to
be done by whatever was launching QEMU, or perhaps via a Dom0 kernel
hook.

Regards,
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 :|

  parent reply	other threads:[~2008-07-02 15:00 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
2008-07-02 16:00                   ` John Levon
2008-07-02 17:14                     ` Ian Jackson
2008-07-02 15:00               ` Daniel P. Berrange [this message]
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=20080702150059.GJ9275@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=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.