Am 11.04.2015 um 17:00 schrieb Peter Lieven:
Am 11.04.2015 um 15:11 schrieb Peter Lieven:
Am 09.04.2015 um 17:17 schrieb Paolo Bonzini:
On 09/04/2015 16:54, Peter Lieven wrote:
#define BM_MIGRATION_COMPAT_STATUS_BITS \
(IDE_RETRY_DMA | IDE_RETRY_PIO | \
IDE_RETRY_READ | IDE_R
Am 11.04.2015 um 15:11 schrieb Peter Lieven:
> Am 09.04.2015 um 17:17 schrieb Paolo Bonzini:
>> On 09/04/2015 16:54, Peter Lieven wrote:
>>> #define BM_MIGRATION_COMPAT_STATUS_BITS \
>>> (IDE_RETRY_DMA | IDE_RETRY_PIO | \
>>> IDE_RETRY_READ | IDE_RETRY_FLUSH)
>>>
>>> Why is there no
Am 09.04.2015 um 17:17 schrieb Paolo Bonzini:
>
> On 09/04/2015 16:54, Peter Lieven wrote:
>> #define BM_MIGRATION_COMPAT_STATUS_BITS \
>> (IDE_RETRY_DMA | IDE_RETRY_PIO | \
>> IDE_RETRY_READ | IDE_RETRY_FLUSH)
>>
>> Why is there no IDE_RETRY_WRITE ?
> Because that's represented by
On 09/04/2015 16:54, Peter Lieven wrote:
>
> #define BM_MIGRATION_COMPAT_STATUS_BITS \
> (IDE_RETRY_DMA | IDE_RETRY_PIO | \
> IDE_RETRY_READ | IDE_RETRY_FLUSH)
>
> Why is there no IDE_RETRY_WRITE ?
Because that's represented by none of read and flush being set. :)
> Honestly,
Am 09.04.2015 um 15:43 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 07.04.2015 um 21:01 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 07.04.2015 um 17:29 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Hi David,
Am 07
* Peter Lieven (p...@kamp.de) wrote:
> Am 07.04.2015 um 21:01 schrieb Dr. David Alan Gilbert:
> >* Peter Lieven (p...@kamp.de) wrote:
> >>Am 07.04.2015 um 17:29 schrieb Dr. David Alan Gilbert:
> >>>* Peter Lieven (p...@kamp.de) wrote:
> Hi David,
>
> Am 07.04.2015 um 10:43 schrieb Dr.
Am 09.04.2015 um 14:49 schrieb Peter Lieven:
Am 07.04.2015 um 21:01 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 07.04.2015 um 17:29 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Hi David,
Am 07.04.2015 um 10:43 schrieb Dr. David Alan Gilbert
On 09/04/2015 14:46, Peter Lieven wrote:
>>>
>>>
>>
>> BMDMA is the PCI HBA for IDE, I think it's the default for most
>> machines that aren't using the AHCI HBA.
>>
>> To get ISA, try launching with the machine "isapc" which will force
>> it, or add the device manually, it's named "isa-ide".
>>
Am 07.04.2015 um 21:01 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Am 07.04.2015 um 17:29 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Hi David,
Am 07.04.2015 um 10:43 schrieb Dr. David Alan Gilbert:
Any particular workload or reproducer?
Wor
Am 07.04.2015 um 21:13 schrieb John Snow:
On 04/07/2015 03:02 PM, Peter Lieven wrote:
Am 07.04.2015 um 20:56 schrieb John Snow:
On 04/07/2015 02:44 PM, Peter Lieven wrote:
Am 07.04.2015 um 17:29 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Hi David,
Am 07.04.2015
Am 07.04.2015 um 22:05 schrieb Paolo Bonzini:
On 07/04/2015 20:44, Peter Lieven wrote:
Has the cdrom the power of taking down the bus?
IDE can only issue one command per bus, so hda/hdb can take down each
other, and hdc/hdd can take down each other. However, hda cannot take
down hdc and vice
Am 07.04.2015 um 21:13 schrieb John Snow:
On 04/07/2015 03:02 PM, Peter Lieven wrote:
Am 07.04.2015 um 20:56 schrieb John Snow:
On 04/07/2015 02:44 PM, Peter Lieven wrote:
Am 07.04.2015 um 17:29 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Hi David,
Am 07.04.2015
On 07/04/2015 20:44, Peter Lieven wrote:
> Has the cdrom the power of taking down the bus?
IDE can only issue one command per bus, so hda/hdb can take down each
other, and hdc/hdd can take down each other. However, hda cannot take
down hdc and vice versa---so likely the CDROM cannot take down t
On 04/07/2015 03:02 PM, Peter Lieven wrote:
Am 07.04.2015 um 20:56 schrieb John Snow:
On 04/07/2015 02:44 PM, Peter Lieven wrote:
Am 07.04.2015 um 17:29 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Hi David,
Am 07.04.2015 um 10:43 schrieb Dr. David Alan Gilbert:
Am 07.04.2015 um 21:01 schrieb Dr. David Alan Gilbert:
> * Peter Lieven (p...@kamp.de) wrote:
>> Am 07.04.2015 um 17:29 schrieb Dr. David Alan Gilbert:
>>> * Peter Lieven (p...@kamp.de) wrote:
Hi David,
Am 07.04.2015 um 10:43 schrieb Dr. David Alan Gilbert:
Any particular wo
Am 07.04.2015 um 20:56 schrieb John Snow:
>
>
> On 04/07/2015 02:44 PM, Peter Lieven wrote:
>> Am 07.04.2015 um 17:29 schrieb Dr. David Alan Gilbert:
>>> * Peter Lieven (p...@kamp.de) wrote:
Hi David,
Am 07.04.2015 um 10:43 schrieb Dr. David Alan Gilbert:
Any particular work
* Peter Lieven (p...@kamp.de) wrote:
> Am 07.04.2015 um 17:29 schrieb Dr. David Alan Gilbert:
> > * Peter Lieven (p...@kamp.de) wrote:
> >> Hi David,
> >>
> >> Am 07.04.2015 um 10:43 schrieb Dr. David Alan Gilbert:
> >> Any particular workload or reproducer?
> > Workload is almost zero. I t
On 04/07/2015 02:44 PM, Peter Lieven wrote:
Am 07.04.2015 um 17:29 schrieb Dr. David Alan Gilbert:
* Peter Lieven (p...@kamp.de) wrote:
Hi David,
Am 07.04.2015 um 10:43 schrieb Dr. David Alan Gilbert:
Any particular workload or reproducer?
Workload is almost zero. I try to figure out if th
Am 07.04.2015 um 17:14 schrieb Paolo Bonzini:
>
> On 07/04/2015 17:11, Peter Lieven wrote:
>>> I'm not sure at what kernel version the switch is, but newer kernels use
>>> some
>>> code shared with the newer SATA world (libata?) where as older kernels had
>>> separate IDE code, so the behaviour o
Am 07.04.2015 um 17:29 schrieb Dr. David Alan Gilbert:
> * Peter Lieven (p...@kamp.de) wrote:
>> Hi David,
>>
>> Am 07.04.2015 um 10:43 schrieb Dr. David Alan Gilbert:
>> Any particular workload or reproducer?
> Workload is almost zero. I try to figure out if there is a way to trigger
* Peter Lieven (p...@kamp.de) wrote:
> Hi David,
>
> Am 07.04.2015 um 10:43 schrieb Dr. David Alan Gilbert:
> Any particular workload or reproducer?
> >>> Workload is almost zero. I try to figure out if there is a way to trigger
> >>> it.
> >>>
> >>> Maybe playing a role: Machine type is -M
On 07/04/2015 17:11, Peter Lieven wrote:
> > I'm not sure at what kernel version the switch is, but newer kernels use
> > some
> > code shared with the newer SATA world (libata?) where as older kernels had
> > separate IDE code, so the behaviour of the two can be quite different.
>
> Thats a go
Hi David,
Am 07.04.2015 um 10:43 schrieb Dr. David Alan Gilbert:
Any particular workload or reproducer?
>>> Workload is almost zero. I try to figure out if there is a way to trigger
>>> it.
>>>
>>> Maybe playing a role: Machine type is -M pc1.2 and we set -kvmclock as
>>> CPU flag since kvmc
* Peter Lieven (p...@kamp.de) wrote:
> Am 06.04.2015 um 21:02 schrieb Peter Lieven:
> > Am 06.04.2015 um 20:50 schrieb John Snow:
> >>
> >> On 04/06/2015 02:47 PM, Peter Lieven wrote:
> >>> Hi all,
> >>>
> >>> is there a known issue in Qemu 2.2.1 where IDE stalls sometimes after a
> >>> migration
Am 06.04.2015 um 21:02 schrieb Peter Lieven:
> Am 06.04.2015 um 20:50 schrieb John Snow:
>>
>> On 04/06/2015 02:47 PM, Peter Lieven wrote:
>>> Hi all,
>>>
>>> is there a known issue in Qemu 2.2.1 where IDE stalls sometimes after a
>>> migration with Qemu 2.2.1?
>>> The migration succeeds, but it s
Am 06.04.2015 um 20:50 schrieb John Snow:
>
>
> On 04/06/2015 02:47 PM, Peter Lieven wrote:
>> Hi all,
>>
>> is there a known issue in Qemu 2.2.1 where IDE stalls sometimes after a
>> migration with Qemu 2.2.1?
>> The migration succeeds, but it seems that the complete I/O is hanging. This
>> happ
On 04/06/2015 02:47 PM, Peter Lieven wrote:
Hi all,
is there a known issue in Qemu 2.2.1 where IDE stalls sometimes after a
migration with Qemu 2.2.1?
The migration succeeds, but it seems that the complete I/O is hanging. This
happens only sometimes
and only with extreme old Linux Guests (SL
27 matches
Mail list logo