Marcelo helped us narrow this down on the IRC channel.
It seems turning off CONFIG_KVM_CLOCK gets around this.
Just thought I'd mention this in case anyone else has run into this.
On Jun 17, 2008, at 2:29 PM, Brian Jackson wrote:
I'm having a problem recently with my guests freezing. It seems to
happen
within a few hours of booting the guest. I can still access the
monitor and
check stuff in there. The kernel that comes with Ubuntu 8.04
(2.6.24) doesn't
have the same issue.
I'm a bit out of my league here as far as figuring out what to do
about this.
Any help tracking this down would be appreciated. (I'm trying the
no-kvm-irqchip and no-kvm-pit options now, but I think I've tried
them in the
past and they didn't do anything)
Host:
Core 2 Duo 2.5G
4G ram
Ubuntu 8.04 x64
2.6.26-rc5 (kvm git tree from earlier today)
kvm userland from earlier today as well
(git describe says kvm-70 for both)
Guest:
Ubuntu 8.04 x64
2.6.26-rc5 (same as host)
qemu-system-x86_64 -m 440M -vnc :1 -std-vga -drive
file=/dev/vm_space/test1,if=virtio,boot=on -kernel /boot/vmlinuz-
kvm-2.6.26-rc5 -initrd /boot/initrd.img-kvm-2.6.26-rc5 -append
"root=/dev/vda" -net
nic,model=e1000 -net tap
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
