Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 696898

Summary: qemu-kvm stuck at "Starting windows" during windows 2008 R2 guest installation with -smp 64 -m 256G
Product: Red Hat Enterprise Linux 6 Reporter: Mike Cao <bcao>
Component: qemu-kvmAssignee: Karen Noel <knoel>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: 6.1CC: amit.shah, bcao, juzhang, michen, mkenneth, mshao, tburke, virt-maint, xfu
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-28 09:26:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screendump when guest stuck none

Description Mike Cao 2011-04-15 08:04:00 UTC
Description of problem:


Version-Release number of selected component (if applicable):
# uname -r
2.6.32-130.el6.x86_64
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.158.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.qemu-img create -f raw /win7sp1 15G
2.start VM installation
start VM with -smp 64 -m 256G
eg:/usr/libexec/qemu-kvm -M rhel6.1.0 -enable-kvm -m 2G -smp 64,sockets=64,cores=1,threads=1 -name VM1 -uuid 042ad1e0-a5f0-bf4c-00aa-754e1f82118c -rtc base=utc -boot order=dc,menu=on -drive file=/win7sp1,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=threads -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,id=hostnet0,vhost=off -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:53:31:e1,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc :3 -vga std -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -monitor stdio -drive file=/en_windows_7_ultimate_with_sp1_x64_dvd_618240.iso,if=none,id=cdrom1,format=raw,cache=none,media=cdrom -device ide-drive,drive=cdrom1,id=cdrom1 -fda /usr/share/virtio-win/virtio-win.vfd
  
Actual results:
guest stuck at "starting windows" referring to screendump ( I wait for 15 mins)

Expected results:
the installation steps should continue within 5 mins

Additional info:
1.Tried vhost=on/off ,both hit this issue
2.Tried vhost=off -vga cirrus/std ,both hit this issue.
3.Tried -m 2G -smp 64 ,guest installation will continue in 5mins
4.Tried -m 256G -smp 2,guest installation will continue in 5mins

Comment 1 Mike Cao 2011-04-15 08:05:14 UTC
Created attachment 492303 [details]
Screendump when guest stuck

Comment 2 Dor Laor 2011-04-17 07:55:05 UTC
It looks to me like a potential clone of BZ 690685
I'm postponing it to 6.2

Comment 3 Mike Cao 2011-04-18 03:13:31 UTC
not sure whether windows 7 supports 64 cpus ,repeat the steps on comment #0 with windows 2008 R2 ,hit the same issue.

Comment 4 Mike Cao 2011-04-18 04:26:11 UTC
also tried start VM  -m 256G -smp 64,sockets=1,cores=64,threads=1 (instead of  sockets=64)

hit the same issue .

Comment 6 Avi Kivity 2011-07-21 15:18:29 UTC
Given that the similar Bug 690685 is (mostly) fixed with 2.6.32-156.el6.x86_64, this might be resolved as well.  Can you please retest?

Comment 7 Mike Cao 2011-07-22 10:31:12 UTC
I will retest it with newest kernel once I can reach the big machine 

Thanks,
Mike

Comment 8 FuXiangChun 2011-07-28 02:10:03 UTC
Hi Avi

tested steps:
1.# uname -r
2.6.32-171.el6.x86_64

2.# rpm -qa|grep kvm
qemu-kvm-0.12.1.2-2.172.el6.x86_64

3 # /usr/libexec/qemu-kvm -M rhel6.1.0 -enable-kvm -m 256G -smp 64,sockets=64,cores=1,threads=1 -name VM1 -uuid 042ad1e0-a5f0-bf4c-00aa-754e1f82118c -rtc base=utc -boot order=dc,menu=on -drive file=win7sp1,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,aio=threads -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,id=hostnet0,vhost=off -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:53:31:e1,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc :3 -vga std -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -monitor stdio -drive file=en_windows_7_ultimate_with_sp1_x64_dvd_618240.iso,if=none,id=cdrom1,format=raw,cache=none,media=cdrom -device ide-drive,drive=cdrom1,id=cdrom1

Actual results:
the installation steps will continue within 1 mins

this bug has been fixed in the latest kernel.  you can close it.