- Users - libvirt List Archives

[libvirt-users] Errors while using blkiotune command
by Saurabh Deochake 23 Mar '13

23 Mar '13

Hi all, I want to limit the I/O bandwidth inside the container, so I used virsh command blkiotune. But when I enter a command: virsh # blkiotune lxcguest --weight 250 I get following errors: error: Unable to change blkio parameters error: Requested operation is not valid: blkio cgroup isn't mounted I also have blkio cgroup mounted. What can be the problem? Thanks in advance. Regards, Saurabh Deochake

4 6

[libvirt-users] [bump] Storage pool created on the "wrong" vg
by Alaric Haag 23 Mar '13

23 Mar '13

________________________________ From: Alaric Haag Sent: Tuesday, March 19, 2013 2:39 PM To: libvirt-users(a)redhat.com Subject: Storage pool created on the "wrong" vg Hello all, (Hopefully, I am posing this question to the correct list!) I seem to have mis-clicked through the creation of an LVM-based storage pool in virt-manager and it is using a volume group containing LVs dedicated to the root/swap filesystems. As these are active LVs, there seems no way to remove this pool. Is that true? My reading thus far suggests that, with LVM storage units, you can't delete them from the pool without REALLY deleting them from the VG. I'm "new enough" to KVM to be missing something obvious, but I'd be pretty shocked if a "structure" like a storage pool can't be deconstructed. Kind regards, Alaric ------------------------ Here's a bit more detail in the hope someone might help: I clicked through the creation of a storage pool, and accidentally used the wrong volume group, so I have: virsh # vol-list vm_pool Name Path ----------------------------------------- lv_root /dev/vg_01/lv_root lv_swap /dev/vg_01/lv_swap These two LVs, in group vg_01, are the / and swap partition of the host system. I meant for the pool to reside on vg_vm, a different volume group. Can I safely run: virsh # vol-delete lv_root --pool=vm_pool virsh # vol-delete lv_swap --pool=vm_pool virsh # pool-delete vm_pool or do the first two steps actually destroy the LVs in vg_01 thus bringing my system crashing down? The link below strongly suggests I cannot delete these logical volumes from the pool, but is a "draft" for OpenSUSE. (I'm running libvirt 0.10.2-18 on RHEL6) http://doc.opensuse.org/products/draft/SLES/SLES-kvm_sd_draft/cha.libvirt.s… If that's the case, is there ANY way to undo my mistake and remove this pool? I am most grateful for any guidance! Alaric

1 0

Re: [libvirt-users] remote connection issue 'virsh -c qemu+ssh:///root@localhost/system list'
by Javi Legido 22 Mar '13

22 Mar '13

