From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: Freeze with KVM_CLOCK, undocumented dependency VIRTIO_BLK ->
 VIRTIO_PCI
Date: Sat, 21 Jun 2008 21:41:17 -0500
Message-ID: <485DBBCD.5060600@codemonkey.ws>
References: <g3j4n7$6b7$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Bernhard Schmidt <berni@birkenwald.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from rv-out-0506.google.com ([209.85.198.236]:52938 "EHLO
	rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751480AbYFVClj (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sat, 21 Jun 2008 22:41:39 -0400
Received: by rv-out-0506.google.com with SMTP id k40so6358710rvb.1
        for <kvm@vger.kernel.org>; Sat, 21 Jun 2008 19:41:36 -0700 (PDT)
In-Reply-To: <g3j4n7$6b7$1@ger.gmane.org>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Bernhard Schmidt wrote:
> Hi,
>
> apologies if those questions have already been answered, I did not find
> anything specific that should still be visible.
>
> I'm currently testing KVM (kvm-0.70 package from Debian unstable,
> rebuilt on Ubuntu Hardy) on a Athlon64 in i386 mode and found two small
> issues while trying to build a small kernel for my guest systems
> (2.6.26-rc6).
>
> a) when I enable KVM_CLOCK in the kernel configuration the guest system
> freezes after
>
> PCI: Found IRQ 11 for device 0000:00:04.0
>  vda: vda1 vda2
> TCP cubic registered
> NET: Registered protocol family 10
> NET: Registered protocol family 17
> Using IPI Shortcut mode
>
> when I disable KVM_CLOCK it mounts the filesystem and boots just fine
>
> Using IPI Shortcut mode
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
>   

There are some outstanding patches for KVM_CLOCK that may fix this problem.

> b) apparently VIRTIO_BLK works only when VIRTIO_PCI and thus PCI is
> enabled in the kernel. Otherwise the vda* device is not visible and the
> guest does not find its root filesystem.
>
> Is this expected? If yes, is it possible to add the appropriate
> dependency in the kernel configuration or amend the description
> accordingly?
>   

VIRTIO_BLK doesn't depend on VIRTIO_PCI.  VIRTIO_PCI allows you use to 
virtio devices under KVM.

This is all documented FWIW in the Kconfig and in a number of places on 
the wiki.

Regards,

Anthony Liguori

> Thanks,
> Bernhard
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>