Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

On Mon, Jul 09, 2018 at 08:36:47AM +0100, Richard W.M. Jones wrote: > On Thu, Jul 05, 2018 at 03:11:32PM +0100, Richard W.M. Jones wrote: > > VMware represents these internally as two signed 64 bit integers, eg: > > > > vm.genid = "-570734802784577186" > > vm.genidx = "-5042519231342505152" >

Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

On Mon, Jul 09, 2018 at 11:05:34AM +0200, Laszlo Ersek wrote: > On 07/09/18 09:36, Richard W.M. Jones wrote: > > On Thu, Jul 05, 2018 at 03:11:32PM +0100, Richard W.M. Jones wrote: > >> VMware represents these internally as two signed 64 bit integers, eg: > >> > >> vm.genid = "-570734802784577186

Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

On 07/09/18 09:36, Richard W.M. Jones wrote: > On Thu, Jul 05, 2018 at 03:11:32PM +0100, Richard W.M. Jones wrote: >> VMware represents these internally as two signed 64 bit integers, eg: >> >> vm.genid = "-570734802784577186" >> vm.genidx = "-5042519231342505152" >> >> I am still trying to get

Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

On Thu, Jul 05, 2018 at 03:11:32PM +0100, Richard W.M. Jones wrote: > VMware represents these internally as two signed 64 bit integers, eg: > > vm.genid = "-570734802784577186" > vm.genidx = "-5042519231342505152" > > I am still trying to get verification, but I believe the first is the > low

Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

On Thu, Jul 05, 2018 at 08:10:15PM +0300, Michael S. Tsirkin wrote: > On Thu, Jul 05, 2018 at 05:43:43PM +0100, Richard W.M. Jones wrote: > > On Thu, Jul 05, 2018 at 04:20:33PM +0200, Laszlo Ersek wrote: > > > QEMU does the right thing. If other hypervisors don't do this -- while > > > still taking

Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

On Thu, Jul 05, 2018 at 07:15:34PM +0200, Laszlo Ersek wrote: > > It has to be said that after reading the spec again [the MSFT spec, > > not qemu's spec] and what other hypervisors are doing, I'm not sure > > qemu is doing the right thing here. > > That's the thing about specs -- interpretation.

Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

On 07/05/18 18:43, Richard W.M. Jones wrote: > On Thu, Jul 05, 2018 at 04:20:33PM +0200, Laszlo Ersek wrote: >> QEMU does the right thing. If other hypervisors don't do this -- while >> still taking and displaying the value in UUID / GUID textual format --, >> they are wrong. The VMGENID spec from

Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

On Thu, Jul 05, 2018 at 05:43:43PM +0100, Richard W.M. Jones wrote: > On Thu, Jul 05, 2018 at 04:20:33PM +0200, Laszlo Ersek wrote: > > QEMU does the right thing. If other hypervisors don't do this -- while > > still taking and displaying the value in UUID / GUID textual format --, > > they are wro

Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

On Thu, Jul 05, 2018 at 05:43:43PM +0100, Richard W.M. Jones wrote: > On Thu, Jul 05, 2018 at 04:20:33PM +0200, Laszlo Ersek wrote: > > QEMU does the right thing. If other hypervisors don't do this -- while > > still taking and displaying the value in UUID / GUID textual format --, > > they are wro

Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

On Thu, Jul 05, 2018 at 04:20:33PM +0200, Laszlo Ersek wrote: > QEMU does the right thing. If other hypervisors don't do this -- while > still taking and displaying the value in UUID / GUID textual format --, > they are wrong. The VMGENID spec from Microsoft >

Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

Hi Rich, On 07/05/18 14:52, Richard W.M. Jones wrote: > On Thu, Jul 05, 2018 at 01:39:29PM +0100, Richard W.M. Jones wrote: >> I was doing a bit of investigation around how different hypervisors >> handle the VM Generation ID feature. QEMU's behaviour seems quite >> strange, I wonder if this is a

Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

On Thu, Jul 05, 2018 at 04:54:16PM +0300, Michael S. Tsirkin wrote: > On Thu, Jul 05, 2018 at 01:52:31PM +0100, Richard W.M. Jones wrote: > > On Thu, Jul 05, 2018 at 01:39:29PM +0100, Richard W.M. Jones wrote: > > > I was doing a bit of investigation around how different hypervisors > > > handle th

Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

On Thu, Jul 05, 2018 at 01:52:31PM +0100, Richard W.M. Jones wrote: > On Thu, Jul 05, 2018 at 01:39:29PM +0100, Richard W.M. Jones wrote: > > I was doing a bit of investigation around how different hypervisors > > handle the VM Generation ID feature. QEMU's behaviour seems quite > > strange, I won

Re: [Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

On Thu, Jul 05, 2018 at 01:39:29PM +0100, Richard W.M. Jones wrote: > I was doing a bit of investigation around how different hypervisors > handle the VM Generation ID feature. QEMU's behaviour seems quite > strange, I wonder if this is a bug or expected? > > (1) I booted a Windows 2016 VM with:

[Qemu-devel] Byte ordering of VM Generation ID in Windows VMs

I was doing a bit of investigation around how different hypervisors handle the VM Generation ID feature. QEMU's behaviour seems quite strange, I wonder if this is a bug or expected? (1) I booted a Windows 2016 VM with: qemu-system-x86_64 -M pc,accel=kvm -m 2G -hda w2k16-mincore.img \ -de