WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [PATCH] qemu-xen: Fix PV segfault

To: Stefan de Konink <skinkie@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] qemu-xen: Fix PV segfault
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Wed, 2 Jul 2008 16:39:45 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, John Levon <levon@xxxxxxxxxxxxxxxxx>, Gerd Hoffmann <kraxel@xxxxxxxxxx>, Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, Kevin Wolf <kwolf@xxxxxxx>
Delivery-date: Wed, 02 Jul 2008 08:40:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <486B9EAD.4090009@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <18538.27111.959001.890654@xxxxxxxxxxxxxxxxxxxxxxxx> <486B3428.5000006@xxxxxxx> <486B3E88.1020904@xxxxxxxxxx> <20080702141917.GD23929@xxxxxxxxxxxxxxxxxxxxxxx> <18539.37231.372982.478747@xxxxxxxxxxxxxxxxxxxxxxxx> <20080702143813.GG23929@xxxxxxxxxxxxxxxxxxxxxxx> <18539.38311.54023.618715@xxxxxxxxxxxxxxxxxxxxxxxx> <486B97D9.1010305@xxxxxxxxx> <18539.39783.262893.291098@xxxxxxxxxxxxxxxxxxxxxxxx> <486B9EAD.4090009@xxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
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 :|

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

<Prev in Thread] Current Thread [Next in Thread>