From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Singapore Citizen Mr. Teo En Ming (Zhang Enming)" Subject: Re: Cannot start Fedora 19 HVM domU with VGA passthru Date: Thu, 18 Jul 2013 20:29:41 +0800 Message-ID: <51E7DFB5.9070607@gmail.com> References: <51E6B95E.3020500@gmail.com> "\"<20130717215625.GL2924@reaktio.net> <51E7A94E.50005@gmail.com> <6d8cfa90cde86eca5915ff398872b459@mail.shatteredsilicon.net> <51E7BE5F.8000504@gmail.com> <51E7C158.5090706@gmail.com> <51E7C633.6080005@gmail.com> <6ea9f69987a517fe0b1eca8ff677ebf3@mail.shatteredsilicon.net>" <51E7C9BB.6090909@gmail.com>" <937f17404d3880088c5ccda6bf1d5ec6@mail.shatteredsilicon.net> <51E7D04E.2040700@gmail.com> <862077afc84754329c828dfec0504ad7@mail.shatteredsilicon.net> Reply-To: singapore.mr.teo.en.ming@gmail.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------090006010608080202030202" Return-path: In-Reply-To: <862077afc84754329c828dfec0504ad7@mail.shatteredsilicon.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Gordan Bobic Cc: xen-users@lists.xen.org, "Teo En Ming (Zhang Enming)" , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --------------090006010608080202030202 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 18/07/2013 20:03, Gordan Bobic wrote: > On Thu, 18 Jul 2013 19:23:58 +0800, "Singapore Citizen Mr. Teo En Ming > (Zhang Enming)" wrote: >> On 18/07/2013 19:02, Gordan Bobic wrote: >>> On Thu, 18 Jul 2013 18:55:55 +0800, "Singapore Citizen Mr. Teo En >>> Ming (Zhang Enming)" wrote: >>>> On 18/07/2013 18:44, Gordan Bobic wrote: >>>>> On Thu, 18 Jul 2013 18:40:51 +0800, "Singapore Citizen Mr. Teo En >>>>> Ming (Zhang Enming)" wrote: >>>>>> On 18/07/2013 18:29, Gordan Bobic wrote: >>>>>>> On Thu, 18 Jul 2013 18:20:08 +0800, "Singapore Citizen Mr. Teo >>>>>>> En Ming (Zhang Enming)" wrote: >>>>>>>> On 18/07/2013 18:09, Gordan Bobic wrote: >>>>>>>>> On Thu, 18 Jul 2013 18:07:27 +0800, "Singapore Citizen Mr. Teo >>>>>>>>> En Ming (Zhang Enming)" >>>>>>>>> wrote: >>>>>>>>>> On 18/07/2013 16:46, Gordan Bobic wrote: >>>>>>>>>>> On Thu, 18 Jul 2013 16:37:34 +0800, "Singapore Citizen Mr. >>>>>>>>>>> Teo En Ming (Zhang Enming)" >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Although Fedora 19 HVM domU with VGA passthrough cannot >>>>>>>>>>>> start, Debian >>>>>>>>>>>> 7.1.0 amd64 HVM domU with VGA passthrough can start. In >>>>>>>>>>>> Debian 7.1.0 >>>>>>>>>>>> amd64 HVM domU with VGA passthrough, Intel HD Graphics 4600 >>>>>>>>>>>> is listed >>>>>>>>>>>> in lspci -vvv. Please refer to lspci.txt. It is strange >>>>>>>>>>>> that no kernel >>>>>>>>>>>> module is being loaded for Intel HD Graphics 4600. There is >>>>>>>>>>>> no "Kernel >>>>>>>>>>>> driver in use" statement after VGA compatible controller: >>>>>>>>>>>> Intel >>>>>>>>>>>> Corporation Haswell Integrated Graphics Controller (rev 06) >>>>>>>>>>>> (prog-if >>>>>>>>>>>> 00 [VGA controller]). >>>>>>>>>>>> >>>>>>>>>>>> No kernel driver is seen in lsmod. Please refer to lsmod.txt >>>>>>>>>>>> >>>>>>>>>>>> When I tried to load the kernel module by executing >>>>>>>>>>>> "modprobe i915", >>>>>>>>>>>> it complains "no such device". >>>>>>>>>>>> >>>>>>>>>>>> ERROR: could not insert 'i915': No such device >>>>>>>>>>>> >>>>>>>>>>>> So is my Intel HD Graphics 4600 VGA Passthrough to Debian >>>>>>>>>>>> 7.1.0 amd64 >>>>>>>>>>>> HVM domU considered successful since the i915 driver cannot >>>>>>>>>>>> be loaded? >>>>>>>>>>>> >>>>>>>>>>>> Thank you very much. >>>>>>>>>>> >>>>>>>>>>> If you have a driver in dom0 claiming the device (other than >>>>>>>>>>> the xen-pciback >>>>>>>>>>> driver), you cannot pass through that device. If you do >>>>>>>>>>> lspci -ccc on F19 >>>>>>>>>>> and you see the driver in use for that device being >>>>>>>>>>> something other than >>>>>>>>>>> xen-pciback, that would explain why you can't pass it through. >>>>>>>>>>> >>>>>>>>>>> Also, did you first do xl pci-assignable-add for that >>>>>>>>>>> device? This attempts >>>>>>>>>>> to detach the device from it's current driver but doesn't >>>>>>>>>>> always work >>>>>>>>>>> especially for GPUs. The only solution is blacklist the >>>>>>>>>>> driver for the >>>>>>>>>>> device in dom0. The downside is that you cannot run a GUI in >>>>>>>>>>> dom0 on that >>>>>>>>>>> device. >>>>>>>>>> >>>>>>>>>> I cannot start Fedora 19 HVM domU with VGA passthrough at >>>>>>>>>> all. Could >>>>>>>>>> you advise me on the workaround? >>>>>>>>>> >>>>>>>>>> As for the Intel HD Graphics (i915) driver, I have it >>>>>>>>>> blacklisted in >>>>>>>>>> /etc/modprobe.d/blacklist.conf already. Please refer to attached >>>>>>>>>> blacklist.conf. >>>>>>>>> >>>>>>>>> Have you confirm that no other driver is bound to the device >>>>>>>>> in lspci -vvv? >>>>>>>>> Also what version of Xen are you running on each of the >>>>>>>>> distros, and which >>>>>>>>> dom0 kernel? >>>>>>>> >>>>>>>> I have checked "lsmod | grep i915" and the command doesn't return >>>>>>>> anything, which means the kernel module i915 is not loaded in >>>>>>>> dom0. >>>>>>> >>>>>>> Check lspci -vvv,find the device in the output and look for the >>>>>>> lines that say: >>>>>>> Kernel driver in use: >>>>>>> Kernel modules: >>> >>> [...] >>> >>>>>> I have checked lspci -vvv in Ubuntu 13.04 dom0 and the Kernel driver >>>>>> in use is pciback for Intel HD Graphics 4600 IGD. >>>>>> >>>>>> As for Fedora 19 HVM domU, I don't know because I cannot start it. >>>>> >>>>> Starting is not required to do this. Do it before starting the domU. >>>> >>>> Sorry, I don't understand what you're trying to say. >>> >>> On F19, don't worry about starting the domU. In dom0, do lspci -vvv, >>> find the Intel graphics device in the output and find what kernel >>> driver / module are bound to it, if any. You can only pass through >>> a PCI device that is connected to the xen pciback driver, and even >>> then often only if no other driver had connected to the device first >>> since that might leave it in an unknown state. >>> >> >> But I can only start Fedora 19 HVM domU with-out vga passthrough. I >> want to be able to start Fedora 19 HVM domU with vga passthrough. > > You are trying to get one step ahead of what I am talking about. > Forget domU for the moment. Before you can even begin thinking > about the domU you have to make sure the device is available > for assigning in dom0. If you have a driver bound to the device > in dom0 you cannot pass it through to domU. So forget domU until > you have actually confirmed there is no driver bound to the > device in dom0. > > What do the following two lines say for the device in lspci -vvv > in _dom0_ on Fedora: > Kernel driver in use: > Kernel modules: > > Gordan > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > Dear Gordan, I have attached the output of lspci -vvv in Ubuntu 13.04 dom0. The filename of the attachment is dom0-lspci.txt. -- Yours sincerely, Singapore Citizen Mr. Teo En Ming (Zhang Enming) --------------090006010608080202030202 Content-Type: text/plain; charset=UTF-8; name="dom0-lspci.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dom0-lspci.txt" 00:00.0 Host bridge: Intel Corporation Haswell DRAM Controller (rev 06) Subsystem: ASRock Incorporation Device 0c00 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge: Intel Corporation Haswell PCI Express x16 Controller (rev 06) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 VGA compatible controller: Intel Corporation Haswell Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device 0412 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: pciback 00:03.0 Audio device: Intel Corporation Haswell HD Audio Controller (rev 06) Subsystem: ASRock Incorporation Device 0c0c Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: pciback 00:14.0 USB controller: Intel Corporation Lynx Point USB xHCI Host Controller (rev 04) (prog-if 30 [XHCI]) Subsystem: ASRock Incorporation Device 8c31 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: pciback 00:16.0 Communication controller: Intel Corporation Lynx Point MEI Controller #1 (rev 04) Subsystem: ASRock Incorporation Device 8c3a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) Subsystem: ASRock Incorporation Device 153b Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: e1000e 00:1a.0 USB controller: Intel Corporation Lynx Point USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI]) Subsystem: ASRock Incorporation Device 8c2d Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: pciback 00:1b.0 Audio device: Intel Corporation Lynx Point High Definition Audio Controller (rev 04) Subsystem: ASRock Incorporation Device c892 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: pciback 00:1c.0 PCI bridge: Intel Corporation Lynx Point PCI Express Root Port #1 (rev d4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d4) (prog-if 01 [Subtractive decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 00:1d.0 USB controller: Intel Corporation Lynx Point USB Enhanced Host Controller #1 (rev 04) (prog-if 20 [EHCI]) Subsystem: ASRock Incorporation Device 8c26 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: pciback 00:1f.0 ISA bridge: Intel Corporation Lynx Point LPC Controller (rev 04) Subsystem: ASRock Incorporation Device 8c50 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: lpc_ich 00:1f.2 SATA controller: Intel Corporation Lynx Point 6-port SATA Controller 1 [AHCI mode] (rev 04) (prog-if 01 [AHCI 1.0]) Subsystem: ASRock Incorporation Device 8c02 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ahci 00:1f.3 SMBus: Intel Corporation Lynx Point SMBus Controller (rev 04) Subsystem: ASRock Incorporation Device 8c22 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- 01:00.1 Audio device: NVIDIA Corporation GF114 HDMI Audio Controller (rev a1) Subsystem: Gigabyte Technology Co., Ltd Device 3527 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 03:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03) (prog-if 01 [Subtractive decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: --------------090006010608080202030202 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --------------090006010608080202030202--