Bug 703121 - no -enable-nesting option
Summary: no -enable-nesting option
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kvm
Version: 5.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: john cooper
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-09 11:11 UTC by Suqin Huang
Modified: 2014-07-25 03:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-11 16:48:37 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Suqin Huang 2011-05-09 11:11:00 UTC
Description of problem:
according to patch http://post-office.corp.redhat.com/archives/rhvirt-patches/2011-April/msg00101.html , svm is exported to guest if kvm_nested, but "invalid option" is shown when I boot guest with -enable-nesting

Version-Release number of selected component (if applicable):
kvm-83-232.el5

How reproducible:
100%

Steps to Reproduce:
1. boot guest with -cpu qemu64,+svm -enable-nesting
2.
3.
  
Actual results:
invalid option -- '-enable-nesting'

Expected results:


Additional info:

Comment 1 john cooper 2011-05-11 16:46:10 UTC
Looks line --disable-kvm-nested is set by default in 5.x builds
which would cause the parse error above as the CLI option wouldn't be
defined.

(In reply to comment #0)
> Description of problem:
> according to patch
> http://post-office.corp.redhat.com/archives/rhvirt-patches/2011-April/msg00101.html
> , svm is exported to guest if kvm_nested, but "invalid option" is shown when I
> boot guest with -enable-nesting

Sorry my comment above was relative to 6.x and confusing in this
context.  The actual goal here was disable of vmx/svm by default.

Comment 2 john cooper 2011-05-11 16:48:37 UTC
--disable-kvm-nested is set by default in the 5.x qemu configure
thus this options isn't supported in 5.x.


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