search for: maxmemorys

Hi all, I'm testing the memory hotplugging on devstack (ocata version). According to the article in https://medium.com/@juergen_thomann/memory-hotplug-with-qemu-kvm-and-libvirt-558f1c635972 , I'm trying to create a virtual machine by setting <maxMemory>. However, I've got an error message in libvirt log as below. 2017-07-20 20:33:21.175+0000: 529: error :

Hi, I've found out that NVDIMM size and label size matter for regular (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the guest OS will not accept the hot plugged memory and will complain with messages such as Block size [0x8000000] unaligned hotplug range: start 0x225000000, size 0x10000000 The start address above is also reported within <memory> element of the hot

Hi I'm trying to Passthrough a GPU to a VM and have it still share its free memory with the host (just like it would with virtio-balloon). Is this something virtio-mem is capable of? I've tried to run it, but it immediately took over 9GB of memory: virt-install --name test --cpu cell0.cpus=0,cell0.memory=4194304,cell1.cpus=1,cell1.memory=4194304 --memory

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

On Fri, Sep 15, 2023 at 02:41:50AM +0100, Daniel Krajnik wrote: > Hi > > I'm trying to Passthrough a GPU to a VM and have it still share its free > memory with the host (just like it would with virtio-balloon). Is this > something virtio-mem is capable of? I've tried to run it, but it immediately > took over 9GB of memory: > > virt-install --name test --cpu >

----- On Feb 15, 2020, at 12:47 AM, Marc Roos M.Roos@f1-outsourcing.eu wrote: > Would you mind sharing your xml? I have strange high host load on idle > windows guest/domain <domain type='kvm'> <name>pathway</name> <uuid>8235e5ae-0756-4286-5407-9fa02d372046</uuid> <description>Pathway Studio Dietrich</description> <memory

Hi , I Sent this to the wrong list (libvirt-devel) on friday ... so i am trying to send it to the correct one this time. Apologize for double posting. I also created a ticket on bugzilla.redhat.com for this https://bugzilla.redhat.com/show_bug.cgi?id=927336 still i am posting it here because is absolutely possible i am doing something wrong and someone here will see it . Description of the

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

Note this fix is incomplete / not ready for upstream: (1) We haven't definitively proven this is the issue. Mor is still investigating and producing the proof. (2) We will need to make a similar change to virt-v2v documentation. Rich.

On Tue, Jun 16, 2020 at 12:54:29PM +0200, Milan Zamazal wrote: > Hi, > > I've found out that NVDIMM size and label size matter for regular > (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the > guest OS will not accept the hot plugged memory and will complain with > messages such as > > Block size [0x8000000] unaligned hotplug range: start

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 >

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

Peter Krempa <pkrempa@redhat.com> writes: > On Tue, Jun 16, 2020 at 12:54:29 +0200, Milan Zamazal wrote: >> Hi, >> > >> I've found out that NVDIMM size and label size matter for regular >> (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the >> guest OS will not accept the hot plugged memory and will complain with >> messages

On Tue, Jun 16, 2020 at 12:54:29 +0200, Milan Zamazal wrote: > Hi, > > I've found out that NVDIMM size and label size matter for regular > (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the > guest OS will not accept the hot plugged memory and will complain with > messages such as > > Block size [0x8000000] unaligned hotplug range: start

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone, Is this being worked on? I rather need this thing... Although my system is Debian Lenny, not RH: kulfon 10.0.0.228 /etc/default % dpkg -l | grep libvirt ii libvirt-bin 0.4.6-10+lenny1 the programs for the libvirt library ii libvirt0 0.4.6-10+lenny1 library for

Hi all, I want to attach cdrom by libvirt.py .But can't find a func in libvirt.py can finish this work. Who can help me ? Regard -- Seven Ling E-mail: jiejie.ling at qq.com

Hi, I can''t seem to get libvirtd to accept remote connections. Both systems are built using genunix''s b130. It seems that connections originating from the xvm0 server itself are fine but as soon as I go on to the other box and run the same python script (or simply virsh) the connection gets dropped immediately. Telnetting to port 16509 confirms that it drops the connection

I run this prog (http://www.compcar.ru/forum/showthread.php?t=7342)and this error appears: Fatal error occurred in main thread. Address:0x004a1f11 Exception:0xc0000005 I added every library whitch Igo needed (native-builtin) / I found them by Ollydebuger in Windows 7/ , but no success :( Could I add some other info to solve this?

This version of the patch includes feedback from jboggs at redhat.com, including fixes to the BuildRequires and Requires in the spec file.

...just looking for some feedback on the direction I'm going. The code won't get all the way to the define stage since I'm in the middle of retrofitting it to use virtinst instead of a home spun node definition.