hi, Qasim:
pls refer to 'qemu-options.hx' and the big switch in 'vl.c'.
Thanks,
Jules.
At 2014-03-28 14:25:43,"Qasim Maqbool" wrote:
Hi,
I need to add a few command line options to QEMU. However, I am yet to
determine how QEMU takes input from the command line and parses the optio
At 2013-10-01 06:16:34,"Eric Blake" wrote: >On 09/29/2013
02:14 PM, Jules Wang wrote: >> Add an option '-f' to migration cmdline. >>
Indicating whether to enable fault tolerant or not. >> >> Signed-off-by: Jules
Wang >> --- >> .help = "migrate to
URI (using -d to not wait for
hi,
>At the moment in your implementation the prefetch buffer can be very large
>(several copies of guest memory size) >are you planning to address this
>issue? >I agree but we need some way to notify the user of such problem.
This issue has been handled (maybe not in the best way). The pref
hi,
At 2013-09-10 22:19:48,"Juan Quintela" wrote:
>> @@ -112,13 +113,24 @@ static void process_incoming_migration_co(void *opaque)
>> {
>> QEMUFile *f = opaque;
>> int ret;
>> +int count = 0;
>>
>> -ret = qemu_loadvm_state(f);
>> -qemu_fclose(f);
>> -if (ret < 0) {
hi,
>> +bool create = false;
> >This variable is never set.
It is set in the following 'if' block.
+create = true;<<===
>> -migration_bitmap = bitmap_new(ram_pages);
>> -bitmap_set(migration_bitmap, 0, ram_pages);
>> -migration_dirty_pages = ram_pages;
>> +i
> Shouldn't this be in migration_state? Just wondering. And yes, I
> don't see either a trivial place how to get it. get_current_migration()?
That's a better idea, I will put 'ft_enabled' in MigrationState Struct.
> I think for the outgoing side it should just be "migrate -f tcp:foo:".
Hi,
>The first is that if the VM failure happen in the middle on the live migration
> >the backup VM state will be inconsistent which means you can't failover to
>it.
Yes, I have concerned about this problem. That is why we need a prefetch buffer.
>Solving it is not simple as you need some tra
