From: Mark van Walraven <markv@netvalue.net.nz>
To: kvm@vger.kernel.org
Cc: Aaron Clausen <mightymartianca@gmail.com>
Subject: Re: KVM on Debian
Date: Fri, 5 Jun 2009 15:39:23 +1200 [thread overview]
Message-ID: <20090605033922.GA21907@mvw.netvalue.net.nz> (raw)
In-Reply-To: <20090604210303.GS31274@mvw.netvalue.net.nz>
Hi,
An update in the hope that this is useful to someone :-)
On Fri, Jun 05, 2009 at 09:03:03AM +1200, Mark van Walraven wrote:
> My next step is to try qemu-kvm, built from source. The Debianised libvirt
> expects the kvm binaries to be in /usr/bin/kvm, so you can symlink them
> from /usr/local/bin if you prefer to install there. I've also experimented
> with shell script wrapper in /usr/bin/kvm that condenses the output of
> qemu-kvm --help so that libvirtd for Lenny works.
Actually, the current Debian Lenny libvirt* (0.4.6-10) seem to work
fine with qemu-kvm-0.10.5 built from source. All I needed to do was
symlink /usr/local/bin/qemu-system-x86_64 to /usr/bin/kvm and copy
extboot.bin into /usr/local/share/qemu/ (I used the one from the
kvm 85+dfsg-3 package in Experimental).
So far, so good.
Mark.
next prev parent reply other threads:[~2009-06-05 3:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 20:37 KVM on Debian Aaron Clausen
2009-06-04 21:03 ` Mark van Walraven
2009-06-05 3:39 ` Mark van Walraven [this message]
2009-06-04 21:50 ` Matthew Palmer
2009-06-05 5:47 ` Michael Tokarev
-- strict thread matches above, loose matches on Subject: below --
2006-11-19 19:18 Avi Kivity
2006-11-15 7:09 Baruch Even
[not found] ` <20061115070905.GM28027-xGn4Jn0woyz+OtfAA3OxFg@public.gmane.org>
2006-11-15 7:47 ` Avi Kivity
2006-11-13 21:35 Baruch Even
[not found] ` <20061113213556.GZ28027-xGn4Jn0woyz+OtfAA3OxFg@public.gmane.org>
2006-11-14 8:38 ` Avi Kivity
2006-11-14 8:46 ` Avi Kivity
[not found] ` <4559824A.4010500-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-14 9:09 ` Baruch Even
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=20090605033922.GA21907@mvw.netvalue.net.nz \
--to=markv@netvalue.net.nz \
--cc=kvm@vger.kernel.org \
--cc=mightymartianca@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