From: "Serge E. Hallyn" <serge@hallyn.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 1/1] If user doesn't specify a uuid, generate a random one
Date: Mon, 26 Mar 2012 15:13:40 +0000 [thread overview]
Message-ID: <20120326151340.GA25460@mail.hallyn.com> (raw)
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>
---
vl.c | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/vl.c b/vl.c
index 112b0e0..2b53b62 100644
--- a/vl.c
+++ b/vl.c
@@ -247,7 +247,9 @@ int nb_numa_nodes;
uint64_t node_mem[MAX_NODES];
uint64_t node_cpumask[MAX_NODES];
+#include <uuid/uuid.h>
uint8_t qemu_uuid[16];
+bool uuid_set = false;
static QEMUBootSetHandler *boot_set_handler;
static void *boot_set_opaque;
@@ -3030,6 +3032,7 @@ int main(int argc, char **argv, char **envp)
" Wrong format.\n");
exit(1);
}
+ uuid_set = true;
break;
case QEMU_OPTION_option_rom:
if (nb_option_roms >= MAX_OPTION_ROMS) {
@@ -3200,6 +3203,14 @@ int main(int argc, char **argv, char **envp)
exit(0);
}
+ if (!uuid_set) {
+ uuid_t uuid;
+ uuid_generate(uuid);
+ for (i = 0; i < 16; i++) {
+ qemu_uuid[i] = uuid[i];
+ }
+ }
+
/* Open the logfile at this point, if necessary. We can't open the logfile
* when encountering either of the logging options (-d or -D) because the
* other one may be encountered later on the command line, changing the
--
1.7.9.1
next reply other threads:[~2012-03-26 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 15:13 Serge E. Hallyn [this message]
2012-03-26 15:21 ` [Qemu-devel] [PATCH 1/1] If user doesn't specify a uuid, generate a random one 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
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=20120326151340.GA25460@mail.hallyn.com \
--to=serge@hallyn.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 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).