search for: e820_host

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

On 07.06.23 15:12, Christoph Hellwig wrote: > On Mon, May 22, 2023 at 10:37:09AM +0200, Juergen Gross wrote: >> In normal cases PCI passthrough in PV guests requires to start the guest >> with e820_host=1. So it should be rather easy to limit allocating the >> 64MB in PV guests to the cases where the memory map has non-RAM regions >> especially in the first 1MB of the memory. >> >> This will cover even hotplug cases. The only case not covered would be a >> guest start...

Hi Does someone know how it is possible these parameters: e820_host max_grant_frames to set with libvirt xml config? I use them with xl config but I want to change to libvirt config/tools. (with libvirt 4.10 it is possible to start pvh domains) -- ------ Greetz

On Mon, May 22, 2023 at 10:37:09AM +0200, Juergen Gross wrote: > In normal cases PCI passthrough in PV guests requires to start the guest > with e820_host=1. So it should be rather easy to limit allocating the > 64MB in PV guests to the cases where the memory map has non-RAM regions > especially in the first 1MB of the memory. > > This will cover even hotplug cases. The only case not covered would be a > guest started with e820_host=1...

Hi I need the e820_host option for a passthrough of an digitaldevices dvb-s2 card. Without this I'cant initialize the card in the domU. On an all my domU's with high IO load like an file server I need to set max_grant_frames = 64 or higher. Without this I get a lot of messages on dom0/domU and kernel exception...

On 09.06.23 17:38, Juergen Gross wrote: > On 07.06.23 15:12, Christoph Hellwig wrote: >> On Mon, May 22, 2023 at 10:37:09AM +0200, Juergen Gross wrote: >>> In normal cases PCI passthrough in PV guests requires to start the guest >>> with e820_host=1. So it should be rather easy to limit allocating the >>> 64MB in PV guests to the cases where the memory map has non-RAM regions >>> especially in the first 1MB of the memory. >>> >>> This will cover even hotplug cases. The only case not covered would be a >...

...pcifront pci-0: claiming resource 0000:00:00.1/2 [ 8.005254] pci 0000:00:00.1: address space collision: [mem 0xbe000000-0xbe7fffff 64bit pref] conflicts with System RAM [mem 0x00100000-0x1007fffff] [ 8.005257] pcifront pci-0: Could not claim resource 0000:00:00.1/2! Device offline. Try using e820_host=1 in the guest config. [ 8.005390] mlx4_core: Mellanox ConnectX core driver v1.1 (Dec, 2011) [ 8.005392] mlx4_core: Initializing 0000:00:00.1 [ 8.005431] mlx4_core 0000:00:00.1: device not available (can''t reserve [mem 0xbe000000-0xbe7fffff 64bit pref]) [ 8.005441] mlx4_core 00...

...kernel). > Please remember that guest kernel is not always under full control of > the host admin, so making guests loose 64MB of RAM always, in default > setup isn't good for customers of such VMs... > In normal cases PCI passthrough in PV guests requires to start the guest with e820_host=1. So it should be rather easy to limit allocating the 64MB in PV guests to the cases where the memory map has non-RAM regions especially in the first 1MB of the memory. This will cover even hotplug cases. The only case not covered would be a guest started with e820_host=1 even if no PCI passthrou...

Hi Gordan, I received my Asus GTX 480 today (bought on ebay). Finally I succeeded in - quadrifying my GTX 480  into a Quadro 6000 ( softmod). - overpassing the 3-4GB of RAM on Windows XP 64 bits (domU) by applying a well known patch for Xen. - playing Crysis 2 and Darksiders II for a few minutes. http://img11.hostingpics.net/pics/953254ScreenshotXenSoftModedQuadro6000.png Using nvlfash I

On Mon, Oct 17, 2011 at 05:36:27PM +0200, Dario Faggioli wrote: > Hi everyone, > > I''m trying to setup PCI-passthrough for a network card on a testbox. > With HVM, everything seems to work, while if I try with a pv-guest the > domain crashes! > > Here''s the thing: > -- > # xl pci-list-assignable-devices > 0000:07:00.0 > 0000:07:00.1 > >

