[Xen-bugs] [Bug 1539] New: OHCI IEEE 1394 Firewire Controller Pass-through to Windows XP HVM DomU But Cannot Detect Digital Video Camera Connected to Firewire Port

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1539

           Summary: OHCI IEEE 1394 Firewire Controller Pass-through to
                    Windows XP HVM DomU But Cannot Detect Digital Video
                    Camera Connected to Firewire Port
           Product: Xen
           Version: unstable
          Platform: x86-64
               URL: http://lists.xensource.com/archives/html/xen-devel/2009-
                    10/msg00535.html
        OS/Version: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: space.time.universe@xxxxxxxxx
                CC: konrad.wilk@xxxxxxxxxx


Using Xen 3.5-unstable changeset 20143 and the available pv-ops dom0 kernels
2.6.30-rc3, 2.6.31-rc6, 2.6.31.1, 2.6.31.4 and 2.6.31.5 I have on my computer,
I managed to pass-through the onboard firewire controller on Intel DQ45CB
motherboard to Windows XP Home Edition SP3 32-bit HVM DomU. Windows XP HVM can
detect the firewire controller. Device manager entry for the firewire
controller shows that it is working properly and has no conflicts. However, a
digital video camera connected to the firewire port cannot be detected in
Windows XP HVM at all.

I was advised by Konrad from Oracle to do testing using a Linux HVM. Hence I
have installed Slackware64 13.0 HVM domU. Slackware64 HVM is also able to
detect the firewire controller. But I could not load the kernel modules for the
firewire controller. Modprobe complains about invalid argument. After applying
the shared IRQ patch from Weidong, Intel to pvops dom0 kernel 2.6.31.5, it
solves an IRQ binding problem for the firewire controller passthrough. However,
I still cannot load kernel modules for the firewire controller in Slackware64
HVM domU. Modprobe still complains about invalid argument.

All the logs and debug messages are in this xen-devel mailing list thread
series:

http://lists.xensource.com/archives/html/xen-devel/2009-10/msg00535.html


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs