This bug has been copied from bug #528761 and has been proposed to be backported to 4.8 z-stream (EUS).
Ah found the problem. It appears that the system.bios entry has changed for guests running under a RHEL 5.4 vs RHEL 5.5 host. Before that value was 'Xen' but now it is 'Red Hat'. Which causes the client to ignore it.
So apparently this was done as a result of a request from hosted: https://bugzilla.redhat.com/show_bug.cgi?id=499453 Will see about modifying the client to accept this new string as well.
Last fix cause xen info to be sent for kvm guests. This should fix it: 192953
IA64 in Full virt will not work due BZ 497837
Hi, the bugzilla from which this one was opened (number 528761) is 7 months old now... It would be fair to see, apart from ping-pong between ON-QA and ASSIGNED, sometimes in the future also the SOLVED status... Excuse for not being polite, but here we are talking about a reported feature that has economic impact and could have leveraged a customer decision vs other virtualization providers Any way to provide free subscriptions for rhel 3 and rh el 4 guests up to solution time? I think it will be appreciated by customers... if credibility is important yet for Red Hat of course Thanks for considering Gianluca
(In reply to comment #26) > Hi, > the bugzilla from which this one was opened (number 528761) is 7 months old > now... > It would be fair to see, apart from ping-pong between ON-QA and ASSIGNED, > sometimes in the future also the SOLVED status... The ping pong that you see is caused by the facts that - the ON_QA to ASSIGNED transition is what is now used in bugzilla where FAILS_QA was used in the past; - there are private comments accompanying these status changes, as QA reports issues with the development packages and engineering fixes them. The comments are private because they point to Red Hat's internal systems and environments. So what probably seems like meaningless status changes is in fact a public observation of the fact that engineering and QA are working to get updated packages tested and polished, to get them to customers. Thank you for your understanding, Jan
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-2010-0406.html