- Users - libvirt List Archives

[libvirt-users] Using the host's LVM to manage virtual disks
by scar 27 Apr '10

27 Apr '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 i am envisioning a scenario that a fellow sysadmin is employing using xen, where the host is configured with LVM. basically, one volume group spans the physical disk. then, various logical volumes are created for the host and (Linux) guest OSes. this makes it easy to resize logical volumes should it be needed. is a setup like this possible with libvirt? the best i can think up, so far, is to create a new logical disk, vm1, and pass that as an argument to the -f option of virt-install. then, during the installation i can setup LVM within the guest. not sure if this would even work if i need to expand the volume size. first i would expand the size of vm1. then, within the vm1 OS i would expand the size of the root partition. i would like to not have to use this second layer of LVM. for example, on the host OS, i would create two logical volumes: vm1-root and vm1-swap, and these are what vm1 would use for root and swap. then, if needed, i can just increase the size of vm1-root, etc. thanks -----BEGIN PGP SIGNATURE----- iEYEAREIAAYFAkvSJ08ACgkQXhfCJNu98qDAoQCfbdN84rlxmFJCwHnsaHXdv0l4 juUAmwfE2Te+l07VfkuJYUI2/us83F5e =AmQ+ -----END PGP SIGNATURE-----

2 2

[libvirt-users] Unable to switch ISO with virsh/kvm
by Don Morrison 26 Apr '10

26 Apr '10

I'd created a VM with "virsh create" that has a CD-ROM attached <disk type='file' device='cdrom'> <source file='/images/myiso_1.2.iso'/> <target dev='sdb' bus='scsi'/> <readonly/> <alias name='scsi0-0-1'/> <address type='drive' controller='0' bus='0' unit='1'/> </disk> Now I'd like to swap that iso out and mount a new one without taking down the guest. But it fails as follows: virsh detach-disk sles-11 sdb error: Failed to detach disk error: this function is not supported by the hypervisor: This type of device cannot be hot unplugged Attaching a new iso also fails. virsh attach-disk sles-11 /images/myiso_1.3,iso sdc --type cdrom --mode readonly error: Failed to attach disk error: internal error No device with bus 'scsi' and target 'sdc' I've tried all of the variations I can think of (including attach-device detach-device, ide vs scsi, block vs file, mounting an empty CDROM device, etc) and I can't get this to work. It does work when the VM is powered down, but I need to do the iso switch when the VM is up, which seems like pretty basic functionality if trying to install an OS that covers multiple ISOs. Is this expected to work? If so, any tips on what I'm doing wrong? Thanks. I'm running SLES 11 SP1 (beta) damkvm:/tmp # virsh --version 0.7.6 damkvm:/tmp # libvirtd --version libvirtd (libvirt) 0.7.6 damkvm:/tmp # virsh version Compiled against library: libvir 0.7.6 Using library: libvir 0.7.6 Using API: QEMU 0.7.6 Running hypervisor: QEMU 0.12.3 Don Morrison

1 0

Re: [libvirt-users] Libvirt Compilation on MS Vista
by Matthias Bolte 26 Apr '10

26 Apr '10

