All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan de Konink <skinkie@xs4all.nl>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: John Levon <levon@movementarian.org>,
	xen-devel@lists.xensource.com, Gerd Hoffmann <kraxel@redhat.com>,
	Kevin Wolf <kwolf@suse.de>,
	Samuel Thibault <samuel.thibault@eu.citrix.com>
Subject: Re: Re: [PATCH] qemu-xen: Fix PV segfault
Date: Wed, 02 Jul 2008 17:28:45 +0200	[thread overview]
Message-ID: <486B9EAD.4090009@xs4all.nl> (raw)
In-Reply-To: <18539.39783.262893.291098@mariner.uk.xensource.com>

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.

>> In any case, if anyone suggests that userspace processes are bad and 
>> fragile, then these persons will not like any processes that support 
>> hardware emulation, such as tapdisk.
> 
> You're quite right.

If tapdisk is a problem, then I'm happy to point at the breakage that 
will occur with loopback devices (NFS + loopback + highio = boom). But 
it is really interesting people talk about 'user-processes' as if they 
are broken by default. I disagree, even if a iscsi setup for each used 
disk a kernel process is running. So one way or the other, dom0 is 
needed to provide access to storage one way or the other. Migrating the 
'storage providers' to DomS would be an interesting idea, but the need 
for it, I don't quite see.


Stefan

  reply	other threads:[~2008-07-02 15:28 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 [this message]
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
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=486B9EAD.4090009@xs4all.nl \
    --to=skinkie@xs4all.nl \
    --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=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.