Bug 1388844

Summary: unable to install KDE to the guest machine using two vcpus
Product: [Fedora] Fedora Reporter: lnie <lnie>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: anaconda-maint-list, berrange, clalancette, ehabkost, extras-orphan, g.kaviyarasu, jonathan, markmc, mkolman, quintela, vanmeeuwen+fedora, virt-maint, vponcova
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:48:00 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:
Description Flags
journal
none
screenshot none

Description lnie 2016-10-26 09:51:18 UTC
Created attachment 1214230 [details]
journal

Description of problem:

Try to install KDE to a guest machine using virt-manager and specify two cpus,several minutes after booting the installer,find the guest machine hangs,and you are unable to continue the installation.

I have reproduced this for several times and saw the following in journal:

Oct 26 17:23:25 localhost.localdomain kernel: kvm [2383]: vcpu1, guest rIP: 0xffffffffb205d722 unhandled rdmsr: 0x34
Oct 26 17:23:43 localhost.localdomain kernel: kvm [2383]: vcpu1, guest rIP: 0xffffffffb205d722 unhandled rdmsr: 0x606
Oct 26 17:23:43 localhost.localdomain kernel: kvm [2383]: vcpu1, guest rIP: 0xffffffffb205d722 unhandled rdmsr: 0x60d
Oct 26 17:23:43 localhost.localdomain kernel: kvm [2383]: vcpu1, guest rIP: 0xffffffffb205d722 unhandled rdmsr: 0x3f8
Oct 26 17:23:43 localhost.localdomain kernel: kvm [2383]: vcpu1, guest rIP: 0xffffffffb205d722 unhandled rdmsr: 0x3f9
Oct 26 17:23:43 localhost.localdomain kernel: kvm [2383]: vcpu1, guest rIP: 0xffffffffb205d722 unhandled rdmsr: 0x3fa
Oct 26 17:23:43 localhost.localdomain kernel: kvm [2383]: vcpu1, guest rIP: 0xffffffffb205d722 unhandled rdmsr: 0x630
Oct 26 17:23:43 localhost.localdomain kernel: kvm [2383]: vcpu1, guest rIP: 0xffffffffb205d722 unhandled rdmsr: 0x631
Oct 26 17:23:43 localhost.localdomain kernel: kvm [2383]: vcpu1, guest rIP: 0xffffffffb205d722 unhandled rdmsr: 0x632
Oct 26 17:23:43 localhost.localdomain kernel: kvm [2383]: vcpu0, guest rIP: 0xffffffffb205d722 unhandled rdmsr: 0x611
Oct 26 17:23:43 localhost.localdomain kernel: kvm [2383]: vcpu0, guest rIP: 0xffffffffb205d722 unhandled rdmsr: 0x639

Not sure if this is the right place to report,please feel free to reassign,thanks.



Version-Release number of selected component (if applicable):

kernel-4.8.3-300.fc25.x86_64
qemu-kvm-2.7.0-6.fc25.x86_64
kde-20161007.x86_64

How reproducible:
always 

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 lnie 2016-10-26 09:51:54 UTC
Created attachment 1214232 [details]
screenshot

Comment 2 lnie 2016-10-26 10:14:50 UTC
Also saw those kvm errors in journal while install workstation to the guest machine,but no system hangs,so reassign to anaconda.

Comment 3 Fedora End Of Life 2017-11-16 19:20:30 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2017-12-12 10:48:00 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.