From: "Serge E. Hallyn" <serge@hallyn.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, "Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] If user doesn't specify a uuid, generate a random one
Date: Tue, 27 Mar 2012 02:12:33 +0000 [thread overview]
Message-ID: <20120327021233.GA18109@mail.hallyn.com> (raw)
In-Reply-To: <4F70C722.9040902@codemonkey.ws>
Quoting Anthony Liguori (anthony@codemonkey.ws):
> On 03/26/2012 10:13 AM, Serge E. Hallyn wrote:
> >Currently, if the user doesn't pass a uuid, the system uuid is set to
> >all zeros. This patch generates a random one instead.
> >
> >Is there a reason to prefer all zeros? If not, can a patch like this
> >one be applied?
> >
> >Signed-off-by: Serge Hallyn<serge.hallyn@canonical.com>
>
> The other hypervisors don't have a concept of a transient guest like QEMU does.
True, and I generally don't like arguments of the form "but (some other)
does it like this," but...
> There is no state preserved between invocations of QEMU.
Right, and I really don't know how many users (besides me) run kvm
by hand, as opposed to using libvirt or testdrive. Perhaps testdrive
should be extended.
> Setting a random UUID doesn't seem like the right answer to me as it
> would potentially break Windows VMs.
>
> Perhaps if the DMI UUID isn't set, you could look at the root filesystem's UUID?
Interesting idea. I don't know enough to know at which point in the code
qemu would know that, but I can take a look.
> Not all platforms have a notion of platform UUID so as Ubuntu
> supports more architectures, this problem would have to be dealt
> with eventually.
So it sounds like in this form certainly it's nacked :)
thanks,
-serge
prev parent reply other threads:[~2012-03-27 2:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 15:13 [Qemu-devel] [PATCH 1/1] If user doesn't specify a uuid, generate a random one Serge E. Hallyn
2012-03-26 15:21 ` Andreas Färber
2012-03-26 17:38 ` Serge E. Hallyn
2012-03-26 18:42 ` Brian Jackson
2012-03-26 19:35 ` Serge E. Hallyn
2012-03-26 19:44 ` Anthony Liguori
2012-03-27 2:12 ` Serge E. Hallyn [this message]
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=20120327021233.GA18109@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=anthony@codemonkey.ws \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).