Bug 678978 - virt-manager doesn't have an option to specify machine type rhel5.5 or above
Summary: virt-manager doesn't have an option to specify machine type rhel5.5 or above
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager
Version: 5.6
Hardware: All
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-21 07:20 UTC by Muhammad Riyas vk
Modified: 2018-11-14 14:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-10 16:29:59 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Muhammad Riyas vk 2011-02-21 07:20:34 UTC 
Description of problem:

To resolve BZ #655990 we have to start qemu with option "-M rhel5.5", but there is no option to specify "rhel5.5.0" with latest virt-manager and it still creates VM with following configuration

 <type arch='x86_64' machine='rhel5.4.0'>hvm</type>

and it cause qemu to start VM with " -M rhel5.4.0"

How reproducible:

Create a RHEL 5.5 or RHEL 5.6 VM from virt-manager and check the xml configuration for the line "machine='rhel5.4.0'"

Additional info:

# rpm -q virt-manager
virt-manager-0.6.1-13.el5
Comment 1 Cole Robinson 2011-03-10 16:29:59 UTC 
I don't think we want to provide this capability in virt-manager.

Basically the machine value is confusing in a UI sense, most users would probably interpret it to mean something about the guest or host OS, when it has little to do with either. I guarantee putting this in the UI would generate many bug reports from ignorant users who changed the setting and caused their windows machine to blue screen.

In the cases where a user needs to legitimately change this value for x86, we should recommend manually editting the XML.

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