er(IR 2008?)
which support sr-iov , but there is not any document which describes
the steps to config. I wonder if your have any clues to help? thanks.
Regards.
Suya.
2011/10/26, Hannes Reinecke :
> On 10/26/2011 06:40 AM, ya su wrote:
>> hi, hannes:
>>
>> I want to use N
hi, hannes:
I want to use NPIV with qemu-kvm, I issued the following command:
echo ':' >
/sys/class/fc_host/host0/vport_create
and it will produce a new host6 and one vport succesfully, but it
does not create any virtual hba pci device. so I don't know
interrupted in the middle of a transaction, some of rams have been
updated, but the others not, do you have any plan for rolling back to
cancel the interrupted transaction? thanks.
Green.
2011/3/9 Yoshiaki Tamura :
> ya su wrote:
>>
>> Yoshi:
>>
>> I think event-tap
Juan:
It's especailly important for ft to be a standalone thread, as it
may cause monitor to be blocked by network problems. what's your
schedule, maybe I can help some.
Yoshi:
in the following code:
+
+s->file = qemu_fopen_ops(s, ft_trans_put_buffer, ft_trans_get_buffer,
+
in ft transactoins?
Green.
2011/3/9 Yoshiaki Tamura :
> ya su wrote:
>>
>> 2011/3/8 Yoshiaki Tamura:
>>>
>>> ya su wrote:
>>>>
>>>> Yokshiaki:
>>>>
>>>> event-tap record block and io wirte events, and replay these
2011/3/8 Yoshiaki Tamura :
> ya su wrote:
>>
>> Yokshiaki:
>>
>> event-tap record block and io wirte events, and replay these on
>> the other side, so block_save_live is useless during the latter ft
>> phase, right? if so, I think it need to process t
Yokshiaki:
event-tap record block and io wirte events, and replay these on
the other side, so block_save_live is useless during the latter ft
phase, right? if so, I think it need to process the following code in
block_save_live function:
if (stage == 1) {
init_blk_migration(mon, f
Yoshiaki:
I have one question about ram_save_live, during migration 3
stage(completation stage), it will call
cpu_physical_memory_set_dirty_tracking(0) to stop recording ram dirty pages.
at the end of migrate_ft_trans_connect function, it will invoke vm_start(),
at this time, cpu_physical_memo
