similar to: Libvirt Virtualization Problem

________________________________ From: centos-virt-bounces at centos.org <centos-virt-bounces at centos.org> on behalf of Laurentiu Soica <laurentiu at soica.ro> Sent: Sunday, August 14, 2016 10:17 AM To: Discussion about the virtualization on CentOS Subject: Re: [CentOS-virt] Nested KVM issue More details on the subject: I suppose it is a nested KVM issue because it raised after I

Reports posted look good for me. Config should provide the best available performance for cloud VM (L2) on Compute Node. 1. Please, remind me what goes wrong from your standpoint ? 2. Which CPU is installed on Compute Node && how much RAM ? Actually , my concern is :- Number_of_ Cloud_VMs versus Number_CPU_Cores ( not threads) Please, check `top` report in

I would attempt to decrease number of VCPUS allocated to cloud VMs. Say try 4 => 2 . My guess there is not enough VCPUs to run OS itself. I also guess CPU model << Haswell. Please , confirm ( or not) if possible. Since Haswell was launched via my experience Intel Xeons based on this kernel (or latter kernels ) behaves much better then SandyBridge or IvyBridge based. Boris.

Sorry, How you trigger the problem ? B. ________________________________ From: centos-virt-bounces at centos.org <centos-virt-bounces at centos.org> on behalf of Laurentiu Soica <laurentiu at soica.ro> Sent: Tuesday, August 16, 2016 3:28 AM To: Discussion about the virtualization on CentOS Subject: Re: [CentOS-virt] Nested KVM issue Hello, The issue reproduced again and it

Is KSM enabled on your Compute Nodes ( presuming CentOS 7.2 on bare metal ) ? ________________________________ From: centos-virt-bounces at centos.org <centos-virt-bounces at centos.org> on behalf of Laurentiu Soica <laurentiu at soica.ro> Sent: Tuesday, August 16, 2016 5:25 AM To: Discussion about the virtualization on CentOS Subject: Re: [CentOS-virt] Nested KVM issue Running the

I would enable ksmtuned logging ,if it has been done verify logs ________________________________ From: centos-virt-bounces at centos.org <centos-virt-bounces at centos.org> on behalf of Laurentiu Soica <laurentiu at soica.ro> Sent: Tuesday, August 16, 2016 7:16 AM To: Discussion about the virtualization on CentOS Subject: Re: [CentOS-virt] Nested KVM issue Yes. It is on both

Hello, 1. <domain type='kvm' id='6'> <name>baremetalbrbm_1</name> <uuid>534e9b54-5e4c-4acb-adcf-793f841551a7</uuid> <memory unit='KiB'>104857600</memory> <currentMemory unit='KiB'>104857600</currentMemory> <vcpu placement='static'>36</vcpu> <resource>

It sounds weird, but attempt to disable KSM and see would it help or no ? ________________________________ From: centos-virt-bounces at centos.org <centos-virt-bounces at centos.org> on behalf of Laurentiu Soica <laurentiu at soica.ro> Sent: Wednesday, August 17, 2016 4:56 AM To: Discussion about the virtualization on CentOS Subject: Re: [CentOS-virt] Nested KVM issue Enabled the

Hello Borins, 1. So, in about three days after a reboot (this happened several times already) the compute node reports high CPU usage. It has 36 vCPUs and it reports a load higher than 40. Usually the load is about 2 or 3. The VMs qemu-kvm processes reports 100% CPU usage (for a VM with 4 CPU it reports almost 400%, for one with 1 CPU it reports almost 100%). The VMs are not accessible anymore

The CPUs are IvyBridge microarchitecture, Xeon E5-2670 v2. I could try lowering the vCPUs but I doubt it would help. Please note that the same VMs are running just fine (with a load of 2 out of an acceptable 36 on the compute node) for about 3 days after a restart. ?n lun., 15 aug. 2016 la 08:42, Boris Derzhavets <bderzhavets at hotmail.com> a scris: > I would attempt to decrease

Hi, Recently We've upgraded some KVM hosts from Fedora 29 to Fedora 30 and now experience broken VM configurations on filesystem after virsh blockcommit. Commands "virsh dumpxml ..." and "virsh dumpxml --inactive ..." is showing diffrent configuration than the one on filesystem. In case of restart libvirtd or system reboot, there are broken VM xml configurations on

Hello, I have an OpenStack setup in virtual environment on CentOS 7. The baremetal has *nested KVM* enabled and 1 compute node as a VM. Inside the compute node I have multiple VMs running. After about every 3 days the VMs get inaccessible and the compute node reports high CPU usage. The qemu-kvm process for each VM inside the compute node reports full CPU usage. Please help me with some hints

For myself KSM is unpredictable feature. The problem is Compute, just this node does "copy on write" , so only Compute. My concern exactly is where would it lead to worse or better Guest behavior ? I am not expecting complete fix. I would track via top/htop and dmesg via Cron on 1-2 hr period. ________________________________ From: centos-virt-bounces at centos.org

Hello, The issue reproduced again and it doesn't look like a swap problem. Some details: on the baremetal, from top: top - 08:08:52 up 5 days, 16:43, 3 users, load average: 36.19, 36.05, 36.05 Tasks: 493 total, 1 running, 492 sleeping, 0 stopped, 0 zombie %Cpu(s): 3.5 us, 87.9 sy, 0.0 ni, 8.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 12357451+total, 14296000 free,

Hello. I have a strange error with one of my VMs. If i use dumpxml to save a VM description the source part of the network part is missing. This prevents redifining the machine from the dumped xml file: This is how it looks before dumpxml: <interface type='bridge'> <mac address='52:54:00:34:a1:56'/> <source bridge='br406'/>

So I notice that some operations by libvirt such as creating a snapshot actually change the source of the active disk image for a domain without requiring a restart of the vm. How can this be achieved manually? There are instances where I am manipulating files with qemu-img or virsh commands and afterward need to change what file the vm is using as its disk. One example is when deleting a

Running the compute node for several days simply triggers it. ?n mar., 16 aug. 2016 la 12:12, Boris Derzhavets <bderzhavets at hotmail.com> a scris: > Sorry, > > How you trigger the problem ? > > B. > > > ------------------------------ > *From:* centos-virt-bounces at centos.org <centos-virt-bounces at centos.org> > on behalf of Laurentiu Soica

Greetings Jano, > Sent: Thursday, May 03, 2018 at 1:44 PM > From: "Ján Tomko" <jtomko@redhat.com> > To: daggs <daggs@gmx.com> > Cc: libvirt-users@redhat.com > Subject: Re: [libvirt-users] changing pci addr of SCSI storage controller: Red Hat, Inc Virtio block device (rev 01) > > On Wed, May 02, 2018 at 07:29:23PM +0200, daggs wrote: > >Greetings,

On 3/23/2015 12:49 PM, Michal Privoznik wrote: > On 23.03.2015 16:02, Fiorenza Meini wrote: >> Hi there, >> I'm running KVM under Openstack . >> >> When I give virsh list command, I see some VM in NON persistent state. >> What does it mean? How can I move it to a persisten state ? > You can do that by running: > > virsh dumpxml $dom > dom.xml

On Wed, Aug 6, 2014 at 1:29 PM, Eric Blake <eblake@redhat.com> wrote: > On 08/06/2014 11:11 AM, Yuanzhen Gu wrote: > > >> Libvirt is only concerned with what virtual hardware you present to the > >> > >> guest, not with the OS running in that guest or what username/password > >> > >> combinations will let you log into that guest OS.