From: "Richard W.M. Jones" <rjones@redhat.com> To: Sasha Levin <levinsasha928@gmail.com> Cc: Anthony Liguori <anthony@codemonkey.ws>, qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org> Subject: Re: [Qemu-devel] Guest kernel device compatability auto-detection Date: Fri, 26 Aug 2011 09:43:36 +0100 [thread overview] Message-ID: <20110826084336.GB24160@amd.home.annexia.org> (raw) In-Reply-To: <1314338882.3647.13.camel@lappy> On Fri, Aug 26, 2011 at 09:08:02AM +0300, Sasha Levin wrote: > You're thinking about trying to expose all interfaces during boot and > seeing which ones the kernel bites? No, that's a bad idea. A current guest would register that as two disks. It might even try to write to them independently. You need an IDE device which can be promoted to virtio at the request of the guest (so you know the guest understands this type of device). > Another thing that comes to mind is that we could start this project > with a script that given a kernel, it would find the optimal hardware > configuration for it (and the matching QEMU command line). It would be better if the guest could communicate what it needs. But no current guest works that way. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org
WARNING: multiple messages have this Message-ID (diff)
From: "Richard W.M. Jones" <rjones@redhat.com> To: Sasha Levin <levinsasha928@gmail.com> Cc: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org> Subject: Re: [Qemu-devel] Guest kernel device compatability auto-detection Date: Fri, 26 Aug 2011 09:43:36 +0100 [thread overview] Message-ID: <20110826084336.GB24160@amd.home.annexia.org> (raw) In-Reply-To: <1314338882.3647.13.camel@lappy> On Fri, Aug 26, 2011 at 09:08:02AM +0300, Sasha Levin wrote: > You're thinking about trying to expose all interfaces during boot and > seeing which ones the kernel bites? No, that's a bad idea. A current guest would register that as two disks. It might even try to write to them independently. You need an IDE device which can be promoted to virtio at the request of the guest (so you know the guest understands this type of device). > Another thing that comes to mind is that we could start this project > with a script that given a kernel, it would find the optimal hardware > configuration for it (and the matching QEMU command line). It would be better if the guest could communicate what it needs. But no current guest works that way. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org
next prev parent reply other threads:[~2011-08-26 8:43 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-25 5:21 Guest kernel device compatability auto-detection Sasha Levin 2011-08-25 5:21 ` [Qemu-devel] " Sasha Levin 2011-08-25 5:33 ` Avi Kivity 2011-08-25 7:32 ` Richard W.M. Jones 2011-08-25 7:32 ` Richard W.M. Jones 2011-08-25 7:40 ` Sasha Levin 2011-08-25 7:40 ` Sasha Levin 2011-08-25 7:48 ` Richard W.M. Jones 2011-08-25 10:01 ` Richard W.M. Jones 2011-08-25 16:25 ` Decker, Schorschi 2011-08-25 16:25 ` [Qemu-devel] " Decker, Schorschi 2011-08-26 6:22 ` Sasha Levin 2011-08-26 6:22 ` Sasha Levin 2011-08-26 8:04 ` Richard W.M. Jones 2011-08-26 8:04 ` [Qemu-devel] " Richard W.M. Jones 2011-08-26 10:18 ` Sasha Levin 2011-08-26 10:18 ` Sasha Levin 2011-08-26 10:28 ` Richard W.M. Jones 2011-08-26 10:28 ` Richard W.M. Jones 2011-08-25 21:48 ` Anthony Liguori 2011-08-25 21:48 ` [Qemu-devel] " Anthony Liguori 2011-08-26 6:08 ` Sasha Levin 2011-08-26 6:08 ` [Qemu-devel] " Sasha Levin 2011-08-26 8:43 ` Richard W.M. Jones [this message] 2011-08-26 8:43 ` Richard W.M. Jones 2011-08-26 8:40 ` Richard W.M. Jones
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=20110826084336.GB24160@amd.home.annexia.org \ --to=rjones@redhat.com \ --cc=anthony@codemonkey.ws \ --cc=kvm@vger.kernel.org \ --cc=levinsasha928@gmail.com \ --cc=qemu-devel@nongnu.org \ /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: linkBe 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.