From: Asdo <asdo@shiftmail.org>
To: "Thomas Løcke" <thomas.granvej6@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Tracking KVM development
Date: Mon, 22 Mar 2010 00:23:35 +0100 [thread overview]
Message-ID: <4BA6AA77.2020700@shiftmail.org> (raw)
In-Reply-To: <1f0fa7ae1003211337u3ce81ec0x9065e19036fd4182@mail.gmail.com>
> I've looked at libvirt a bit, and I fail at seeing the attraction. I
> think I will stay with plain qemu-kvm, unless there are some very
> compelling reasons for going down the libvirt route.
>
Virsh (uses libvirt) is almost irreplaceable for us...
How do you start and stop virtual machines easily, get a list of the
running ones... How do you ensure a virtual machine is never started
twice? (would obviously have disastrous results on the filesystem) How
do you connect on-demand to the graphics of the VM from your laptop,
with a good security so that only the system administrator can do that?
(virt-viewer provides very easy support for this, tunnelling VNC
graphics over SSH, you connect by specifying the name of the host and
the name of the VM... just great!)
If there is another way I'm interested, in fact libvirt also brings
problems to us mainly because it takes a while to support latest KVM
features, and also installing libvirt from source and configuring it
properly for the host first time is much more difficult than for KVM
sources.
Thank you
next prev parent reply other threads:[~2010-03-22 0:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 11:21 Tracking KVM development Thomas Løcke
2010-03-21 12:23 ` Avi Kivity
2010-03-21 16:37 ` Thomas Løcke
2010-03-21 16:42 ` Avi Kivity
2010-03-21 20:09 ` Alexander Graf
2010-03-21 20:16 ` Michael Tokarev
2010-03-21 20:19 ` Andre Przywara
2010-03-21 20:37 ` Thomas Løcke
2010-03-21 23:23 ` Asdo [this message]
2010-03-22 12:20 ` Kenni Lund
2010-03-21 20:50 ` Zdenek Kaspar
-- strict thread matches above, loose matches on Subject: below --
2010-03-22 16:33 Tomasz Chmielewski
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=4BA6AA77.2020700@shiftmail.org \
--to=asdo@shiftmail.org \
--cc=kvm@vger.kernel.org \
--cc=thomas.granvej6@gmail.com \
/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