[libvirt-users] Running hypervisor upgrade problem
by Naor Shlomo
Hello experts,
I tried upgrading libvirt and compiled version 1.1.1
The problem is that when I run "virsh version" I get the following output:
Compiled against library: libvirt 1.1.1
Using library: libvirt 1.1.1
Using API: QEMU 1.1.1
Running hypervisor: QEMU 0.12.1
The problem is that it reports that the Running hypervisor is: QEMU 0.12.1
I wanted to upgrade everything to the latest stable so I also upgraded the qemu-kvm to 1.5.2 but for some reason the reported qemu hypervisor is left outdated. Could you please tell me why is that and how do I upgrade it to the latest?
Thanks in advance,
Naor
11 years
[libvirt-users] lxc-enter-namespace not supportted with python?
by hzguanqiang＠corp.netease.com
Hi, Daniel.
It seems that the virsh command 'lxc-enter-namespace' encapsulates several functions just as 'virDomainLxcOpenNamespace', 'virDomainGetSecurityLabel', 'virDomainLxcEnterSecurityLabel' , 'virDomainLxcEnterNamespace', 'virFork', etc. And I found only 'virDomainLxcOpenNamespace' is provided by python package 'libvirtmod_lxc '. Does this mean that 'lxc-enter-namespace' can only be used through virsh command and not supported with python?
Thanks
------------------
Best regards!
GuanQiang
2013-08-21
11 years
[libvirt-users] Stop the relabeling of CD images
by Cristian Ciupitu
Hi,
I'm installing the operating system for my virtual machines from CD
images and I would like for libvirtd to stop relabeling the
corresponding files. Since the installation media is no big secret, I
have labeled the files with system_u:object_r:public_content_t:s0, but
libvirtd keeps changing them to system_u:object_r:svirt_image_t:s0. It
also changes the ownership to qemu:qemu. This means that I can not make
the files immutable (chattr +i).
The XML dump of the machine looks like this :
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/extra/Software/Linux/Fedora/Fedora-Live-Desktop-x86_64-19/Fedora-Live-Desktop-x86_64-19-1.iso'>
<seclabel relabel='no'/>
</source>
<target dev='hdc' bus='ide'/>
<readonly/>
<shareable/>
<address type='drive' controller='0' bus='1' target='0' unit='0'/>
</disk>
I am using libvirt-daemon-1.1.1-2.fc19.x86_64. You might also find
interesting bug #568935 [1].
So how do I stop libvirtd from changing the permissions of the CD
images?
Thank you,
Cristian Ciupitu
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=568935
11 years
Re: [libvirt-users] Multi Queue KVM Support
by Paolo Bonzini
Il 20/08/2013 13:13, Naor Shlomo ha scritto:
> Hi Paolo and thanks for your help.
>
> I upgraded the following (compiled from source)
> qemu : 1.5.2 stable
> libvirt : 1.1.1
>
> but for some reason when I run the version command inside virsh:
>
> Compiled against library: libvirt 1.1.1
> Using library: libvirt 1.1.1
> Using API: QEMU 1.1.1
> Running hypervisor: QEMU 0.12.1
>
> It says that my running Hypervisor is QEMU 0.12.1
>
> Could you please tell me what did I miss, how do I upgrade the hypervisor?
Not sure. Adding the libvirt-users mailing list.
> Thanks,
> Naor
>
> -----Original Message-----
> From: Paolo Bonzini [mailto:paolo.bonzini@gmail.com] On Behalf Of Paolo Bonzini
> Sent: Tuesday, August 20, 2013 12:28 PM
> To: Naor Shlomo
> Cc: kvm(a)vger.kernel.org
> Subject: Re: Multi Queue KVM Support
>
> Il 20/08/2013 05:21, Naor Shlomo ha scritto:
>> Hi Paolo,
>>
>> The host is running CentOS release 6.3 (Final).
>> I did "yum upgrade libvirt" and "yum upgrade qemu-kvm" a couple of days ago and ended up with these versions.
>>
>> What do you suggest regarding qemu? compile 6.5 or later myself?
>
> RHEL/CentOS 6.5 is not yet out, it's still a few months before it's released.
>
> You can compile QEMU 1.6 from source, or wait for CentOS to have the feature.
>
> Paolo
>
>> I appreciate your help,
>> Naor
>>
>> -----Original Message-----
>> From: Paolo Bonzini [mailto:paolo.bonzini@gmail.com] On Behalf Of
>> Paolo Bonzini
>> Sent: Monday, August 19, 2013 11:22 PM
>> To: Naor Shlomo
>> Cc: kvm(a)vger.kernel.org
>> Subject: Re: Multi Queue KVM Support
>>
>> Il 19/08/2013 13:29, Naor Shlomo ha scritto:
>>> Hello experts,
>>>
>>> I am trying to use the multi queue support on a Linux guest running Kernel 3.9.7.
>>>
>>> The host's virsh version command reports the following output:
>>> Compiled against library: libvirt 0.10.2 Using library: libvirt
>>> 0.10.2 Using API: QEMU 0.10.2 Running hypervisor: QEMU 0.12.1
>>
>> Is it RHEL or CentOS or Scientific Linux, or something else? If RHEL/CentOS, what release?
>>
>>> The problem is that virtio_has_feature(vdev, VIRTIO_NET_F_MQ) returns FALSE and I don't know why.
>>
>> This version of QEMU is too old. It's possible that 6.5 will have multiqueue, but I'm not entirely sure.
>>
>> Paolo
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in the
>> body of a message to majordomo(a)vger.kernel.org More majordomo info at
>> http://vger.kernel.org/majordomo-info.html
>>
>
11 years
[libvirt-users] Error while adding volume through virsh
by varun bhatnagar
Hi,
I was trying to add volume...I got one xml snippet and I modified it
according to my node configuration:
< volume>
<name>testNode/cluster.vmdk </name>
<allocation>0 </allocation>
<capacity unit='G'>2<capacity>
</volume>
Now when I executed "virsh vol-create datastore1 /local/new_volume.xml" one
error message came saying:
"Error: Failed to create volume from /local/new_volume.xml"
Error: internal error: Creation of raw volumes is not supported"
Can anyone tell me what is going wrong here?
Regards,
Varun
11 years
[libvirt-users] RHEV hosts
by Parakkal, Navin S
Hi,
I have couple of RHEV hosts (ovpxen,RHV2, RHV10 etc) and i'm trying to connect from one of the client machine (C1). All the RHEV host have libvirt modified by vdsm. It looks like the below
## beginning of configuration section by vdsm-4.10.2
listen_addr="0.0.0.0"
unix_sock_group="kvm"
unix_sock_rw_perms="0770"
auth_unix_rw="sasl"
host_uuid="036118ab-705f-4aeb-9a13-013dc8af6b41"
keepalive_interval=-1
log_outputs="1:file:/var/log/libvirtd.log"
log_filters="3:virobject 3:virfile 2:virnetlink 3:cgroup 3:event 3:json 1:libvirt 1:util 1:qemu"
ca_file="/etc/pki/vdsm/certs/cacert.pem"
cert_file="/etc/pki/vdsm/certs/vdsmcert.pem"
key_file="/etc/pki/vdsm/keys/vdsmkey.pem"
## end of configuration section by vdsm-4.10.2
# ls
bkp-2013-08-16_110734_cacert.pem cacert.pem vdsmcert.pem
bkp-2013-08-16_110734_vdsmcert.pem engine_web_ca.pem
[root@ovpxen certs]# pwd
/etc/pki/vdsm/certs
[root@ovpxen certs]# certtool -i --infile engine_web_ca.pem | head
X.509 Certificate Information:
Version: 3
Serial Number (hex): 09
Issuer: C=US,O=HP,CN=CA-IWFVM00772.hpswlabs.adapps.hp.com.64431
Validity:
Not Before: Wed Jan 23 13:24:14 UTC 2013
Not After: Sun Jan 22 07:54:14 UTC 2023
Subject: C=US,O=HP,CN=CA-IWFVM00772.hpswlabs.adapps.hp.com.64431
Subject Public Key Algorithm: RSA
Modulus (bits 1024):
certtool -i --infile cacert.pem | head
X.509 Certificate Information:
Version: 3
Serial Number (hex): 09
Issuer: C=US,O=HP,CN=CA-IWFVM00772.hpswlabs.adapps.hp.com.64431
Validity:
Not Before: Wed Jan 23 13:24:14 UTC 2013
Not After: Sun Jan 22 07:54:14 UTC 2023
Subject: C=US,O=HP,CN=CA-IWFVM00772.hpswlabs.adapps.hp.com.64431
Subject Public Key Algorithm: RSA
Modulus (bits 1024):
[root@ovpxen certs]# certtool -i --infile vdsmcert.pem | head
X.509 Certificate Information:
Version: 3
Serial Number (hex): 0c
Issuer: C=US,O=HP,CN=CA-IWFVM00772.hpswlabs.adapps.hp.com.64431
Validity:
Not Before: Thu Aug 15 11:09:22 UTC 2013
Not After: Wed Aug 15 05:39:22 UTC 2018
Subject: O=HP,CN=16.184.46.53
Subject Public Key Algorithm: RSA
Modulus (bits 2048):
Now from the client C1 which cert should i place in /etc/pki/CA/cacert.pem so that i can access from the client using the URI
qemu+tls://ovpxen.ind.hp.com/system. Please note the host IWFVM00772.hpswlabs.adapps.hp.com is ovirt managed host. It is not the client.
My problem here is i can't change the hypervisor hosts as there are too many of them and it is configured by vdsm . What certs should i take from host so that i can use it in the client so that i can connect to multiple hosts from the client using virsh or virt-manager . I need tls as remote protocol as i'm trying to automate commands.
Regards,
Navin
11 years
[libvirt-users] Modify Iptables Rules (virbr0 & virbr1)
by Jorge Fábregas
Hi,
I have some guests running in the "default" network (virbr0) and I've
also created a similar (NAT) network (virbr1). Therefore, the FORWARD
chain for the CentOS 6.4 host looks like this:
http://fpaste.org/29229/75281379/
...where line 3-7 are related to virbr0 and 8-12 to virbr1. My 2 questions:
1) I've noticed that I can ping from a guest within virbr0 to any guest
on the virbr1 network. However, I can't do the same from virbr1 (ping
guests on virbr0). This is because of "line 6" on the pastebin, where
the traffic is REJECTED.
I originally thought that If I create multiple NAT networks (just like
the default virbr0) they would be able to talk to each other (the host
doing the actual forwarding) but as you can see, based on the iptables
rules that libvirt injects, this only happens for the first network.
That is, the first network can reach all other networks (just because it
happens to be the first one defined). Is this the intention (only
default can talk to the others but not the other way around)?
2) I would like both networks to talk to each other. If I remove line #6
I can make virbr1 guests talk to virbr0 guests. What is the correct
way to handle this? I obviously don't want to perform "iptables -D
FORWARD line-number..." every time I start libvirt. (I really like to
leave the networks as they are, NAT, dhcp running etc).
Thanks!
Jorge
11 years
