On 10/03/2020 13:44, Michael S. Tsirkin wrote:
On Tue, Mar 10, 2020 at 01:28:32PM +0200, Liran Alon wrote:
On 10/03/2020 13:18, Michael S. Tsirkin wrote:
On Tue, Mar 10, 2020 at 01:05:02PM +0200, Liran Alon wrote:
On 10/03/2020 11:32, Michael S. Tsirkin wrote:
On Tue, Mar 10, 2020 at
On Tue, Mar 10, 2020 at 01:28:32PM +0200, Liran Alon wrote:
>
> On 10/03/2020 13:18, Michael S. Tsirkin wrote:
> > On Tue, Mar 10, 2020 at 01:05:02PM +0200, Liran Alon wrote:
> > > On 10/03/2020 11:32, Michael S. Tsirkin wrote:
> > > > On Tue, Mar 10, 2020 at 01:54:01AM +0200, Liran Alon wrote:
>
On 10/03/2020 13:18, Michael S. Tsirkin wrote:
On Tue, Mar 10, 2020 at 01:05:02PM +0200, Liran Alon wrote:
On 10/03/2020 11:32, Michael S. Tsirkin wrote:
On Tue, Mar 10, 2020 at 01:54:01AM +0200, Liran Alon wrote:
Instead of hard-coding the VMX version, make it a VMPORT object property.
On Tue, Mar 10, 2020 at 01:05:02PM +0200, Liran Alon wrote:
>
> On 10/03/2020 11:32, Michael S. Tsirkin wrote:
> > On Tue, Mar 10, 2020 at 01:54:01AM +0200, Liran Alon wrote:
> > > Instead of hard-coding the VMX version, make it a VMPORT object property.
> > > This would allow user to control
On 10/03/2020 11:32, Michael S. Tsirkin wrote:
On Tue, Mar 10, 2020 at 01:54:01AM +0200, Liran Alon wrote:
Instead of hard-coding the VMX version, make it a VMPORT object property.
This would allow user to control it's value via "-global vmport.vmx-version=X".
Reviewed-by: Nikita Leshenko
On Tue, Mar 10, 2020 at 01:54:01AM +0200, Liran Alon wrote:
> Instead of hard-coding the VMX version, make it a VMPORT object property.
> This would allow user to control it's value via "-global
> vmport.vmx-version=X".
>
> Reviewed-by: Nikita Leshenko
> Signed-off-by: Liran Alon
More detail
