Re: [RESEND PATCH] kvm: Allow the Hyper-V vendor ID to be specified

2015-10-16 Thread Paolo Bonzini
On 16/10/2015 00:16, Alex Williamson wrote: > According to Microsoft documentation, the signature in the standard > hypervisor CPUID leaf at 0x4000 identifies the Vendor ID and is > for reporting and diagnostic purposes only. We can therefore allow > the user to change it to whatever they

Re: [Qemu-devel] [RESEND PATCH] kvm: Allow the Hyper-V vendor ID to be specified

2015-10-16 Thread Igor Mammedov
On Fri, 16 Oct 2015 08:26:14 -0600 Alex Williamson wrote: > On Fri, 2015-10-16 at 09:30 +0200, Paolo Bonzini wrote: > > > > On 16/10/2015 00:16, Alex Williamson wrote: > > > According to Microsoft documentation, the signature in the standard > > > hypervisor CPUID

Re: [RESEND PATCH] kvm: Allow the Hyper-V vendor ID to be specified

2015-10-16 Thread Alex Williamson
On Fri, 2015-10-16 at 09:30 +0200, Paolo Bonzini wrote: > > On 16/10/2015 00:16, Alex Williamson wrote: > > According to Microsoft documentation, the signature in the standard > > hypervisor CPUID leaf at 0x4000 identifies the Vendor ID and is > > for reporting and diagnostic purposes only.

[RESEND PATCH] kvm: Allow the Hyper-V vendor ID to be specified

2015-10-15 Thread Alex Williamson
According to Microsoft documentation, the signature in the standard hypervisor CPUID leaf at 0x4000 identifies the Vendor ID and is for reporting and diagnostic purposes only. We can therefore allow the user to change it to whatever they want, within the 12 character limit. Add a new

[PATCH] kvm: Allow the Hyper-V vendor ID to be specified

2015-10-02 Thread Alex Williamson
According to Microsoft documentation, the signature in the standard hypervisor CPUID leaf at 0x4000 identifies the Vendor ID and is for reporting and diagnostic purposes only. We can therefore allow the user to change it to whatever they want, within the 12 character limit. Add a new