From: Dor Laor <dlaor@redhat.com>
To: Yolkfull Chow <yzhou@redhat.com>
Cc: kvm@vger.kernel.org, autotest@test.kernel.org, jasowang@redhat.com
Subject: Re: [Autotest] [PATCH] Assign an UUID for each VM in kvm command line
Date: Wed, 15 Jul 2009 16:36:38 +0300 [thread overview]
Message-ID: <4A5DDB66.9080400@redhat.com> (raw)
In-Reply-To: <1247649149-28353-1-git-send-email-yzhou@redhat.com>
On 07/15/2009 12:12 PM, Yolkfull Chow wrote:
> Would submit this patch which is from our internal kvm-autotest patches submitted by Jason.
> So that we could go on test case about parameters verification(UUID, DMI data etc).
>
> Signed-off-by: Yolkfull Chow<yzhou@redhat.com>
> ---
> client/tests/kvm/kvm_vm.py | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/client/tests/kvm/kvm_vm.py b/client/tests/kvm/kvm_vm.py
> index 503f636..68cc235 100644
> --- a/client/tests/kvm/kvm_vm.py
> +++ b/client/tests/kvm/kvm_vm.py
> @@ -287,6 +287,10 @@ class VM:
> elif params.get("display") == "nographic":
> qemu_cmd += " -nographic"
>
> + uuid = os.popen("cat /proc/sys/kernel/random/uuid").readline().strip()
> + if uuid:
> + qemu_cmd += " -uuid %s" % uuid
If you'll change the uuid on every run, the guest will notice that. Some
guest (M$) might not love it.
Why not use a static uuid or even just test uuid in a specific test
without having it in all tests?
btw: why you're at it, please add uuid to the block devices too.
+ the -smbios option.
Thanks,
dor
> +
> return qemu_cmd
>
>
next prev parent reply other threads:[~2009-07-15 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 9:12 [PATCH] Assign an UUID for each VM in kvm command line Yolkfull Chow
2009-07-15 13:36 ` Dor Laor [this message]
2009-07-16 2:42 ` [Autotest] " Yolkfull Chow
2009-07-16 4:11 ` sudhir kumar
2009-07-16 8:27 ` Michael Goldish
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=4A5DDB66.9080400@redhat.com \
--to=dlaor@redhat.com \
--cc=autotest@test.kernel.org \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=yzhou@redhat.com \
/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.