Re: [Qemu-devel] Virtual Machine Generation ID

On 01/19/17 18:47, Ben Warren wrote: > Thanks Laszlo! >> On Jan 19, 2017, at 1:25 AM, Laszlo Ersek > > wrote: >> >> On 01/19/17 08:09, Ben Warren wrote: >>> On Jan 18, 2017, at 4:02 PM, Ben Warren

Re: [Qemu-devel] Virtual Machine Generation ID

Thanks Laszlo! > On Jan 19, 2017, at 1:25 AM, Laszlo Ersek wrote: > > On 01/19/17 08:09, Ben Warren wrote: >> >>> On Jan 18, 2017, at 4:02 PM, Ben Warren >>> wrote: >>> >>> Hi Michael, On Jan 17, 2017, at 9:45 AM, Michael S. Tsirkin

Re: [Qemu-devel] Virtual Machine Generation ID

On 01/19/17 08:09, Ben Warren wrote: > >> On Jan 18, 2017, at 4:02 PM, Ben Warren >> wrote: >> >> Hi Michael, >>> On Jan 17, 2017, at 9:45 AM, Michael S. Tsirkin >>> wrote: >>> >>> On Mon, Jan 16, 2017 at 10:57:42AM -0800, Ben Warren wrote: I think

Re: [Qemu-devel] Virtual Machine Generation ID

> On Jan 18, 2017, at 4:02 PM, Ben Warren wrote: > > Hi Michael, >> On Jan 17, 2017, at 9:45 AM, Michael S. Tsirkin wrote: >> >> On Mon, Jan 16, 2017 at 10:57:42AM -0800, Ben Warren wrote: >>> I think we have a misunderstanding here. I’m storing the

Re: [Qemu-devel] Virtual Machine Generation ID

Hi Michael, > On Jan 17, 2017, at 9:45 AM, Michael S. Tsirkin wrote: > > On Mon, Jan 16, 2017 at 10:57:42AM -0800, Ben Warren wrote: >> I think we have a misunderstanding here. I’m storing the VM >> Generation ID __data__ (a GUID) in a fw_cfg blob, not the address. > > Yes, I

Re: [Qemu-devel] Virtual Machine Generation ID

On Tue, Jan 17, 2017 at 05:24:04PM +0100, Igor Mammedov wrote: > On Tue, 17 Jan 2017 07:01:27 -0800 > Ed Swierk wrote: > > > You mean what causes the guest to re-read the vmgenid guid? The > > vmgenid ACPI table defines a notify method, and when the guest > > receives

Re: [Qemu-devel] Virtual Machine Generation ID

On Mon, Jan 16, 2017 at 10:57:42AM -0800, Ben Warren wrote: > I think we have a misunderstanding here. I’m storing the VM > Generation ID __data__ (a GUID) in a fw_cfg blob, not the address. Yes, I think I gathered this much from the discussion. This is what I'm saying - don't. Have guest loader

Re: [Qemu-devel] Virtual Machine Generation ID

> On Jan 17, 2017, at 7:21 AM, Michael S. Tsirkin wrote: > > Let's not top-post anymore pls. > > On Tue, Jan 17, 2017 at 07:01:27AM -0800, Ed Swierk wrote: >> You mean what causes the guest to re-read the vmgenid guid? The >> vmgenid ACPI table defines a notify method, and

Re: [Qemu-devel] Virtual Machine Generation ID

