From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] Add UUID command-line option
Date: Mon, 25 Aug 2008 09:22:54 -0500 [thread overview]
Message-ID: <48B2C03E.4060700@codemonkey.ws> (raw)
In-Reply-To: <48B27C10.3000009@qumranet.com>
Avi Kivity wrote:
> Blue Swirl wrote:
>> On 8/24/08, Avi Kivity <avi@qumranet.com> wrote:
>>
>>
>> UUID can be used in all machines, so it would be nice if the interface
>> was same. I don't see much benefit in vmport compared to ROM solution.
>>
>>
>
> Maybe UUID is generic but the vast majority of things that need to
> communicate to qemu will be arch specific.
Because it's not an interface we control. VMware automatically upgrades
their tool chain and doesn't support backwards compatibility in their
tools. They're completely free to change the semantics of the interface.
This could really cause confusion within guests. It's one thing to
implement vmport based ops when there is existing guest software that we
can get working but I think it's not a great idea to write new guest
software that's QEMU specific using an interface that we have no control
over.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-08-25 14:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 11:32 [Qemu-devel] [PATCH 0/6] Add UUID command-line option Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 1/6] Use IO port for qemu<->guest BIOS communication Gleb Natapov
2008-08-24 17:39 ` Blue Swirl
2008-08-25 9:48 ` Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 2/6] Add -uuid command line option Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 3/6] Add "info uuid" command to monitor Gleb Natapov
2008-08-24 17:43 ` Blue Swirl
2008-08-25 9:46 ` Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 4/6] Use libuuid if available Gleb Natapov
2008-08-24 17:50 ` Blue Swirl
2008-08-25 9:44 ` Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 5/6] Add UUID to BIOS configuration info Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 6/6] Pass cpu speed into SM BIOS Gleb Natapov
2008-08-24 18:14 ` Blue Swirl
2008-08-25 9:44 ` Gleb Natapov
2008-08-24 12:01 ` [Qemu-devel] [PATCH 0/6] Add UUID command-line option Blue Swirl
2008-08-24 12:24 ` Gleb Natapov
2008-08-24 12:45 ` Blue Swirl
2008-08-24 13:05 ` Gleb Natapov
2008-08-24 13:35 ` Blue Swirl
2008-08-24 14:11 ` Gleb Natapov
2008-08-24 17:17 ` Blue Swirl
2008-08-24 19:23 ` Kevin O'Connor
2008-08-24 13:09 ` Avi Kivity
2008-08-24 13:43 ` Blue Swirl
2008-08-24 13:55 ` Avi Kivity
2008-08-24 16:56 ` Blue Swirl
2008-08-25 9:32 ` Avi Kivity
2008-08-25 14:22 ` Anthony Liguori [this message]
2008-08-24 18:50 ` Kevin O'Connor
2008-08-25 9:29 ` Avi Kivity
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=48B2C03E.4060700@codemonkey.ws \
--to=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).