From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: "Marcel Apfelbaum" <marcel.a@redhat.com>,
seabios@seabios.org, qemu-devel@nongnu.org,
"Michael S. Tsirkin" <mst@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [SeaBIOS] [PATCH] don't expose pvpanic device in the UI
Date: Tue, 6 Aug 2013 04:03:17 -0400 (EDT) [thread overview]
Message-ID: <1394462966.9192671.1375776197295.JavaMail.root@redhat.com> (raw)
In-Reply-To: <20130806073406.GL10891@redhat.com>
----- Original Message -----
From: "Gleb Natapov" <gleb@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>, "Marcel Apfelbaum" <marcel.a@redhat.com>, seabios@seabios.org, qemu-devel@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>, "Paolo Bonzini" <pbonzini@redhat.com>, "Eric Blake" <eblake@redhat.com>, "Andreas Färber" <afaerber@suse.de>
Sent: Tuesday, August 6, 2013 5:34:06 PM
Subject: Re: [SeaBIOS] [PATCH] don't expose pvpanic device in the UI
On Mon, Aug 05, 2013 at 09:32:18PM +0300, Michael S. Tsirkin wrote:
> > > As you see we do let people change many parameters
> > > that do affect activation.
> > By editing XML user can shoot himself in the foot, we should not prevent
> > that.
>
> So that's what I'm saying basically.
> At the moment there's no way to remove this device from XML.
> That's just wrong.
Can say the same about PV acpi hotpulg device.
> In QEMU, we have a standard way to specify devices with -device.
> That should be the interface for anything new really
> unless there's a very compelling reason for something else.
We are disagree on compelling reason in this case obviously.
> *Not* building it into the PC machine type.
>
> > It should not be required though.
>
> libvirt can pass -device pvpanic by default if nothing
> is specified in XML. That discussion really has to happen
> on libvirt list.
>
As Paolo said you are just pushing the "problem" up the stack
where it is harder to "solve". I put "problem" and "solve" in
quotes because I disagree that the problem that need to be solved
is identified correctly. The correct problem to be solved IMO is
writing Windows driver for the device.
[VR]
This one shouldn't be too complicated. Can be done on weekend.
--
Gleb.
_______________________________________________
SeaBIOS mailing list
SeaBIOS@seabios.org
http://www.seabios.org/mailman/listinfo/seabios
next prev parent reply other threads:[~2013-08-06 8:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1375688843-19573-1-git-send-email-hutao@cn.fujitsu.com>
[not found] ` <20130805081055.GA356@redhat.com>
[not found] ` <20130805081617.GB2258@redhat.com>
[not found] ` <20130805091826.GA877@redhat.com>
[not found] ` <20130805092044.GH2258@redhat.com>
[not found] ` <20130805150333.GC877@redhat.com>
[not found] ` <20130805160421.GB15901@redhat.com>
2013-08-05 18:32 ` [Qemu-devel] [SeaBIOS] [PATCH] don't expose pvpanic device in the UI Michael S. Tsirkin
2013-08-06 7:34 ` Gleb Natapov
2013-08-06 8:03 ` Vadim Rozenfeld [this message]
2013-08-06 8:05 ` Gleb Natapov
2013-08-06 8:14 ` Vadim Rozenfeld
2013-08-06 8:38 ` Gleb Natapov
[not found] ` <51FF6A79.9060603@redhat.com>
[not found] ` <703333176.9515483.1375697447963.JavaMail.root@redhat.com>
[not found] ` <20130805151723.GF877@redhat.com>
[not found] ` <1970367422.9695773.1375718517492.JavaMail.root@redhat.com>
[not found] ` <20130805161833.GA4244@redhat.com>
[not found] ` <51FFD6CE.5090302@redhat.com>
[not found] ` <20130805182628.GC4244@redhat.com>
[not found] ` <20130806072152.GK10891@redhat.com>
2013-08-06 8:33 ` Michael S. Tsirkin
2013-08-06 8:36 ` Gleb Natapov
2013-08-06 8:45 ` Andreas Färber
2013-08-06 9:15 ` Michael S. Tsirkin
2013-08-06 9:20 ` Gleb Natapov
2013-08-06 10:04 ` Michael S. Tsirkin
2013-08-06 17:53 ` Andreas Färber
2013-08-06 9:56 ` Markus Armbruster
2013-08-06 10:11 ` Michael S. Tsirkin
2013-08-06 9:21 ` Michael S. Tsirkin
2013-08-06 9:32 ` Gleb Natapov
2013-08-06 10:19 ` Michael S. Tsirkin
2013-08-06 10:44 ` Gleb Natapov
2013-08-06 11:03 ` Andreas Färber
2013-08-06 11:16 ` Gleb Natapov
2013-08-06 11:48 ` Markus Armbruster
2013-08-06 12:03 ` Gleb Natapov
2013-08-06 12:09 ` Michael S. Tsirkin
2013-08-06 12:45 ` Andreas Färber
2013-08-07 8:17 ` Stefan Hajnoczi
2013-08-06 11:54 ` Gerd Hoffmann
2013-08-06 12:08 ` Gleb Natapov
2013-08-06 10:35 ` Andreas Färber
2013-08-06 11:00 ` Gleb Natapov
2013-08-06 11:23 ` Andreas Färber
2013-08-06 12:00 ` Gleb Natapov
2013-08-06 12:02 ` Gerd Hoffmann
2013-08-06 12:05 ` Michael S. Tsirkin
2013-08-06 12:17 ` Gleb Natapov
2013-08-06 17:22 ` Andreas Färber
2013-08-06 12:08 ` Michael S. Tsirkin
2013-08-06 12:19 ` Gleb Natapov
2013-08-06 9:26 ` Hu Tao
2013-08-06 9:29 ` Gleb Natapov
2013-08-06 10:13 ` Michael S. Tsirkin
2013-08-06 10:14 ` Gleb Natapov
2013-08-06 10:23 ` Michael S. Tsirkin
2013-08-06 10:28 ` Gleb Natapov
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=1394462966.9192671.1375776197295.JavaMail.root@redhat.com \
--to=vrozenfe@redhat.com \
--cc=afaerber@suse.de \
--cc=gleb@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcel.a@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).