Cannot start Fedora 19 HVM domU

Cannot start Fedora 19 HVM domU

[Singapore Citizen Mr. Teo En Ming (Zhang Enming)]

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

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.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)


[-- Attachment #2: fedora19 --]
[-- Type: text/plain, Size: 1819 bytes --]

# XL domain configuration file for Fedora 19 x86_64 HVM domU
# Please refer to "man xl.cfg" for further explanations.
# See also docs/misc/xl-network-configuration.markdown and
# docs/misc/xl-disk-configuration.txt
# Written by Teo En Ming (Zhang Enming)
# Email: teo.en.ming@gmail.com
# Mobile Phone: +65-9117-5902
# Country: Singapore
# Date: 17 July 2013 Wed
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' ]

[-- Attachment #3: qemu-dm-Fedora19.log --]
[-- Type: text/x-log, Size: 5508 bytes --]

domid: 3
Strip off blktap sub-type prefix to /etc/xen/images/fedora19.img (drv 'aio')
Using file /etc/xen/images/fedora19.img in read-write mode
Strip off blktap sub-type prefix to /home/teo-en-ming/Fedora-19-x86_64-DVD.iso (drv 'aio')
Using file /home/teo-en-ming/Fedora-19-x86_64-DVD.iso in read-only mode
Watching /local/domain/0/device-model/3/logdirty/cmd
Watching /local/domain/0/device-model/3/command
Watching /local/domain/3/cpu
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = fcff33d4-1f75-4737-ac58-ae26f11a6b4a
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/3/xen_extended_power_mgmt): read error
medium change watch on `hdc' (index: 1): aio:/home/teo-en-ming/Fedora-19-x86_64-DVD.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
vcpu-set: watch node error.
[xenstore_process_vcpu_set_event]: /local/domain/3/cpu has no CPU!
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
xs_read(/local/domain/3/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/3/log-throttling'
medium change watch on `/local/domain/3/log-throttling' - unknown device, ignored
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
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
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
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

[-- Attachment #4: xl-Fedora19.log --]
[-- Type: text/x-log, Size: 85 bytes --]

Waiting for domain Fedora19 (domid 3) to die [pid 3747]
Domain 3 has been destroyed.

[-- Attachment #5: Type: text/plain, Size: 126 bytes --]

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

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Pasi Kärkkäinen]

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 ? 

 
> 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

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Singapore Citizen Mr. Teo En Ming (Zhang Enming)]

[-- Attachment #1: Type: text/plain, Size: 7980 bytes --]

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 #2: lspci.txt --]
[-- Type: text/plain, Size: 6856 bytes --]

00:00.0 Host bridge: Intel Corporation Haswell DRAM Controller (rev 06)
	Subsystem: ASRock Incorporation Device 0c00
	Physical Slot: 0
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: <access denied>

00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
	Subsystem: Red Hat, Inc Qemu virtual machine
	Physical Slot: 1
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] (prog-if 80 [Master])
	Subsystem: XenSource, Inc. Device 0001
	Physical Slot: 1
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
	Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
	Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
	Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
	Region 4: I/O ports at c1a0 [size=16]
	Kernel driver in use: ata_piix

00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01) (prog-if 00 [UHCI])
	Subsystem: Red Hat, Inc Qemu virtual machine
	Physical Slot: 1
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Interrupt: pin D routed to IRQ 23
	Region 4: I/O ports at c180 [size=32]
	Kernel driver in use: uhci_hcd

00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 01)
	Subsystem: Red Hat, Inc Qemu virtual machine
	Physical Slot: 1
	Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 9

00:02.0 VGA compatible controller: Intel Corporation Haswell Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller])
	Subsystem: ASRock Incorporation Device 0412
	Physical Slot: 2
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at f1000000 (64-bit, non-prefetchable) [size=4M]
	Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at c100 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>

00:03.0 Unassigned class [ff80]: XenSource, Inc. Xen Platform Device (rev 01)
	Subsystem: XenSource, Inc. Xen Platform Device
	Physical Slot: 3
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 28
	Region 0: I/O ports at c000 [size=256]
	Region 1: Memory at f0000000 (32-bit, prefetchable) [size=16M]
	Kernel driver in use: xen-platform-pci