Hi Olivia. Another think that you should check is socat package. In my documented example the hypervisor running KVM is a Debian squeeze, and I had to proceed this way: sudo aptitude update; sudo aptitude install netcat socat -R sudo vim /bin/netcatsocket #!/bin/bash socat - unix-client:$2 sudo chmod +x /bin/netcatsocket You can try it and see if it helps or not. PD: looping in again the list, I replied just to Olivia before Cheers El 21/03/2013 12:47, "Yin Olivia-R63875" <r63875(a)freescale.com> escribió: > Hi Javier, > > Thanks for your help. > From the pages you provided, I guess you suggest is as below: > * Cannot recv data: Host key verification failed. : Connection reset by > peer > > Sucede al lanzar: > > virt-manager -c qemu+ssh://usuario@hipervisor/system > > Solucion: iniciar una sesion SSH para almacenar las claves del hipervisor > en el cliente: > > ssh usuario@hipervisor > > Exactly, I've login with ssh and then connect with virsh. > > user@x86:~$ ssh root(a)10.193.20.109 > root(a)10.193.20.109's password: > root@ppc:~# exit > logout > Connection to 10.193.20.109 closed. > > user@x86:~$ virsh -c qemu+ssh://root@10.193.20.109/system list --all > root(a)10.193.20.109's password: > error: failed to connect to the hypervisor > error: End of file while reading data: nc: invalid option -- 'U' > BusyBox v1.19.4 (2013-03-08 13:08:18 CST) multi-call binary. > > Usage: nc [-iN] [-wN] [-l] [-p PORT] [-f FILE|IPADDR PORT] [-e PROG]: > Input/output error > > It still failed to connect the hypervisor, instead of ssh issue. > > Best Regards, > Olivia > > > -----Original Message----- > > From: javilegido(a)gmail.com [mailto:javilegido@gmail.com] On Behalf Of > Javi > > Legido > > Sent: Thursday, March 21, 2013 7:35 PM > > To: Yin Olivia-R63875 > > Subject: Re: [libvirt-users] remote connection issue 'virsh -c > > qemu+ssh:///root@localhost/system list' > > > > Hi Olivia. > > > > It's in spanish, but pretty easy to follow, maybe it helps you: > > > > > http://wiki.legido.com/doku.php?id=informatica:linux:virtualizacion:kvm#adm > > inistrar_kvm_y_vm_desde_una_gui_en_el_cliente > > > > With this guide you should be able to connect from a client machine (for > > instance your laptop) to the hypervisor (KVM) if both have SSH > connectivity. > > > > Cheers. > > > > Javier > > > > 2013/3/21 Yin Olivia-R63875 <r63875(a)freescale.com>: > > > Hi, > > > > > > I'm trying remote connection with qemu hypervisor on FSL PPC board. > > > > > > The libvirt server is the PPC board. > > > > > > root@ppc:~# ifconfig eth0 10.193.20.109 root@ppc:~# libvirtd -d > > > root@ppc:~# virsh -c qemu:///system define test.xml root@ppc:~# virsh > > > -c qemu:///system start test root@ppc:~# virsh -c qemu:///system list > > > --all > > > Id Name State > > > ---------------------------------------------------- > > > 2 test running > > > > > > Connect from an X86 PC (Ubuntu 10.04) to the PPC board. > > > > > > user@x86:~$ virsh -c qemu+ssh://root@10.193.20.109/system list --all > > > The authenticity of host '10.193.20.109 (10.193.20.109)' can't be > > established. > > > RSA key fingerprint is 2f:56:07:08:da:7d:ac:41:45:57:d2:12:15:19:67:e0. > > > Are you sure you want to continue connecting (yes/no)? yes > > > root(a)10.193.20.109's password: > > > error: failed to connect to the hypervisor > > > error: End of file while reading data: Warning: Permanently added > > '10.193.20.109' (RSA) to the list of known hosts. > > > nc: invalid option -- 'U' > > > BusyBox v1.19.4 (2013-03-08 13:08:18 CST) multi-call binary. > > > > > > Usage: nc [-iN] [-wN] [-l] [-p PORT] [-f FILE|IPADDR PORT] [-e PROG]: > > > Input/output error > > > > > > > > > > > > I tried to verify the remote connection on localhost. But it also > failed > > as below: > > > > > > root@mpc8572ds:~# virsh -c qemu+ssh:///root@localhost/system list > > > --all root@localhost's password: > > > error: failed to connect to the hypervisor > > > error: End of file while reading data: nc: invalid option -- 'U' > > > BusyBox v1.19.4 (2013-03-08 13:08:18 CST) multi-call binary. > > > > > > Usage: nc [-iN] [-wN] [-l] [-p PORT] [-f FILE|IPADDR PORT] [-e PROG]: > > > Input/output error > > > > > > > > > Could anyone give suggestion on this issue? > > > > > > > > > Best Regards, > > > Olivia > > > > > > > > > _______________________________________________ > > > libvirt-users mailing list > > > libvirt-users(a)redhat.com > > > https://www.redhat.com/mailman/listinfo/libvirt-users > > >

1 0

