Red Hat Bugzilla – Bug 1001487
host call trace when booting win2k8-64 guest with large memory and multiple vcpu
Last modified: 2013-09-09 21:34:50 EDT
Description of problem:
host call trace when booting win2k8-64 guest with large memory and multiple vcpu and guest boot take more than 10min.
win2k8r2-64 hit this issue, but win2k3-32/64, win8-32/64, win2012-64 won't
I added dmesg log to attachment.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.verify mem and cpu in host
total used free shared buffers cached
Mem: 503 67 435 0 0 62
-/+ buffers/cache: 5 498
Swap: 3 0 3
#cat /proc/cpuinfo(total 48 cores)
processor : 47
vendor_id : AuthenticAMD
cpu family : 16
model : 9
model name : AMD Opteron(tm) Processor 6172
3.boot guest(not overcommit)
#/usr/libexec/qemu-kvm -name vm1 -nodefaults \
-m 420G \
-smp 32,cores=8,threads=1,sockets=4 \
-M pc-i440fx-rhel7.0.0 -cpu Opteron_G3 -rtc base=utc,clock=host,driftfix=slew -k en-us -boot menu=on -monitor stdio -vnc :2 -spice disable-ticketing,port=5932 -vga qxl -qmp tcp:0:5556,server,nowait -drive file=/home/win2008-x64.qcow2,if=none,id=disk,format=qcow2,cache=none,werror=stop,rerror=stop -device ide-hd,drive=disk,bus=ide.1,unit=0,id=disk0,bootindex=1 -balloon virtio
guest boot take more than 10min and host call trace
guest can boot with no errors
I will update test result in Intel host later
Created attachment 790810 [details]
host dmesg log
The host kernel seems to be spinning on a spinlock for 22s!
Is that machine on virtlab? I don't have any machine that big around, so I'll have to look for one to try to reproduce the issue.
Something you could do, is to get a kernel dump, store in it in the machine itself and let me log in.
(In reply to Luiz Capitulino from comment #3)
> The host kernel seems to be spinning on a spinlock for 22s!
> Is that machine on virtlab? I don't have any machine that big around, so
> I'll have to look for one to try to reproduce the issue.
> Something you could do, is to get a kernel dump, store in it in the machine
> itself and let me log in.
Can you reply this info?
There's a number of fixes between kernels 3.10.0-11.el7 and 3.10.0-15.el7. If you really can't get the issue anymore with latest kernel, then I think you should close this bz as WORKSFORME.
According to comment 6 and comment 7, set this bug as WORKSFORME.