search for: pt_iomul_init

hi, I want to pass through "01:00.0",declared as pci=['01:00.0'] in cfg file. but found error log "pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x1:0x0.0x0". in qemu-dm-example.hvm.log In fact, /dev/xen/pci_iomul does not exist. So where /dev/xen/pci_iomul implemented ? I have searched xen and linux code, found nothing. where pci_iomul device...

...Is this a known problem when booting through xen.efi or is it a bug? 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=0xf7000004) pt_register_regions: IO region registered (size=0x10000000 base_addr=0xe000000c) pt_register_regions: IO regi...

...in/1/log-throttling'' medium change watch on `/local/domain/1/log-throttling'' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 03:00.0 ... pt_iomul_init: Error: pt_iomul_init can''t open file /dev/xen/pci_iomul: No such file or directory: 0x3:0x0.0x0 pt_register_regions: IO region registered (size=0x10000000 base_addr=0xd000000c) pt_register_regions: IO region registered (size=0x00010000 base_addr=0xfba20004) pt_register_regions: IO region...

...ly. How can I tell what went wrong? When I create domU I get this in logs: dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 03:00.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: 0x3:0x0.0x0 pt_register_regions: IO region registered (size=0x10000000 base_addr=0xd000000c) pt_register_regions: IO region registered (size=0x00010000 base_addr=0xfe7f0004) pt_register_regions: IO region...

...tual slot 0 [jason@virt-host ~]$ cat /var/log/xen/qemu-dm-Windows7.log ... dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 00:14.2 ... 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.0x2 pt_register_regions: IO region registered (size=0x00004000 base_addr=0xfeb00004) pci_intx: intx=1 register_real_device: Real physical device 00:14.2 registered successfuly! IRQ type = INTx ......

...ze: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 0d:00.0 ... register_real_device: Enable 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: 0xd:0x0.0x0 pt_register_regions: IO region registered (size=0x00000100 base_addr=0x00009001) pt_register_regions: IO region registered (size=0x00004000 base_addr=0xdf03c004) pt_register_regions: IO region...

Hello I am new in XEN and Linux. I am trying the VGA passthru. I can xen-pciback.hide EtherNet, Serial Com port. But when I xen-pciback.hide my VGA. I can no longer login to the Linux(Fedora 12). Then how can I xm create a XP DomU guest? Can anyone help? I am using Intel Q35 MB with Intel Core2 CPU. _______________________________________________ Xen-users mailing list

I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB

Hi developers, I met some domU issues and the log suggests missing interrupt. Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938 In summary, this is the suspicious log: (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3 I''ve checked the code in question and found that mode 3 is an ''reserved_1'' mode. I want to trace down the source of this