- Users - libvirt List Archives

[libvirt-users] libvirt_lxc and sysfs
by pr.G 10 Jun '13

10 Jun '13

Hello. Is it possible to start container via libvirt_lxc without mounting /sys inside container? When I start container via lxc-start and do not add mount point to config, then /sys inside container is empty. When I do it via virsh -c lxc:// container.xml, then /sys contains sysfs of the host and /sys on host becomes remounting read-only. Am I doing something wrong or is this feature of libvirt_lxc? Thanks. root@host:~# uname -a Linux host 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2+deb7u2 x86_64 GNU/Linux root@host:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 7.0 (wheezy)" ... root@host:~# dpkg -l | grep libvirt ii libvirt-bin 0.9.12-11 amd64 programs for the libvirt library ii libvirt0 0.9.12-11 amd64 library for interfacing with different virtualization systems container.xml: <domain type='lxc'> <name>ns1</name> <memory>524288</memory> <os> <type>exe</type> <init>/sbin/init</init> </os> <vcpu>1</vcpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/lib/libvirt/libvirt_lxc</emulator> <filesystem type='mount'> <source dir='/var/lxc/ns1/rootfs'/> <target dir='/'/> </filesystem> <interface type='bridge'> <source bridge='br0'/> <mac address='52:54:00:de:74:06'/> </interface> <console type='pty' /> </devices> </domain>

3 5

[libvirt-users] transient domains with saved state of persistent doamin
by Alexandr 10 Jun '13

10 Jun '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Good day, i writing testing system and want to use libvirt for it, now i reading libvirt development guide and found info about transient domains which looks like what i need, but it's still unclear for me if it possible to implement what i want using libvirt. my idea is to make persistent domain, prepare it for testing (install os, needed software, drivers, e.t.c.), save it's state when system are running (for quick start later) and after this use this saved state with new transient domain which use new hard drive image with backing store instead of snapshot (qcow2 allow this) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRtMPuAAoJEH3ap8veG8EH6B4IAKpRbXjphIYEhD5achPTyu/T vIN7SPV1NaYhZpdwmQmspcOLXgawHuCP2gMYgJkXhH+/p1d/MXQXXWX77a/8WS9t Lajuin3yG9F1Bq/1EoCNFZtARMtWvimAXeq4KMUKeNrVqrU+WPZ5/a0m6kN7xAOe wErFMnvpiefIysOb3Z0WWvwMuyPfjzZKehkYM03NyVec/1K//jXzNNvjBFUylvXX Sz5EcNGr6/SN23uS218GVPJzb+uM6ZlmIvxsxs30+AWK+r8DW/9imvhTXqnbLiJV TaTAwMekCwqs0xqRf9yk8mTI6dXt5nfnMAAUpMcinaIGMn9/oZFpDq0K2L6C5L8= =bWmZ -----END PGP SIGNATURE-----

1 0

[libvirt-users] Setting RBD cache parameters for libvirt+qemu
by John Nielsen 08 Jun '13

08 Jun '13

I am running some qemu-kvm virtual machines via libvirt using Ceph RBD as the back-end storage. Today I was testing an update to libvirt-1.0.6 on one of my hosts and discovered that it includes this change: [libvirt] [PATCH] Forbid use of ':' in RBD pool names ...People are known to be abusing the lack of escaping in current libvirt to pass arbitrary args to QEMU. I am one of those people--I have been storing colon-separated arguments in my disk source 'name' attribute to control the RBD cache settings on a per-volume basis. Under libvirt-1.0.6 such VM's refuse to start: error: Failed to start domain foo error: unsupported configuration: ':' not allowed in RBD source volume name 'mypool/foo:rbd_cache_size=268435456:rbd_cache_max_dirty=134217728:rbd_cache_target_dirty=33554432:rbd_cache_max_dirty_age=5' So my question is how do I control the cache settings now? Thanks, JN

2 3

