- Users - libvirt List Archives

[libvirt-users] Check memory inside a container
by Saurabh Deochake 14 Mar '13

14 Mar '13

Hi all, I'm new to LXC and libvirt. I have created a LXC container using libvirt. In domain XML file I have mentioned "memory" and "current memory" as 256 MB. Now I want to check the memory inside the container, but whenever I run top command or try to cat /proc/meminfo, it shows host machine's memory which is 3GB. So is there any command by which I can check containers memory? Regards, Saurabh Deochake.

2 2

[libvirt-users] backup disk/state
by Evaggelos Balaskas 13 Mar '13

13 Mar '13

Hi there, i am trying to understand something that bothering me for some time now. A running domain has two things that someone needs to take backup. So there is the disk and the state. Using snapshots as checkpoint someone can take the disk snapshot but i cant understand how to "transfer" the saved state from "backup ed" disk. Reading through Kashyap's and Eric's posts (mostly) i can now understand a lot about backing up and snapshotting but i cant figure out (perhaps i need to read more) how to boot up the snapshot disk with the saved (?) state. Thanks in advance -- Evaggelos Balaskas - Unix System Engineer http://gr.linkedin.com/in/evaggelosbalaskas

2 1

[libvirt-users] RHEL 5 libvirt client - QEMU+SSH fails with "login authentication type 2" problem
by Saravanan Shanmugham (sarvi) 13 Mar '13

13 Mar '13

Hi, I have RHEL5 libvirt client compiled at ${BSPACE}/usrcisco This client when connecting to a libvirtd/server fails to connect as follows -bash-3.2$ ${BSPACE}/usrcisco/bin/virsh -c qemu+ssh://sarvi@cnh-nehalem-1/system?socket=/var//run/libvirt/libvirt-sock error: failed to connect to the hypervisor error: authentication failed: unsupported authentication type 2 I have the libvirt client compiled and installed as follows PYTHON=${BSPACE}/usrcisco/bin/python LDFLAGS="-L${BSPACE}/libnl-1.1.2/lib/ -L${BSPACE}/device-mapper.1.02.28/lib/ioctl/" CFLAGS="-I${BSPACE}/libnl-1.1.2/include -I${BSPACE}/device-mapper.1.02.28/include/" CPPFLAGS="-I${BSPACE}/device-mapper.1.02.28/include/ -I${BSPACE}/libnl-1.1.2/include" ./configure --prefix=${BSPACE}/usrcisco --enable-static --with-libvirtd=no --with-hal=no --with-python --with-PACKAGE=yes --with-packager=no --with-packager-version=no --with-gnu-ld=no --with-apparmor=no --with-apparmor-mount=no--with-attr=no --with-audit=no --with-avahi=no --with-blkid=no --with-capng=no --with-curl=no --with-dbus=no --with-fuse=no --with-hal=no --with-netcf=no --with-numactl=no --with-openwsman=no --with-pciaccess=no --with-sanlock=no --with-sasl=no --with-selinux=no --with-selinux-mount=no --with-udev=no --with-yajl=no --with-xen=no --with-xen-inotify=no --with-qemu=no --with-uml=no --with-openvz=no--with-vmware=no --with-phyp=no --with-xenapi=no --with-libxl=no --with-vbox=no --with-gnutls=no --without-ssh2 --with-rhel5-api=yes The same library sources when compiled on RHEL6 as above, without specifying the "--with-rhel5-api=yes" compiles AND connect to the same server fine I am looking for pointers as to what the problem could be OR how to trouble shoot the problem. Thanks, Sarvi

1 2

[libvirt-users] update qemu-kvm with running guests?
by Jamie Fargen 12 Mar '13

12 Mar '13

Good Afternoon, I was curious to know what happens to running guests when the qemu-kvm rpm is update via yum. I assume that the current qemu processes would be running the old binary, but the new processes would be started using the new binary. Please let me know if this assumption is correct. Regards, Jamie Ian Fargen

2 1

[libvirt-users] QEMU+SSH login issue on RHEL 4
by Shantan Marepally (shanredd) 11 Mar '13

