Bug 529695

Summary: Unable to start a KVM guest from Satellite webui
Product: Red Hat Satellite 5 Reporter: Milan Zázrivec <mzazrivec>
Component: VirtualizationAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED DUPLICATE QA Contact: Brandon Perkins <bperkins>
Severity: medium Docs Contact:
Priority: low    
Version: 530   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-23 12:33:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Milan Zázrivec 2009-10-19 14:34:43 UTC 
Description of problem:
It is impossible to start previously installed KVM guest from Satellite
web ui.

Version-Release number of selected component (if applicable):
Satellite 5.3.0 / rhn-virtualization-host-5.3.0-12.el5sat

How reproducible:
Deterministic

Steps to Reproduce:
1. Have a RHEL-5.4 (or later) x86_64 KVM host (the hardware needs to
support full virtualization) registered to a Satellite 5.3.0
2. Install a KVM guest on your host & register it to the satellite
3. Power off your KVM guest (via virt-manager for example)
4. In satellite webui, see virtualization tab of your kvm host
5. Attempt to start your KVM guest from webui
6. See the action result in events tab
  
Actual results:
KVM guest domain does not start, following error shows in the system
events tab:
...
This action's status is: Failed.
The client picked up this action on 10/19/09 10:21:43 AM EDT.
The client completed this action on 10/19/09 10:21:43 AM EDT.
Client execution returned "Error occurred while attempting to recreate
domain 55708f20199a93cee5c7955994d273c4: unknown OS type xen" (code 1)
...

Expected results:
No error, KVM guest starts successfully.

Additional info:
N/A
Comment 1 Milan Zázrivec 2009-10-23 12:33:15 UTC 

*** This bug has been marked as a duplicate of bug 510606 ***