search for: maxmemory

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 : virDomainDefCheckUnsupportedMemoryHotplug:1192 : unsupported configuration: memory hotplug tunables <maxMemory> are not supported by this hypervisor driver virt-aa-helper: error: c...

...t;. Is this observation correct? Is it guaranteed to be stable in future versions? I need to determine the right NVDIMM size to make the subsequent memory modules correctly aligned and then I can't change the NVDIMM size, to not damage data stored in the NVDIMM. Additionally, when adjusting maxMemory due to NVDIMM presence, should I increase it by the specified NVDIMM <size> or a different value? Thank you, Milan

...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 maxMemory=65536,maxMemory.slots=8 --memdev model=virtio-mem,target.node=0,target.block=2048,target.size=1000 --disk size=400 --network network=ai --location=/tmp/debian-12.1.0-amd64-netinst.iso --os-variant=debian11 --graphics none --extra-args "console=ttyS0 Best wishes, Daniel -------------- ne...

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 memory during runtime until it reaches a fixed maximum va...

...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 > maxMemory=65536,maxMemory.slots=8 --memdev > model=virtio-mem,target.node=0,target.block=2048,target.size=1000 --disk > size=400 --network network=ai > --location=/tmp/debian-12.1.0-amd64-netinst.iso --os-variant=debian11 > --graphics none --extra-args "console=ttyS0 When using PCI device a...

...;name>pathway</name> <uuid>8235e5ae-0756-4286-5407-9fa02d372046</uuid> <description>Pathway Studio Dietrich</description> <memory unit='KiB'>16146944</memory> <currentMemory unit='KiB'>4147456</currentMemory> <!-- maxMemory unit='KiB' slots='8'>16146944</maxMemory --> <vcpu placement='static' current='2'>4</vcpu> <vcpus> <vcpu id='0' enabled='yes' hotpluggable='no'/> <vcpu id='1' enabled='yes' hotplu...

...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 problem: When the virsh setmem command is used to inflate (or deflate) the balloon on a VM to which 8GB of MaxMemory or more are allocated then the information reported with virsh dominfo , virsh dumpxml after the balloon change has been performed are wrong. The actual balloon is inflated correctly though and that is verifiable both in the vm itself and through the "virsh dommemstat" commands. Platfo...

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 VM on start. This is also the memory the guest is able to use if the balloon driver is not loaded as the balloon driver voluntarily gives up memory...

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.

...nd then I can't change the NVDIMM size, to not damage data > stored in the NVDIMM. Libvirt doesn't ever assign a "base" address value itself. We just start QEMU, and then fill in the XML "base" with the value that QEMU has assigned. > Additionally, when adjusting maxMemory due to NVDIMM presence, should I > increase it by the specified NVDIMM <size> or a different value? IIRC, maxMemory has to allow for the sum of the basic RAM amount, plus RAM intended to be used for all possible future (NV)DIMMS that will be hotplugged. Regards, Daniel -- |: https://ber...

...173.el7_8.1.x86_64 > libvirt-daemon-driver-qemu-4.5.0-23.el7_7.6.x86_64 > qemu-kvm-1.5.3-173.el7_8.1.x86_64 > The guest Linux OS is Suse. > The VM cfg does contain the mem balloon device configuration. > Inside of the VM we have a Kubernetes. The host system has 64GB, the VM > has maxmemory and currentmemory set to 32GB. Ok, so even with the VM running, your host has many 10's of GB of free memory available for other tasks. > I would like to ask you, how we can test that the memory ballooning > mechanism works? Does it works on this version or not. What I see > on the h...

...73.el7_8.1.x86_64 > libvirt-daemon-driver-qemu-4.5.0-23.el7_7.6.x86_64 > qemu-kvm-1.5.3-173.el7_8.1.x86_64 > The guest Linux OS is Suse. > The VM cfg does contain the mem balloon device configuration. > Inside of the VM we have a Kubernetes. The host system has 64GB, the > VM has maxmemory and currentmemory set to 32GB. Ok, so even with the VM running, your host has many 10's of GB of free memory available for other tasks. > I would like to ask you, how we can test that the memory ballooning > mechanism works? Does it works on this version or not. What I see on > th...

...MM support so I don't know the > intricacies. I've cc'd Martin Kletzander who did that part. Martin, do you know how the QEMU part is supposed to work? I haven't received any response on the QEMU list, do you know who could I ask directly? >> Additionally, when adjusting maxMemory due to NVDIMM presence, should I >> increase it by the specified NVDIMM <size> or a different value? >> >> Thank you, >> Milan >>

...rectly > aligned and then I can't change the NVDIMM size, to not damage data > stored in the NVDIMM. Unfortunatelly I didn't implement NVDIMM support so I don't know the intricacies. I've cc'd Martin Kletzander who did that part. > > Additionally, when adjusting maxMemory due to NVDIMM presence, should I > increase it by the specified NVDIMM <size> or a different value? > > Thank you, > Milan >

...nit__', '__module__', '_conn', '_o', 'attachDevice', 'autostart', 'blockPeek', 'blockStats', 'connect', 'coreDump', 'create', 'destroy', 'detachDevice', 'info', 'interfaceStats', 'maxMemory', 'maxVcpus', 'memoryPeek', 'migrate', 'name', 'pinVcpu', 'reboot', 'resume', 'save', 'schedulerParameters', 'schedulerType', 'setAutostart', 'setMaxMemory', 'setMemory', 'setSchedulerPar...

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

...aybe I''m just doing something wrong. xvm 8974 1 0 15:13:03 ? 0:00 /usr/lib/libvirtd -d -l xvm0# cat /etc/libvirt/libvirtd.conf listen_tls=0 listen_tcp=1 tls_no_verify_certificate=0 tls_no_verify_certificate=0 xvm0# python test.py xen+tcp://xvm0 Dom Domain-0, state: 1, maxMemory: -1, memory: 2097152, nbVirtCPU: 4, cpuTime: 4160258030391 xvm0# virsh -c xen+tcp://xvm0 list Id Name State ---------------------------------- 0 Domain-0 running remote$ virsh -c "xen+tcp://xvm0" list error: server closed connection error: failed to con...

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.