| Summary: | Processor device can't be seen in win10 guest which has machine type 'pc-q35-rhel7.3.0' | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | mxie <mxie> | ||||||||||||
| Component: | qemu-kvm-rhev | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | jingzhao <jinzhao> | ||||||||||||
| Severity: | low | Docs Contact: | |||||||||||||
| Priority: | low | ||||||||||||||
| Version: | 7.3 | CC: | ailan, chayang, jinzhao, juzhang, juzhou, knoel, lhuang, mxie, mzhan, tzheng, virt-maint, xiaodwan | ||||||||||||
| Target Milestone: | rc | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2018-05-09 09:54:36 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Attachments: |
|
||||||||||||||
Created attachment 1197837 [details]
win7-q35
Created attachment 1197838 [details]
win10-i440fx-rhel7.3.0
Created attachment 1197839 [details]
win10-i440fx-rhel7.2.0
can we please check with the latest Windows 10 release? 1709 seems to be working fine for me, but it comes with quite heavily updated (comparing to previous releases) intelppm.sys driver. Thanks, Vadim. Created attachment 1359303 [details]
win10-q35-new
(In reply to jingzhao from comment #7) > Created attachment 1359303 [details] > win10-q35-new Great! Thanks a lot. If you don't mind I would like to close this issue then. Vadim. I also can't reproduce the problem with below builds now,I agree to close it qemu-kvm-rhev-2.10.0-21.el7_5.2.x86_64 libvirt-3.9.0-14.el7_5.4.x86_64 kernel-3.10.0-862.el7.x86_64 OVMF-20171011-4.git92d07e48907f.el7.noarch |
Created attachment 1197836 [details] win10-q35 Description of problem: Processor device can't be seen in win10 guest which has machine type 'pc-q35-rhel7.3.0' Version-Release number of selected component (if applicable): qemu-kvm-rhev-2.6.0-22.el7.x86_64 libvirt-2.0.0-6.el7.x86_64 kernel:3.10.0-495.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.check cpu info for host # virsh capabilities <capabilities> <host> <uuid>98eb1f80-d898-11e1-b040-24be05109f18</uuid> <cpu> <arch>x86_64</arch> <model>IvyBridge</model> <vendor>Intel</vendor> <topology sockets='1' cores='4' threads='2'/> <feature name='ds'/> <feature name='acpi'/> <feature name='ss'/> <feature name='ht'/> <feature name='tm'/> <feature name='pbe'/> <feature name='dtes64'/> <feature name='monitor'/> <feature name='ds_cpl'/> <feature name='vmx'/> <feature name='smx'/> <feature name='est'/> <feature name='tm2'/> <feature name='xtpr'/> <feature name='pdcm'/> <feature name='pcid'/> <feature name='osxsave'/> <feature name='arat'/> <feature name='xsaveopt'/> <feature name='invtsc'/> <pages unit='KiB' size='4'/> <pages unit='KiB' size='2048'/> </cpu> ...... <guest> <os_type>hvm</os_type> <arch name='i686'> <wordsize>32</wordsize> <emulator>/usr/libexec/qemu-kvm</emulator> <machine maxCpus='240'>pc-i440fx-rhel7.3.0</machine> <machine canonical='pc-i440fx-rhel7.3.0' maxCpus='240'>pc</machine> <machine maxCpus='240'>pc-i440fx-rhel7.0.0</machine> <machine maxCpus='240'>rhel6.3.0</machine> <machine maxCpus='240'>rhel6.4.0</machine> <machine maxCpus='240'>rhel6.0.0</machine> <machine maxCpus='240'>pc-i440fx-rhel7.1.0</machine> <machine maxCpus='240'>pc-i440fx-rhel7.2.0</machine> <machine maxCpus='240'>pc-q35-rhel7.3.0</machine> <machine canonical='pc-q35-rhel7.3.0' maxCpus='240'>q35</machine> <machine maxCpus='240'>rhel6.5.0</machine> <machine maxCpus='240'>rhel6.6.0</machine> <machine maxCpus='240'>rhel6.1.0</machine> <machine maxCpus='240'>rhel6.2.0</machine> <domain type='qemu'/> <domain type='kvm'> <emulator>/usr/libexec/qemu-kvm</emulator> </domain> </arch> <features> <cpuselection/> <deviceboot/> <disksnapshot default='on' toggle='no'/> <acpi default='on' toggle='yes'/> <apic default='on' toggle='no'/> <pae/> <nonpae/> </features> </guest> ...... 2.Prepare a win10 guest which has machine type 'pc-q35-rhel7.3.0' 3.Open device manager after logging into the guest and click 'show hidden devices' and then find there is no processor device,pls refer to sceenshot 'win10-q35' Actual results: As above description Expected results: Processor device can be seen in win10 guest which has machine type 'pc-q35-rhel7.3.0' Additional info: 1.Processor device shows normal in win7 guest which has machine type 'pc-q35-rhel7.3.0',pls refer to screenshot 'win7-q35' 2.Although processor device could be seen in win10 guest which has machine type 'pc-i440fx-rhel7.3.0', the status shows gray,pls refer to screenshut "win10-i440fx-rhel7.3.0".If win10 guest has machine type 'pc-i440fx-rhel7.2.0', the process device shows black which is normal status,,pls refer to screenshut "win10-i440fx-rhel7.2.0"