search for: register_real_device

...hrough UEFI. My system is: DQ77KB motherboard with bios version 44 Core i7-3779T with VT-d Intel HD graphics 4000 In the qemu log it seem like xen cannot reach the vga-bios. 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_regi...

Folks, I download the Neocleus 1:1 patch from following link: http://lists.xensource.com/archives/html/xen-devel/2007-05/msg01144.html Currently I want to add Neocleus 1:1 Patch to the xen-3.1.0 to make the HVM guest grab the device directly. When I add these patches and recompile and install the Xen source and try to start the HVM guest, the HVM guest can not start and the system hang.

...My second question is: How can i debug the problem? I can''t access domU through SSH after it''s created. When I set gfx_passthru to 0 it''s starting normally. 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:...

...39;14\.2'' ... [ 3.863511] pciback 0000:00:14.2: seizing device [ 5.081737] xen-pciback: backend is vpci [ 239.702436] xen-pciback: vpci: 0000:00:14.2: assign to virtual 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...

...ing): read error qemu: ignoring not-understood drive `/local/domain/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=0x0001...

...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 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 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:...

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.

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.

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

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

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

Hi Keir, Please pull the ia64 trees: http://xenbits.xensource.com/ext/ia64/xen-unstable.hg http://xenbits.xensource.com/ext/ia64/linux-2.6.18-xen.hg This includes updates of acpi related files, save/restore update for pv_ops and bug fixes from Akio, and mini-os update from Samuel Thibault. Thanks, -- yamahata _______________________________________________ Xen-devel mailing list

The OpRegion shouldn''t be mapped 1:1 because the address in the host can''t be used in the guest directly. This patch traps read and write access to the opregion of the Intel GPU config space (offset 0xfc). To work correctly this patch needs a change in hvmloader. HVMloader will allocate 2 pages for the OpRegion and write this address on the config space of the Intel GPU. Qemu

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

Hello, I''m also seeing this exact same problem. I''ve posted on xen-users, but did not get an answer. Venkat seems to be experiencing the same problem as me. I have the latest BIOS for my motherboard DQ35JO. (BIOS ver 933) I''m running a Q6600 as well. It hangs at "Brought up 4 CPUs." I''ve tried all sorts of combinations of Xen versions and kernels to