00:05.0 Audio device: Intel Corporation Haswell HD Audio Controller (rev 06)
	Subsystem: ASRock Incorporation Device 0c0c
	Physical Slot: 5
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Interrupt: pin A routed to IRQ 36
	Region 0: Memory at f1630000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel

00:06.0 USB controller: Intel Corporation Lynx Point USB xHCI Host Controller (rev 04) (prog-if 30 [XHCI])
	Subsystem: ASRock Incorporation Device 8c31
	Physical Slot: 6
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 88
	Region 0: Memory at f1620000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd

00:07.0 USB controller: Intel Corporation Lynx Point USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI])
	Subsystem: ASRock Incorporation Device 8c2d
	Physical Slot: 7
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 44
	Region 0: Memory at f1638000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: ehci_hcd

00:08.0 Audio device: Intel Corporation Lynx Point High Definition Audio Controller (rev 04)
	Subsystem: ASRock Incorporation Device c892
	Physical Slot: 8
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Interrupt: pin A routed to IRQ 89
	Region 0: Memory at f1634000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel

00:09.0 USB controller: Intel Corporation Lynx Point USB Enhanced Host Controller #1 (rev 04) (prog-if 20 [EHCI])
	Subsystem: ASRock Incorporation Device 8c26
	Physical Slot: 9
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 21
	Region 0: Memory at f1639000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: ehci_hcd

00:1f.0 ISA bridge: Intel Corporation Lynx Point LPC Controller (rev 04)
	Subsystem: Red Hat, Inc Device 1100
	Physical Slot: 31
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 16
	Region 3: Memory at <ignored> (32-bit, non-prefetchable)


[-- Attachment #3: lsmod.txt --]
[-- Type: text/plain, Size: 3671 bytes --]

Module                  Size  Used by
bnep                   17567  2 
rfcomm                 33700  0 
bluetooth             119455  10 rfcomm,bnep
rfkill                 19012  3 bluetooth
binfmt_misc            12957  1 
nfsd                  216170  2 
nfs                   308313  0 
nfs_acl                12511  2 nfs,nfsd
auth_rpcgss            37143  2 nfs,nfsd
fscache                36739  1 nfs
lockd                  67306  2 nfs,nfsd
sunrpc                173730  6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd
ext2                   59231  1 
loop                   22641  0 
snd_hda_codec_realtek   188858  1 
sd_mod                 36136  0 
crc_t10dif             12348  1 sd_mod
tuner_simple           17175  1 
tuner_types            16409  1 tuner_simple
tda9887                12645  1 
tda8290                17278  0 
wm8775                 12749  1 
tuner                  17497  2 
cx25840                39782  1 
pvrusb2               124313  0 
cx2341x                21461  1 pvrusb2
dvb_core               77734  1 pvrusb2
tveeprom               20593  1 pvrusb2
v4l2_common            13222  5 cx2341x,pvrusb2,cx25840,tuner,wm8775
videodev               70889  6 v4l2_common,cx2341x,pvrusb2,cx25840,tuner,wm8775
v4l2_compat_ioctl32    16655  1 videodev
usb_storage            43870  0 
media                  18148  1 videodev
usblp                  17343  0 
snd_hda_intel          26259  2 
snd_hda_codec          78031  2 snd_hda_intel,snd_hda_codec_realtek
snd_hwdep              13186  1 snd_hda_codec
snd_pcm                68083  2 snd_hda_codec,snd_hda_intel
snd_page_alloc         13003  2 snd_pcm,snd_hda_intel
snd_seq                45126  0 
psmouse                69265  0 
snd_seq_device         13176  1 snd_seq
crc32c_intel           12747  0 
serio_raw              12931  0 
joydev                 17266  0 
evdev                  17562  17 
snd_timer              22917  2 snd_seq,snd_pcm
pcspkr                 12579  0 
ghash_clmulni_intel    13173  0 
aesni_intel            50667  0 
parport_pc             22364  0 
parport                31858  1 parport_pc
snd                    52889  12 snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_realtek
soundcore              13065  1 snd
aes_x86_64             16843  1 aesni_intel
aes_generic            33026  2 aes_x86_64,aesni_intel
iTCO_wdt               17081  0 
cryptd                 14517  2 aesni_intel,ghash_clmulni_intel
processor              28157  0 
i2c_piix4              12536  0 
thermal_sys            18040  1 processor
iTCO_vendor_support    12704  1 iTCO_wdt
i2c_core               23876  11 i2c_piix4,videodev,v4l2_common,tveeprom,pvrusb2,cx25840,tuner,wm8775,tda8290,tda9887,tuner_simple
button                 12937  0 
usbhid                 36418  0 
hid                    81328  1 usbhid
ext4                  350763  1 
crc16                  12343  2 ext4,bluetooth
jbd2                   62115  1 ext4
mbcache                13114  2 ext4,ext2
dm_mod                 63645  6 
sg                     25874  0 
sr_mod                 21899  0 
cdrom                  35401  1 sr_mod
ata_generic            12479  0 
uhci_hcd               26865  0 
xhci_hcd               73434  0 
floppy                 53087  0 
ehci_hcd               40215  0 
usbcore               128741  8 ehci_hcd,xhci_hcd,uhci_hcd,usbhid,usblp,usb_storage,pvrusb2
xen_blkfront           17398  3 
ata_piix               29535  0 
usb_common             12354  1 usbcore
xen_netfront           21985  0 
libata                140630  2 ata_piix,ata_generic
scsi_mod              162269  5 libata,sr_mod,sg,usb_storage,sd_mod

[-- Attachment #4: Type: text/plain, Size: 126 bytes --]

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

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Gordan Bobic]

 On Thu, 18 Jul 2013 16:37:34 +0800, "Singapore Citizen Mr. Teo En Ming 
 (Zhang Enming)"	<singapore.mr.teo.en.ming@gmail.com> 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.

 Gordan

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Singapore Citizen Mr. Teo En Ming (Zhang Enming)]

