Am Montag, 23. Juni 2008 schrieb Bernhard Schmidt:
> I don't quite understand. VIRTIO_BLK can be selected in the kernel
> without selecting VIRTIO_PCI, it does not generate any build error but
> the virtual blockdevice simply does appear. Does VIRTIO_BLK have any use
> without VIRTIO_PCI?
Yes,
On Thu, 2008-07-03 at 17:03 +0300, Avi Kivity wrote:
> Mark McLoughlin wrote:
> > 2) Although we currently build virtio_pci as a module in Fedora, it
> > leads to a pretty strange situation where e.g. mkinitrd and
> > anaconda need to explicitly include the virtio_pci module; I
> >
Mark McLoughlin wrote:
2) Although we currently build virtio_pci as a module in Fedora, it
leads to a pretty strange situation where e.g. mkinitrd and
anaconda need to explicitly include the virtio_pci module; I
don't think there's analogous situation where bus probing logic
Mark McLoughlin wrote:
I wonder would it be useful to default to building in (i.e. not as a
module) virtio_pci if building with e.g. KVM_GUEST?
There's two issues here:
1) It's easy to forget about virtio_pci - if we used KVM_GUEST as a
general "this kernel may be run on KVM" config, th
On Sat, 2008-06-21 at 21:41 -0500, Anthony Liguori wrote:
> Bernhard Schmidt wrote:
> > 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 expec
Hi,
a) when I enable KVM_CLOCK in the kernel configuration the guest system
freezes after
PCI: Found IRQ 11 for device :00:04.0
vda: vda1 vda2
TCP cubic registered
NET: Registered protocol family 10
NET: Registered protocol family 17
Using IPI Shortcut mode
There are some outstanding patc
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 wh
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 smal