11 Mar '13

Hi All, I am trying to compile libvirt tools from source on RHEL 4. I could get the sources compiled, but when I try to connect to libvirtd using QEMU+SSH I get the following error: error: failed to connect to the hypervisor error: authentication failed: unsupported authentication type 2 With root as the user, I could login, rest other users get the error. All authentication related settings are setup fine. When I try the login using QEMU+SSH to the same libvirtd, compiled on RHEL 5, with any other user things seem to be working fine. The thing that was different in the build is that I am trying to build a minimal virsh client on RHEL 4. The following are the configure parameters I used: ./configure --enable-static --with-libvirtd=no --with-hal=no --with-python --with-PACKAGE=yes --with-packager=no --with-packager-version=no --with-gnu-ld=no --with-apparmor=no --with-apparmor-mount=no--with-attr=no --with-audit=no --with-avahi=no --with-blkid=no --with-capng=no --with-curl=no --with-dbus=no --with-fuse=no --with-hal=no --with-netcf=no --with-numactl=no --with-openwsman=no --with-pciaccess=no --with-sanlock=no --with-sasl=no --with-selinux=no --with-selinux-mount=no --with-udev=no --with-yajl=no --with-xen=no --with-xen-inotify=no --with-qemu=no --with-uml=no --with-openvz=no --with-vmware=no --with-phyp=no --with-xenapi=no --with-libxl=no --with-vbox=no --with-gnutls=no Are there any specific options that are needed for QEMU+SSH to work? any other ideas what could go wrong? Thanks, Shantan Ps: The following are the debug logs with the error message: 2013-03-11 20:13:21.887+0000: 19285: debug : virNetClientIOEventLoopPassTheBuck:1423 : Giving up the buck (nil) 2013-03-11 20:13:21.887+0000: 19285: debug : virNetClientIOEventLoopPassTheBuck:1437 : No thread to pass the buck to 2013-03-11 20:13:21.887+0000: 19285: debug : virNetClientCloseLocked:644 : client=0x2a98c0d9c0, sock=0x2a98c0d6c0, reason=3 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0d6c0 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectRef:295 : OBJECT_REF: obj=0x2a98c0d9c0 2013-03-11 20:13:21.887+0000: 19285: debug : virKeepAliveStop:299 : RPC_KEEPALIVE_STOP: ka=0x2a98c0dae0 client=0x2a98c0d9c0 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollRunOnce:640 : Poll got 1 event(s) 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollDispatchTimeouts:425 : Dispatch 0 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollDispatchHandles:470 : Dispatch 2 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollDispatchHandles:484 : i=0 w=1 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollDispatchHandles:498 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollDispatchHandles:484 : i=1 w=2 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollDispatchHandles:487 : Skip deleted n=1 w=2 f=7 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollCleanupTimeouts:516 : Cleanup 0 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollCleanupTimeouts:552 : Found 0 out of 0 timeout slots used, releasing 0 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollCleanupHandles:564 : Cleanup 2 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollCleanupHandles:577 : EVENT_POLL_PURGE_HANDLE: watch=2 2013-03-11 20:13:21.887+0000: 19286: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0d9c0 2013-03-11 20:13:21.887+0000: 19286: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0d6c0 2013-03-11 20:13:21.887+0000: 19286: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x2a98c0d6c0 2013-03-11 20:13:21.887+0000: 19286: debug : virNetSocketDispose:998 : sock=0x2a98c0d6c0 fd=7 2013-03-11 20:13:21.887+0000: 19286: debug : virEventPollRemoveHandle:180 : EVENT_POLL_REMOVE_HANDLE: watch=2 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0dae0 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x2a98c0dae0 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0d9c0 2013-03-11 20:13:21.887+0000: 19286: debug : virFileClose:73 : Closed fd 7 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0d9c0 2013-03-11 20:13:21.887+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c0d9c0 2013-03-11 20:13:21.888+0000: 19285: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x2a98c0d9c0 2013-03-11 20:13:21.888+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c20650 2013-03-11 20:13:21.888+0000: 19285: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x2a98c20650 2013-03-11 20:13:21.887+0000: 19286: debug : virFileClose:73 : Closed fd 9 2013-03-11 20:13:21.889+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c205e0 2013-03-11 20:13:21.889+0000: 19285: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x2a98c205e0 2013-03-11 20:13:21.889+0000: 19286: debug : virProcessAbort:92 : aborting child process 19287 2013-03-11 20:13:21.889+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x2a98c09e80 2013-03-11 20:13:21.889+0000: 19285: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x2a98c09e80 2013-03-11 20:13:21.889+0000: 19286: debug : virProcessAbort:100 : trying SIGTERM to child process 19287 2013-03-11 20:13:21.889+0000: 19285: debug : virFileClose:73 : Closed fd 10 2013-03-11 20:13:21.889+0000: 19285: debug : virFileClose:73 : Closed fd 8 2013-03-11 20:13:21.889+0000: 19285: debug : virNetMessageClear:56 : msg=0x2a98c0da20 nfds=0 2013-03-11 20:13:21.889+0000: 19285: debug : do_open:1206 : driver 1 remote returned ERROR 2013-03-11 20:13:21.889+0000: 19285: debug : virObjectUnref:258 : OBJECT_UNREF: obj=0x571630 2013-03-11 20:13:21.889+0000: 19285: debug : virObjectUnref:260 : OBJECT_DISPOSE: obj=0x571630 error: failed to connect to the hypervisor error: authentication failed: unsupported authentication type 2 2013-03-11 20:13:21.889+0000: 19285: debug : virEventPollAddTimeout:225 : Used 0 timeout slots, adding at least 10 more 2013-03-11 20:13:21.889+0000: 19285: debug : virEventPollInterruptLocked:716 : Interrupting 2013-03-11 20:13:21.889+0000: 19285: debug : virEventPollAddTimeout:248 : EVENT_POLL_ADD_TIMEOUT: timer=1 frequency=0 cb=0x411e39 opaque=(nil) ff=(nil) 2013-03-11 20:13:21.909+0000: 19286: debug : virProcessAbort:107 : process has ended: exit status 255 2013-03-11 20:13:21.909+0000: 19285: debug : virEventPollRemoveTimeout:300 : EVENT_POLL_REMOVE_TIMEOUT: timer=1 2013-03-11 20:13:21.909+0000: 19285: debug : virEventPollInterruptLocked:712 : Skip interrupt, 0 1084229984

