From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ben Warren <ben@skyportsystems.com>
Cc: Ed Swierk <eswierk@skyportsystems.com>,
qemu-devel@nongnu.org, Igor Mammedov <imammedo@redhat.com>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] Virtual Machine Generation ID
Date: Tue, 17 Jan 2017 19:45:32 +0200 [thread overview]
Message-ID: <20170117194321-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <85C3D50B-7AFD-41E7-AD1B-634A42D04BB2@skyportsystems.com>
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 reserve guest memory and write the
address into a fw cfg blob, and have qemu write the id at that address.
This way you can update guest memory at any time.
--
MST
next prev parent reply other threads:[~2017-01-17 17:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 0:23 [Qemu-devel] Virtual Machine Generation ID Ed Swierk
2016-09-16 0:36 ` Michael S. Tsirkin
2016-10-04 22:51 ` Ed Swierk
2016-10-05 9:45 ` Igor Mammedov
2016-10-06 1:29 ` Michael S. Tsirkin
2016-12-07 2:15 ` Ben Warren
2016-12-11 3:28 ` Michael S. Tsirkin
2017-01-15 6:17 ` Ben Warren
2017-01-16 8:47 ` Igor Mammedov
2017-01-16 14:21 ` Michael S. Tsirkin
2017-01-16 18:57 ` Ben Warren
2017-01-17 13:26 ` Igor Mammedov
2017-01-17 14:26 ` Ed Swierk
2017-01-17 14:33 ` Michael S. Tsirkin
2017-01-17 15:01 ` Ed Swierk
2017-01-17 15:21 ` Michael S. Tsirkin
2017-01-17 17:35 ` Ben Warren
2017-01-17 16:24 ` Igor Mammedov
2017-01-17 17:42 ` Michael S. Tsirkin
2017-01-17 17:45 ` Michael S. Tsirkin [this message]
2017-01-19 0:02 ` Ben Warren
2017-01-19 7:09 ` Ben Warren
2017-01-19 9:25 ` Laszlo Ersek
2017-01-19 17:47 ` Ben Warren
2017-01-19 18:20 ` Laszlo Ersek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170117194321-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ben@skyportsystems.com \
--cc=eswierk@skyportsystems.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.