From: Daniel Veillard <veillard@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Work toward Qemu support for libvirt
Date: Mon, 28 Aug 2006 14:08:56 -0400 [thread overview]
Message-ID: <20060828180856.GI16526@redhat.com> (raw)
Hi,
this is just a heads up for people who might be interested (there was a thread
last month here about this). Daniel Berrange has worked toward adding QEmu
support in libvirt:
https://www.redhat.com/archives/libvir-list/2006-August/msg00123.html
https://www.redhat.com/archives/libvir-list/2006-August/msg00127.html
(and following messages)
One of the point of the integration is the use of a daemon who will launch
the qemu instances, in order to keep the control on the console and maintain
some state. Then the library communicate with a socket to the daemon who
dispatches the command to the qemu processes.
It's never too late for feedback or suggestions, some of you may have done
similar things in the past, but earlier fedback always make things easier :-)
Daniel
--
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard | virtualization library http://libvirt.org/
veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
reply other threads:[~2006-08-28 18:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060828180856.GI16526@redhat.com \
--to=veillard@redhat.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).