| 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-kvm | Assignee: | Karen Noel <knoel> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.1 | CC: | 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: | |||||
| Attachments: |
|
||||||
|
Description
Mike Cao
2011-04-15 08:04:00 UTC
Created attachment 492303 [details]
Screendump when guest stuck
It looks to me like a potential clone of BZ 690685 I'm postponing it to 6.2 not sure whether windows 7 supports 64 cpus ,repeat the steps on comment #0 with windows 2008 R2 ,hit the same issue. also tried start VM -m 256G -smp 64,sockets=1,cores=64,threads=1 (instead of sockets=64) hit the same issue . 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? I will retest it with newest kernel once I can reach the big machine Thanks, Mike 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. |