Re: [Xen-devel] Cannot start Fedora 19 HVM domU with VGA passthru

["Singapore Citizen Mr. Teo En Ming (Zhang Enming)" <singapore.mr.teo.en.ming@xxxxxxxxx>]

On 18/07/2013 05:56, Pasi Kärkkäinen wrote:
> On Wed, Jul 17, 2013 at 11:33:50PM +0800, Singapore Citizen Mr. Teo En Ming 
> (Zhang Enming) wrote:
> > Hi,
> >
> > I can start Windows 8 Enterprise and Windows 8.1 Pro HVM domUs but I
> > cannot start Fedora 19 HVM domU. The domU configuration files
> > between Windows 8 HVM domUs and Fedora 19 HVM domU are very similar,
> > basically Fedora 19 HVM domU configuration file is copied from
> > Windows 8 HVM domU. When I tried to start Fedora 19 HVM domU, the
> > LCD monitor remains blank screen permanently.
> >
> > I have attached Fedora 19 HVM domU configuration file and the
> > relevant log files.
> >
> > Please advise.
> >
> > Thank you very much.
> You forgot to mention this issue is related to VGA passthru in the subject.
>
> Does the F19 HVM guest start if you disable gfx_passthru, and remove the GPU 
> from the pci = [] list,
> so only passthru the USB stuff etc ?
Yes. Fedora 19 HVM domU does start if I disable gfx_passthru and remove 
the IGD from the pci = [ ] list.
>   
> > device_model_version="qemu-xen-traditional"
> > name="Fedora19"
> > builder="hvm"
> > vcpus=4
> > memory=2048
> > on_poweroff="destroy"
> > on_reboot="restart"
> > on_crash="destroy"
> > disk=[ 'format=raw, vdev=hda, access=rw, target=/etc/xen/images/fedora19.img', 
> > 'format=raw, vdev=hdc, access=ro, devtype=cdrom, 
> > target=/home/teo-en-ming/Fedora-19-x86_64-DVD.iso' ]
> > vif=[ 'bridge=virbr0,type=ioemu,model=e1000' ]
> > #boot=[c|d|n]
> > #Selects the emulated virtual device to boot from. Options are hard disk (c), 
> > cd-rom (d) or network/PXE (n).
> > #Multiple options can be given and will be attempted in the order they are 
> > given. e.g. to boot from cd-rom
> > #but fallback to the hard disk you can give dc. The default is cd.
> > #boot="dc"
> > boot="c"
> > acpi=1
> > #xen_platform_pci=1
> > #viridian=1
> > #stdvga=1
> > vnc=1
> > vnclisten="0.0.0.0"
> > vncdisplay=0
> > vncunused=1
> > vncpasswd=""
> > sdl=0
> > usb=1
> > usbdevice="tablet"
> > # Enable Xen VGA Passthrough
> > gfx_passthru=1
> > # VGA Passthrough Gigabyte Geforce GTX 560 1 GB GDDR5 PCI Express x16 VGA card.
> > #pci = [ 
> > '01:00.0','01:00.1','00:1b.0','00:1a.0','00:1a.1','00:1a.2','00:1a.7','00:1d.0','00:1d.1','00:1d.2','00:1d.7'
> >  ]
> > # PCI Passthrough Intel HD Audio Controller.
> > #pci = [ '00:1b.0' ]
> > # PCI Passthrough all the USB Controllers.
> > # pci = [ 
> > '00:1a.0','00:1a.1','00:1a.2','00:1a.7','00:1d.0','00:1d.1','00:1d.2','00:1d.7' 
> > ]
> > # Passthrough Intel HD Graphics 4600, audio controllers and USB controllers
> > pci = [ '00:02.0','00:03.0','00:14.0','00:1a.0','00:1b.0','00:1d.0' ]
> > #pci = [ '00:02.0' ]
> > dm-command: hot insert pass-through pci dev
> > register_real_device: Assigning real physical device 00:02.0 ...
> > register_real_device: Disable MSI translation via per device option
> > register_real_device: Disable power management
> > pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such 
> > file or directory: 0x0:0x2.0x0
> I wonder what these /dev/xen/pci_iomul errors are ..
>
>
>
> > pt_register_regions: IO region registered (size=0x00400000 base_addr=0xee400004)
> > pt_register_regions: IO region registered (size=0x10000000 base_addr=0xd000000c)
> > pt_register_regions: IO region registered (size=0x00000040 base_addr=0x0000f001)
> > pci_intx: intx=1
> > register_real_device: Real physical device 00:02.0 registered successfuly!
> > IRQ type = INTx
> > dm-command: hot insert pass-through pci dev
> > register_real_device: Assigning real physical device 00:03.0 ...
> > register_real_device: Disable MSI translation via per device option
> > register_real_device: Disable power management
> > pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such 
> > file or directory: 0x0:0x3.0x0
> > pt_register_regions: IO region registered (size=0x00004000 base_addr=0xee834004)
> > pci_intx: intx=1
> > register_real_device: Real physical device 00:03.0 registered successfuly!
> > IRQ type = INTx
> > dm-command: hot insert pass-through pci dev
> > register_real_device: Assigning real physical device 00:14.0 ...
> > register_real_device: Disable MSI translation via per device option
> > register_real_device: Disable power management
> > pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such 
> > file or directory: 0x0:0x14.0x0
> > pt_register_regions: IO region registered (size=0x00010000 base_addr=0xee820004)
> > pci_intx: intx=1
> > register_real_device: Real physical device 00:14.0 registered successfuly!
> > IRQ type = INTx
> > dm-command: hot insert pass-through pci dev
> > register_real_device: Assigning real physical device 00:1a.0 ...
> > register_real_device: Disable MSI translation via per device option
> > register_real_device: Disable power management
> > pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such 
> > file or directory: 0x0:0x1a.0x0
> > pt_register_regions: IO region registered (size=0x00000400 base_addr=0xee83c000)
> > pci_intx: intx=1
> > register_real_device: Real physical device 00:1a.0 registered successfuly!
> > IRQ type = INTx
> > dm-command: hot insert pass-through pci dev
> > register_real_device: Assigning real physical device 00:1b.0 ...
> > register_real_device: Disable MSI translation via per device option
> > register_real_device: Disable power management
> > pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such 
> > file or directory: 0x0:0x1b.0x0
> And here..
>
> > pt_register_regions: IO region registered (size=0x00004000 base_addr=0xee830004)
> > pci_intx: intx=1
> > register_real_device: Real physical device 00:1b.0 registered successfuly!
> > IRQ type = INTx
> > dm-command: hot insert pass-through pci dev
> > register_real_device: Assigning real physical device 00:1d.0 ...
> > register_real_device: Disable MSI translation via per device option
> > register_real_device: Disable power management
> > pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such 
> > file or directory: 0x0:0x1d.0x0
> And here aswell.
>
>
> > pt_register_regions: IO region registered (size=0x00000400 base_addr=0xee83b000)
> > pci_intx: intx=1
> > register_real_device: Real physical device 00:1d.0 registered successfuly!
> > IRQ type = INTx
> > igd_write_opregion: Map OpRegion: bcaec018 -> fdffc018
> > pt_iomem_map: e_phys=e0000000 maddr=d0000000 type=8 len=268435456 index=2 
> > first_map=1
> > pt_iomem_map: e_phys=f1000000 maddr=ee400000 type=0 len=4194304 index=0 
> > first_map=1
> > pt_iomem_map: e_phys=f1620000 maddr=ee820000 type=0 len=65536 index=0 
> > first_map=1
> > pt_iomem_map: e_phys=f1630000 maddr=ee834000 type=0 len=16384 index=0 
> > first_map=1
> > pt_iomem_map: e_phys=f1634000 maddr=ee830000 type=0 len=16384 index=0 
> > first_map=1
> > pt_iomem_map: e_phys=f1638000 maddr=ee83c000 type=0 len=4096 index=0 first_map=1
> > pt_iomem_map: e_phys=f1639000 maddr=ee83b000 type=0 len=4096 index=0 first_map=1
> > pt_ioport_map: e_phys=c100 pio_base=f000 len=64 index=4 first_map=1
> > Waiting for domain Fedora19 (domid 3) to die [pid 3747]
> > Domain 3 has been destroyed.
> -- Pasi
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.



--
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

Attachment: lspci.txt
Description: Text document

Attachment: lsmod.txt
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel