Il 14/04/2014 17:16, Andreas Färber ha scritto:
>> Huh?! If you ever tried changing the order of PCI devices such as
>> virtio-blk-pci on the command line (or changing between if=virtio and
>> -device virtio-blk-pci) then surely it does change the order of the
>> /dev/vdX the guest sees and will
On 04/15/2014 01:16 AM, Andreas Färber wrote:
> Am 10.04.2014 17:18, schrieb Alexey Kardashevskiy:
>> On 04/11/2014 12:52 AM, Andreas Färber wrote:
>>> Am 10.04.2014 16:40, schrieb Alexey Kardashevskiy:
On 04/10/2014 10:40 PM, Alexander Graf wrote:
>
> Juan, is a different command line
Am 10.04.2014 17:18, schrieb Alexey Kardashevskiy:
> On 04/11/2014 12:52 AM, Andreas Färber wrote:
>> Am 10.04.2014 16:40, schrieb Alexey Kardashevskiy:
>>> On 04/10/2014 10:40 PM, Alexander Graf wrote:
Juan, is a different command line device order supposed to work with
migration?
>
On 04/11/2014 12:52 AM, Andreas Färber wrote:
> Am 10.04.2014 16:40, schrieb Alexey Kardashevskiy:
>> On 04/10/2014 10:40 PM, Alexander Graf wrote:
>>>
>>> Juan, is a different command line device order supposed to work with
>>> migration?
>>
>>
>> We discussed this on IRC with Paolo and the conclu
Am 10.04.2014 16:40, schrieb Alexey Kardashevskiy:
> On 04/10/2014 10:40 PM, Alexander Graf wrote:
>>
>> Juan, is a different command line device order supposed to work with
>> migration?
>
>
> We discussed this on IRC with Paolo and the conclusion is that yes, the
> order should not matter.
Huh
On 04/10/2014 10:40 PM, Alexander Graf wrote:
>
> On 14.03.14 05:18, Alexey Kardashevskiy wrote:
>> At the moment sPAPR IOMMU table is a device which participates in
>> a migration stream. Normally QEMU uses a get_dev_path() hook from
>> the device's bus to compose the section name and @instance_i
On 14.03.14 05:18, Alexey Kardashevskiy wrote:
At the moment sPAPR IOMMU table is a device which participates in
a migration stream. Normally QEMU uses a get_dev_path() hook from
the device's bus to compose the section name and @instance_id which are
used to match the section to the real device.
At the moment sPAPR IOMMU table is a device which participates in
a migration stream. Normally QEMU uses a get_dev_path() hook from
the device's bus to compose the section name and @instance_id which are
used to match the section to the real device. This works till the user
changes the device order