...VF on a Dell R620, I''m getting in domU: [ 58.162639] pci 0000:00:00.6: address space collision: [mem 0xd500c000-0xd500ffff 64bit pref] conflicts with System RAM [mem 0x00100000-0x176ffffff] [ 58.162654] pcifront pci-0: Could not claim resource 0000:00:00.6/0! Device offline. Try using e820_host=1 in the guest config. and in dom0 (XEN) mm.c:807: d2: Forcing read-only access to MFN d510c (XEN) mm.c:807: d0: Forcing read-only access to MFN d510c (XEN) mm.c:618:d0 Could not get page ref for pfn d510c (XEN) mm.c:618:d0 Could not get page ref for pfn d510c (XEN) mm.c:618:d2 Could not get page...

On 1/4/19 9:14 AM, Christoph wrote: > Hi > > Does someone know how it is possible these parameters: > > e820_host > max_grant_frames > > to set with libvirt xml config? Currently, those settings are not supported by libvirt. Do you need to adjust them for PCI passthrough to PV domains? I took a quick peek at xl.cfg(5) and based on the description of those settings didn't see a counterpart in...

Hi Does someone know how it is possible these parameters: e820_host max_grant_frames to set with libvirt xml config? I use them with xl config but I want to change to libvirt config/tools. (with libvirt 4.10 it is possible to start pvh domains) -- ------ Greetz

...("ramdisk", string), ("features", string, {''const'': True}), # Use host''s E820 for PCI passthrough. ("e820_host", libxl_defbool), diff -r ac45608496cd -r cdb947baea10 tools/libxl/xl_cmdimpl.c --- a/tools/libxl/xl_cmdimpl.c Thu May 17 16:39:51 2012 +0100 +++ b/tools/libxl/xl_cmdimpl.c Thu May 17 17:51:32 2012 +0100 @@ -843,7 +843,7 @@ static void parse_config_data(const char char *cmdline = NULL...

...ci-0: claiming resource 0000:00:00.0/1pcifront pci-0: claiming resource 0000:00:00.0/6pci 0000:00:00.0: address space collision: [mem 0xf0000000-0xffffffff pref] conflicts with 0000:00:00.0 [mem 0xfdef0000-0xfdef03ff]pcifront pci-0: Could not claim resource 0000:00:00.0/6! Device offline. Try using e820_host=1 in the guest config. This appears to show that the PCI device is conflicting with itself (reg 14 with reg 30) because the address space for reg 30 is different in pciback to pcifront. I have tried setting up the domain with both XM and XL with the same resultAdding passthrough and permissive sett...

I have a system with several reserved ranges low in the e820 map which cause problems when starting PV domains with PCI devices. The machine memory map looks like: (XEN) 0000000000000000 - 0000000000060000 (usable) (XEN) 0000000000060000 - 0000000000068000 (reserved) (XEN) 0000000000068000 - 000000000009ac00 (usable) (XEN) 000000000009ac00 - 00000000000a0000 (reserved) (XEN) 00000000000e0000

Is there anyone actually using VT-d for GPU cards? From what I understand NVidia is impossible, but AMD does work for some cards. I would appreciate any hints from people that are actively using this technology. -- Simon Toth

I''m using Xen 4.3, installed from source on Ubuntu 13.04. I''ve successfully installed a Windows 8 guest, and had Xen pass it an AMD FirePro W7000 GPU (technically 2 PCI devices - the second is for the sound), as well as the virtualised graphics adapter. Windows finds the card fine, and I''ve installed AMD''s drivers. Device Manager says that the card cannot

...;:0},"u":{"kernel":"/boot/vmlinuz-3.2.0-24-generic-pae","slack_memkb":-1,"bootloader":null,"bootloader_args":[],"cmdline":"root=/dev/xvda2 ro ","ramdisk":"/boot/initrd.img-3.2.0-24-generic-pae","e820_host":"<default>"}},"disks":[{"backend_domid":0,"pdev_path":"xen//domains/ fsb.t.org/disk.img ","vdev":"xvda2","backend":"unknown","format":"raw","script":null,"removab...

The following series flushes my documentation queue and replaces previous postings of those patches. The main difference is that the xl cfg file is now formatted using POD instead of markdown and presented as a manpage. I have setup a cron job to build docs/html and publish it at http://xenbits.xen.org/docs/unstable/ (it''s a bit bare right now). The motivation for some of these patches