Bug 831959 - when host node did not support VT, give detailed tips about it, or add an option in GUI to switch to soft qemu [NEEDINFO]
when host node did not support VT, give detailed tips about it, or add an opt...
Status: CLOSED WONTFIX
Product: oVirt
Classification: Community
Component: ovirt-engine-webadmin (Show other bugs)
3.1 RC
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Nobody's working on this, feel free to take it
virt
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-14 04:01 EDT by wenchao xia
Modified: 2014-01-05 06:04 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-01-05 06:04:23 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
iheim: needinfo? (xiawenc)


Attachments (Terms of Use)

  None (edit)
Description wenchao xia 2012-06-14 04:01:02 EDT
Description of problem:
  When using ovirt GUI to create a VM, it fails and reports "internal error", better to report more detailed information.

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

How reproducible:
  every time

Steps to Reproduce:
1. setup a host node in VM, which do not support KVM.
2. add the VM as a node in engine.
3. create a VM on that node.
  
Actual results:
  reports internal error.

Expected results:
  reports "node do not support KVM."

Additional info:
  I hope there would be a button in GUI to switch between soft qemu and KVM.
Comment 1 Itamar Heim 2012-06-14 07:56:15 EDT
there are several checks around this today in both bootstrapping and monitoring.

is this a host that was installed from the engine (bootstrap) or a devel environemnt with installVds=false?
is the cluster the host is in a virt cluster or a gluster cluster?
Comment 3 Itamar Heim 2014-01-05 06:04:23 EST
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.

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