[Let's keep the list involved] 2010/4/20 Tim McLeod <tim.mcleod(a)simulamen.eu>: > Matthias, > > Thank you for the swift response. Now, the current state is the result of following the instructions found a la Web in the attached 'print to PDF' file. Situation as follows: > > 1. MinGW. MinGW-5.1.4.exe installed without error; no issues. > 2. MSYS. Failed to locate the executable MSYS-1.0.11-2004.04.30-1.exe, but MSYS-1.0.11.exe did install without error. > 3. msysDTK. msysDTK-1.0.1.exe installed without error; no issues. > 4. GTK. gtk-dev-2.12.9-win32-2.exe installed without error; no issues. > 5. M4. Failed to locate compressed file m4-1.4.7-MSYS.tar.bz2, used m4-1.4.13-1-msys-1.0.11-bin.tar.lzma instead. Did not understand instruction to extract to the 'root' folder but instead replaced the original M4.exe found in C:\MSYS\1.0\bin with the M4.exe found in the lzma file. > 6. Autoconf. Failed to 'make' source found in autoconf-2.62.tar.gz due to a '[m4sugar.m4f] Error 1' error, but following a reference found on the Web to this error not occurring in autoconf-2.52.tar.gz, successfully 'made' and installed this version. When moving on to step 7, Automake, compilation failed since autoconf 2.6 or newer was required. However, autoconf-2.60.tar.gz failed with the 'm4sugar.m4f' error in the same way as v2.62. > > Brick wall; sore head! As I'm sure you have guessed my background is MS Windows rather than Linux so I am finding these. Probably minor issues to you, extremely daunting and frustrating to me. I am encouraged that you have successfully compiled a Windows Libvirt client, hope you can point me in the right direction. Many thanks... > > Tim > Okay, so the problem is setting up a working MinGW/MSYS environment. You used the instructions posted here: https://www.redhat.com/archives/libvir-list/2008-June/msg00145.html I didn't try that, but I wrote a set of scripts to automate the MinGW/MSYS setup and libvirt compliation on Windows. I'll clean them up a bit and post them, so you can try to use them. Probably we should also improve http://libvirt.org/windows.html with more details. Matthias

2 1

[libvirt-users] Problems moving qemu machine to libvirt
by Erik de Castro Lopo 26 Apr '10

26 Apr '10

Hi all, I have a qemu-system-arm machine that I am currently starting using: qemu-system-arm -M versatilepb -nographic \ -hda img.qcow2 \ -net vde,vlan=0,sock=/var/run/qemu-vde.ctl \ -net nic,vlan=0,macaddr=52:54:00:12:34:22 \ -kernel vmlinuz-2.6.18-6-versatile \ -initrd initrd.img-2.6.18-6-versatile \ -append "root=/dev/sda1 console=ttyAMA0,115200n8" I converted the above to a virsh XML file using: virsh domxml-from-native qemu-argv run.argc > arm32.xml which resulted in this (minor modifications to provide full paths): <domain type='qemu'> <name>arm32</name> <uuid>e433002b-107f-5b16-415b-7afb3e3a4d84</uuid> <memory>262144</memory> <currentMemory>262144</currentMemory> <vcpu>1</vcpu> <os> <type arch='arm' machine='versatilepb'>hvm</type> <kernel>/kvm/arm32/vmlinuz-2.6.18-6-versatile</kernel> <initrd>/kvm/arm32/initrd.img-2.6.18-6-versatile</initrd> </os> <features> <acpi/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/kvm/arm32/arm32.sh</emulator> <disk type='file' device='disk'> <source file='/kvm/arm32/img.qcow2'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> <controller type='ide' index='0'/> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target port='0'/> </console> </devices> </domain> Since libvirt doesn't support VDE networking I use a wrapper around qemu-system-arm (/kvm/arm32/arm32.sh) containing: #!/bin/bash exec /usr/bin/qemu-system-arm $@ \ -net nic,vlan=0,macaddr=52:54:00:12:34:22 \ -net vde,vlan=0,group=vde2-net,mode=0770,sock=/var/run/qemu-vde.ctl \ -append "root=/dev/sda1 console=ttyAMA0,115200n8" However, doing this I get the following error when I attempt to start the VM: error: Failed to start domain arm32 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/10 qemu: could not open disk image console=ttyAMA0,115200n8\"": No such file or directory The first problem (console log output) is probably due to the second, where it seems that this: <cmdline>root=/dev/sda1 console=ttyAMA0,115200n8</cmdline> is not being passed to qemu correctly. I have tried quoting the command line but that doesn't help. Anyone have any clues? Cheers, Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

2 1

[libvirt-users] QEmu 0.12.3 Libvirt-0.8.0 and serials ports
by Jorge Alejandro Rodríguez 25 Apr '10

25 Apr '10

I have a problem with libvirt and serial ports. When I run a xml with serial tag over libvirt0.8.0 and qemu 0.11 this is the line that libvirt execute LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.11 -cpu qemu32 -enable-kvm -m 0 -smp 1 -name uml2 -uuid 431cb9f4-fdba-c4e8-a35f-23b52f91120a -monitor unix:/var/lib/libvirt/qemu/uml2.monitor,server,nowait -boot cd -drive file=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/fs/root_cow_fs,if=ide,bus=0,unit=0,boot=on -drive file=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/fs/opt_fs.iso,if=ide,media=cdrom,bus=0,unit=1 -net nic,macaddr=fe:fd:00:00:02:01,vlan=0,name=net0 -net tap,fd=19,vlan=0,name=hostnet0* -serial unix:/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/uml2_socket,server,nowait * -parallel none -usb -vnc :1001 -vga cirrus -balloon virtio and the virtual machine created have a serial port but when I run the same xml in a machine with qemu 0.12.3 this is the line that libvirt execute LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 0 -smp 1,sockets=1,cores=1,threads=1 -name uml2 -uuid 3e3a4836-94b4-869c-4180-724c970c1909 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/uml2.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot cd -drive file=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/fs/root_cow_fs,if=none,id=drive-ide0-0-0,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/fs/opt_fs.iso,if=none,media=cdrom,id=drive-ide0-0-1,readonly=on -device ide-drive,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -device rtl8139,vlan=0,id=net0,mac=fe:fd:00:00:02:01,bus=pci.0,addr=0x4 -net tap,fd=18,vlan=0,name=hostnet0 -chardev socket,id=serial0,path=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/uml2_socket,server,nowait -device isa-serial,chardev=serial0 -usb -vnc :1001 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 the virtual machine don't have any serial port. If you execute the line: /usr/bin/kvm -M pc-0.11 -cpu qemu32 -enable-kvm -m 0 -smp 1 -name uml2 -uuid 431cb9f4-fdba-c4e8-a35f-23b52f91120a -monitor unix:/var/lib/libvirt/qemu/uml2.monitor,server,nowait -boot cd -drive file=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/fs/root_cow_fs,if=ide,bus=0,unit=0,boot=on -drive file=/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/fs/opt_fs.iso,if=ide,media=cdrom,bus=0,unit=1 -net nic,macaddr=fe:fd:00:00:02:01,vlan=0,name=net0 -net tap,fd=19,vlan=0,name=hostnet0* -serial unix:/root/.vnuml/simulations/tutorial-r1_xp/vms/uml2/uml2_socket,server,nowait * -parallel none -usb -vnc :1001 -vga cirrus -balloon virtio (the same line before) over qemu 0.12.3 the viertual machine have serial port. Any ideas?

2 2

[libvirt-users] Failed to insert a cd in a virtual machine running
by Jorge Alejandro Rodríguez 22 Apr '10

22 Apr '10

I can't attach a cd when a vm is running with qemu 0.12.3 (ubuntu 10.04), the problem is not with qemu because when I start the vm with kvm command (without libvirt) I can change the cd with qemu-monitor without any problem and eject it too (libvirt say me that it isn't supported by hypervisor). the versions of libvirt that I have tried are 0.7.7 and 0.8.0. Any ideas? Thanks. Jorge

