search for: e_phys

Hi, everyone! I am working on xen-4.2.0 with spice remote connect. My host is Fedora 14 and guest is win7. I have installed spice package and now I can connect to guest by spice client. For better graphics experience, I want to try the VGA passthrough. With spice tool, I have to create a VM by xl command, and now I am wondering if it supports VGA passghrouth? If so, how should I test it ?

...se() failed xen be: console-0: xen be: console-0: initialise() failed initialise() failed xen be: console-0: xen be: console-0: initialise() failed initialise() failed xen be: console-0: xen be: console-0: initialise() failed initialise() failed cirrus vga map change while on lfb mode pt_iomem_map: e_phys=f3100000 maddr=df040000 type=0 len=262144 index=3 first_map=1 pt_iomem_map: e_phys=f3140000 maddr=df640000 type=0 len=262144 index=3 first_map=1 pt_iomem_map: e_phys=f3180000 maddr=df03c000 type=0 len=16384 index=1 first_map=1 pt_iomem_map: e_phys=f3184000 maddr=df63c000 type=0 len=16384 index=1 fi...

...0xfbbfc004) pt_register_regions: IO region registered (size=0x00000100 base_addr=0x0000b801) pt_register_regions: Expansion ROM registered (size=0x00020000 base_addr=0xfbbc0000) pci_intx: intx=1 register_real_device: Real physical device 04:00.0 registered successfuly! IRQ type = INTx pt_iomem_map: e_phys=e0000000 maddr=d0000000 type=8 len=268435456 index=0 first_map=1 pt_iomem_map: e_phys=f1040000 maddr=fba20000 type=0 len=65536 index=2 first_map=1 pt_iomem_map: e_phys=f1050000 maddr=fbafc000 type=0 len=16384 index=0 first_map=1 pt_iomem_map: e_phys=f1054000 maddr=fbbfc000 type=0 len=16384 index=0...

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

...map(PCIDevice *pci_dev, int region_num, { AssignedDevice *r_dev = container_of(pci_dev, AssignedDevice, dev); AssignedDevRegion *region = &r_dev->v_addrs[region_num]; - PCIRegion *real_region = &r_dev->real_device.regions[region_num]; uint32_t old_ephys = region->e_physbase; uint32_t old_esize = region->e_size; int first_map = (region->e_size == 0); - int ret = 0; + int ret; DEBUG("e_phys=%08x r_virt=%p type=%d len=%08x region_num=%d \n", e_phys, region->u.r_virtbase, type, e_size, region_num); @@ -166,27 +166,1...

...map(PCIDevice *pci_dev, int region_num, { AssignedDevice *r_dev = container_of(pci_dev, AssignedDevice, dev); AssignedDevRegion *region = &r_dev->v_addrs[region_num]; - PCIRegion *real_region = &r_dev->real_device.regions[region_num]; uint32_t old_ephys = region->e_physbase; uint32_t old_esize = region->e_size; int first_map = (region->e_size == 0); - int ret = 0; + int ret; DEBUG("e_phys=%08x r_virt=%p type=%d len=%08x region_num=%d \n", e_phys, region->u.r_virtbase, type, e_size, region_num); @@ -166,27 +166,1...

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.

...map(PCIDevice *pci_dev, int region_num, { AssignedDevice *r_dev = container_of(pci_dev, AssignedDevice, dev); AssignedDevRegion *region = &r_dev->v_addrs[region_num]; - PCIRegion *real_region = &r_dev->real_device.regions[region_num]; uint32_t old_ephys = region->e_physbase; uint32_t old_esize = region->e_size; int first_map = (region->e_size == 0); - int ret = 0; + int ret; DEBUG("e_phys=%08x r_virt=%p type=%d len=%08x region_num=%d \n", e_phys, region->u.r_virtbase, type, e_size, region_num); @@ -166,27 +166,1...

...map(PCIDevice *pci_dev, int region_num, { AssignedDevice *r_dev = container_of(pci_dev, AssignedDevice, dev); AssignedDevRegion *region = &r_dev->v_addrs[region_num]; - PCIRegion *real_region = &r_dev->real_device.regions[region_num]; uint32_t old_ephys = region->e_physbase; uint32_t old_esize = region->e_size; int first_map = (region->e_size == 0); - int ret = 0; + int ret; DEBUG("e_phys=%08x r_virt=%p type=%d len=%08x region_num=%d \n", e_phys, region->u.r_virtbase, type, e_size, region_num); @@ -166,27 +166,1...

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

I''ve seen a recent report claiming that it works: http://linux-bsd-sharing.blogspot.pt/2012/10/howto-xen-413-windows-8-hvm-domu-with.html However, in my case, with a slightly different HW configuration the story is totally different. :-（ My config: HW: I7-3770 + AsRock H77M-ITX board Dom0: Debian Wheezy stock xen (v4.1.3) + Debian stock kernel (3.2.x / 3.6.x) 64 bit version. Note that

...list search yielded (http://comments.gmane.org/gmane.comp.emulators.xen.devel/128172), however there was no solution for an HVM VM. I''ve attached the log file for booting. The expansion/option ROM gets installed at 0xf7a00000 and is first accessed and mapped with the line: pt_iomem_map: e_phys=f3000001 maddr=f7a00000 type=8 len=524288 index=6 first_map=1 However the following log line seems to immediately map the same address space to a strange e_phys location: pt_iomem_map: e_phys=ffffffff maddr=f7a00000 type=8 len=524288 index=6 first_map=0 Any help or suggestions would be appreciat...