qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC PATCH v8 20/21] replay: command line options


From: Paolo Bonzini
Subject: Re: [Qemu-devel] [RFC PATCH v8 20/21] replay: command line options
Date: Mon, 09 Feb 2015 13:26:53 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0


On 09/02/2015 13:15, Pavel Dovgaluk wrote:
>> From: Paolo Bonzini [mailto:address@hidden
>> On 22/01/2015 09:53, Pavel Dovgalyuk wrote:
>>> This patch introduces command line options for enabling recording or 
>>> replaying
>>> virtual machine behavior. "-record" option starts recording of the execution
>>> and saves it into the log, specified with "fname" parameter. "-replay" 
>>> option
>>> is intended for replaying previously saved log.
>>>
>>> Signed-off-by: Pavel Dovgalyuk <address@hidden>
>>>                  break;
>>>              case QEMU_OPTION_snapshot:
>>>                  snapshot = 1;
>>> @@ -3105,6 +3114,7 @@ int main(int argc, char **argv, char **envp)
>>>  #endif
>>>              case QEMU_OPTION_bt:
>>>                  add_device_config(DEV_BT, optarg);
>>> +                not_compatible_replay_param++;
>>
>> Could it be enough to add a migration blocker?
> 
> Record/replay core does not use migration subsystem.
> That is why it should check the hardware by itself.

Right.  But is there anything that supports migration but not replay?
If the two overlap, you can just check migration blockers to see if
record/replay can be allowed.

>>
>>>                  break;
>>>              case QEMU_OPTION_audio_help:
>>>                  AUD_help ();
>>> @@ -3244,6 +3254,7 @@ int main(int argc, char **argv, char **envp)
>>>                  if (!opts) {
>>>                      exit(1);
>>>                  }
>>> +                not_compatible_replay_param++;
>>
>> Why not compatible?
> 
> Replay for audio adapter will be added in latter patches.
> Trying to record/replay machine with audio using current
> set of patches will break the replay.

For this case you can try adding a mechanism similar to migration
blockers (replay blockers).

Paolo



reply via email to

[Prev in Thread] Current Thread [Next in Thread]