[libvirt-users] Libvirt dead, pid still exists
by SHREE DUTH AWASTHI 21 Mar '13

21 Mar '13

Hi All, Refering to the link below, I got to know that previous versions of Libvirtd had this issue. https://www.redhat.com/archives/libvirt-users/2012-August/msg00104.html We are using libvirt-0.10.0 but we are facing the same issue. Procedure to reproduce : 1. Login to some domain name say CLA-0 using virsh. (i) # virsh list --all Id Name State ---------------------------------------------------- 4 CLA-0 running (ii) # virsh console 4 Connected to domain CLA-0 Escape character is ^] 2. Whenever we exit from the above CLA-0 domain by pressing ctrl-] We are getting the Segmentation fault, however core is not generated but we have debugged it through gdb Program received signal SIGSEGV, Segmentation fault. 0x00007ffff5a96c71 in pthread_mutex_lock () from /lib64/libpthread.so.0 (gdb) bt #0 0x00007ffff5a96c71 in pthread_mutex_lock () from /lib64/libpthread.so.0 #1 0x00007ffff78c8b97 in ?? () from /usr/lib64/libvirt.so.0 #2 0x00007ffff78b6297 in ?? () from /usr/lib64/libvirt.so.0 #3 0x00007ffff7865b65 in virHashRemoveEntry () from /usr/lib64/libvirt.so.0 #4 0x00007ffff78b60d0 in ?? () from /usr/lib64/libvirt.so.0 #5 0x00007ffff78c95f9 in ?? () from /usr/lib64/libvirt.so.0 #6 0x00007ffff78ce711 in virStreamAbort () from /usr/lib64/libvirt.so.0 #7 0x000000000042b546 in ?? () #8 0x000000000042b8f3 in ?? () #9 0x00007ffff78c983a in ?? () from /usr/lib64/libvirt.so.0 #10 0x00007ffff7843cc5 in virEventPollRunOnce () from /usr/lib64/libvirt.so.0 #11 0x00007ffff78428f5 in virEventRunDefaultImpl () from /usr/lib64/libvirt.so.0 #12 0x00007ffff793407d in virNetServerRun () from /usr/lib64/libvirt.so.0 #13 0x000000000040c483 in ?? () #14 0x00007ffff534cbbe in __libc_start_main () from /lib64/libc.so.6 ---Type <return> to continue, or q <return> to quit--- #15 0x000000000040b139 in ?? () #16 0x00007fffffffe7d8 in ?? () #17 0x000000000000001c in ?? () #18 0x0000000000000001 in ?? () #19 0x00007fffffffea73 in ?? () #20 0x0000000000000000 in ?? () After this point libvirtd is dead. # service libvirtd status libvirtd dead but pid file exists >From the mail conversation between you and Andrey we came to know that patch has been provided for this problem. Could you please share us the fix. Thanking you in anticipation. Thanks and Regards, Shree Duth Awasthi.

1 0

[libvirt-users] About live migration with snapshots
by Chiang Hubert 21 Mar '13

21 Mar '13

Hello, I'd like to live migration with snapshots. But it doesn't work. It comes out a message "cannot migrate domain with 1 snapshots" Then I try to trace the code(Libvirt 0.9.8 to 1.0.3), I find out the code in src/qemu/qemu_migration.c @ Line 1395 - 1440 (Libvirt 1.0.3) It will check the VM which has snapshots or not. I just curious about this limitation, why the VM can't live migration with snapshots? What happen if I skip this check? Does it has any suggestion way or virsh command with options to do live migration with snapshots? Thanks a lot. Hubert

3 2

[libvirt-users] SSD Trim needed? Physical Block Device Keep Track Of Guest FS Blocks?
by d hee 21 Mar '13

21 Mar '13

