Bug 616346 - libvirt doesn't allow me to run RHEL5 guest on RHEL-6 host
libvirt doesn't allow me to run RHEL5 guest on RHEL-6 host
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm (Show other bugs)
6.1
All Linux
low Severity medium
: rc
: ---
Assigned To: Virtualization Maintenance
Virtualization Bugs
: RHELNAK
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-20 04:33 EDT by Matěj Cepl
Modified: 2010-07-20 08:34 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-20 08:34:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Matěj Cepl 2010-07-20 04:33:25 EDT
Description of problem:
Whenever I try to start a virtual machine on my RHEL-6 host, I get this error message:

johanka:~# LANG=C virsh start tikanga
error: Failed to start domain tikanga
error: internal error Process exited while reading console log output: Supported machines are:
pc         RHEL 6.0.0 PC (alias of rhel6.0.0)
rhel6.0.0  RHEL 6.0.0 PC (default)
rhel5.5.0  RHEL 5.5.0 PC
rhel5.4.4  RHEL 5.4.4 PC
rhel5.4.0  RHEL 5.4.0 PC

Which (aside from being completely unhelpful ... which machine we are talking about here? host or guest?) is just wrong. My host is RHEL-6, guest RHEL-5

Version-Release number of selected component (if applicable):
johanka:~# rpm -q libvirt qemu-kvm
libvirt-0.8.1-15.el6.x86_64
qemu-kvm-0.12.1.2-2.96.el6.x86_64


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Matěj Cepl 2010-07-20 04:36:22 EDT
RHEL-4 guest starts without a problem.
Comment 3 Matěj Cepl 2010-07-20 04:45:07 EDT
When I changed via

virsh edit tikanga 

line

<type arch='x86_64' machine='pc-0.12'>hvm</type>

to 

<type arch='x86_64' machine='pc'>hvm</type>

guest starts again.

Is this a regression or wasn't this supposed to work all the time and it was just a mistake that it did?
Comment 4 RHEL Product and Program Management 2010-07-20 04:57:40 EDT
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 5 Amit Shah 2010-07-20 05:06:19 EDT
libvirt should've selected a rhel-5 machine type for your installation. Using pc-0.12 was wrong; was this guest installed a while ago?
Comment 6 Daniel Berrange 2010-07-20 06:11:16 EDT
Earlier version of RHEL6 kvm still included the 'pc-0.12' machine type. This was recently disabled

- kvm-Disable-non-rhel-machine-types-pc-0.12-pc-0.11-pc-0..patch [bz#607263]

Hence any guests which happened to have that wouldn't work. IMHO this is NOTABUG.
Comment 7 Bill Burns 2010-07-20 08:34:26 EDT
Closed per comment #6

Note You need to log in before you can comment on or make changes to this bug.