[-- Attachment #1: Type: text/plain, Size: 2107 bytes --]

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)" <singapore.mr.teo.en.ming@gmail.com> 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.
>
> Gordan
>
Dear Gordan,

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.

Thank you very much.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)


[-- Attachment #2: blacklist.conf --]
[-- Type: text/plain, Size: 1644 bytes --]

# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.

# evbug is a debug tool that should be loaded explicitly
blacklist evbug

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

# replaced by e100
blacklist eepro100

# replaced by tulip
blacklist de4x5

# causes no end of confusion by creating unexpected network interfaces
blacklist eth1394

# snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support much
# hardware on its own (Ubuntu bug #2011, #6810)
blacklist snd_intel8x0m

# Conflicts with dvb driver (which is better for handling this device)
blacklist snd_aw2

# causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306)
blacklist i2c_i801

# replaced by p54pci
blacklist prism54

# replaced by b43 and ssb.
blacklist bcm43xx

# most apps now use garmin usb driver directly (Ubuntu: #114565)
blacklist garmin_gps

# replaced by asus-laptop (Ubuntu: #184721)
blacklist asus_acpi

# low-quality, just noise when being used for sound playback, causes
# hangs at desktop session start (Ubuntu: #246969)
blacklist snd_pcsp

# ugly and loud noise, getting on everyone's nerves; this should be done by a
# nice pulseaudio bing (Ubuntu: #77010)
blacklist pcspkr

# EDAC driver for amd76x clashes with the agp driver preventing the aperture
# from being initialised (Ubuntu: #297750). Blacklist so that the driver
# continues to build and is installable for the few cases where its
# really needed.
blacklist amd76x_edac

blacklist i915

blacklist snd_hda_intel

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

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

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Gordan Bobic]

 On Thu, 18 Jul 2013 18:07:27 +0800, "Singapore Citizen Mr. Teo En Ming 
 (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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.
>>
>> Gordan
>>
> Dear Gordan,
>
> 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?

 Gordan

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Singapore Citizen Mr. Teo En Ming (Zhang Enming)]

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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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.
>>>
>>> Gordan
>>>
>> Dear Gordan,
>>
>> 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?
>
> Gordan
>

Dear Gordan,

I have checked "lsmod | grep i915" and the command doesn't return 
anything, which means the kernel module i915 is not loaded in dom0.