[libvirt-users] [offtopic] OpenNebulaConf2013: Extended keynote lineup and deadline for talk proposals
by Javier Fontan 06 Jun '13

06 Jun '13

Hello, I hope you don't find this email too offtopic. We have just published an expanded keynote line-up for the OpenNebula Conference 2013 (http://blog.opennebula.org/?p=4707) that includes experts from leading institutions using OpenNebula. The first ever OpenNebula Conference will be held on Sept. 24-26 in Berlin and is intended to serve as a meeting point for OpenNebula cloud users, developers, administrators, builders, integrators and researchers. As you may know OpenNebula uses libvirt to manage KVM and VMware VMs and some of you may be using it in production. I think your experiences will be very valuable. There are only 10 days left to submit talk proposals (the deadline is June 15th). We are looking forward to welcoming you personally in Berlin!. Cheers -- Join us at OpenNebulaConf2013 in Berlin from the 24th to the 26th of September 2013! Javier Fontán Muiños Project Engineer OpenNebula - The Open Source Toolkit for Data Center Virtualization www.OpenNebula.org | jfontan(a)opennebula.org | @OpenNebula

1 0

[libvirt-users] a problem about nested vm
by denghuancong 05 Jun '13

05 Jun '13

hi, I have a problem that confuse me so long. I run a guest os(VM1) on a physical machine(PM1) that had enabled virtualization . Now, I also want to run a guest os (VM2) under VM1,but VM1 print the following message to me: [2013-06-05 10:43:04,379][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,382][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,409][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,412][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,414][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,418][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,421][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,426][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,428][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,432][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules. so, how can i enable the virtualization option in vm1??? thanks a lot. :)

1 0

[libvirt-users] libvirt tls error
by yue 03 Jun '13

03 Jun '13

centos6.3,libvirt 0.9.10. [root@ovirtdev private]# virsh -c qemu+tls://ovirtdev.localhost/system list 2013-04-22 03:37:09.362+0000: 9898: info : libvirt version: 0.9.10, package: 21.el6_3.8 (CentOS BuildSystem <http://bugs.centos.org>, 2013-01-28-19:24:16, c6b10.bsys.dev.centos.org) 2013-04-22 03:37:09.362+0000: 9898: warning : virNetClientIncomingEvent:1665 : Something went wrong during async message processing error: Unable to read TLS confirmation: Input/output error error: failed to connect to the hypervisor thanks

3 2

[libvirt-users] About the change of a VM's vcpu count in runtime?
by Dennis Chen 02 Jun '13

02 Jun '13

Hi, We know that there is a command "setvcpus" in virsh used to "change number of virtual CPUs", now we just have the need to change vcpu count dynamically for a running VM, so I tried this command (the vcpu count is 2 in the VM xml file), below is the result: virsh # setvcpus 3 --count 4 error: invalid argument: requested vcpus is greater than max allowable vcpus for the domain: 4 > 2 virsh # setvcpus 3 --count 1 error: Operation not supported: qemu didn't unplug the vCPUs properly So I tried another way: log into the running VM, and "echo 0 > /sys/devices/system/cpu/cpu1/online", after that I can find only one processor in the vm through '/proc/cpuinfo', but in virsh, the vcpuinfo still shows: virsh # vcpuinfo 3 VCPU: 0 CPU: 0 State: running CPU time: 13.5s CPU Affinity: yyyy VCPU: 1 CPU: 1 State: running CPU time: 6.9s CPU Affinity: yyyy So the question is: is there any method I can't find yet to change the vcpu count of a running vm dynamically? BRs, Dennis

3 6

[libvirt-users] Using source installed open vswitch with libvirt(or virsh).
by 황진환 01 Jun '13

01 Jun '13