On Tue, 17 Jan 2017 07:01:27 -0800 Ed Swierk wrote: > You mean what causes the guest to re-read the vmgenid guid? The > vmgenid ACPI table defines a notify method, and when the guest > receives the corresponding event, it re-reads the guid. (Also it > appears that

Re: [Qemu-devel] Virtual Machine Generation ID

Let's not top-post anymore pls. On Tue, Jan 17, 2017 at 07:01:27AM -0800, Ed Swierk wrote: > You mean what causes the guest to re-read the vmgenid guid? The > vmgenid ACPI table defines a notify method, and when the guest > receives the corresponding event, it re-reads the guid. (Also it >

Re: [Qemu-devel] Virtual Machine Generation ID

You mean what causes the guest to re-read the vmgenid guid? The vmgenid ACPI table defines a notify method, and when the guest receives the corresponding event, it re-reads the guid. (Also it appears that with Windows Server 2012 at least, if no notify method is defined, as is the case with Xen,

Re: [Qemu-devel] Virtual Machine Generation ID

Why is using fw_cfg for vmgenid preferable to the approach used for RSDP: call acpi_add_rom_blob() to allocate a MemoryRegion with the initial vmgenid guid, and call acpi_ram_update() with the new guid whenever the host needs to change it? --Ed On Tue, Jan 17, 2017 at 5:26 AM, Igor Mammedov

Re: [Qemu-devel] Virtual Machine Generation ID

Because this relies on guest to run code to read out the new fw cfg. Thus guest can not reliably detect that host didn't update the gen id - new one might be there in fw cfg but not yet read. RSDP never changes during guest lifetime so the issue does not occur. On Tue, Jan 17, 2017 at 06:26:57AM

Re: [Qemu-devel] Virtual Machine Generation ID

On Mon, 16 Jan 2017 10:57:42 -0800 Ben Warren wrote: > > On Jan 16, 2017, at 6:21 AM, Michael S. Tsirkin wrote: > > > > On Sat, Jan 14, 2017 at 10:17:53PM -0800, Ben Warren wrote: > >> Hi Michael, > >> > >> > >>On Dec 10, 2016, at 7:28 PM,

Re: [Qemu-devel] Virtual Machine Generation ID

> On Jan 16, 2017, at 6:21 AM, Michael S. Tsirkin wrote: > > On Sat, Jan 14, 2017 at 10:17:53PM -0800, Ben Warren wrote: >> Hi Michael, >> >> >>On Dec 10, 2016, at 7:28 PM, Michael S. Tsirkin wrote: >> >>On Tue, Dec 06, 2016 at 06:15:34PM -0800, Ben

Re: [Qemu-devel] Virtual Machine Generation ID

On Sat, Jan 14, 2017 at 10:17:53PM -0800, Ben Warren wrote: > Hi Michael, > > > On Dec 10, 2016, at 7:28 PM, Michael S. Tsirkin wrote: > > On Tue, Dec 06, 2016 at 06:15:34PM -0800, Ben Warren wrote: > > Hi Michael, > > I’m well on my way to

Re: [Qemu-devel] Virtual Machine Generation ID

On Sat, 14 Jan 2017 22:17:53 -0800 Ben Warren wrote: > Hi Michael, > > > On Dec 10, 2016, at 7:28 PM, Michael S. Tsirkin wrote: > > > > On Tue, Dec 06, 2016 at 06:15:34PM -0800, Ben Warren wrote: > >> Hi Michael, > >> > >> I’m well on my way to

Re: [Qemu-devel] Virtual Machine Generation ID

Hi Michael, > On Dec 10, 2016, at 7:28 PM, Michael S. Tsirkin wrote: > > On Tue, Dec 06, 2016 at 06:15:34PM -0800, Ben Warren wrote: >> Hi Michael, >> >> I’m well on my way to implementing this, but I am really new to the QEMU >> code base and am struggling with some

Re: [Qemu-devel] Virtual Machine Generation ID

On Tue, Dec 06, 2016 at 06:15:34PM -0800, Ben Warren wrote: > Hi Michael, > > I’m well on my way to implementing this, but I am really new to the QEMU code > base and am struggling with some concepts. Please see below: > > On Oct 5, 2016, at 6:29 PM, Michael S. Tsirkin wrote:

Re: [Qemu-devel] Virtual Machine Generation ID

Hi Michael, I’m well on my way to implementing this, but I am really new to the QEMU code base and am struggling with some concepts. Please see below: > On Oct 5, 2016, at 6:29 PM, Michael S. Tsirkin wrote: > > On Tue, Oct 04, 2016 at 03:51:40PM -0700, Ed Swierk wrote: >> On

Re: [Qemu-devel] Virtual Machine Generation ID

On Tue, Oct 04, 2016 at 03:51:40PM -0700, Ed Swierk wrote: > On Thu, Sep 15, 2016 at 5:36 PM, Michael S. Tsirkin wrote: > > On Thu, Sep 15, 2016 at 05:23:28PM -0700, Ed Swierk wrote: > >> I'm wondering what it will take to finish up work on vmgenid. > >> > >>

Re: [Qemu-devel] Virtual Machine Generation ID

On Tue, 4 Oct 2016 15:51:40 -0700 Ed Swierk wrote: > On Thu, Sep 15, 2016 at 5:36 PM, Michael S. Tsirkin wrote: > > On Thu, Sep 15, 2016 at 05:23:28PM -0700, Ed Swierk wrote: > >> I'm wondering what it will take to finish up work on vmgenid. > >> >

Re: [Qemu-devel] Virtual Machine Generation ID

On Thu, Sep 15, 2016 at 5:36 PM, Michael S. Tsirkin wrote: > On Thu, Sep 15, 2016 at 05:23:28PM -0700, Ed Swierk wrote: >> I'm wondering what it will take to finish up work on vmgenid. >> >> https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg05599.html > > We have

Re: [Qemu-devel] Virtual Machine Generation ID

On Thu, Sep 15, 2016 at 05:23:28PM -0700, Ed Swierk wrote: > I'm wondering what it will take to finish up work on vmgenid. > > https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg05599.html > > It appears all of the designs explored through the 19 iterations were > problematic in some way.

[Qemu-devel] Virtual Machine Generation ID

I'm wondering what it will take to finish up work on vmgenid. https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg05599.html It appears all of the designs explored through the 19 iterations were problematic in some way. Is any of them vaguely acceptable to all involved in the discussions?