I am running Xen 4.4-unstable changeset 27238 with Linux kernel 
3.11.0-rc1 on a Ubuntu 13.04 host.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Gordan Bobic]

 On Thu, 18 Jul 2013 18:20:08 +0800, "Singapore Citizen Mr. Teo En Ming 
 (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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:

 The kernel driver might not be called the same thing in both kernels.

> I am running Xen 4.4-unstable changeset 27238 with Linux kernel
> 3.11.0-rc1 on a Ubuntu 13.04 host.

 And on F19?

 Gordan

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Singapore Citizen Mr. Teo En Ming (Zhang Enming)]

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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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:
>
> The kernel driver might not be called the same thing in both kernels.
>
>> I am running Xen 4.4-unstable changeset 27238 with Linux kernel
>> 3.11.0-rc1 on a Ubuntu 13.04 host.
>
> And on F19?
>
> Gordan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

Dear Gordan,

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.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Gordan Bobic]

 On Thu, 18 Jul 2013 18:40:51 +0800, "Singapore Citizen Mr. Teo En Ming 
 (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>> 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:
>>
>> The kernel driver might not be called the same thing in both 
>> kernels.
>>
>>> I am running Xen 4.4-unstable changeset 27238 with Linux kernel
>>> 3.11.0-rc1 on a Ubuntu 13.04 host.
>>
>> And on F19?
>>
>> Gordan
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>
>
> Dear Gordan,
>
> 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.

 Gordan

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Singapore Citizen Mr. Teo En Ming (Zhang Enming)]

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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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:
>>>
>>> The kernel driver might not be called the same thing in both kernels.
>>>
>>>> I am running Xen 4.4-unstable changeset 27238 with Linux kernel
>>>> 3.11.0-rc1 on a Ubuntu 13.04 host.
>>>
>>> And on F19?
>>>
>>> Gordan
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xen.org
>>> http://lists.xen.org/xen-devel
>>>
>>
>> Dear Gordan,
>>
>> 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.
>
> Gordan
>

Sorry, I don't understand what you're trying to say.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Gordan Bobic]

 On Thu, 18 Jul 2013 18:55:55 +0800, "Singapore Citizen Mr. Teo En Ming 
 (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>>>> 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.

 Gordan

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Singapore Citizen Mr. Teo En Ming (Zhang Enming)]

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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>>>>> 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.
>
> Gordan
>

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.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Gordan Bobic]

 On Thu, 18 Jul 2013 19:23:58 +0800, "Singapore Citizen Mr. Teo En Ming 
 (Zhang Enming)"	<singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>>>> 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)" 
>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Singapore Citizen Mr. Teo En Ming (Zhang Enming)]

[-- Attachment #1: Type: text/plain, Size: 6017 bytes --]

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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>>>>> 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)" 
>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)


[-- Attachment #2: dom0-lspci.txt --]
[-- Type: text/plain, Size: 11002 bytes --]

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- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: <access denied>

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000e000-0000efff
	Memory behind bridge: e0000000-ee0fffff
	Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at ee400000 (64-bit, non-prefetchable) [size=4M]
	Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at f000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at ee834000 (64-bit, non-prefetchable) [disabled] [size=16K]
	Capabilities: <access denied>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at ee820000 (64-bit, non-prefetchable) [disabled] [size=64K]
	Capabilities: <access denied>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at ee840000 (64-bit, non-prefetchable) [size=16]
	Capabilities: <access denied>

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 73
	Region 0: Memory at ee800000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at ee83d000 (32-bit, non-prefetchable) [size=4K]
	Region 2: I/O ports at f080 [size=32]
	Capabilities: <access denied>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at ee83c000 (32-bit, non-prefetchable) [disabled] [size=1K]
	Capabilities: <access denied>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 22
	Region 0: Memory at ee830000 (64-bit, non-prefetchable) [disabled] [size=16K]
	Capabilities: <access denied>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: cfa00000-cfbfffff
	Prefetchable memory behind bridge: 00000000cfc00000-00000000cfdfffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=03, subordinate=04, sec-latency=32
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 23
	Region 0: Memory at ee83b000 (32-bit, non-prefetchable) [disabled] [size=1K]
	Capabilities: <access denied>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: <access denied>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 74
	Region 0: I/O ports at f0d0 [size=8]
	Region 1: I/O ports at f0c0 [size=4]
	Region 2: I/O ports at f0b0 [size=8]
	Region 3: I/O ports at f0a0 [size=4]
	Region 4: I/O ports at f060 [size=32]
	Region 5: Memory at ee83a000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: <access denied>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin C routed to IRQ 11
	Region 0: Memory at ee839000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at f040 [size=32]

01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560] (rev a1) (prog-if 00 [VGA controller])
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at ec000000 (32-bit, non-prefetchable) [disabled] [size=32M]
	Region 1: Memory at e0000000 (64-bit, prefetchable) [disabled] [size=128M]
	Region 3: Memory at e8000000 (64-bit, prefetchable) [disabled] [size=64M]
	Region 5: I/O ports at e000 [disabled] [size=128]
	Expansion ROM at ee000000 [disabled] [size=512K]
	Capabilities: <access denied>

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 10
	Region 0: Memory at ee080000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=03, secondary=04, subordinate=04, sec-latency=32
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
	Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>


