similar to: does virsh have a history with timestamps ?

Hi ML, i'm thinking about using balloon memory for our domains. We have about 15 domains running concurrently, and i think it might be nice if a domain requires more RAM it grabs it, and if it don't need it anymore, it releases it. But i have no experience with it. So i have some questions: - is live migration possible with balloon ? - is it stable ? - the domain needs an appropriate

Hi, i have atwo node HA-cluster with pacemaker, corosync, libvirt and KVM. Recently i configured a new VirtualDomain which runs fine, but live Migration does not succeed. This is the error: VirtualDomain(vm_snipanalysis)[14322]: 2019/09/18_16:56:54 ERROR: snipanalysis: live migration to ha-idg-2 failed: 1 Sep 18 16:56:54 [6970] ha-idg-1 lrmd: notice: operation_finished:

Hi, i wanted to benchmark a windows guest, compare standard driver and virtio driver. I installed the domain first with an IDE disk. I followed https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows to install the virtIO driver. In the device manager my VirtIO disk is recognized as a VirtIO SCSI disk from RedHat which seems ok for me. But the driver is, following the device

Hi, i'm playing a bit around with vcpus. My guest is Windows 10 1903. This is the excerpt from the config: ... <vcpu placement='static' current='2'>4</vcpu> <vcpus> <vcpu id='0' enabled='yes' hotpluggable='no'/> <vcpu id='1' enabled='yes' hotpluggable='yes'/> <vcpu id='2'

Hi, i have a Linux domain (Ubuntu 14.04) where we like to be able to change the amount of usable memory. We have a balloon device and statistics are switched in 5 sec. rhythm. The domain shows very quickly changes (following top) when we change the memory size with setmem, but the host does not show changes in the use of memory for the respective domain. Is that expected behavior ? Host is SLES

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

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, i'm cuurently a bit confused if a guest does have a valid snapshot or not. This is the xml: ... <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/crispor_1604/crispor_1604.sn'/> <backingStore type='file' index='1'> <format

----- On Feb 7, 2020, at 3:43 PM, Peter Krempa pkrempa@redhat.com wrote: > On Fri, Feb 07, 2020 at 15:25:22 +0100, Lentes, Bernd wrote: ... > > Libvirt is probably lacking the metadata for the snapshot. That is not a > problem though, because since libvirt doesn't support deletion of > external snapshots anyways currently you'd need to use the below > approach anyways.

----- On Jun 13, 2019, at 1:08 PM, Bernd Lentes bernd.lentes@helmholtz-muenchen.de wrote: I found further information in /var/log/messages for both occurrences: 2019-06-01T03:05:31.620725+02:00 ha-idg-2 systemd-coredump[14253]: Core Dumping has been disabled for process 30590 (qemu-system-x86). 2019-06-01T03:05:31.712673+02:00 ha-idg-2 systemd-coredump[14253]: Process 30590 (qemu-system-x86) of

----- On Jun 5, 2019, at 4:49 PM, Peter Krempa pkrempa@redhat.com wrote: > On Wed, Jun 05, 2019 at 13:33:49 +0200, Lentes, Bernd wrote: >> Hi Peter, >> >> thanks for your help. >> >> ----- On Jun 5, 2019, at 9:27 AM, Peter Krempa pkrempa@redhat.com wrote: > > [...] > >> >> > >> > So that's interresting. Usually assertion

----- On Jun 13, 2019, at 9:56 AM, Peter Krempa pkrempa@redhat.com wrote: > > Thanks for comming back to me with the information. > > Unfortunately this is not a full debug log but I can try to tell you > what I see here: I configured libvirtd that way: ha-idg-1:~ # grep -Ev '^$|#' /etc/libvirt/libvirtd.conf log_level = 1 log_filters="1:qemu 3:remote 4:event

----- On Feb 14, 2020, at 4:13 PM, Peter Krempa pkrempa@redhat.com wrote: > > Sounds like qemu doesn't support unplug of vcpus. Which version of qemu > do you use? ha-idg-2:~ # rpm -qa|grep qemu qemu-seabios-1.11.0-5.18.1.noarch qemu-ovmf-x86_64-2017+git1510945757.b2662641d5-3.16.1.noarch qemu-block-curl-2.11.2-5.18.1.x86_64 qemu-sgabios-8-5.18.1.noarch

Pacemaker always knows where its resources are running. Query it, stop the domain, then use the queried location as the host to which to issue the snapshot? Cheers, Peter On Mon, 15 Oct 2018, 20:36 Lentes, Bernd, < bernd.lentes@helmholtz-muenchen.de> wrote: > Hi, > > i have a two node cluster with virtual guests as resources. > I'd like to snapshot the guests once in the

Hi, i try to run virt-manager on a SLES 11 SP1 box. I'm using kernel 2.6.32.12 and virt-manager 0.9.4-106.1.x86_64 . The system is a 64bit box. Here is the output: ========================= pc56846:/media/idg2/SysAdmin_AG_Wurst/software_und_treiber/virt_manager/sles_11_sp1 # virt-manager & [1] 9659 pc56846:/media/idg2/SysAdmin_AG_Wurst/software_und_treiber/virt_manager/sles_11_sp1 #

Hi, i have a strange situation: A domain is still running where domblklist points to a snapshot file and also dumpxml says the current drive is that snapshot file. But the file has been deleted hours ago. And the domain is still running. I can login via ssh, the database and the webserver are still running, domain is performant. How can that be ? Also lsof shows that the file is deleted:

Hi, recently i had some domains stopped without any obvious reason for me. Unfortunately i didn't find the cause. I'd like to log information about the domains that i have more information the next time this will happen. In /etc/libvirt/libvirtd.conf i have: log_level = 3 log_outputs="3:file:/var/log/libvirt/libvirtd.log" which creates enormous log files, but with logrotate and

Hi, i'm using virt-manager to manage serveral guests on a sles 11 host. For one guest, i configured a password to enter the console via virt-manager (not via VNC). How can i get rid of it ? Thanks in advance. Bernd -- Bernd Lentes Systemadministration Institut f?r Entwicklungsgenetik Geb?ude 35.34 - Raum 208 HelmholtzZentrum m?nchen bernd.lentes at helmholtz-muenchen.de phone: +49 89

Hi, i have a two node cluster with virtual guests as resources. I'd like to snapshot the guests once in the night and thought i had a procedure. But i realize that things in a cluster are a bit more complicated than expected :-)) I will shutdown the guests to have a clean snapshot. I can shutdown the guests via pacemaker. But then arises the first problem: When i issue a "virsh

Hi, i can store the disk of a guest in a plain partition which isn't formatted. That's no problem, i did it already several times, although the promised speed increase didn't appear. But is it possible to create from such a guest a snapshot in a .sn file using virsh ? Regards, Bernd -- Bernd Lentes Systemadministration Institut für Entwicklungsgenetik Gebäude 35.34 - Raum