From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Andreas Färber" <afaerber@suse.de>
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: Mon, 26 Mar 2012 17:38:58 +0000 [thread overview]
Message-ID: <20120326173858.GA1199@mail.hallyn.com> (raw)
In-Reply-To: <4F708997.9030705@suse.de>
Quoting Andreas Färber (afaerber@suse.de):
> Am 26.03.2012 17:13, schrieb Serge E. Hallyn:
> > 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?
>
> Yes, documented somewhere in the archives, we wanted to have
> reproducible defaults in QEMU (cf. MAC address, IP addresses) so that it
> doesn't change for each invocation or depending on host.
Thanks. Though I don't know of a case offhand, I guess I could imagine
a case where a guest's userspace acts differently (and mis-behaves)
based on the random uuid...
> As a general rule, randomization should be done either explicitly (-uuid
> `uuidgen` or -generate-me-a-uuid) or via frontends such as libvirt.
>
> If all zeros causes genuine problems then we should change the default,
> taking care of backwards compatibility as usual.
The bug this was in reply to is at http://pad.lv/959308 . IIUC the main
problem is that our crash database uses the uuid, so users need to set
one to report bugs. (There was also a suggestion that Microsoft requires
it for Logo Certification.) My suggestion was also to have callers
specify it, but the crash db issue means we'd have to wrap all calls to
qemu.
So thanks - I understand if this patch doesn't make it upstream. I'll
just carry a patch in our package in that case.
thanks,
-serge
next prev parent reply other threads:[~2012-03-26 17:38 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 [this message]
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
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=20120326173858.GA1199@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=afaerber@suse.de \
--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).