[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

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

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Gordan Bobic]

 On Thu, 18 Jul 2013 20:29:41 +0800, "Singapore Citizen Mr. Teo En Ming 
 (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>>>> 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)" 
>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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:
>>
> I have attached the output of lspci -vvv in Ubuntu 13.04 dom0. The
> filename of the attachment is dom0-lspci.txt.

 You need to do this as root, otherwise some of the output is missing.

 And the dump from the machine where you have domU working isn't
 useful, you need to post the same lspci dump from the system
 where it _doesn't_ work.

 Gordan

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Singapore Citizen Mr. Teo En Ming (Zhang Enming)]

[-- Attachment #1: Type: text/plain, Size: 6741 bytes --]

On 18/07/2013 20:35, Gordan Bobic wrote:
> On Thu, 18 Jul 2013 20:29:41 +0800, "Singapore Citizen Mr. Teo En Ming 
> (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
>> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>>>>> 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)" 
>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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:
>>>
>> I have attached the output of lspci -vvv in Ubuntu 13.04 dom0. The
>> filename of the attachment is dom0-lspci.txt.
>
> You need to do this as root, otherwise some of the output is missing.
>
> And the dump from the machine where you have domU working isn't
> useful, you need to post the same lspci dump from the system
> where it _doesn't_ work.
>
> Gordan
>

I have attached the output of lspci -vvv as root in Ubuntu 13.04 dom0. 
The filename of the attachment is root-dom0-lspci.txt.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)


