From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dennis Jacobfeuerborn <d.jacobfeuerborn@conversis.de>
Subject: Virtio block device and LVM
Date: Sat, 22 Mar 2008 23:01:19 +0100
Message-ID: <47E581AF.2060206@conversis.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: kvm-devel@lists.sourceforge.net
Return-path: <kvm-devel-bounces@lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/kvm-devel>,
	<mailto:kvm-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=kvm-devel>
List-Post: <mailto:kvm-devel@lists.sourceforge.net>
List-Help: <mailto:kvm-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/kvm-devel>,
	<mailto:kvm-devel-request@lists.sourceforge.net?subject=subscribe>
Sender: kvm-devel-bounces@lists.sourceforge.net
Errors-To: kvm-devel-bounces@lists.sourceforge.net
List-Id: kvm.vger.kernel.org

Hi,
I'm trying to get the paravirtualized block device going but get in trouble 
with LVM. Both host and guest a very recent snapshot of Fedora 9 rawhide. 
The guest is a pristine F9 install with / mounted as /dev/VolGroup00/LogVol00.

When I boot with the command:
/usr/bin/qemu-kvm -m 512 -drive file=/root/test-1.img,media=disk,boot=on
the guest boots fine but when I try to boot with:
/usr/bin/qemu-kvm -m 512 -drive file=/root/test-1.img,if=virtio,boot=on
the kernel panics because it cannot find any volume-groups and thus not 
mount /.

Do I have to make any specific changes to the guest to make it 
recognize/detect the volume-group on the virtual block device?

Regards,
   Dennis

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/