qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] q35 and ahci


From: Alexander Graf
Subject: Re: [Qemu-devel] q35 and ahci
Date: Tue, 3 Jul 2012 20:52:50 +0200

On 03.07.2012, at 20:46, Jason Baron wrote:

> On Tue, Jul 03, 2012 at 08:41:29PM +0200, Alexander Graf wrote:
>> On 03.07.2012, at 20:38, Jason Baron wrote:
>> 
>>> On Tue, Jul 03, 2012 at 08:25:52PM +0200, Alexander Graf wrote:
>>>> On 03.07.2012, at 18:16, Jason Baron wrote:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> Update on q35 testing with various os's.
>>>>> 
>>>>> Linux
>>>>> -----
>>>>> -RHEL6.3 installs + runs 
>>>>> -Fedora 16 install + runs
>>>>> -Fedora 17 - squashfs errors 
>>>>> running on already installed f17 seems ok.
>>>>> 
>>>>> Windows
>>>>> -------
>>>>> -W7 - install error:
>>>>> 
>>>>> "A required cd/dvd device driver is missing. If you have a
>>>>> driver floppy disk, CD, DVD, or USB flash drive, please insert it now.
>>>>> "
>>>>> 
>>>>> Related to the new ahci controller, since if I go back to an
>>>>> ide conroller it keeps going (albeit the install is *very* slow).
>>>>> 
>>>>> So I'm wondering if we need an ide compatibility mode? Or perhaps, there
>>>>> are other ideas.
>>>> 
>>>> Does it work with AHCI and -M pc? It should. Last time I tried it did at 
>>>> least :).
>>>> 
>>>> 
>>>> Alex
>>>> 
>>>> 
>>> 
>>> Yes, adding the ahci controller to -M pc, I see a disk drive and the
>>> controller show up in the device manager. I read in some of the ahci
>>> commit messages that the cdrom device didn't show up. Did cdrom ever
>>> work with ahci?
>> 
>> It did on Linux at least, yes. Does it work on Linux for you?
>> 
> 
> I meant did a cdrom on the ahci controller configure on windows?
> 
> Yes, Linux seems to be happy with the drive and cdrom on the ahci. See
> my above test results. (ich9-ahci is the default controller for q35).

Ah, good. I don't remember tbh. But I suppose since it doesn't work for you, 
it's broken :). Do you have time to look into it?

There are a bunch of debug #define's in the ide-core and ahci code that should 
be able to point you to where it starts failing. It's probably easiest to take 
it slow and find a way to only have the cdrom attached to ahci. Otherwise the 
debug output will be full of disk stuff :).


Alex




reply via email to

[Prev in Thread] Current Thread [Next in Thread]