From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexandre Bique <bique.alexandre@gmail.com>
Cc: Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] ATAPI pass through v2
Date: Tue, 07 Jul 2009 18:01:05 -0500 [thread overview]
Message-ID: <4A53D3B1.2020903@codemonkey.ws> (raw)
In-Reply-To: <5d3bb3090907071550s6e832c45k804bca769aa57f70@mail.gmail.com>
Alexandre Bique wrote:
> On Tue, Jul 7, 2009 at 10:44 PM, Paul Brook<paul@codesourcery.com> wrote:
>
>>>> I expect that running qemu as root counts as a 'bad idea' (I gather
>>>> that commands are filtered when running as a regular user), but even so,
>>>> I wonder if guests should be prevented from performing firmware updates?
>>>>
>>> Yeps.
>>>
>> I disagree. Upgrading the firmware from within the guest sounds like a
>> legitimate use, especially given the proliferation of proprietary windows-
>> only upgrade utilities.
>>
>
> Maybe we could agree on a switch to forward/block this command ?
>
No need for a switch IMHO. If a user is doing pass through, they ought
to expect that the guest has direct access to the device.
The fact that we can prevent this with ATAPI is a special case. When we
eventually merge in VT-d based PCI pass through, we would not be able to
enforce this sort of switch. That would result in confusion on the part
of users.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-07-07 23:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 18:31 [Qemu-devel] [PATCH 0/5] ATAPI pass through v2 Bique Alexandre
2009-07-07 20:03 ` Stuart Brady
2009-07-07 21:21 ` Alexandre Bique
2009-07-07 22:44 ` Paul Brook
2009-07-07 22:50 ` Alexandre Bique
2009-07-07 23:01 ` Anthony Liguori [this message]
2009-07-07 23:15 ` Stuart Brady
2009-07-08 16:09 ` Ian Jackson
2009-07-08 16:38 ` Avi Kivity
2009-07-08 17:28 ` Carl-Daniel Hailfinger
2009-07-08 18:03 ` Anthony Liguori
2009-07-08 18:09 ` Avi Kivity
2009-07-08 17:20 ` Anthony Liguori
2009-07-08 17:48 ` Vincent Hanquez
2009-07-08 18:06 ` Anthony Liguori
2009-07-07 22:58 ` Anthony Liguori
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=4A53D3B1.2020903@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=bique.alexandre@gmail.com \
--cc=paul@codesourcery.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: 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).