search for: rolu

Using Xen 4.2 unstable rev. 25483. I get errors like this: pt_pci_read_config: [00:10:0] Error: Failed to read register with offset exceeding FFh. [Offset:ffh][Length:1] in my qemu log for a domU with some devices passed through to it. I investigated and found that at hw/pass-through.c line 1717

When booting a recently compiled Xen 4.2 on Ubuntu 12.04, dom0 crashes. I''ve included a serial console log below. I''ve used: Xen 4.2 unstable rev. 25483, compiled on the same machine. I had to apply the AT_EMPTY_PATH patch from http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to get it to compile. Linux 3.2.0-25, which is the default kernel in Ubuntu''s

I was reading the Wiki page here: http://wiki.xen.org/wiki/VTd_HowTo don''t know how updated it is, BUT at the top it said: -------------------- -------------------- -------------------- -------------------- -------------------- -------------------- _Xen 4.1 xl tools notes _ * Only devices with FLR capabilities are supported. * Passing through a PCI card without FLR capability

...========== commit fa2e8e3bc869c04d4a4d9b8f70c1cab7e53778d6 Author: Jan Beulich <jbeulich@suse.com> Date: Fri Jun 29 17:06:25 2012 +0100 passthrough: fix off-by-one in PCI config space register index check Register 255 (0xff) is still valid to be accessed. Reported-by: Rolu <rolu@roce.org> Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>

Just out of annoyance more than curiosity, but ever since I started using Xen 4.2-unstable rev-25467, every time I try to run "sudo xl create <domu_config_file>", or "sudo xl reboot", or "sudo xl destroy", it always gives me this message: "*xend is running, which prevents xl from working correctly. If you still want to force the execution of xl please

I''ve been trying to pass through a GPU to a domU, so far with a lot of trouble but finally a success. PCI passthrough works, I''ve had the usb hubs work successfully. Today I tried to pass through my ATI card to an ubuntu hvm domU with no gfx_passthru and got this: [...] (XEN) memory_map:add: dom14 gfn=f3040 mfn=f7c40 nr=4 (XEN) memory_map:remove: dom14 gfn=f3040 mfn=f7c40 nr=4