guests locking up issue

guests locking up issue

[Brian Jackson]

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

Re: guests locking up issue

[Marcelo Tosatti]

On Tue, Jun 17, 2008 at 02:29:59PM -0500, 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

Can you please backout commit 695a86229a2c98918ad3d5059f1a141bdf18349c
for a try?

$ git-diff-tree -p 695a86229a2c98918ad3d5059f1a141bdf18349c | patch -p1 -R

Re: guests locking up issue

[William Boughton]

I'm seeing this as well.

with KVM-70

my host: 
dual quad core Intel E5320
4G ram
Debian Etch
2.6.26-rc6 x86_64

my guest:
debian etch 
2.6.26-rc6 x86_64
512 Mb ram

started with:

qemu-system-x86_64 -drive \
file=/mnt/kvms/images/guitest.img,if=ide,boot=on -m 512  \
-vnc localhost:2  -name guitest -monitor stdio -net \
nic,model=e1000,macaddr=00:12:8E:BA:AC:22 -net \
tap,script=/etc/qemu-ifup,ifname=tapguitest -k en-gb -smp 4

further details of my setup including .configs  are at 
http://www.yuri.org.uk/~murble/kvm/

I'm also able to reproduce this with the same image on a
dual Quad-Core AMD Opteron(tm) Processor 2354 with 16Gb of RAM.



regards

Bill
-- 
Bill Boughton           <bill@boughton.de>

Re: guests locking up issue

[Brian Jackson]

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 majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: guests locking up issue

[William Boughton]

> with KVM-70
> 
> my host: 
> dual quad core Intel E5320
> 4G ram
> Debian Etch
> 2.6.26-rc6 x86_64
> 
> my guest:
> debian etch 
> 2.6.26-rc6 x86_64
> 512 Mb ram

I rebuild my guest kernels without CONFIG_KVM_CLOCK, just with
CONFIG_HAVE_KVM=y

It now seems far more stable with -smp 4

> started with:
> 
> qemu-system-x86_64 -drive \
> file=/mnt/kvms/images/guitest.img,if=ide,boot=on -m 512  \
> -vnc localhost:2  -name guitest -monitor stdio -net \
> nic,model=e1000,macaddr=00:12:8E:BA:AC:22 -net \
> tap,script=/etc/qemu-ifup,ifname=tapguitest -k en-gb -smp 4
> 
> further details of my setup including .configs  are at 
> http://www.yuri.org.uk/~murble/kvm/
> 
> I'm also able to reproduce this with the same image on a
> dual Quad-Core AMD Opteron(tm) Processor 2354 with 16Gb of RAM.

I left two guest running all night building kernels in a loop
with -j3 and -smp 4 using both virtio-blk and net.  One running
on the Intel quad core machine the other on the AMD quadcore machine
running the same guest image file, kvm version and guest kernel
version.

Some time in the night the Intel guest froze the AMD hosted one
is still going strong.  The Intel host is hosting some other KVM
guests without virtio / smp which had bad been running several
days until I upgraded to 2.6.26-rc6 yesterday evening without any
crashes.

The guest running on Intel qemu monitor is still responsive but
the qemu-system-x86 was using 200% CPU constantly.

both guests were started with:

qemu-system-x86_64 -drive \
file=/mnt/kvms/images/guitest.img,if=virtio,boot=on -m 512 -vnc \
localhost:2 -name guitest -monitor stdio -net \
nic,model=virtio,macaddr=00:12:8E:BA:AC:22 -net \
tap,script=/etc/qemu-ifup,ifname=tapguitest -k en-gb -smp 4

Details of the amd host configuration are at
http://www.yuri.org.uk/~murble/kvm/amd/

When I quit from the qemu monitor on the intel host i got
a softlockup on the host 
http://www.yuri.org.uk/~murble/kvm/intel-host-softlockup.txt

my new guest .config

http://www.yuri.org.uk/~murble/kvm/new.guest.config.txt

used on both guests.


regards 

bill
-- 
Bill Boughton