Alexander Graf writes:
> On 12.07.2012, at 10:17, Markus Armbruster wrote:
>
>> [Alex's illegibly long lines wrapped]
>>
>> Alexander Graf writes:
>>
>>> On 09.07.2012, at 10:50, Markus Armbruster wrote:
>>>
Alexander Graf writes:
> We've had support for creating AHCI devices
On 12.07.2012, at 10:17, Markus Armbruster wrote:
> [Alex's illegibly long lines wrapped]
>
> Alexander Graf writes:
>
>> On 09.07.2012, at 10:50, Markus Armbruster wrote:
>>
>>> Alexander Graf writes:
>>>
We've had support for creating AHCI devices using -device for a while now,
Alexander Graf writes:
> On 12.07.2012, at 13:09, Markus Armbruster wrote:
>
>> Alexander Graf writes:
>>
>>> On 12.07.2012, at 10:17, Markus Armbruster wrote:
>>>
[Alex's illegibly long lines wrapped]
Alexander Graf writes:
> On 09.07.2012, at 10:50, Markus Armbrust
Il 12/07/2012 13:09, Markus Armbruster ha scritto:
>> >
>> > It isn't. AHCI is on the same level as IDE. They both speak ATA, but
>> > the guest os interface is completely different. You can write a
>> > generic IDE driver, but that won't be able to talk to an AHCI
>> > controller in AHCI mode. You
On 12.07.2012, at 13:09, Markus Armbruster wrote:
> Alexander Graf writes:
>
>> On 12.07.2012, at 10:17, Markus Armbruster wrote:
>>
>>> [Alex's illegibly long lines wrapped]
>>>
>>> Alexander Graf writes:
>>>
On 09.07.2012, at 10:50, Markus Armbruster wrote:
> Alexander Graf
Alexander Graf writes:
> On 12.07.2012, at 10:17, Markus Armbruster wrote:
>
>> [Alex's illegibly long lines wrapped]
>>
>> Alexander Graf writes:
>>
>>> On 09.07.2012, at 10:50, Markus Armbruster wrote:
>>>
Alexander Graf writes:
> We've had support for creating AHCI devices
Gerd Hoffmann writes:
> Hi,
>
>> What I'd like to avoid is casual users setting up new guests with our
>> shiny new q35 board getting their IDE drives connected to some slow, old
>> controller just because they haven't discovered that if=ide doesn't cut
>> it anymore, and they need to use if=ah
Hi,
> What I'd like to avoid is casual users setting up new guests with our
> shiny new q35 board getting their IDE drives connected to some slow, old
> controller just because they haven't discovered that if=ide doesn't cut
> it anymore, and they need to use if=ahci now.
That will not work. a
On 12.07.2012, at 10:17, Markus Armbruster wrote:
> [Alex's illegibly long lines wrapped]
>
> Alexander Graf writes:
>
>> On 09.07.2012, at 10:50, Markus Armbruster wrote:
>>
>>> Alexander Graf writes:
>>>
We've had support for creating AHCI devices using -device for a while now,
[Alex's illegibly long lines wrapped]
Alexander Graf writes:
> On 09.07.2012, at 10:50, Markus Armbruster wrote:
>
>> Alexander Graf writes:
>>
>>> We've had support for creating AHCI devices using -device for a while now,
>>> but it's cumbersome to users. We really should provide an easier wa
On 09.07.2012, at 10:50, Markus Armbruster wrote:
> Alexander Graf writes:
>
>> We've had support for creating AHCI devices using -device for a while now,
>> but it's cumbersome to users. We really should provide an easier way for
>> them to leverage the power of AHCI!
>>
>> So let's introduce
On 09.07.2012, at 13:19, Markus Armbruster wrote:
> Alexander Graf writes:
>
>> On 09.07.2012, at 13:06, Markus Armbruster wrote:
>>
>>> Kevin Wolf writes:
>>>
Am 09.07.2012 10:50, schrieb Markus Armbruster:
> Alexander Graf writes:
>
>> We've had support for creating AHCI
Alexander Graf writes:
> On 09.07.2012, at 13:06, Markus Armbruster wrote:
>
>> Kevin Wolf writes:
>>
>>> Am 09.07.2012 10:50, schrieb Markus Armbruster:
Alexander Graf writes:
> We've had support for creating AHCI devices using -device for a while now,
> but it's cumbersome
On 09.07.2012, at 13:06, Markus Armbruster wrote:
> Kevin Wolf writes:
>
>> Am 09.07.2012 10:50, schrieb Markus Armbruster:
>>> Alexander Graf writes:
>>>
We've had support for creating AHCI devices using -device for a while now,
but it's cumbersome to users. We really should provid
Kevin Wolf writes:
> Am 09.07.2012 10:50, schrieb Markus Armbruster:
>> Alexander Graf writes:
>>
>>> We've had support for creating AHCI devices using -device for a while now,
>>> but it's cumbersome to users. We really should provide an easier way for
>>> them to leverage the power of AHCI!
>
Gerd Hoffmann writes:
> Hi,
>
>>> If -hda has the semantics of "create an IDE device", then no, we can't
>>> change it. It doesn't however. IIRC on -M pseries -hda creates SCSI
>>> devices. On s390 -hda creates virtio devices. So if on -M q35 -hda would
>>> create if=ahci, I don't see how th
Hi,
>> If -hda has the semantics of "create an IDE device", then no, we can't
>> change it. It doesn't however. IIRC on -M pseries -hda creates SCSI devices.
>> On s390 -hda creates virtio devices. So if on -M q35 -hda would create
>> if=ahci, I don't see how that breaks the CLI.
>
> It does
On Mon, Jul 09, 2012 at 12:03:49PM +0200, Kevin Wolf wrote:
> Am 09.07.2012 12:02, schrieb Gleb Natapov:
> > On Mon, Jul 09, 2012 at 11:52:32AM +0200, Kevin Wolf wrote:
> >>> If -hda has the semantics of "create an IDE device", then no, we can't
> >>> change it. It doesn't however. IIRC on -M pser
Am 09.07.2012 12:02, schrieb Gleb Natapov:
> On Mon, Jul 09, 2012 at 11:52:32AM +0200, Kevin Wolf wrote:
>>> If -hda has the semantics of "create an IDE device", then no, we can't
>>> change it. It doesn't however. IIRC on -M pseries -hda creates SCSI
>>> devices. On s390 -hda creates virtio devi
On Mon, Jul 09, 2012 at 11:52:32AM +0200, Kevin Wolf wrote:
> > If -hda has the semantics of "create an IDE device", then no, we can't
> > change it. It doesn't however. IIRC on -M pseries -hda creates SCSI
> > devices. On s390 -hda creates virtio devices. So if on -M q35 -hda would
> > create i
Am 09.07.2012 11:36, schrieb Alexander Graf:
>
> On 09.07.2012, at 11:27, Kevin Wolf wrote:
>
>> Am 09.07.2012 11:13, schrieb Alexander Graf:
>>>
>>> On 09.07.2012, at 11:11, Kevin Wolf wrote:
Can we even make it the default with q35 as long as our AHCI controller
doesn't also expose a
On Mon, Jul 09, 2012 at 11:44:11AM +0200, Alexander Graf wrote:
>
> On 09.07.2012, at 11:41, Gleb Natapov wrote:
>
> > On Mon, Jul 09, 2012 at 11:36:47AM +0200, Alexander Graf wrote:
> >>
> >> On 09.07.2012, at 11:27, Kevin Wolf wrote:
> >>
> >>> Am 09.07.2012 11:13, schrieb Alexander Graf:
> >
On 09.07.2012, at 11:41, Gleb Natapov wrote:
> On Mon, Jul 09, 2012 at 11:36:47AM +0200, Alexander Graf wrote:
>>
>> On 09.07.2012, at 11:27, Kevin Wolf wrote:
>>
>>> Am 09.07.2012 11:13, schrieb Alexander Graf:
On 09.07.2012, at 11:11, Kevin Wolf wrote:
> Am 09.07.2012 10:
On Mon, Jul 09, 2012 at 11:36:47AM +0200, Alexander Graf wrote:
>
> On 09.07.2012, at 11:27, Kevin Wolf wrote:
>
> > Am 09.07.2012 11:13, schrieb Alexander Graf:
> >>
> >> On 09.07.2012, at 11:11, Kevin Wolf wrote:
> >>
> >>> Am 09.07.2012 10:50, schrieb Markus Armbruster:
> Alexander Graf
On 09.07.2012, at 11:27, Kevin Wolf wrote:
> Am 09.07.2012 11:13, schrieb Alexander Graf:
>>
>> On 09.07.2012, at 11:11, Kevin Wolf wrote:
>>
>>> Am 09.07.2012 10:50, schrieb Markus Armbruster:
Alexander Graf writes:
> We've had support for creating AHCI devices using -device fo
Am 09.07.2012 11:13, schrieb Alexander Graf:
>
> On 09.07.2012, at 11:11, Kevin Wolf wrote:
>
>> Am 09.07.2012 10:50, schrieb Markus Armbruster:
>>> Alexander Graf writes:
>>>
We've had support for creating AHCI devices using -device for a while now,
but it's cumbersome to users. We re
On 09.07.2012, at 11:11, Kevin Wolf wrote:
> Am 09.07.2012 10:50, schrieb Markus Armbruster:
>> Alexander Graf writes:
>>
>>> We've had support for creating AHCI devices using -device for a while now,
>>> but it's cumbersome to users. We really should provide an easier way for
>>> them to lever
Am 09.07.2012 10:50, schrieb Markus Armbruster:
> Alexander Graf writes:
>
>> We've had support for creating AHCI devices using -device for a while now,
>> but it's cumbersome to users. We really should provide an easier way for
>> them to leverage the power of AHCI!
>>
>> So let's introduce a ne
Alexander Graf writes:
> We've had support for creating AHCI devices using -device for a while now,
> but it's cumbersome to users. We really should provide an easier way for
> them to leverage the power of AHCI!
>
> So let's introduce a new if= option to -drive, giving users the same
> command l
We've had support for creating AHCI devices using -device for a while now,
but it's cumbersome to users. We really should provide an easier way for
them to leverage the power of AHCI!
So let's introduce a new if= option to -drive, giving users the same
command line experience as for scsi or ide.
30 matches
Mail list logo
