Bug 495615 - Update rhn_register to properly parse the dmi information on for registration on a kvm host
Summary: Update rhn_register to properly parse the dmi information on for registration...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rhn-client-tools
Version: 5.3
Hardware: All
OS: Linux
high
urgent
Target Milestone: rc
: ---
Assignee: Pradeep Kilambi
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On: 495612 501787
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-14 03:25 UTC by Daniel Riek
Modified: 2009-09-02 11:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-02 11:20:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:1354 0 normal SHIPPED_LIVE rhn-client-tools bug fix and enhancement update 2009-09-01 10:50:43 UTC

Description Daniel Riek 2009-04-14 03:25:44 UTC 
Expand the parsing of dmi information to identify the virtualization host to support KVM.

See bug 495612 for the kvm side.
Comment 1 Todd Sanders 2009-04-29 20:45:35 UTC 
Daniel - Can you explain this further?  What doe you mean by identify the KVM Host?  Did you mean KVM "guest"?

-Todd
Comment 11 Petr Sklenar 2009-06-29 12:00:24 UTC 
hello,
my tests environment:

1. Serve, Domain-0
dhcp-lab-159.englab.brq.redhat.com
- rhn_register to rhn.webqa
- XEN hypervizor
- it's Domain-0


2. xen20.englab.brq.redhat.com, Domain-U
- xen20 is created on dhcp-lab-159.englab.brq.redhat.com
- rhn_register to rhn_webqa
- it's Domain-U

3. Details for dhcp-lab-159.englab.brq.redhat.com on rhn.webqa.r.c but there isn't info about its domain-1 xen20

---
should I use only KVM virtualization or XEN hypervizor?
Is rhn.webqa.r.c supported for it?
Comment 17 errata-xmlrpc 2009-09-02 11:20:48 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1354.html
Note You need to log in before you can comment on or make changes to this bug.