2 2

[libvirt-users] snapshot-create fails with "error: Failed to open file '(null)': Bad address"
by Thomas Stein 11 Mar '13

11 Mar '13

Hello. I'm not able to create a snapshot for none of my vm's running on a particular node. And i have absolut no idea where to look to solve this. Someone can point me to the right direction? hn images # qemu-x86_64 -version qemu-x86_64 version 1.2.2 (qemu-kvm-1.2.0), Copyright (c) 2003-2008 Fabrice Bellard hn images # libvirtd --version libvirtd (libvirt) 1.0.3 hn images # qemu-img info gentoo-template.qcow2 image: gentoo-template.qcow2 file format: qcow2 virtual size: 130G (139586437120 bytes) disk size: 30G cluster_size: 65536 hn images # virsh snapshot-create gentoo-template error: Failed to open file '(null)': Bad address hn images # hn images # uname -a Linux hn 3.8.2 #1 SMP Sat Mar 9 12:17:41 CET 2013 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GenuineIntel GNU/Linux hn images # thank you t.

2 2

[libvirt-users] ANNOUNCE: Oz 0.10.0 Release
by Chris Lalancette 09 Mar '13

09 Mar '13

All, I'm pleased to announce release 0.10.0 of Oz. Oz is a program for doing automated installation of guest operating systems with limited input from the user. Release 0.10.0 is a bugfix and feature release for Oz. Some of the highlights between Oz 0.9.0 and 0.10.0 are: * Support for installing OpenSUSE 12.1 and 12.2 * Support for python3 * Support for Ubuntu 12.04.1, 12.04.2, and 12.10 * Fix up <command> ordering so that commands are run in the order they are specified in the XML * Updates and fixes to the documentation * Increase the shutdown timeout to support slower qemu guests * Add a default screenshot directory as /var/lib/oz/screenshots * Support for RHEL 5.9 * Support for Fedora 18 * Switch over to pycurl for header information; this allows http authentication to work * Switch to using the libvirt built-in screenshot mechanism. This removes the gvnc dependency and makes screenshots more reliable, but requires libvirt 0.9.7 or newer * Delete auto-generated ssh keys after customization A tarball of this release is available, as well as packages for Fedora-17. Instructions on how to get and use Oz are available at http://github.com/clalancette/oz/wiki . If you have questions or comments about Oz, please feel free to contact me at clalancette(a)gmail.com, or open up an issue on the github page: http://github.com/clalancette/oz/issues . Thanks to everyone who contributed to this release through bug reports, patches, and suggestions for improvement. Chris Lalancette

1 0

[libvirt-users] ubuntu, libvirt and virtio block devices
by Jeff Dickens 08 Mar '13

08 Mar '13

-- Hi. I'm running Ubuntu Precise 12.04 LTS. I created some virtual machines using vmbuilder, and then migrated those from their .qcow files to lvm. However, those virtual machines are still using disk type "file": Code: <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/dev/vg1/lvname'/> <target dev='hda' bus='ide'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> Now I've noticed that this disk should probably have type "block" - using this is supposed to provide superior performance. It would also make Berteaud's virt-backup script happy and willing to snapshot the lvm making the backup very quick. So I tried setting up the disk like this: Code: <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/vg1/lvname'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> I had to edit fstab to look for the disk on vda instead of hda but it came up. However performance was terrible. It seemed like it was going to lock up, although it never did. So my question is: *How should I be setting up my LVM-based virtual machines to use virtio block devices ?* IT Manager 978-632-1513

1 1

Re: [libvirt-users] Virsh+QEMU, SSH issue on compiled libvirt
by Will Dennis 08 Mar '13

08 Mar '13

Hi Shantan, I believe the problem may be that libvirt 1.x requires TLS by default on connections. I saw that same problem the 1st time I replaces a running libvirt 0.9.x with 1.0.0. I believe there may be a way to turn off this requirement in libvirtd.conf, e.g. # # Network connectivity controls # # Flag listening for secure TLS connections on the public TCP/IP port. # NB, must pass the --listen flag to the libvirtd process for this to # have any effect. # # It is necessary to setup a CA and issue server certificates before # using this capability. # # This is enabled by default, uncomment this to disable it #listen_tls = 0 # Listen for unencrypted TCP connections on the public TCP/IP port. # NB, must pass the --listen flag to the libvirtd process for this to # have any effect. # # Using the TCP socket requires SASL authentication by default. Only # SASL mechanisms which support data encryption are allowed. This is # DIGEST_MD5 and GSSAPI (Kerberos5) # # This is disabled by default, uncomment this to enable it. #listen_tcp = 1 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< On the two instances of libvirt 1.x I have deployed, I just configure and use TLS. Instructions on doing this may be found here: http://wiki.libvirt.org/page/TLSSetup HTH, Will

6 12

[libvirt-users] Libvirt remote-client compilation for RHEL4
by Saravanan Shanmugham (sarvi) 07 Mar '13

07 Mar '13

Hi, We are trying to compile Libvirt 1.02 from source for an RHEL4 target. Our virtualization hosts are running the fedora 17/ RHEL6 with the latest standard libvirt binaries. This is where VMs will be created. But our user/development machines are RHEL4 and we would like users to be able to use virsh/libvirt/python to control the Vms running on RHEL6/fedora17 remotely from the their RHEL4 machines. We are trying to compile a minimalist libvirt necessary on RHEL4 that would make remote control of VMs possible. Has anyone tried this? Any suggestions on what options to pass to ./configure to minimize what needs to be compiled for this purpose? Or on RHEL 4? Thx, Sarvi

3 6