1 1

[libvirt-users] Allowing incoming traffic to a virtual network
by Mathias Tausig 22 Apr '10

22 Apr '10

Hello! I have some virtual networks defined on a virtualization host (using libvirt 0.7.7 and kvm 0.12.3) with some virtual bridges (virbr1, virbr2) which are all plugged into a phisical bridge br0. Now I would like to allow external hosts to connect to guest machines, but the automatically created iptables rules forbid it. I have found this rather old post on the mailing list http://www.redhat.com/archives/libvir-list/2007-January/msg00048.html which suggests a "forwarding" element for the network configuration, but this seem to be unimplemented. cheers Mathias

1 0

Re: [libvirt-users] New VM Snapshot API Not working
by Tej Parkash, ERS, HCLTech 21 Apr '10

21 Apr '10

All, Ok, I got it working..... Problem was that I didnt include xen option for configure step. But looks like Xen Hypervisor does not have support of Snapshot. :( I guess I have to fall back to save and restore method... Sorry for the noise. Thanks Tej ________________________________________ From: Tej Parkash, ERS, HCLTech Sent: Wednesday, April 21, 2010 2:31 PM To: libvir-list(a)redhat.com Subject: New VM Snapshot API Not working All, I have compiled new libvirt library 0.8.0. Compilation and installation went really fine except "make check" which has show some test got failed. Here is what make check said. Failed Test: ---------------snip----------- PASS: statstest TEST: qparamtest ................................ 32 OK PASS: qparamtest TEST: capabilityschematest !!!!!!!!!!!! 12 FAILED FAIL: capabilityschematest TEST: interfaceschematest !!!!!!!!!!!!!!!!!! 18 FAILED FAIL: interfaceschematest TEST: networkschematest !!!!!!!!!!! 11 FAILED FAIL: networkschematest TEST: storagepoolschematest !!!!!!!!!!!!!!!!!!!! 20 FAILED FAIL: storagepoolschematest TEST: storagevolschematest !!!!!!!!!!!! 12 FAILED FAIL: storagevolschematest TEST: domainschematest !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 40 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 80 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 120 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 160 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 200 !! 202 FAILED FAIL: domainschematest TEST: nodedevschematest !!!!!!!!!!!!!! 14 FAILED FAIL: nodedevschematest TEST: nwfilterschematest !!!!!!!!!!!!!!!!!!!!!!!!!!! 27 FAILED FAIL: nwfilterschematest TEST: test_conf.sh .. 2 OK ---------------- snip --------------------------- ==================== 9 of 40 tests failed ==================== make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/tmp/libvirt-0.8.0/tests' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/tmp/libvirt-0.8.0/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/libvirt-0.8.0/tests' make: *** [check-recursive] Error 1 ------------------------------------------------------------------------- However installation went fine. After I started create some snapshot, I am getting some remote error: root@hcl:~# xm li Name ID Mem VCPUs State Time(s) Domain-0 0 622 2 r----- 1755.3 Test 3 256 1 -b---- 4.4 root@hcl:~# virsh snapshot-create 3 error: unmarshalling remote_error root@hcl:~# virsh snapshot-create 3 test.xml error: unmarshalling remote_error I have even written a C code with API's but same problem. Here is livirt version n all root@hcl:/tmp/libvirt-0.8.0# libvirtd --version libvirtd (libvirt) 0.8.0 root@hcl:/tmp/libvirt-0.8.0# virsh -v 0.8.0 root@hcl:/tmp/libvirt-0.8.0# Any Idea???????????????? Any suggestion???????/ Thanks Tej DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. -----------------------------------------------------------------------------------------------------------------------

2 1

Re: [libvirt-users] Libvirt Compilation on MS Vista
by Matthias Bolte 21 Apr '10

21 Apr '10

2010/4/19 Tim McLeod <tim.mcleod(a)simulamen.eu>: > Does a comprehensive set of instructions on how to compile Libvirt on a > Microsoft Vista platform exist? Has this ever been accomplished? I would > very much appreciate input from persons who can give me confidence that a > Windows client application can be developed on top of Libviet that connects > to a QEMU system on an Ubuntu server. The Libvirt Windows Support page > (http://libvirt.org/windows.html) implies the exercise is trivial. Over the > last three weeks of failure I have come to find this assertion extremely > amusing. > Compiling libvirt for Windows in not very well documented. You can use the mingw32 cross-compile toolchain provided by Fedora. I think several people build libvirt for Windows this way. Another option is to use MinGW and MSYS on Windows to compile libvirt for Windows. I did that successfully. So before I start to describe the setup/compilation process and so on... could you describe what your current setup looks like and what problems you're facing? Matthias

2 1

[libvirt-users] Question about libvirt general storage driver/framework
by Povilas 21 Apr '10

21 Apr '10

Hello, I have setup consisting of few nodes dedicated to virtualisation and shared storage application. For running virtual machines we are using KVM, and libvirt to manage them. Also, I am trying to setup some tools for managing storage volumes. I know about libvirt storage pools and existing storage volumes support, but what I would like to see in libvirt is generic storage driver (ideally it could depend on external application or script), or some framework for managing storage. Now we are testing NBD setup, and for some reasons I don't want to use kvm-nbd. We would like to use custom nbd client and manage block device creation/deletion for ourselves. Maybe in future we will use iSCSI instead of NBD, so platform/transport agnostic framework or driver would be very helpful. I've searched and read both mailing lists (libvir-list and libvirt-users), and have found that some libvirt users were asking for similar or same feature. E.g : https://www.redhat.com/archives/libvir-list/2009-August/msg00348.html So, the main question is: maybe there is some progress already done or someone is thinking about working on it ? -- Regards, Povilas

1 0