I am trying to figure out if a SSD drive needs to receive trim commands from the KVM guest filesystem(strictly Linux ext4 in this case).... When a file is deleted inside a KVM guest(ext4 and raw image)....If a SSD is the underlying block device that the KVM raw disk image resides on, does the SDD drive need to know which block(s) are marked for reuse within the raw image? Or is it since the Guest raw image is a container that the physical hard drive has no concern about the filesystem blocks within the Guest? Meaning the physical disk would only be concerned with the image itself as a whole...such as if the whole image was deleted? Thanks, -Darin

2 1

[libvirt-users] Storage pool created on the "wrong" vg
by Alaric Haag 20 Mar '13

20 Mar '13

Hello all, (Hopefully, I am posing this question to the correct list!) I seem to have mis-clicked through the creation of an LVM-based storage pool in virt-manager and it is using a volume group containing LVs dedicated to the root/swap filesystems. As these are active LVs, there seems no way to remove this pool. Is that true? My reading thus far suggests that, with LVM storage units, you can't delete them from the pool without REALLY deleting them from the VG. I'm "new enough" to KVM to be missing something obvious, but I'd be pretty shocked if a "structure" like a storage pool can't be deconstructed. Kind regards, Alaric

1 0

[libvirt-users] network bridge hairpin parameter support
by Zang MingJie 20 Mar '13

20 Mar '13

Hi: Currently we encounter a problem where OpenStack may forget or misconfig the bridge hairpin setting, and will cause some unexpected behavior [1]. Although this bug is marked fixed, but if we manually restart the vm by virsh will also trigger the problem. And because the bridge interface is created and managed by libvirt, we are considering move the hairpin configuration to libvirt. Now I start writing a patch to achieve this, but after digging into the source code, I found only kvm/qemu and uml backend may support this parameter. Other backends manage their own bridge, and seems no way to modify it. I expect is there any solution working in progress or should we add the new hairpin parameter in libvirt configuration ? [1] https://bugs.launchpad.net/nova/+bug/933640

1 0

[libvirt-users] network bridge hairpin parameter support
by Zang MingJie 19 Mar '13

19 Mar '13

Hi: Currently we encounter a problem where OpenStack may forget or misconfig the bridge hairpin setting, and will cause some unexpected behavior [1]. Although this bug is marked fixed, but if we manually restart the vm by virsh will also trigger the problem. And because the bridge interface is created and managed by libvirt, we are considering move the hairpin configuration to libvirt. Now I start writing a patch to achieve this, but after digging into the source code, I found only kvm/qemu and uml backend may support this parameter. Other backends manage their own bridge, and seems no way to modify it. I expect is there any solution working in progress or should we add the new parameter in libvirt configuration ? [1] https://bugs.launchpad.net/nova/+bug/933640

1 0

[libvirt-users] libvirt rpm src
by Drew Morris 19 Mar '13

19 Mar '13

Hi Guys, Do you know where the source RPMS are for libvirt? Can't find them in the official downloads section. -- Regards, Drew Morris

4 3

[libvirt-users] Unable to connect to console to recently cloned VM's
by Javi Legido 19 Mar '13

19 Mar '13

Hi all. I was using libvirt under Debian squeeze (I guess it was 0.8.3-5+squeeze4 or something similar). I was able to clone machines with below command: sudo virt-clone --connect=qemu:///system -o template -n template_clone -f /var/lib/libvirt/images/template_clone.qcow2 After that I was able to start the VM and connect to the console: sudo virsh console template_clone I recently Installed libvirt on a Debian wheezy ( libvirt-bin 0.9.12-11). I recuperated the old "template" VM, and I tried to create a new one successfully. What I CAN do: 1. Start both VM's (the template imported from the old installation and the new one) 2. Connect to the console of both VM's 3. Clone them What I CAN'T do: 1. Access to the console of the cloned VM, they stalled at the prompt. Just in case config of the VM: <domain type='kvm'> <name>template-1.dev.jj.com</name> <uuid>f75dcbdc-8fc9-b50c-6612-c34dfebea16f</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>524288</currentMemory> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64' machine='pc-1.1'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/var/lib/libvirt/images/template-1.dev.jj.com.qcow2'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <interface type='network'> <mac address='52:54:00:c0:c6:24'/> <source network='default'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> Is somebody else experiencing the same problem? I'm not sure even that the clones VM is working, since I'm able to start it up but no connect to it. Thanks. Javier

