From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernhard Schmidt Subject: Freeze with KVM_CLOCK, undocumented dependency VIRTIO_BLK -> VIRTIO_PCI Date: Sat, 21 Jun 2008 14:54:31 +0000 (UTC) Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from main.gmane.org ([80.91.229.2]:52125 "EHLO ciao.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751981AbYFVBFF (ORCPT ); Sat, 21 Jun 2008 21:05:05 -0400 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1KAE0s-0005A5-S2 for kvm@vger.kernel.org; Sun, 22 Jun 2008 01:05:02 +0000 Received: from ppp-88-217-44-141.dynamic.mnet-online.de ([88.217.44.141]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Jun 2008 01:05:02 +0000 Received: from berni by ppp-88-217-44-141.dynamic.mnet-online.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Jun 2008 01:05:02 +0000 Sender: kvm-owner@vger.kernel.org List-ID: 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. 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? Thanks, Bernhard