| Summary: | Bug in kvm / libvirtd | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Claus Reheis <rehcla.mail> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | mageia, marja11, nic, thierry.vignaud, tmb |
| Version: | 5 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Claus Reheis
2015-06-21 13:58:09 CEST
Sander Lepik
2015-06-21 14:46:36 CEST
CC:
(none) =>
mageia, thierry.vignaud, tmb (In reply to Claus Reheis from comment #0) > Description of problem: > > After a fresh installation of Mageia_5_x64 I selected gnome-boxes from the > software-center and installed it. > All went fine and when booting Mageia 5 all services start without errors. > Then I installed Mageia 5 in a virtual machine. > All seemed good I rebooted the virtual machine and after boot, the machine > stops when gdm should show up! > > I did journalctl -b and found this messages: > > kvm [4680]: vcpu2 unhandled rdmsr: 0x606 This can be ignored, quemu does not support rdmsr > libvirtd[3477]: Cannot recv data: Connection reset by peer > kvm [6421]: vcpu2 unhandled rdmsr: 0x606 > libvirtd[6347]: internal error: End of file from monitor This comes from when the vm dies... check /var/log/libvirt/qemu/${guestname}.log for the real reason it crashes
Thierry Vignaud
2015-06-22 15:06:36 CEST
Keywords:
(none) =>
NEEDINFO Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, I will have to close this bug as OLD. Thank you. CC:
(none) =>
nic Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD. Status:
NEW =>
RESOLVED |