Re: KVM in -next is somewhat busted

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



(fixed kvm@ address)


On 02/08/2010 04:27 PM, Alan Cox wrote:
Reliably at boot time with todays -next I get the following:

BUG: unable to handle kernel paging request at 0000000000001028
IP: [<ffffffffa001c4c4>] balloon+0x1a1/0x309 [virtio_balloon]
PGD 2cd42067 PUD 3b9dc067 PMD 0
Oops: 0000 [#1] SMP
last sysfs file: /sys/devices/virtio-pci/virtio4/block/vdd/removable
CPU 3
Pid: 511, comm: vballoon Not tainted 2.6.33-rc7-next-20100208+ #51 /
RIP: 0010:[<ffffffffa001c4c4>]  [<ffffffffa001c4c4>] balloon+0x1a1/0x309 [virtio_balloon]

Looks like the guest is broken, not the host. Do things work if you leave out CONFIG_VIRTIO_BALLOON?

Copying Adam Litke, who's name is on the latest balloon changes.

--
error compiling committee.c: too many arguments to function

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

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux