search for: virt_typ

...;0x06' function='0x0'/> </memballoon> </devices> </domain> 2. [root at overcloud-novacompute-0 ~]# lsmod | grep kvm kvm_intel 162153 70 kvm 525409 1 kvm_intel [root at overcloud-novacompute-0 ~]# cat /etc/nova/nova.conf | grep virt_type|grep -v '^#' virt_type=kvm [root at overcloud-novacompute-0 ~]# cat /etc/nova/nova.conf | grep cpu_mode|grep -v '^#' cpu_mode=host-passthrough Thanks, Laurentiu ?n dum., 14 aug. 2016 la 21:44, Boris Derzhavets <bderzhavets at hotmail.com<mailto:bderzhavets at hotmail.com...

...17-13.el7_2.5 on both the baremetal and the compute VM. Please, post 1) # virsh dumpxml VM-L1 ( where on L1 level you expect nested KVM to appear) 2) Login into VM-L1 and run :- # lsmod | grep kvm 3) I need outputs from VM-L1 ( in case it is Compute Node ) # cat /etc/nova/nova.conf | grep virt_type # cat /etc/nova/nova.conf | grep cpu_mode Boris. The only workaround now is to shutdown the compute VM and start it back from baremetal with virsh start. A simple restart of the compute node doesn't help. It looks like the qemu-kvm process corresponding to the compute VM is the problem....

...;0x06' function='0x0'/> </memballoon> </devices> </domain> 2. [root at overcloud-novacompute-0 ~]# lsmod | grep kvm kvm_intel 162153 70 kvm 525409 1 kvm_intel [root at overcloud-novacompute-0 ~]# cat /etc/nova/nova.conf | grep virt_type|grep -v '^#' virt_type=kvm [root at overcloud-novacompute-0 ~]# cat /etc/nova/nova.conf | grep cpu_mode|grep -v '^#' cpu_mode=host-passthrough Thanks, Laurentiu ?n dum., 14 aug. 2016 la 21:44, Boris Derzhavets <bderzhavets at hotmail.com<mailto:bderzhavets at hotmail.com...

...;0x06' function='0x0'/> </memballoon> </devices> </domain> 2. [root at overcloud-novacompute-0 ~]# lsmod | grep kvm kvm_intel 162153 70 kvm 525409 1 kvm_intel [root at overcloud-novacompute-0 ~]# cat /etc/nova/nova.conf | grep virt_type|grep -v '^#' virt_type=kvm [root at overcloud-novacompute-0 ~]# cat /etc/nova/nova.conf | grep cpu_mode|grep -v '^#' cpu_mode=host-passthrough Thanks, Laurentiu ?n dum., 14 aug. 2016 la 21:44, Boris Derzhavets <bderzhavets at hotmail.com> a scris: > > > > --...

...memballoon> > </devices> > </domain> > > 2. > [root at overcloud-novacompute-0 ~]# lsmod | grep kvm > kvm_intel 162153 70 > kvm 525409 1 kvm_intel > > [root at overcloud-novacompute-0 ~]# cat /etc/nova/nova.conf | grep > virt_type|grep -v '^#' > virt_type=kvm > > [root at overcloud-novacompute-0 ~]# cat /etc/nova/nova.conf | grep > cpu_mode|grep -v '^#' > cpu_mode=host-passthrough > > Thanks, > Laurentiu > > ?n dum., 14 aug. 2016 la 21:44, Boris Derzhavets <bderzhavets at h...

...t; >> </domain> >> >> 2. >> [root at overcloud-novacompute-0 ~]# lsmod | grep kvm >> kvm_intel 162153 70 >> kvm 525409 1 kvm_intel >> >> [root at overcloud-novacompute-0 ~]# cat /etc/nova/nova.conf | grep >> virt_type|grep -v '^#' >> virt_type=kvm >> >> [root at overcloud-novacompute-0 ~]# cat /etc/nova/nova.conf | grep >> cpu_mode|grep -v '^#' >> cpu_mode=host-passthrough >> >> Thanks, >> Laurentiu >> >> ?n dum., 14 aug. 2016 la 21:4...

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

This patch obsoletes any previous ones. This is an upstream candidate, so I'm looking for feedback so we can push this and start using it.

This version fixes a few bugs found by jboggs. It also includes some logging facilities that need to be fleshed out more.

This patch is ready for pushing upstream.

The previous patch was missing this file. Resending.

...API provides mostly useful information about the host, the limitation of not being able to report information about specific qemu binaries or machine types lead to introduction. virConnectGetDomainCapabilities(conn, emulator_binary_path, architecture, machine_type, virt_type, flags) https://libvirt.org/formatdomaincaps.html The XML returned by this API describes the capabilities of an VM which would be started using the parameters given to the API (note that if the parameters are NULL a default is provided). The <os> subelement describes supported OS loader t...

...17-13.el7_2.5 on both the baremetal and the compute VM. Please, post 1) # virsh dumpxml VM-L1 ( where on L1 level you expect nested KVM to appear) 2) Login into VM-L1 and run :- # lsmod | grep kvm 3) I need outputs from VM-L1 ( in case it is Compute Node ) # cat /etc/nova/nova.conf | grep virt_type # cat /etc/nova/nova.conf | grep cpu_mode Boris. The only workaround now is to shutdown the compute VM and start it back from baremetal with virsh start. A simple restart of the compute node doesn't help. It looks like the qemu-kvm process corresponding to the compute VM is the problem....

...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.

...17-13.el7_2.5 on both the baremetal and the compute VM. Please, post 1) # virsh dumpxml VM-L1 ( where on L1 level you expect nested KVM to appear) 2) Login into VM-L1 and run :- # lsmod | grep kvm 3) I need outputs from VM-L1 ( in case it is Compute Node ) # cat /etc/nova/nova.conf | grep virt_type # cat /etc/nova/nova.conf | grep cpu_mode Boris. The only workaround now is to shutdown the compute VM and start it back from baremetal with virsh start. A simple restart of the compute node doesn't help. It looks like the qemu-kvm process corresponding to the compute VM is the problem....

...17-13.el7_2.5 on both the baremetal and the compute VM. Please, post 1) # virsh dumpxml VM-L1 ( where on L1 level you expect nested KVM to appear) 2) Login into VM-L1 and run :- # lsmod | grep kvm 3) I need outputs from VM-L1 ( in case it is Compute Node ) # cat /etc/nova/nova.conf | grep virt_type # cat /etc/nova/nova.conf | grep cpu_mode Boris. The only workaround now is to shutdown the compute VM and start it back from baremetal with virsh start. A simple restart of the compute node doesn't help. It looks like the qemu-kvm process corresponding to the compute VM is the problem....

...+class DomainConfigScreen(ConfigScreen): + def __init__(self): + ConfigScreen.__init__(self, "Create A New Virtual Machine") + self.__config = DomainConfig() + self.__config.set_architecture(self.get_libvirt().get_default_architecture()) + self.__config.set_virt_type(self.get_libvirt().get_default_virt_type()) + + def get_elements_for_page(self, screen, page): + if page == VM_DETAILS_PAGE: return self.get_vm_details_page(screen) + elif page == LOCAL_INSTALL_PAGE: return self.get_local_install_page(screen) + elif page == SELECT_...

...17-13.el7_2.5 on both the baremetal and the compute VM. Please, post 1) # virsh dumpxml VM-L1 ( where on L1 level you expect nested KVM to appear) 2) Login into VM-L1 and run :- # lsmod | grep kvm 3) I need outputs from VM-L1 ( in case it is Compute Node ) # cat /etc/nova/nova.conf | grep virt_type # cat /etc/nova/nova.conf | grep cpu_mode Boris. The only workaround now is to shutdown the compute VM and start it back from baremetal with virsh start. A simple restart of the compute node doesn't help. It looks like the qemu-kvm process corresponding to the compute VM is the problem....

...ute VM. > > *Please, post* > > 1) # virsh dumpxml VM-L1 ( where on L1 level you expect nested KVM to > appear) > 2) Login into VM-L1 and run :- > # lsmod | grep kvm > 3) I need outputs from VM-L1 ( in case it is Compute Node ) > > # cat /etc/nova/nova.conf | grep virt_type > # cat /etc/nova/nova.conf | grep cpu_mode > > Boris. > > > > > > The only workaround now is to shutdown the compute VM and start it back > from baremetal with virsh start. > A simple restart of the compute node doesn't help. It looks like the > qemu-kvm p...

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