similar to: Memory ballooning

What about running tasks/containers directly on the host? -----Original Message----- To: Daniel P. Berrangé Cc: libvirt-users@redhat.com Subject: RE: EXT: Re: KVM/QEMU Memory Ballooning Hi Daniel, Thank you very much for the quick answer. Now it is clear how this memballooning driver works, and how it can be managed manually. I really appreciate your answer. Regards, Csongor -----Original

On Thu, Sep 17, 2020 at 09:06:51AM +0000, Sprencz, Pal Csongor (GE Healthcare) wrote: > In short we have a ScientificLinux7 base host OS system, on top of > that I would want to run a KVM/QEMU virtual machine. > The kvm version is used on the host OS is the following. > qemu-kvm-common-1.5.3-173.el7_8.1.x86_64 > libvirt-daemon-driver-qemu-4.5.0-23.el7_7.6.x86_64 >

On Tue, Feb 11, 2020 at 18:48:43 +0100, Lentes, Bernd wrote: > Hi guys, Hi Bernd, > > despite reading hours and hours in the internet i'm still struggling with > "memory", "currentmemory" and "maxMemory". to briefly summarize what those three knobs do: 1) memory - this is the initial memory size for a VM. qemu grants this amount of memory to the

Oh to bad. I am currently working on some hybrid solution having mesos as an orchestrator combined with some kvm/qemu vm's. dcos does not allow this, and I wondered maybe if your kubernetes was limiting your options there also. -----Original Message----- Cc: libvirt-users Subject: RE: EXT: Re: KVM/QEMU Memory Ballooning Unfortunaltly it is not way what we can apply, due to the containers

Hi guys, despite reading hours and hours in the internet i'm still struggling with "memory", "currentmemory" and "maxMemory". Maybe you can help me to sort it out. My idea is that a guest has an initial value of memory (which "memory" seems to be) when booting. We have some Windows 10 guests which calculate some stuff and i would like to increase

Hi list, I try to understand memory ballooning. I have a xen server (kernel 2.6.27.54-0.2-xen) with 32 gb total memory. A domU has been started with "memory=4096" and "maxmem=8192". This is the status of the balloon driver in the domU: test:~ # cat /proc/xen/balloon Current allocation: 4194304 kB Requested target: 4194304 kB Minimum target: 565248 kB Maximum

I''m trying to configure GRUB to allocate fixed amount of dedicated memory to dom0, according to this best practices thread (http://wiki.xensource.com/xenwiki/XenBestPractices | "Xen dom0 dedicated memory and preventing dom0 memory ballooning "). When I reboot, dom0 has the fixed amount of memory as it was configured, but neither xm info shows the rest of memory available

Hi all, How can I manage automatically memory ballooning under a kvm host (C5.6 and future C6)?? For example if I define a kvm guest to boot up with 512MB of RAM and I have configured 1GB as a maximum memory for this guest, how can I allocate this memory when guest will need it?? And the opposite question, can memory balloon be deallocated?? And is it possible to do this automatically or

I have a xen server setup that I want to install a lot of vms on if possible. The vms will have no utilization for the most part; and brief utilization when active. The server has 2GB of RAM. We were running into a problem were the dom0 would not let us add anymore vms because we were out of physical memory. I have started to read about memory ballooning and hoping someone could point me

Hi, all I am trying to get used memory of a running vm using libvirt and then to calculate the memory usage, but with no luck. 1.The used memory returned by virDomainGetInfo is equal to max memory with no virtio balloon driver set. When using virtio balloon driver and setting currentMemory less than memory in the xml, the used memory returned by virDomainGetInfo is nearly equal to

> On Tue Feb 11 06:01:10 UTC 2014, Rusty Russell wrote: > Hi all! > > We're debating the design of the balloon for the OASIS spec. > Noone likes the current one, but there are fundamental usage pattern > questions which we're fumbling with. > > So if you know anyone who is using it in production? If, so, how? In > particular, would you be happy with

On Sun, Jul 12, 2020, 12:31 Mauricio Tavares <raubvogel at gmail.com> wrote: > On Sun, Jul 12, 2020 at 3:15 PM Kay Schenk <kay.schenk at gmail.com> wrote: > > > > Hello all-- > > I'm in a bind trying to reset an older Nether DSL modem. I did a manual > > reset on it. It was set up as "pass thru" by me and I want to "undo" > that.

On 20/02/14 14:53 +1030, Rusty Russell wrote: >Adam Litke <alitke at redhat.com> writes: >>> On Tue Feb 11 06:01:10 UTC 2014, Rusty Russell wrote: >>> Hi all! >>> >>> We're debating the design of the balloon for the OASIS spec. >>> Noone likes the current one, but there are fundamental usage pattern >>> questions which

On Wed, May 18, 2016 07:39, Mauricio Tavares wrote: > On Wed, May 18, 2016 at 4:32 AM, James Hogarth > <james.hogarth at gmail.com> wrote: >> On 17 May 2016 20:52, "Mauricio Tavares" <raubvogel at gmail.com> >> wrote: >>> >>> On Tue, May 17, 2016 at 3:04 PM, <cpolish at surewest.net> wrote: >>> > On 2016-05-17 12:09,

Hi, Since this message(https://www.redhat.com/archives/libvirt-users/2012-October/msg00054.html) qemu folks have released one minor version in the 1.2 branch and shiny new 1.3 some days ago and the problem still persists. At first I has blamed libvirt, but I was not correct at all - since I have released package ``slices'' for myself including both newer libvirth and qemu, I wasn`t able

CC'ing virtualization list. On (Thu) 31 Mar 2016 [19:00:24], Dr. David Alan Gilbert wrote: > Hi, > I was reading the balloon code and am confused as to how/if ballooning > works on hosts where the host page size is larger than the > target page size. > > static void balloon_page(void *addr, int deflate) > { > #if defined(__linux__) > if

CC'ing virtualization list. On (Thu) 31 Mar 2016 [19:00:24], Dr. David Alan Gilbert wrote: > Hi, > I was reading the balloon code and am confused as to how/if ballooning > works on hosts where the host page size is larger than the > target page size. > > static void balloon_page(void *addr, int deflate) > { > #if defined(__linux__) > if

Perhaps a bit off-topic (I asked on the rescue list -- http://web.archiveorange.com/archive/v/OaDWVGdLhxWVWIEabz4F -- and was told to try here), but I am kinda shooting in the dark: I have been finding online scattered and vague info stating that this card can be made to work with a sparc solaris 10 box (http://old.nabble.com/eSATA-or-firewire-in-Solaris-Sparc-system-td27150246.html is the

We have some test servers running SLES11SP1 and we''ve updated to the latest kernel from Novell: 2.6.32.13-0.5-xen Since running the updates on these servers our xen ballooning parameters are not working. Because of memory problems in the past we set dom0 to 2048 meg of ram in grub and set the following parameters in /etc/xen/xend-config.sxp: (dom0-min-mem 2048) (enable-dom0-ballooning

When you pass a device in the pci chain (after virsh nodedev-dettach'ing it from host) to the guest, how much is passed without being emulated/abstracted?