qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: David Kozub <zub@linux.fjfi.cvut.cz>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, kwolf@redhat.com
Subject: Re: [Qemu-devel] Emulation of TCG OPAL self-encrypting drive
Date: Wed, 16 Jan 2019 17:35:40 -0500	[thread overview]
Message-ID: <e2e14237-32be-8e3d-242c-c19e98d04d60@redhat.com> (raw)
In-Reply-To: <20190107091618.GD27089@stefanha-x1.localdomain>



On 1/7/19 4:16 AM, Stefan Hajnoczi wrote:
> On Sat, Jan 05, 2019 at 07:27:03PM +0100, David Kozub wrote:
>> Hi,
>>
>> Can QEMU emulate an OPAL disk? The only relevant thing I found is a post
>> from 2017 about TPM that mentions OPAL:
>> https://lists.gnu.org/archive/html/qemu-devel/2017-07/msg04586.html
> 
> CCing John Snow (IDE/ATA) and Kevin Wolf (QEMU block layer).
> 
>> specifically this bit:
>>
>>> Well, at some point somebody's going to want us to implement this,
>>> but... they can do that when they do that.
>>
>> So I assume it is not implemented. (?)
> 
> Right.
> 
>> I agree with the sentiment expressed in the mail linked above w.r.t. OPAL
>> security. I'm interested in this from SW development/debugging/fiddling
>> perspective. A sufficient solution for me would not add any real encryption
> 
> QEMU supports LUKS encrypted disk images so no new code is needed for
> the actual encryption.
> 
>> but would respond to the various OPAL commands send via ATA TRUSTED
>> SEND/RECEIVE commands.
>>
>> In fact, a more generic solution would work for me: If it was possible to
>> send ATA commands from QEMU to a separate process which could then handle
>> them as it liked and reply back to QEMU. This could be useful for other
>> fiddling/debugging situations too.
> 
> Might as well implement it in QEMU so users can easily take advantage of
> it without setting up external software.
> 
>> Or, just a pass-through to a block device in the host - but a pass-through
>> that would allow OPAL commands.
> 
> You can pass through a storage controller using PCI passthrough or you
> can pass through a SCSI LUN, but there is no ATA passthrough.
> 
>> I'm grateful for any hints/ideas. Perhaps something like this is already
>> possible with QEMU?
>>
>> Best regards,
>> David
>>

I can answer some questions about the ATA layer, but I'm not well read
on OPAL or the interrelationship between the two.

We don't have an ATA-style passthrough in QEMU right now and nobody has
ever asked! Would you mind elaborating for me what kind of setup you're
looking to accomplish and maybe I can give you some better hints?

--js

  parent reply	other threads:[~2019-01-16 22:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05 18:27 [Qemu-devel] Emulation of TCG OPAL self-encrypting drive David Kozub
2019-01-07  9:16 ` Stefan Hajnoczi
2019-01-09 23:05   ` David Kozub
2019-01-10 10:32     ` Stefan Hajnoczi
2019-01-16 22:35   ` John Snow [this message]
2019-01-17 23:04     ` David Kozub
2019-01-18  0:01       ` John Snow
2019-01-23 22:39         ` David Kozub
2019-01-23 22:58           ` John Snow
2019-01-24 10:24             ` David Kozub
2019-01-24 17:41               ` John Snow

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=e2e14237-32be-8e3d-242c-c19e98d04d60@redhat.com \
    --to=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=zub@linux.fjfi.cvut.cz \
    /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).