[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EB7AEE5.8020803@redhat.com>
Date: Mon, 07 Nov 2011 11:11:49 +0100
From: Gerd Hoffmann <kraxel@...hat.com>
To: Jan Kiszka <jan.kiszka@....de>
CC: Pekka Enberg <penberg@...nel.org>, Avi Kivity <avi@...hat.com>,
"kvm@...r.kernel.org list" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
qemu-devel Developers <qemu-devel@...gnu.org>,
Alexander Graf <agraf@...e.de>,
Blue Swirl <blauwirbel@...il.com>,
Américo Wang <xiyou.wangcong@...il.com>,
Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] KVM: Add wrapper script around QEMU to test kernels
Hi,
> "Usable" - I've tried kvm-tool several times and still (today) fail to
> get a standard SUSE image (with a kernel I have to compile and provide
> separately...) up and running *). Likely a user mistake, but none that
> is very obvious. At least to me.
Same here.
No support for booting from CDROM.
No support for booting from Network.
Thus no way to install a new guest image.
Booting an existing qcow2 guest image failed, the guest started throwing
I/O errors. And even to try that I had to manually extract the kernel
and initrd images from the guest. Maybe you should check with the Xen
guys, they have a funky 'pygrub' which sort-of automates the
copy-kernel-from-guest-image process.
Booting the host kernel failed too. Standard distro kernel. The virtio
bits are modular, not statically compiled into the kernel. kvm tool
can't handle that.
You have to build your own kernel and make sure you flip the correct
config bits, then you can boot it to a shell prompt. Trying anything
else just doesn't work today ...
cheers,
Gerd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists