From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: Re: [PATCH] qemu-xen: Fix PV segfault Date: Wed, 2 Jul 2008 16:39:45 +0100 Message-ID: <20080702153945.GL9275@redhat.com> References: <18538.27111.959001.890654@mariner.uk.xensource.com> <486B3428.5000006@suse.de> <486B3E88.1020904@redhat.com> <20080702141917.GD23929@totally.trollied.org.uk> <18539.37231.372982.478747@mariner.uk.xensource.com> <20080702143813.GG23929@totally.trollied.org.uk> <18539.38311.54023.618715@mariner.uk.xensource.com> <486B97D9.1010305@xs4all.nl> <18539.39783.262893.291098@mariner.uk.xensource.com> <486B9EAD.4090009@xs4all.nl> Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <486B9EAD.4090009@xs4all.nl> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefan de Konink Cc: xen-devel@lists.xensource.com, Ian Jackson , John Levon , Gerd Hoffmann , Samuel Thibault , Kevin Wolf List-Id: xen-devel@lists.xenproject.org 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 :|