[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH] ATA: Allow WIN_SECURITY_FREEZE_LOCK as nop
From: |
Alexander Graf |
Subject: |
Re: [Qemu-devel] [PATCH] ATA: Allow WIN_SECURITY_FREEZE_LOCK as nop |
Date: |
Thu, 9 Feb 2012 16:01:31 +0100 |
On 09.02.2012, at 15:59, Kevin Wolf wrote:
> Am 09.02.2012 15:49, schrieb Alexander Graf:
>>
>> On 09.02.2012, at 15:28, Kevin Wolf wrote:
>>
>>> Am 30.01.2012 23:29, schrieb Alexander Graf:
>>>> When using Windows 8 with an AHCI disk drive, it issues a blue screen.
>>>> The reason is that WIN_SECURITY_FREEZE_LOCK / CFA_WEAR_LEVEL is not
>>>> supported by our ATA implementation, but Windows expects it to be there.
>>>
>>> Is there anything that makes Windows believe that we support it? The
>>> spec says bits in IDENTIFY word 82 and 128 must be set to indicate
>>> support for the security feature set, and we don't set those.
>>>
>>> Might be just a Windows bug, of course...
>>
>> IIUC it's mandatory in more recent ATA versions, so that's probably why it
>> assumes it's there.
>
> ACS-2 says it's optional for both ATA and ATAPI devices.
Ah, right. I was looking at the "Historical Command Assignments" table and
figured C means it's required, but that of course is wrong.
Then I seriously have no idea why Windows is erroring out here. I mean, it does
work just fine for IDE devices. And we don't tell the guest anything special
for AHCI.
Alex