Bug 455004

Summary: kernel-xen-2.6.21.xx: not possible to load ivtv-module
Product: [Fedora] Fedora Reporter: Rolf Linder <mail>
Component: kernel-xenAssignee: Xen Maintainance List <xen-maint>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 8   
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-01-09 06:40:31 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 Rolf Linder 2008-07-11 12:20:29 UTC
Description of problem:

Unable to load ivtv-module in kernel-xen-2.6.21.xxx

Version-Release number of selected component (if applicable):
Since kernel-xen-2.6.21.xx (in Fedora7) you're unable to load the ivtv-module
into the domU kernel (also with the needed kernel parm 'swiotlb=force'. with
kernel 2.6.20.xxx its working as a charm...but with 2.6.21 it ends up with a
kernel panic (and the crash of the domU)

How reproducible:
run a kernel 2.6.21-based domU (for example a fedora8 domU) and build the
ivtv-0.10.6 driver and 'modprobe ivtv'

Steps to Reproduce:
1. setup fedora8 domU (add kernel parm 'swiotlb=force')
2. build ivtv-driver
3. modprobe ivtv
  
Actual results:
domU crash / kernel panic

Expected results:
Load of this module


Since Fedora9 does currently not provide any PCI passthrough support you're
unable to use any actual fedora domU guests with a ivtv-module loaded....the
last working solution is to setup a fedora7 guest...

Additional info:

scenario is used to build a mythtv-backend system running in a domU which does
work on fedora7 but not anymore with fedora8 (kernel crash) or fedora9 (no pci
passthrogh)

probably see also http://www.ivtvdriver.org

Comment 1 Bug Zapper 2008-11-26 10:59:41 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2009-01-09 06:40:31 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.