qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Help] Windows2012 as Guest 64+cores on KVM Halts


From: hangaohuai
Subject: [Qemu-devel] [Help] Windows2012 as Guest 64+cores on KVM Halts
Date: Thu, 9 Feb 2017 14:18:02 +0800
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1

Dear all:
I try to boot windows2012R2 (more than 64 cores)on kvm platform with hyper-v 
on*<relaxed state='on'/>*.
the guest halts on the starting time.
Also tested in these cases:
<topology sockets='64' cores='1' threads='1'/>  - boot sucess
<topology sockets='1' cores='64' threads='1'/>  - boot sucess
<topology sockets='1' cores='1' threads='64'/>  - boot sucess
<topology sockets='1' cores='68' threads='1'/>  - boot failed
<topology sockets='68' cores='1' threads='1'/>  - boot sucess(in Guest we can 
found 64)
<topology sockets='1' cores='1' threads='68'/>  - boot failed

Environment:
GUEST:
  windows2012R2
HOST:
    kernel version:4.10.0-rc4
    QEMU version:QEMU emulator version 2.8.50 (v2.8.0-664-gd1c82f7-dirty)
part of GuestXML:
  <vcpu placement='static'>68</vcpu>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
    <hyperv>
      <relaxed state='on'/>
    </hyperv>
  </features>
  <cpu>
    <topology sockets='1' cores='68' threads='1'/>
  </cpu>

//////////////////////////////////
debug info:
virsh qemu-monitor-command win2012 --hmp "info cpus"
  CPU #61: pc=0xfffff8031296a21c thread_id=21410
  CPU #62: pc=0xfffff8031296a21c thread_id=21411
  CPU #63: pc=0xfffff8031296a21c thread_id=21414
  CPU #64: pc=0x00000000000fd31c (halted) thread_id=21415
  CPU #65: pc=0x00000000000fd31c (halted) thread_id=21416
  CPU #66: pc=0x00000000000fd31c (halted) thread_id=21417
  CPU #67: pc=0x00000000000fd31c (halted) thread_id=21418


Any suggestions?

Thanks a lot.

Gaohuai Han





reply via email to

[Prev in Thread] Current Thread [Next in Thread]