- Users - libvirt List Archives

[libvirt-users] KVM Raw Format Image Causes lseek Error when Copying
by d hee 08 Mar '13

08 Mar '13

When copying a raw KVM image to my usb drive I got a lseek error...why is this? localhost temp # lr /kvm_guests/newInstall.img -rw-r--r-- 1 root root 10G Oct 22 05:36 /kvm_guests/newInstall.img localhost temp # localhost temp # cp /kvm_guests/newInstall.img . cp: cannot lseek `./newInstall.img': Invalid argument localhost temp # df -h Filesystem Size Used Avail Use% Mounted on /dev/sdc1 15G 7.2G 7.8G 48% /mnt/temp After copy error, only 4 Gigs were copied: localhost temp # lr total 7.2G drwxr-xr-x 2 root root 8.0K Mar 6 18:10 . drwxr-xr-x 16 root root 4.0K Nov 6 09:10 .. -rwxr-xr-x 1 root root 4.0G Mar 6 18:16 newInstall.img

3 2

[libvirt-users] Developing on host machine, running code on guest VM
by Brad Barrows 07 Mar '13

07 Mar '13

Currently I am developing my projects on my host laptop and am sharing my development folder with my Guest VMs via NFS. This works however it is somewhat a hassle do to UID/GID issues.. I was wondering if there was something similar to Shared Drives in VirtualBox? Is NFS the best way to go about this kind of development or is there another feature I am missing? I have added a group on the VM with the same GID and the host users GID which works (until some file loses the group rw for some reason..). Any ideas? Thank you! Brad

3 5

[libvirt-users] libvirt (and qemu) and RHEL 6.3, 6.4, ...
by Skardal, Harald 07 Mar '13

07 Mar '13

Is there any information available that describes which versions of RHEL 6.X are supported by the different libvirt releases, and also qemu releases? For instance, can you install libvirt 1.0.2 and qemu 1.4 on the newly released RHEL 6.4? I see the following in the release notes for 1.0.3 on libvirt.org: tests: skip virstoragetest on RHEL 5 (Eric Blake), I read that to mean that libvirt 1.0.3 is tested with the most recent RHEL 5.X releases? Together with a matching qemu? But I see nothing else that indicates which KVM virtualization releases works with RHEL 6.3, 6.4, etc. Anyone know where one can find out? Harald Skardal Stratus Technologies

2 1

[libvirt-users] lxc--sshd
by Brandon Foster 07 Mar '13

07 Mar '13

Hey all, I am new to libvirt lxc and am trying to get a container that i can ssh to. So far i've booted up a container and gave it an Ip address, it can ping out and I can ping it but I cannot get ssh to work. When i try to run an ssh command inside the container I get a command not found error. here is my xml file <domain type='lxc'> <name>helloworld</name> <memory>102400</memory> <os> <type>exe</type> <init>/bin/sh</init> </os> <devices> <console type='pty'/> <filesystem type='mount'> <source dir='/export/helloworld/config'/> <target dir='/etc/httpd'/> </filesystem> <filesystem type='mount'> <source dir='/export/helloworld/data'/> <target dir='/var/www'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:5e:02:45'/> <source bridge='br0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> <model type='virtio' /> </interface> </devices> </domain> I havent restricted it with busybox for simplicity thinking it was because I wasn't allowing it access to necessary ssh files, but Im not sure what I am missing now. surely someone has done this before. thanks -- Brandon Foster Infrastructure Administrator Liferay, Inc. Enterprise. Open Source. For life.

1 3

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

07 Mar '13

On Wed, 06 Mar 2013 10:35:08 +0100, Peter Krempa wrote: >This is true for normal connections using TCP. SSH tunneling works in a different way. Hi Peter, Can you tell me why I got the "I/O Error" message (like Shantan did) when trying qemu+ssh method against libvirtd 1.x when it worked fine with libvirtd 0.9.x? What changed with that method between 0.9.x and 1.x? (I am somewhat new to all things libvirt, so documentation references are gladly accepted :) Thanks, Will

1 0

[libvirt-users] Virsh+QEMU, SSH issue on compiled libvirt
by Shantan Marepally (shanredd) 06 Mar '13

06 Mar '13

Hi All, I am trying to build libvirt from source, the compilation went fine and I see that various libvirt tools are being generated, but when I try to use the generated virsh with qemu and ssh (example virsh qemu+ssh://uri/system) I am not able to login and it fails with the following error: error: failed to connect to the hypervisor error: End of file while reading data: : Input/output error I verified the following so far: * QEMU driver is being enabled (--with-qemu, --with-qemu-user, --with-qemu-group), other options are default * Permissions and ssh logging setup are all fine (the same command with a precompiled virsh works fine) Any ideas? Thanks for your time. Shantan

1 0

[libvirt-users] Debugging TLS connection between virt-viewer and libvirt running on separate hosts
by Will Dennis 06 Mar '13

06 Mar '13

Hi all, I'm running libvirt 1.0.2 on one host (Ubuntu 12.04), and virt-manager/virt-viewer on another (FC18), and using TLS to secure the comm's between the hosts. I was able to get virt-manager to connect the the hypervisor host via qemu+tls method, but virt-viewer will not connect (either invoked from the "Show the graphical console" option on virt-manager's VM window, or by invoking virt-viewer directly.) Both fail with a generic error (virt-manager's view console says "viewer connection to hypervisor host got refused or disconnected") but does not give a more explicit error. I did a tcpdump, and the trace does show the client machine connecting to TCP port 16514 on the hypervisor host, which is owned by the libvirtd daemon. From what I can see in the packets from that dump, it looks like the endpoints are exchanging certificate info, but of course the session is encrypted, so can't really see what else is going on... Is there a way someone can give me to debug the communications for either the client or server side? (There's nothing being written to logs as far as I can see.) Thanks, Will