P{font-size:10pt; line-height:16; margin-left:0; margin-top:0; margin-right:0; margin-bottom:0; font-family:gulim;} (English is not my first language Sorry for my poor English )   OS :  Linux nc233 2632-220171el6x86_64 #1 SMP Tue May 15 17:16:46 CDT 2012 x86_64 x86_64 x86_64 GNU/Linux CentOS release 63 (Final) open vswitch : 11190 virsh : 100 ibvirtd (libvirt) : 100   I have tried to see what the virsh setting can do to open vswitch(ovs) until now I had installed open vswitch from a source, not by using rpm or rpm build of the source (I had tried to do 'ovs rpm build' described at INSTALLRHEL included in ovs, But i failed to do it)   What i tried is this(http://blogscottloweorg/2012/11/07/using-vlans-with-ovs-and-libvirt/)  I installed and started up ovs and it looked like properly working I could create and delete bridges and ports with 'ovs-vsctl'    1 what i created before running 'virsh net-define'  -------------------------------------------- # ovs-vsctl show 76d9d6aa-cfce-4868-bf99-7d16bcfe38eb     Bridge "br0"         Port "br0"             Interface "br0"                 type: internal         Port "eth1"             Interface "eth1" --------------------------------------------     2 And then runned 'virsh net-define netxml' 'netxml' i used -------------------------------------------- <network>     <name>ovs-network</name>     <forward mode='bridge'/>     <bridge name='br0'/>     <virtualport type='openvswitch'/>     <portgroup name='vlan-01' default='yes'>     </portgroup>     <portgroup name='vlan-02'>         <vlan>         <tag id='2'/>         </vlan>     </portgroup>     <portgroup name='vlan-03'>         <vlan>         <tag id='3'/>         </vlan>     </portgroup>     <portgroup name='vlan-all'>         <vlan trunk='yes'>         <tag id='2'/>         <tag id='3'/>         </vlan>     </portgroup> </network> --------------------------------------------     3 vmxml which was used for 'virsh define vmxml' -------------------------------------------- <domain type="kvm">     <name>vm</name>     <memory>1048576</memory>     <vcpu>1</vcpu>     <os>         <type arch="x86_64" machine="pc">hvm</type>                 <boot dev="hd"/>     </os>     <features>         <acpi/>         <apic/>         <pae/>     </features>     <clock mode="localtime">         <timer name="rtc" tickpolicy="catchup" wallclock="guest"/>         <timer name="hpet" present="no"/>     </clock>     <devices>                  <emulator>/usr/bin/qemu-system-x86_64</emulator>                  <disk device="disk" type="file">                          <driver cache="writeback" io="threads" name="qemu" type="qcow2"/>             <source file="/root/img/vmimg"/>             <target bus="virtio" dev="vda"/>         </disk>         <interface type="network">             <mac address="d2:0d:45:a3:92:ea"/>             <source network='ovs-network' portgroup='vlan-02'/>         </interface>         <console type="pty">             <target port="0"/>         </console>         <input bus="usb" type="tablet"/>         <input bus="ps2" type="mouse"/>         <graphics autoport="yes" keymap="en-us" listen="0000"             port="-1" type="vnc"/>     </devices> </domain> --------------------------------------------     4 runned 'virsh start vm', and failed (messages had not been printed in english at my server, so i googled and tried to choose simillar sentecne which were shown in libvirt related threads please consider it) ----------------------------------------- #virsh start vm error : Failled to start domain vm error : Unable to add port vnet0 to OVS bridge br0 -----------------------------------------     At that time, /var/log/libvirt/libvirtdlog  (these are also translated) ----------------------------------------- 2013-05-23 04:32:14588+0000: 11455: error : virNetDevGetMTU:343 : Cannot get interface MTU on 'ovsbr0': No such device  2013-05-23 04:32:14678+0000: 11455: error : virExecWithHook:419 : Cannot find 'ovs-vsctl' in path: No such file or directory 2013-05-23 04:32:14679+0000: 11455: error : virNetDevOpenvswitchRemovePort:173 : Unable to delete port (null) from OVS: command does not allowed -----------------------------------------     I think above errors comes from install location of OVS as written in libvirtdlog How can i solve that by hands? (I'm also trying to solve the problem by installing ovs, using rpm build) There are not only fedora or ubuntu linux, so the solution may exist Are there a way to get libvirt to recognize ovs-vsctl? (As i mentioned above, ovs-vsctl and ovs are properly working)   Thank you for reading

3 2

[libvirt-users] /dev/tty only on a new container
by Sebastien Douche 01 Jun '13

01 Jun '13

Hi folks :), I migrated the host from the Debian Squeeze to Ubuntu 12.10. Old containers work but I can't use the ssh command, /dev/tty is missing. On a new container, /dev/tty is here. The libvirt configuration is the same. Any ideas? Thanks. -- Sebastien Douche <sdouche(a)gmail.com> Twitter: @sdouche / G+: +sdouche

3 4

[libvirt-users] iSCSI-based Storage Pool and virsh attach-device problems/questions
by Ken Stanley 31 May '13

31 May '13

Hello all, I am attempting to use the 'virsh attach-device' command to add storage to a guest from a pre-defined iSCSI-based storage pool. My desire is to attach a volume from the storage pool and have the storage pool recognize that the volume is in use and either flag it as such, or remove it from the pool so that subsequent queries to the pool will only return available storage volumes. The end goal is to have an automated system use the libvirt API assign storage volumes to new and existing guests on demand. I guess my first question is: Is this possible? Does libvirt give any indication that a storage volume within a pool is available or already in use? I would prefer to avoid having to externally manage this sort of thing if I can. I am using Debian Wheezy for the Dom0 and iSCSI SAN (identical setup), along with libvirt 1.0.5-2 from the experimental branch. I have Xen 4.1.4-3+deb7u1 installed, along with its accompanying packages. All of this is currently running under VirtualBox, but that is only for my testing/development purposes. I am able to get the Dom0 to recognize the SAN, and add the storage pool. When I attempt to use 'virsh attach-device', I get the following error: "error: Failed to attach device from device.xml \ error: POST operation failed: xend_post: error from xen daemon: (xend.err 'Block device must have physical details specified')". I have tracked this specific error down to the Xen python blkif.py, located under /usr/lib/xen-4.1/lib/python/xen/xend/server/blkif.py for my installation. After reading through the source, I found that under the getDeviceDetails def there is a non-existent configuration called 'uname' that is undefined. Looking deeper into the code, under the getDeviceConfiguration def, I see that the code is trying to read from the backend configuration, and expecting to see a 'type' and 'params' to use for setting the aforementioned 'uname' value. This is where I hit the wall, so to speak. After reading through the XML documentation for libvirt (http://libvirt.org/formatdomain.html#elementsDisks) I see nothing that I can further add to my XML description that would make sense for adding a volume from a storage pool. For kicks and giggles, I've tried using the disk type 'carom', which gets me past the failing python condition, but then gives me the following error when trying to do anything – in this case, just a simple dumpxml on the domain – with the guest through virsh: "error: internal error domain information incomplete, vbd has no src". Subsequently, if I try to call 'detach-device', I get the same error, leaving me with no other alternative but to destroy/undefine, and recreate the domain using define/start. I am able to ssh into the guest after the call to 'attach-device', but no device is present nor registered (as seen with dmesg). If I reboot the guest libvirt reports that the guest is "idle", but I cannot console into it due to the error mentioned in the previous paragraph. I can, however, use 'xm console <guest>' and gain access that way. Any and all advice that you can give would be greatly appreciated. I will do everything that I can to assist as far as trying all suggestions and following directions. :) Storage Pool XML: <pool type="iscsi"> <name>virtimages</name> <source> <host name="hv02.kstanley.vm"/> <device path="iqn.2013-05.vm.kstanley.hv02:vdisks"/> </source> <target> <path>/dev/disk/by-path</path> </target> </pool> Device XML: <disk type="volume" device="disk"> <source pool="virtimages" volume="unit:0:0:1"/> <target dev="xvdb" bus="virtio"/> </disk> Regards, Ken Stanley

1 0