Bug 219195 - Need to update PV-FB to latest upstream config file syntax [virtinstall]
Summary: Need to update PV-FB to latest upstream config file syntax [virtinstall]
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: python-virtinst
Version: 5.0
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 218050
TreeView+ depends on / blocked
 
Reported: 2006-12-11 20:50 UTC by Daniel Berrangé
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Fixed In Version: RC
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-02-08 01:38:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Generate new style PVFB config (1.05 KB, patch)
2006-12-11 20:53 UTC, Daniel Berrangé 		no flags Details | Diff
View All

Comment 1 Daniel Berrangé 2006-12-11 20:53:15 UTC 
Created attachment 143327 [details]
Generate new style PVFB config

This patch updates the generation of config files for paravirt guests to use
the new style configuration syntax
Comment 2 RHEL Program Management 2006-12-11 21:00:28 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 6 Jay Turner 2006-12-13 20:50:59 UTC 
QE ack for RHEL5.
Comment 7 Jeremy Katz 2006-12-15 15:55:05 UTC 
I've committed the patch and have it queued to kick off the build just as soon
as there's a go for the kernel patch being in.
Comment 8 RHEL Program Management 2007-02-08 01:38:34 UTC 
A package has been built which should help the problem described in 
this bug report. This report is therefore being closed with a resolution 
of CURRENTRELEASE. You may reopen this bug report if the solution does 
not work for you.
Note You need to log in before you can comment on or make changes to this bug.