1 0

[libvirt-users] Live external snapshot coalescing
by Skardal, Harald 06 Mar '13

06 Mar '13

On standard Fedora 18 I was attempting blockcommit on a *live* VM, libvirt said it was not supported, so I tried fedora-virt-preview as recommended. We found a problem with qemu 1.4, there seems to be an acknowledged bug, a missing library. On a different system we loaded Fedora 18, and then pulled qemu (1.3) and libvirt (1.0.2) from rawhide. I tried blockcommit with domain shut down, it said must be up. Started the domain, and voila, it seems to have worked. Question: The committed snap file (the one I committed to the image below) is still in there, and virsh snapshot-list lists it. But the base and the upstream snap file has been updated, the upstream snap file points to the base image as per qemu-img info. How/where do I update the metadata so that virsh displays the correct thing? I.e. the committed snapshot should disappear? Is it as simple as removing the committed snap? Do I have to restart anything to get the virsh output correct? Cheers, Harald Skardal, Stratus Technologies.

3 2

[libvirt-users] Fwd: OpenVSwitch and libvirt integration problem at shutdown/reboot
by Ernesto Domato 05 Mar '13

05 Mar '13

Hi everyone, I'm forwarding this mail that I wrote to OpenVSwitch dev list because I think that you could maybe help me a little :-) What did you think about the patch to libvirt that I'm using?. At least, it worked for me :-) Thanks. Ernesto ---------- Forwarded message ---------- From: Ernesto Domato <edomat(a)gmail.com> Date: Mon, Mar 4, 2013 at 2:09 PM Subject: OpenVSwitch and libvirt integration problem at shutdown/reboot To: dev(a)openvswitch.org Hi everyone, this mail is related to a bug report that I did on Debian (#701760) that I wasn't able to resolve yet and want to know if someone has the same problem and how could I fix it. The problem that I'm having is that on shutdown/reboot of the machine that holds the virtual machines that use OVS, the OVS-Switch is going down before libvirt finish to shutdown the VMs. This cause that libvirt can¡t unregister the virtual interface from the OVS-Switch and it hangs the shutdown/reboot process. The only way that I have to solve this at that point is to log in by SSH and restart the OVS-Switch so libvirt can finish unregistering the interfaces and the system continue with the task asked. What I tried too is to patch the libvirt to use the --no-wait flag for ovs-vsctl command that deletes the virtual interface so it doesn't hang when OVS-Switch isn't running. It worked on the sense that the system does shutdown/reboot but next time it boot, the VMs stop responding, I have to delete the virtual interface from OVS-Switch and register it again and then the VM start responding again. I guess that this happens because the virtual interface was never deleted from OVS-DB and when the system boots again there's like an old reference to the virtual interface that provoke this behavior. Have anyone had this problem?, how did you solve it?, what your suggestion for me?. Looking at the manpages, I'll try another patch for libvirt that will delete the interface with the flag --if-exists before adding it back on libvirt start of the VM so, if the OVS-DB already has the interface, it is deleted. If this works, do you think it's a good solution?, or should it be implemented in other ways?. Thanks for all and excuse my english but it's not my native language. Ernesto

2 1

[libvirt-users] Qemu-1.4.0-2 and Qemu-1.4.0-1 is broken on virt-preview and rawhide
by Skardal, Harald 05 Mar '13

05 Mar '13

All, Our testing seems to indicate that Qemu-1.4.0-2 and Qemu-1.4.0-1 is broken on virt-preview and rawhide. I'm getting undefined symbol: usbredirparser_send_start_bulk_receiving when running qemu-system-x86_64 -version.. Do others see this issue? Is there a known solution? Harald Failing cases: ------------------------------------------------------------------------ -------------------------------------- Failed on Qemu-1.4.0-2 ---------------------- [root@node1 ~]# rpm -q --file /usr/bin/qemu-system-x86_64 qemu-system-x86-1.4.0-2.fc18.x86_64 [root@node1 ~]# /usr/bin/qemu-system-x86_64 --version /usr/bin/qemu-system-x86_64: symbol lookup error: /usr/bin/qemu-system-x86_64: undefined symbol: usbredirparser_send_start_bulk_receiving Failed on Qemu-1.4.0-1 ---------------------- [root@localhost ~]# rpm -q --file /usr/bin/qemu-system-x86_64 qemu-system-x86-1.4.0-1.fc18.x86_64 [root@localhost ~]# /usr/bin/qemu-system-x86_64 --version /usr/bin/qemu-system-x86_64: symbol lookup error: /usr/bin/qemu-system-x86_64: undefined symbol: usbredirparser_send_start_bulk_receiving ------------------------------------------------------------------------ -------------------------------------- Passed on Qemu-1.3.0-9 ---------------------- [root@node0 ~]# rpm -q --file /usr/bin/qemu-system-x86_64 qemu-system-x86-1.3.0-9.fc18.x86_64 [root@node0 ~]# /usr/bin/qemu-system-x86_64 --version QEMU emulator version 1.3.0, Copyright (c) 2003-2008 Fabrice Bellard

2 1