From: Bernhard Schmidt <berni@birkenwald.de>
To: kvm@vger.kernel.org
Subject: Freeze with KVM_CLOCK, undocumented dependency VIRTIO_BLK -> VIRTIO_PCI
Date: Sat, 21 Jun 2008 14:54:31 +0000 (UTC) [thread overview]
Message-ID: <g3j4n7$6b7$1@ger.gmane.org> (raw)
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
next reply other threads:[~2008-06-22 1:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 14:54 Bernhard Schmidt [this message]
2008-06-22 2:41 ` Freeze with KVM_CLOCK, undocumented dependency VIRTIO_BLK -> VIRTIO_PCI Anthony Liguori
2008-06-22 23:22 ` Bernhard Schmidt
2008-07-04 9:27 ` Christian Borntraeger
2008-07-02 10:11 ` Mark McLoughlin
2008-07-03 14:03 ` Avi Kivity
2008-07-03 14:44 ` Mark McLoughlin
2008-07-03 14:49 ` Avi Kivity
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='g3j4n7$6b7$1@ger.gmane.org' \
--to=berni@birkenwald.de \
--cc=kvm@vger.kernel.org \
/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