1 1

[libvirt-users] unssafe operation with virt-manager
by digvijay chauhan 17 Mar '13

17 Mar '13

I tried to migrate with virt-manager's GUI but when i invoke migrate command it gives me error that "unable to migrate vm unsafe operation"

2 1

[libvirt-users] How to pass USB device to the guest VM
by Marc Haber 16 Mar '13

16 Mar '13

Hi, I am trying to access my Galaxy Tab from Samsung KIES running on Windows 7 inside a KVM VM. This unfortunately does not seem to work as expected. My Distribution is debian unstable. I therefore have qemu-system-x86 version 1.4.0+dfsg-1exp, libvirt 1.0.3-1 and virt-manager 0.9.4-2. lsusb shows the Tab as follows: Bus 001 Device 016: ID 04e8:6877 Samsung Electronics Co., Ltd Galaxy S in Virt Manager, I can add a USB Host Device 001:016 SAMSUNG SAMSUNG_Android. This ends up in the VM as "USB 04e8:6877" and shows up in XML as <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x04e8'/> <product id='0x6877'/> </source> </hostdev> However, when I start Windows 7, the Galaxy Tab is not detected and also does not show up in Device Manager. The KVM process is called as: qemu-system-x86 -machine accel=kvm:tcg -name mywindows -S -M pc-1.1 -m 4096 -smp 2,sockets=2,cores=1,threads=1 -uuid 8e6e01e8-2191-9dcc-e2e4-5eb7ae55c450 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/snsvw001.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/dev/luksdev/mywindows,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=23,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:c4:16:65,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -device usb-host,hostbus=1,hostaddr=16,id=hostdev0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 This looks correct to me as a layman. Also, when I boot up the same VM with Linux as guest OS, the Galaxy Tablet does not show up in lsusb. What is happening on my system so that the USB device is not detected in Windows and Linux? Any ideas how to fix that? Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 31958061 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062

1 0

Re: [libvirt-users] [virt-tools-list] C'ant migrate with virt-manager or virsh
by Cole Robinson 15 Mar '13

15 Mar '13

On 03/14/2013 03:17 AM, Digvijay wrote: > [root@node0 ~]# virsh migrate --live try1 qemu+ssh://root@100.100.102.106/system > --unsafe > root(a)100.100.102.106's password: > error: operation failed: migration job: unexpectedly failed > error: Reconnected to the hypervisor > CC-ing libvirt-users I think that virsh command should work. Look at /var/log/libvirt/qemu/$vmname.log on both the source host and the destination host. > > I tried to run the migration but it is not doing profitably.I also used virtual > machine manager but it is giving me " unsafe operation" > > Unable to migrate guest: Unsafe migration: Migration may lead to data corruption > if disks use cache != none > > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in cb_wrapper > callback(asyncjob, *args, **kwargs) > File "/usr/share/virt-manager/virtManager/migrate.py", line 553, in _async_migrate > vm.migrate(dstconn, migrate_uri, rate, live, secure, meter=meter) > File "/usr/share/virt-manager/virtManager/domain.py", line 1163, in migrate > self._backend.migrate(destconn.vmm, flags, newname, interface, rate) > File "/usr/lib64/python2.7/site-packages/libvirt.py", line 822, in migrate > if ret is None:raise libvirtError('virDomainMigrate() failed', dom=self) > libvirtError: Unsafe migration: Migration may lead to data corruption if disks > use cache != none Like the error says, your disks need to have cache=None or libvirt won't allow the migration. You can change that setting per disk in the VM details UI in virt-manager. - Cole