[-- Attachment #2: root-dom0-lspci.txt --]
[-- Type: text/plain, Size: 24862 bytes --]

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- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000e000-0000efff
	Memory behind bridge: e0000000-ee0fffff
	Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [88] Subsystem: ASRock Incorporation Device 0c01
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee00258  Data: 0000
	Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
			ExtTag- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Latency L0 <256ns, L1 <8us
			ClockPM- Surprise- LLActRep- BwNot+
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis- ARIFwd-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- ARIFwd-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -3.5dB
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [140 v1] Root Complex Link
		Desc:	PortNumber=02 ComponentID=01 EltType=Config
		Link0:	Desc:	TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+
			Addr:	00000000fed19000
	Capabilities: [d94 v1] #19
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at ee400000 (64-bit, non-prefetchable) [disabled] [size=4M]
	Region 2: Memory at d0000000 (64-bit, prefetchable) [disabled] [size=256M]
	Region 4: I/O ports at f000 [disabled] [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [d0] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [a4] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at ee834000 (64-bit, non-prefetchable) [disabled] [size=16K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
			ExtTag- RBE- FLReset+
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0 <64ns, L1 <1us
			ClockPM- Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; Disabled- Retrain- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at ee820000 (64-bit, non-prefetchable) [disabled] [size=64K]
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] MSI: Enable- Count=1/8 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at ee840000 (64-bit, non-prefetchable) [size=16]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 74
	Region 0: Memory at ee800000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at ee83d000 (32-bit, non-prefetchable) [size=4K]
	Region 2: I/O ports at f080 [size=32]
	Capabilities: [c8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee002d8  Data: 0000
	Capabilities: [e0] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at ee83c000 (32-bit, non-prefetchable) [disabled] [size=1K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 22
	Region 0: Memory at ee830000 (64-bit, non-prefetchable) [disabled] [size=16K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
			ExtTag- RBE- FLReset+
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0 <64ns, L1 <1us
			ClockPM- Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; Disabled- Retrain- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=01
			Status:	NegoPending- InProgress-
		VC1:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=2 ArbSelect=Fixed TC/VC=04
			Status:	NegoPending- InProgress-
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: cfa00000-cfbfffff
	Prefetchable memory behind bridge: 00000000cfc00000-00000000cfdfffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
			ExtTag- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 <1us, L1 <4us
			ClockPM- Surprise- LLActRep+ BwNot+
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+
			Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+ ARIFwd-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- ARIFwd-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [90] Subsystem: ASRock Incorporation Device 8c10
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=03, subordinate=04, sec-latency=32
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
			ExtTag- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #4, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 <1us, L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #3, PowerLimit 10.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
		RootCap: CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+ ARIFwd-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- ARIFwd-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [90] Subsystem: ASRock Incorporation Device 244e
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 23
	Region 0: Memory at ee83b000 (32-bit, non-prefetchable) [disabled] [size=1K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 73
	Region 0: I/O ports at f0d0 [size=8]
	Region 1: I/O ports at f0c0 [size=4]
	Region 2: I/O ports at f0b0 [size=8]
	Region 3: I/O ports at f0a0 [size=4]
	Region 4: I/O ports at f060 [size=32]
	Region 5: Memory at ee83a000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee00298  Data: 0000
	Capabilities: [70] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin C routed to IRQ 11
	Region 0: Memory at ee839000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at f040 [size=32]

01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560] (rev a1) (prog-if 00 [VGA controller])
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at ec000000 (32-bit, non-prefetchable) [disabled] [size=32M]
	Region 1: Memory at e0000000 (64-bit, prefetchable) [disabled] [size=128M]
	Region 3: Memory at e8000000 (64-bit, prefetchable) [disabled] [size=64M]
	Region 5: I/O ports at e000 [disabled] [size=128]
	Expansion ROM at ee000000 [disabled] [size=512K]
	Capabilities: [60] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [78] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <256ns, L1 <4us
			ClockPM+ Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
	Capabilities: [b4] Vendor Specific Information: Len=14 <?>
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [128 v1] Power Budgeting <?>
	Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 10
	Region 0: Memory at ee080000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [60] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [78] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <256ns, L1 <4us
			ClockPM+ Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=03, secondary=04, subordinate=04, sec-latency=32
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff
	Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [c0] Subsystem: ASRock Incorporation Device 1080


[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

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

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Gordan Bobic]

 On Thu, 18 Jul 2013 20:57:55 +0800, "Singapore Citizen Mr. Teo En Ming 
 (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
> On 18/07/2013 20:35, Gordan Bobic wrote:
>> On Thu, 18 Jul 2013 20:29:41 +0800, "Singapore Citizen Mr. Teo En 
>> Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
>>> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>>>> 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)" 
>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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:
>>>>
>>> I have attached the output of lspci -vvv in Ubuntu 13.04 dom0. The
>>> filename of the attachment is dom0-lspci.txt.
>>
>> You need to do this as root, otherwise some of the output is 
>> missing.
>>
>> And the dump from the machine where you have domU working isn't
>> useful, you need to post the same lspci dump from the system
>> where it _doesn't_ work.
>>
>> Gordan
>>
>
> I have attached the output of lspci -vvv as root in Ubuntu 13.04
> dom0. The filename of the attachment is root-dom0-lspci.txt.

 Right, that is showing
 Kernel driver in use: pciback
 for the Intel VGA device.

 But that is expected, you said you have it working on Ubuntu.
 You now need to make sure you have the same lspci output on
 Fedora dom0 before you start the domU.

 Gordan

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Singapore Citizen Mr. Teo En Ming (Zhang Enming)]

On 18/07/2013 21:04, Gordan Bobic wrote:
> On Thu, 18 Jul 2013 20:57:55 +0800, "Singapore Citizen Mr. Teo En Ming 
> (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
>> On 18/07/2013 20:35, Gordan Bobic wrote:
>>> On Thu, 18 Jul 2013 20:29:41 +0800, "Singapore Citizen Mr. Teo En 
>>> Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
>>>> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>>>>> 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)" 
>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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:
>>>>>
>>>> I have attached the output of lspci -vvv in Ubuntu 13.04 dom0. The
>>>> filename of the attachment is dom0-lspci.txt.
>>>
>>> You need to do this as root, otherwise some of the output is missing.
>>>
>>> And the dump from the machine where you have domU working isn't
>>> useful, you need to post the same lspci dump from the system
>>> where it _doesn't_ work.
>>>
>>> Gordan
>>>
>>
>> I have attached the output of lspci -vvv as root in Ubuntu 13.04
>> dom0. The filename of the attachment is root-dom0-lspci.txt.
>
> Right, that is showing
> Kernel driver in use: pciback
> for the Intel VGA device.
>
> But that is expected, you said you have it working on Ubuntu.
> You now need to make sure you have the same lspci output on
> Fedora dom0 before you start the domU.
>
> Gordan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

Dear Gordan,

I think you are confused. I only have *one* dom0, which is the Ubuntu 
13.04 dom0. I don't have any other dom0.

What I am trying to do is to start Fedora 19 HVM domU in Ubuntu 13.04 
dom0, but am unable to.

Hope this clears everything.

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Gordan Bobic]

 On Thu, 18 Jul 2013 21:13:54 +0800, "Singapore Citizen Mr. Teo En Ming 
 (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
> On 18/07/2013 21:04, Gordan Bobic wrote:
>> On Thu, 18 Jul 2013 20:57:55 +0800, "Singapore Citizen Mr. Teo En 
>> Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
>>> On 18/07/2013 20:35, Gordan Bobic wrote:
>>>> On Thu, 18 Jul 2013 20:29:41 +0800, "Singapore Citizen Mr. Teo En 
>>>> Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
>>>>> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>>>> 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)" 
>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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:
>>>>>>
>>>>> I have attached the output of lspci -vvv in Ubuntu 13.04 dom0. 
>>>>> The
>>>>> filename of the attachment is dom0-lspci.txt.
>>>>
>>>> You need to do this as root, otherwise some of the output is 
>>>> missing.
>>>>
>>>> And the dump from the machine where you have domU working isn't
>>>> useful, you need to post the same lspci dump from the system
>>>> where it _doesn't_ work.
>>>>
>>>
>>> I have attached the output of lspci -vvv as root in Ubuntu 13.04
>>> dom0. The filename of the attachment is root-dom0-lspci.txt.
>>
>> Right, that is showing
>> Kernel driver in use: pciback
>> for the Intel VGA device.
>>
>> But that is expected, you said you have it working on Ubuntu.
>> You now need to make sure you have the same lspci output on
>> Fedora dom0 before you start the domU.
>>
> I think you are confused. I only have *one* dom0, which is the Ubuntu
> 13.04 dom0. I don't have any other dom0.
>
> What I am trying to do is to start Fedora 19 HVM domU in Ubuntu 13.04
> dom0, but am unable to.
>
> Hope this clears everything.

 It does, thanks. I was under the impression you were dual booting dom0s
 and one was letting you boot domU and the other wasn't. Apologies.

 Gordan

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Singapore Citizen Mr. Teo En Ming (Zhang Enming)]

On 18/07/2013 21:55, Gordan Bobic wrote:
> On Thu, 18 Jul 2013 21:13:54 +0800, "Singapore Citizen Mr. Teo En Ming 
> (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
>> On 18/07/2013 21:04, Gordan Bobic wrote:
>>> On Thu, 18 Jul 2013 20:57:55 +0800, "Singapore Citizen Mr. Teo En 
>>> Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
>>>> On 18/07/2013 20:35, Gordan Bobic wrote:
>>>>> On Thu, 18 Jul 2013 20:29:41 +0800, "Singapore Citizen Mr. Teo En 
>>>>> Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
>>>>>> 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)" <singapore.mr.teo.en.ming@gmail.com> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>>>>> 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)" 
>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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:
>>>>>>>
>>>>>> I have attached the output of lspci -vvv in Ubuntu 13.04 dom0. The
>>>>>> filename of the attachment is dom0-lspci.txt.
>>>>>
>>>>> You need to do this as root, otherwise some of the output is missing.
>>>>>
>>>>> And the dump from the machine where you have domU working isn't
>>>>> useful, you need to post the same lspci dump from the system
>>>>> where it _doesn't_ work.
>>>>>
>>>>
>>>> I have attached the output of lspci -vvv as root in Ubuntu 13.04
>>>> dom0. The filename of the attachment is root-dom0-lspci.txt.
>>>
>>> Right, that is showing
>>> Kernel driver in use: pciback
>>> for the Intel VGA device.
>>>
>>> But that is expected, you said you have it working on Ubuntu.
>>> You now need to make sure you have the same lspci output on
>>> Fedora dom0 before you start the domU.
>>>
>> I think you are confused. I only have *one* dom0, which is the Ubuntu
>> 13.04 dom0. I don't have any other dom0.
>>
>> What I am trying to do is to start Fedora 19 HVM domU in Ubuntu 13.04
>> dom0, but am unable to.
>>
>> Hope this clears everything.
>
> It does, thanks. I was under the impression you were dual booting dom0s
> and one was letting you boot domU and the other wasn't. Apologies.
>
> Gordan
>
Dear Gordan,

Do you know how to solve the problem of Fedora 19 HVM domU not starting 
up in Ubuntu 13.04 dom0 with Intel IGD VGA passthrough?

-- 
Yours sincerely,

Singapore Citizen Mr. Teo En Ming (Zhang Enming)

Re: Cannot start Fedora 19 HVM domU with VGA passthru

[Gordan Bobic]

 On Thu, 18 Jul 2013 22:41:24 +0800, "Singapore Citizen Mr. Teo En Ming 
 (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
> On 18/07/2013 21:55, Gordan Bobic wrote:
>> On Thu, 18 Jul 2013 21:13:54 +0800, "Singapore Citizen Mr. Teo En 
>> Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
>>> On 18/07/2013 21:04, Gordan Bobic wrote:
>>>> On Thu, 18 Jul 2013 20:57:55 +0800, "Singapore Citizen Mr. Teo En 
>>>> Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:
>>>>> On 18/07/2013 20:35, Gordan Bobic wrote:
>>>>>> On Thu, 18 Jul 2013 20:29:41 +0800, "Singapore Citizen Mr. Teo 
>>>>>> En Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>> wrote:
>>>>>>> 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)" <singapore.mr.teo.en.ming@gmail.com> 
>>>>>>>> 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)" 
>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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)" 
>>>>>>>>>>>>>>>>>> <singapore.mr.teo.en.ming@gmail.com> 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:
>>>>>>>>
>>>>>>> I have attached the output of lspci -vvv in Ubuntu 13.04 dom0. 
>>>>>>> The
>>>>>>> filename of the attachment is dom0-lspci.txt.
>>>>>>
>>>>>> You need to do this as root, otherwise some of the output is 
>>>>>> missing.
>>>>>>
>>>>>> And the dump from the machine where you have domU working isn't
>>>>>> useful, you need to post the same lspci dump from the system
>>>>>> where it _doesn't_ work.
>>>>>>
>>>>>
>>>>> I have attached the output of lspci -vvv as root in Ubuntu 13.04
>>>>> dom0. The filename of the attachment is root-dom0-lspci.txt.
>>>>
>>>> Right, that is showing
>>>> Kernel driver in use: pciback
>>>> for the Intel VGA device.
>>>>
>>>> But that is expected, you said you have it working on Ubuntu.
>>>> You now need to make sure you have the same lspci output on
>>>> Fedora dom0 before you start the domU.
>>>>
>>> I think you are confused. I only have *one* dom0, which is the 
>>> Ubuntu
>>> 13.04 dom0. I don't have any other dom0.
>>>
>>> What I am trying to do is to start Fedora 19 HVM domU in Ubuntu 
>>> 13.04
>>> dom0, but am unable to.
>>>
>>> Hope this clears everything.
>>
>> It does, thanks. I was under the impression you were dual booting 
>> dom0s
>> and one was letting you boot domU and the other wasn't. Apologies.
>>
>
> Do you know how to solve the problem of Fedora 19 HVM domU not
> starting up in Ubuntu 13.04 dom0 with Intel IGD VGA passthrough?

 I never used Intel GPUs for this sort of thing. Did you try it with
 secondary passthrough (normal PCI device passthrough without
 gfx_passthru option set)?