similar to: kernel log flooded with: xen_balloon: reserve_additional_memory: add_memory() failed: -17

Hi All Back in August there was a report of these errors popping up in dmesg, and as far as I can tell it's still unresolved even in the latest kernel. System RAM resource [mem 0xc8000000-0xcfffffff] cannot be added xen_balloon: reserve_additional_memory: add_memory() failed: -17 On this example its running 3.10.20-11.el6.centos.alt.x86_64 To replicate this just disable Dom0 memory

My /var/log/messages log is being flooded with kernel messages showing the following messages Aug 1 11:22:52 host43 kernel: System RAM resource 48000000 - 4fffffff cannot be added Aug 1 11:22:52 host43 kernel: xen_balloon: reserve_additional_memory: add_memory() failed: ?17 Doing a search I found a thread from xen-devel that talks a bit about it. I?m not sure if this is related to the same

Hi, > biting this behavior. The specific > error I''m seeing is > > xen_balloon: reserve_additional_memory: add_memory() failed: -17 > System RAM resource 88000000 - 8fffffff cannot be added > > This is a lab system that I''m actively working on so I can give > whatever info you need or run whatever. Below is the xl info and xl > dmesg output [...]

Dear List, I have problems using Xen dom0 Kernel including the IMA Kernel Module (Linux Integrity Measurement - http://linux-ima.sourceforge.net/) The IMA supports only kernel > 2.6.32 and I dont know how to find and build a Xen dom0 kernel in version greater or equal than 2.6.32. There is just kernel 2.6.18-xen in the Mercurial repository which is normally used during the standard

Dear List, I have problems using Xen dom0 Kernel including the IMA Kernel Module (Linux Integrity Measurement - http://linux-ima.sourceforge.net/) The IMA supports only kernel > 2.6.32 and I dont know how to find and build a Xen dom0 kernel in version greater or equal than 2.6.32. There is just kernel 2.6.18-xen in the Mercurial repository which is normally used during the standard

On Thu, 2020-02-13 at 15:07 -0800, Johan Hattne via samba wrote: >> Dear all; >> >> I'm trying to use winbindd to resolve names in an AD setup. I can >> authenticate just fine, but I've noticed that for some users "getent >> passwd" returns a GECOS field populated with displayName from the LDAP >> servers and for others is does not. For

Hello, I am doing tests to convert old rotting servers into a big shiny new Xen platform. I have been able to migrate a Windows 2003 server without a scratch. I am trying to do the same thing with Windows 2000 Server but things aren''t so great... I made an image from the disk that worked in a machine. Then I boot on this image using Xen. Windows 2000 starts to boot up then give me a

Hello, I wants to make a self compiled kernel for my domUs on a debian etch server with Xen 3.1.4 and 2.6.18.8 dom0 kernel. So, I download sources for linux-2.6.26.8, and I enabled all the Xen features : Symbol: HVC_XEN [=y] Symbol: XEN_BALLOON [=y] Symbol: XEN_FBDEV_FRONTEND [=y] Symbol: XEN_SCRUB_PAGES [=y] Symbol: XEN_KBDDEV_FRONTEND [=y] Symbol: XEN_BLKDEV_FRONTEND [=y] Symbol:

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where

Hi, I am doing some experimentation with xen and Ceph and have a problem booting my guest when my disk = [] uses an alternate block script. Installation from a .iso was ok since the boot device was a file but now trying to boot from the rbd neither the hvmbuilder or pygrub can start as they treat the first value after target= as the /dev node to try and use. My disk parameter looks like: disk =

https://bugzilla.mindrot.org/show_bug.cgi?id=2627 Bug ID: 2627 Summary: Documentation update: semantic of ClientAliveCountMax 0 unclear Product: Portable OpenSSH Version: 7.3p1 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 Component: sshd

This is the follow-up of "[PATCH RFCv1 0/5] mm/memory_hotplug: selective merging of memory resources" [1] Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant

Hi all, I added a 2nd line vif = [''....''] to my config file but no NIC was added to the VM Thanks in advance for any help ! Yassine _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

This is the follow up of [1]: [PATCH v1 0/3] mm/memory_hotplug: Make virtio-mem play nicely with kexec-tools I realized that this is not only helpful for virtio-mem, but also for dax/kmem - it's a fix for that use case (see patch #3) of persistent memory. Also, while testing, I discovered that kexec-tools will *not* add dax/kmem memory (anything not directly under the root when parsing

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where

Some add_memory*() users add memory in small, contiguous memory blocks. Examples include virtio-mem, hyper-v balloon, and the XEN balloon. This can quickly result in a lot of memory resources, whereby the actual resource boundaries are not of interest (e.g., it might be relevant for DIMMs, exposed via /proc/iomem to user space). We really want to merge added resources in this scenario where

Hi, I''m running OpenBSD 4.5 as HVM guest. Here is part of my .cfg file: kernel = ''/usr/lib/xen-3.2-1/boot/hvmloader'' device_model = ''/usr/lib64/xen-3.2-1/bin/qemu-dm'' builder = ''hvm'' It is running fine with vnc, but when I ssh to openbsd, and I type cat, vi, etc. it freezes. Any ideas? Thanks in advance. -- Sergio Roberto Charpinel

This series is based on [1]: [PATCH v2 00/10] virtio-mem: paravirtualized memory That will hopefull get picked up soon, rebased to -next. The following patches were reverted from -next [2]: [PATCH 0/3] kexec/memory_hotplug: Prevent removal and accidental use As discussed in that thread, they should be reverted from -next already. In theory, if people agree, we could take the first two patches