Red Hat Bugzilla – Bug 215041
RHEL5: update Guest firmware for Xen-IPF to RHEL5
Last modified: 2007-11-30 17:07:37 EST
+++ This bug was initially created as a clone of Bug #201073 +++
Escalated to Bugzilla from IssueTracker
-- Additional comment from firstname.lastname@example.org on 2006-08-02 13:03 EST --
1. Feature request: IPF-Xen Guest firmware to support VTI (fully virtualized) guests
2. Description more details.
Priority (Must Have, High, Medium, Low): Must have
Target Releases: RHEL5 Beta1
3. Business Justification: Montecito POR
4. Status of the code: Yes (Intel will provide to RedHat )
5. Hardware to Red Hat: Yes (Intel has provided Montecito platforms to Redhat)
6. Partner management contact: email@example.com
7. Partner technical contact: firstname.lastname@example.org
This event sent from IssueTracker by bjohnson [Intel]
-- Additional comment from email@example.com on 2006-10-17 17:00 EST --
Created an attachment (id=138728)
08/24/2006 guest firmware source rpm
The guest firmware in xen-ia64-guest-firmware-1.0.0-4.ia64.rpm on
RHEL-4.91-Server-Supplementary-ia64-ftp.iso is old. Its GFW shows:
07/31/06 - QEMU 0.8.1 changes resulting IRQ conflict to NIC. This GFW
The latest GFW is 08/24/2006 whose GFW.info should show:
08/24/06 - Fixed VTi network due to GFW conflict with latest QEMU
adding a fake PCI device (xen_platform) for VBD/VNIF
which is using IRQ 10 same as VNIF.
The latest and correct guest firmware xen-ia64-guest-firmware-1.0.0-5.src.rpm
is uploaded here.
Please make sure to pick up this guest firmware ASAP.
-- Additional comment from firstname.lastname@example.org on 2006-10-17 19:42 EST --
You should open up a new BZ for the 1.0.0-5 guest firmware update.
As per Prarit's request, opening a new BZ for the 1.0.0-5 firmware update.
Apparently this is needed to boot fully virt guests on ia64 due to interface
Created attachment 140923 [details]
1.0.0-5 guest firmware provided by Intel
Do not "piggy-back" requests on the same IT/Bugzilla. If you have a new version
of xen ia64 guest FW, then you should close the existing bugzilla (if it is not
in the post or modified state) and open a new one.
A newer issue tracker 107419 is created. Its ancestor issue tracker 104465 is
Closing this out as not a bug.