From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Gabriel L. Somlo" <gsomlo@gmail.com>
Cc: qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] RFC: Proposal to add QEMU "Guest Environment Variables"
Date: Wed, 4 Feb 2015 09:29:39 +0000 [thread overview]
Message-ID: <20150204092939.GI3032@redhat.com> (raw)
In-Reply-To: <20150203190921.GR3354@HEDWIG.INI.CMU.EDU>
On Tue, Feb 03, 2015 at 02:09:22PM -0500, Gabriel L. Somlo wrote:
> Hi,
>
> I'm interested in adding a way for a host to pass environment variables
> into a qemu guest VM -- analogous to setting environment variables for
> a process to access via getenv() and friends.
>
> The QEMU Guest Agent (QGA) does not appear to quite fit the bill, at
> least not in its current form: The agent must have been successfully
> started on the guest before the host would have to connect to it (in
> a separate act from just starting the guest in the first place), and
> get it to execute any hypothetical commands to configure or otherwise
> influence the guest.
> So, my question for the QEMU dev team:
>
> 1. Would you consider this feature a useful addition to QEMU ?
> I.e., would this be acceptable (of interest) to the upstream project?
>
> 2. Is anything similar already being worked on (so I could either join
> that effort, or back off, as the case may be) ? :)
IMHO this is already a solved problem via the cloud-init project which
is the widely used standard for injecting information into guest OS
at boot time. Any OS distro shipping cloud images is already going to
have cloud-init provided.
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 :|
next prev parent reply other threads:[~2015-02-04 9:29 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
2015-02-04 9:29 ` Daniel P. Berrange [this message]
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=20150204092939.GI3032@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).