search for: pt_register_regions

Displaying 12 results from an estimated 12 matches for "pt_register_regions".

2012 Nov 12
4
xen EFI boot and vga-passthrough
...ster_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 region registered (size=0x00000040 base_addr=0x0000f001) setup_vga_pt: vga bios size (0x0) is invalid! register_real_device: Setu...
2010 Jun 24
1
VGA passthrough - guest shows blank screen on startup
...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 registered (size=0x00000100 base_addr=0x0000a001) pt_register_regions: Expansion ROM registered (size=0x00020000 base_addr=0xf...
2013 Feb 27
8
VGA passthrough radeon 4850 as primary card
...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 registered (size=0x00000100 base_addr=0x0000d001) pt_register_regions: Expansion ROM registered (size=0x00020000 base_addr=0xf...
2008 Dec 12
22
Disabling cirrus-vga
Hi xen developers, Does any of you know how to disable the cirrus-vga emulation for hvm in xen? I have been trying to disable that from the source codes, but even with that, I still see a VGA controller when I boot up my guest domain. In particular, I would like to do this because I am passing through a graphics card to my guest domain using direct pass through. Thanks, - billy
2013 Jan 16
1
rombios unable to loaded MPT BIOS
...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 registered (size=0x00040000 base_addr=0xdf040004) pt_register_regions: Expansion ROM registered (size=0x00080000 base_addr=0xd...
2010 May 08
8
VGA Passthru
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
2012 Sep 01
1
Can't pass through onboard Intel HDA, works in KVM
...egister_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 ... [jason@virt-host ~]$ lspci -tv -[0000:00]-+-00.0 ATI Technologies Inc RD890 PCI to PCI bridge (external gfx0 port B)...
2010 Apr 22
2
pci-attach - HOWTO
Hi, I tried to attach passrough io device to domU, the command (ended successfully in dom0), but when I entered the domU and typed the "lspci" command I didn''t see the new device, although the dom0 removed it from the "pci-list-assignable-devices". When I tried to detach it from the domU, the detach command returned with timeout error. What did I miss? perhaps I
2013 Jul 23
73
Bug: Limitation of <=2GB RAM in domU persists with 4.3.0
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
2008 Jun 27
2
PCI device assignment to guests (userspace)
Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.
2008 Jun 27
2
PCI device assignment to guests (userspace)
Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.
2012 Dec 03
21
Issue about domU missing interrupt
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