qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Gabriel L. Somlo" <gsomlo@gmail.com>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: Proposal to add QEMU "Guest Environment Variables"
Date: Wed, 4 Feb 2015 16:12:52 +0000	[thread overview]
Message-ID: <20150204161252.GB3032@redhat.com> (raw)
In-Reply-To: <20150204155917.GA16281@HEDWIG.INI.CMU.EDU>

On Wed, Feb 04, 2015 at 10:59:18AM -0500, Gabriel L. Somlo wrote:
> On Wed, Feb 04, 2015 at 03:24:32PM +0000, Daniel P. Berrange wrote:
> > Yes, there is some overhead in setting up QEMU on the host to provide
> > the data cloud-init needs, but it isn't all that difficult. For example
> > Rich Jones describes how to setup a virtual disk for cloud-init
> > 
> >   https://rwmj.wordpress.com/2013/12/10/creating-a-cloud-init-config-disk-for-non-cloud-boots/
> > 
> > Given the prevalence of cloud-init across distros, I think you'll be hard
> > pressed to get them to support an alternative method, even if it is a bit
> > simpler at the QEMU setup level.
> 
> Have a look at this:
> 
> http://www.vmware.com/pdf/Scripting_API_23.pdf
> 
> (page 36, GuestInfo Variables).
> 
> It's a rather generic, flexible feature. Some people use it for
> early boot, but that's just one of the many use cases, so maybe
> focusing on "how to implement early boot configuration" is going
> a bit off on a tangent :)
> 
> I'd like to add that mechanism (or at least the host->guest bits)
> to qemu, for "feature parity". That should be a good thing, making
> it easier to port "whatever" to qemu, without having to massively
> rearchitect it to work around a missing feature...
> 
> Also, it's really non-intrusive. At this point, I could implement it
> by passing environment strings in via "-smbios file=./Type11EnvStrBlob",
> and read them on the guest side via 'dmidecode -t11', with some grep
> and awk magic thrown in for good measure :)

Perhaps cloud-init project would be interested in using the custom
smbios field as a data source for its needs. It already has the concept
of pluggable data sources, so adding another could be interesting.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2015-02-04 16:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 19:09 [Qemu-devel] RFC: Proposal to add QEMU "Guest Environment Variables" Gabriel L. Somlo
2015-02-03 19:14 ` Denis V. Lunev
2015-02-03 20:14   ` Gabriel L. Somlo
2015-02-03 20:23     ` Denis V. Lunev
2015-02-03 19:26 ` Eric Blake
2015-02-03 20:54   ` Gabriel L. Somlo
2015-02-03 20:11 ` Michael Roth
2015-02-03 21:38   ` Gabriel L. Somlo
2015-02-03 21:49     ` Denis V. Lunev
2015-02-03 22:14       ` Gabriel L. Somlo
2015-02-03 22:08     ` Michael Roth
2015-02-04  9:31     ` Daniel P. Berrange
2015-02-04 15:20       ` Gabriel L. Somlo
2015-02-04 15:24         ` Daniel P. Berrange
2015-02-04 15:59           ` Gabriel L. Somlo
2015-02-04 16:12             ` Daniel P. Berrange [this message]
2015-02-04  9:29 ` Daniel P. Berrange
2015-02-04 15:55 ` Christopher Covington
2015-02-04 16:00 ` Richard W.M. Jones
2015-02-04 16:06   ` Gabriel L. Somlo

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=20150204161252.GB3032@redhat.com \
    --to=berrange@redhat.com \
    --cc=gsomlo@gmail.com \
    --cc=mdroth@linux.vnet.ibm.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).