2 2

[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 14 Mar '13

14 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) 14 Mar '13

14 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 13 Mar '13

13 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) 12 Mar '13

12 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 12 Mar '13

12 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 10 Mar '13

10 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 09 Mar '13

09 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 09 Mar '13

09 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) 08 Mar '13

08 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

[libvirt-users] libvirt v1.0.2 fails to boot LXC container, but v1.0.0 works
by Dennis Jenkins 08 Mar '13

08 Mar '13

Hello. tl;dr = v1.0.0 can boot my LXC containers, v.1.0.1 and v.1.0.2 fails. Paraphrased error message: "lxcContainerMountProcFuse:616 : Failed to mount ..../meminfo" I'd like to know if my host is misconfigured, or my domains, or ... why 1.0.2 and 1.0.1 are not working for me. I've been using libvirt for a while to manage QEMU instances. I have experimented with lxc. Back in October of last year, I had some working LXC containers. I don't recall what version of libvirt I was using at the time. I recently attempted to boot my containers, and they failed (libvirt v1.0.2). I then reverted to v1.0.1 and tried again. Failed with the same result (same error text, just different line numbers). I then reverted to 1.0.0 and my containers boot up just fine. My host runs Gentoo Linux on an Inter core-i5 with 16G ram. I regularly (weekly) apply all available Gentoo updates. I strongly perfer to install all third-party software (including libvirt) from Gentoo portage, not manually from source or git. v1.0.2 is the most recent version available. First, items common to all test cases: *** GCC version ostara ~ # gcc --version gcc (Gentoo 4.6.3 p1.11, pie-0.5.2) 4.6.3 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. *** Linux kernel ostara ~ # uname -a Linux ostara 3.6.11-gentoo #4 SMP PREEMPT Sat Jan 26 10:27:55 CST 2013 x86_64 Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz GenuineIntel GNU/Linux ostara ~ # zcat /proc/config.gz | egrep "CONFIG_(CGROUP|.*_NS|NAMESPACES)" CONFIG_CGROUPS=y CONFIG_CGROUP_DEBUG=y CONFIG_CGROUP_FREEZER=y CONFIG_CGROUP_DEVICE=y CONFIG_CGROUP_CPUACCT=y CONFIG_CGROUP_PERF=y CONFIG_CGROUP_SCHED=y CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y CONFIG_NF_CONNTRACK_NETBIOS_NS=m # CONFIG_PATA_NS87415 is not set # CONFIG_PATA_NS87410 is not set *** Gento "USE flags" when building Libvirt: ostara ~ # equery u libvirt | xargs echo -audit -avahi +caps -firewalld -iscsi +libvirtd +lvm +lxc +macvtap +nfs +nls -numa -openvz -parted +pcap -phyp -policykit -python +qemu -rbd +sasl +udev +uml +vepa +virt-network -virtualbox -xen *** libvirt config over-rides: ostara ~ # egrep "^\w" < /etc/libvirt/libvirtd.conf host_uuid = "ab8c50b8-2337-4a02-9274-00923fe8f476" ostara ~ # egrep "^\w" < /etc/libvirt/libvirt.conf ostara ~ # egrep "^\w" < /etc/conf.d/libvirtd rc_need="net" LIBVIRTD_OPTS="--listen" LIBVIRTD_KVM_SHUTDOWN="managedsave" *** Network when no domains (qemu or libvirt) are running: ostara ~ # ifconfig -a | grep -e "^[a-z]" br0: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500 br1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 *** Network with libvirt running (libvirt manages "virbr0" for my qemu instances. It attaches to "br0"). ostara ~ # /etc/init.d/libvirtd start * Starting libvirtd ... [ ok ] ostara ~ # ifconfig -a | grep -e "^[a-z]" br0: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500 br1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 *** Mounts (cgroup is mounted) ostara ~ # mount rootfs on / type rootfs (rw) proc on /proc type proc (rw,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=2050547,mode=755) devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) /dev/md3 on / type ext3 (rw,noatime,errors=continue,barrier=1,data=writeback) tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755) shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) cgroup_root on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755) openrc on /sys/fs/cgroup/openrc type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib64/rc/sh/cgroup-release-agent.sh,name=openrc) cpuset on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) debug on /sys/fs/cgroup/debug type cgroup (rw,nosuid,nodev,noexec,relatime,debug) cpu on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu) cpuacct on /sys/fs/cgroup/cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct) memory on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) devices on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) freezer on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) blkio on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) perf_event on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) /chroot/ssh-jails/jamiel/home/jamiel on /home/jamiel type none (rw,bind) libvirt on /run/libvirt/lxc/dwj-lnx-dev type fuse (rw,nosuid,nodev) *** My LXC containers: ostara ~ # virsh -c lxc:// list --all Id Name State ---------------------------------------------------- - dwj-lnx-dev shut off - vm1 shut off *** Config from one container (itself is Gentoo Linux, sharing some file-systems) ostara ~ # virsh -c lxc:// dumpxml dwj-lnx-dev <domain type='lxc'> <name>dwj-lnx-dev</name> <uuid>fbcd8c3a-9939-12b4-727d-5d3526bc448f</uuid> <memory unit='KiB'>500000</memory> <currentMemory unit='KiB'>500000</currentMemory> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/vm/lxc/dwj-lnx-dev'/> <target dir='/'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/usr/portage'/> <target dir='/usr/portage'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/usr/src'/> <target dir='/usr/src'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/home'/> <target dir='/home'/> </filesystem> <interface type='bridge'> <mac address='82:00:00:00:01:00'/> <source bridge='br0'/> </interface> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> </domain> ostara ~ # ls -l /vm/lxc/dwj-lnx-dev total 108 drwxr-xr-x 2 root root 4096 Oct 18 09:38 bin drwxr-xr-x 2 root root 4096 Apr 27 2011 boot drwxr-xr-x 10 root root 45056 Jan 26 10:52 dev drwxr-xr-x 53 root root 4096 Feb 8 11:23 etc drwxr-xr-x 2 root root 4096 Apr 27 2011 home lrwxrwxrwx 1 root root 5 Oct 18 00:46 lib -> lib64 drwxr-xr-x 2 root root 4096 Oct 18 00:51 lib32 drwxr-xr-x 10 root root 4096 Oct 18 09:11 lib64 drwxr-xr-x 4 root root 4096 Apr 27 2011 mnt drwxr-xr-x 4 root root 4096 May 22 2012 opt drwxr-xr-x 2 root root 4096 Apr 27 2011 proc drwx------ 3 root root 4096 Oct 18 08:13 root drwxr-xr-x 2 root root 4096 Oct 18 00:57 run drwxr-xr-x 2 root root 4096 Oct 18 09:11 sbin drwxr-xr-x 2 root root 4096 Apr 27 2011 sys drwxrwxrwt 4 root root 4096 Feb 8 11:23 tmp drwxr-xr-x 13 root root 4096 May 4 2011 usr drwxr-xr-x 14 root root 4096 May 22 2012 var ************ v 1.0.0 works great! ostara ~ # virsh --version 1.0.0 ostara ~ # virsh -c lxc:// list --all Id Name State ---------------------------------------------------- - dwj-lnx-dev shut off - vm1 shut off ostara ~ # virsh -c lxc:// start dwj-lnx-dev Domain dwj-lnx-dev started ostara ~ # virsh -c lxc:// list --all Id Name State ---------------------------------------------------- 21364 dwj-lnx-dev running - vm1 shut off ************* v 1.0.2 fails: ostara ~ # /etc/init.d/libvirtd start * Caching service dependencies ... [ ok ] * Starting libvirtd ... [ ok ] ostara ~ # virsh --version 1.0.2 ostara ~ # ls -l /var/lib/libvirt/lxc/ total 0 ostara ~ # virsh -c lxc:// start dwj-lnx-dev error: Failed to start domain dwj-lnx-dev error: internal error guest failed to start: PATH=/bin:/sbin TERM=linux container=lxc-libvirt container_uuid=fbcd8c3a-9939-12b4-727d-5d3526bc448f LIBVIRT_LXC_UUID=fbcd8c3a-9939-12b4-727d-5d3526bc448f LIBVIRT_LXC_NAME=dwj-lnx-dev /sbin/init 2013-02-08 18:09:28.402+0000: 1: info : libvirt version: 1.0.2 2013-02-08 18:09:28.402+0000: 1: error : lxcContainerMountProcFuse:616 : Failed to mount /.oldroot//var/run/libvirt/lxc/dwj-lnx-dev/meminfo on /proc/meminfo: No such file or directory 2013-02-08 18:09:28.402+0000: 23867: info : libvirt version: 1.0.2 2013-02-08 18:09:28.402+0000: 23867: error : virLXCControllerRun:1468 : error receiving signal from container: Input/output error 2013-02-08 18:09:28.814+0000: 23867: error : virCommandWait:2287 : internal error Child process (ip link del veth1) unexpected exit status 1: Cannot find device "veth1" ostara ~ # ls -l /var/lib/libvirt/lxc/ total 0 ostara ~ # mount | grep libvirt libvirt on /run/libvirt/lxc/dwj-lnx-dev type fuse (rw,nosuid,nodev) ostara ~ # ls -l /run/libvirt/lxc total 0 drwxr-xr-x 2 root root 40 Feb 8 12:09 dwj-lnx-dev srwx------ 1 root root 0 Feb 8 12:09 dwj-lnx-dev.sock srwx------ 1 root root 0 Feb 8 11:22 vm1.sock ostara ~ # ls -l /run/libvirt/lxc/dwj-lnx-dev total 0 *** "veth1" (regarding the rror "Cannot find device") *** "veth1" is still no created. But I do know that when *** using libvirt v1.0.0, and the container is running, the device DOES exist (not shown above) ostara ~ # ifconfig -a | egrep "^\w" br0: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500 br1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 *** The last entry in "/var/log/libvirt/lxc/dwj-lnx-dev.log" 2013-02-08 18:09:27.771+0000: starting up PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.6.3:/usr/x86_64-pc-linux-gnu/i686-pc-mingw32/gcc-bin/4.7.2 LIBVIRT_DEBUG=3 LIBVIRT_LOG_OUTPUTS=3:stderr /usr/libexec/libvirt_lxc --name dwj-lnx-dev --console 20 --security=none --handshake 23 --background --veth veth1 PATH=/bin:/sbin TERM=linux container=lxc-libvirt container_uuid=fbcd8c3a-9939-12b4-727d-5d3526bc448f LIBVIRT_LXC_UUID=fbcd8c3a-9939-12b4-727d-5d3526bc448f LIBVIRT_LXC_NAME=dwj-lnx-dev /sbin/init 2013-02-08 18:09:28.402+0000: 1: info : libvirt version: 1.0.2 2013-02-08 18:09:28.402+0000: 1: error : lxcContainerMountProcFuse:616 : Failed to mount /.oldroot//var/run/libvirt/lxc/dwj-lnx-dev/meminfo on /proc/meminfo: No such file or directory 2013-02-08 18:09:28.402+0000: 23867: info : libvirt version: 1.0.2 2013-02-08 18:09:28.402+0000: 23867: error : virLXCControllerRun:1468 : error receiving signal from container: Input/output error 2013-02-08 18:09:28.814+0000: 23867: error : virCommandWait:2287 : internal error Child process (ip link del veth1) unexpected exit status 1: Cannot find device "veth1"

5 10