From: Fam Zheng <famz@redhat.com>
To: Janne Karhunen <janne.karhunen@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Allow users to specify the vmdk virtual hardware version.
Date: Thu, 21 Apr 2016 11:26:12 +0800 [thread overview]
Message-ID: <20160421032612.GF24822@dhcp-14-234.nay.redhat.com> (raw)
In-Reply-To: <CAE=NcrYs7LLxoh4yofm0uOTRR9y5vqE_z2qPiZSO-3Ayk4jk-w@mail.gmail.com>
On Wed, 04/20 20:02, Janne Karhunen wrote:
> On Wed, Apr 20, 2016 at 7:22 PM, Fam Zheng <famz@redhat.com> wrote:
>
> >> Replace hardcoded vmdk description file hardware version flag with
> >> a user definable version.
> >
> > Hi Janne,
> >
> > Since this is a new feature, please explain why this change is desired (i.e.
> > the necessity.)
>
> See here what it controls for vmware:
>
> https://kb.vmware.com/selfservice/microsites/search.do?languag
> e=en_US&cmd=displayKC&externalId=1003746
>
> Seems that the vmware cluster I'm using is configured to eat vmdks
> with only certain virtual hardware versions specified as being
> supported, so this patch allows me to define that version. Besides
> that, I've read that to mean that it's a hint from me (as the vmdk
> author) to the cluster that this is the vmware virtual hardware
> version I have tested this vmdk to run with. It's actually relatively
> useful metadata as such.
>
> In other words, without the patch not a single qemu-img generated vmdk
> is 'good' for the system I'm using.
Thanks for the explanation, please add this information into the commit message
in next submission and also fix the option code so I can ack your patch.
Fam
next prev parent reply other threads:[~2016-04-21 3:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 22:27 [Qemu-devel] [PATCH] Allow users to specify the vmdk virtual hardware version Janne Karhunen
2016-04-21 2:22 ` Fam Zheng
2016-04-21 3:02 ` Janne Karhunen
2016-04-21 3:26 ` Fam Zheng [this message]
2016-04-21 3:30 ` Janne Karhunen
2016-04-21 3:22 ` Janne Karhunen
2016-04-21 4:44 ` Fam Zheng
2016-04-22 15:23 ` Janne Karhunen
2016-04-25 0:45 ` Fam Zheng
-- strict thread matches above, loose matches on Subject: below --
2016-04-21 19:29 Janne Karhunen
2016-04-29 7:41 ` Fam Zheng
2016-05-02 11:30 ` Janne Karhunen
2016-05-03 0:49 ` Fam Zheng
2016-05-03 9:45 ` Janne Karhunen
2016-05-03 9:43 Janne Karhunen
2016-05-06 5:15 ` Janne Karhunen
2016-05-06 9:07 ` Fam Zheng
2016-05-06 9:04 ` Fam Zheng
2016-05-06 11:05 ` Kevin Wolf
2016-05-06 17:53 ` Janne Karhunen
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=20160421032612.GF24822@dhcp-14-234.nay.redhat.com \
--to=famz@redhat.com \
--cc=janne.karhunen@gmail.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).