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
Summary: when host node did not support VT, give detailed tips about it, or add an opt...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: 3.1 RC
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-14 08:01 UTC by wenchao xia
Modified: 2023-09-14 01:29 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-05 11:04:23 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)

Description wenchao xia 2012-06-14 08:01:02 UTC 
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 11:56:15 UTC 
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 11:04:23 UTC 
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.
Comment 4 Red Hat Bugzilla 2023-09-14 01:29:55 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.