April 2010 - Users - Libvirt List Archives

Re: [libvirt-users] Libvirt Compilation on MS Vista

by Matthias Bolte

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

14 years, 3 months

2
1
0 / 0

[libvirt-users] Question about libvirt general storage driver/framework

by Povilas

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

14 years, 3 months

1
0
0 / 0

[libvirt-users] New Snapshot API Not working

by Tej Parkash, ERS, HCLTech

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. -----------------------------------------------------------------------------------------------------------------------

14 years, 3 months

1
0
0 / 0

[libvirt-users] Need help using libvirt with qcow2 delta and base images

by Wang David

Hi, I am having trouble configuring a virtual machine domain and its corresponding xml definition to use a qcow2 delta disk. The delta disk is backed by a qcow2 base disk. I am able to successfully start the guest OS with the delta disk at the command line using qemu. However, I am not able to start the guest OS using the libvirt tools including virsh and virt-manager. I am hoping that someone knows how to configure a virtual machine domain that works with a qcow2 delta disk, and have it managed by the virt-family tools. First, I create a delta and base disk from a raw image file with the following commands: qemu-img convert ubuntu910server64.img -O qcow2 ubuntu910server64_base.qcow2 qemu-img create -b ubuntu910server64_base.qcow2 -f qcow2 ubuntu910server64_delta.qcow2 Then, I can successfully start the guest OS on the command line with qemu-system-x86_64 -m 256 -hda ubuntu910server64_delta.qcow2 My attempt to modify the virtual machine domain configuration fails. Here are my steps: -- Edit the configuration # virsh edit ubuntu910server64 -- Replace some lines <disk type='file' device='disk'> - <source file='/var/lib/libvirt/images/ubuntu910server64.img'/> - <target dev='vda' bus='virtio'/> + <source file='/var/lib/libvirt/images/ubuntu910server64_delta.qcow2'/> + <target dev='hda' bus='ide'/> </disk> -- Attempt to start the machine # virsh start ubuntu910server64 Connecting to uri: qemu:///system error: Failed to start domain ubuntu910server64 error: internal error unable to start guest: qemu: could not open disk image /var/lib/libvirt/images/ubuntu910server64_delta.qcow2 If I have posted this to the wrong forum, please direct me to the right location. Thanks! -dave

14 years, 3 months

2
4
0 / 0

[libvirt-users] Restarting network on host completely cuts off guests. Why? How to prevent?

by Andreas Ntaflos

Hi list, this probably isn't a completely libvirt-specific question but I'll try anyway. Please ignore if it is too much off-topic. On an Ubuntu (9.10) virtualisation host, running KVM and libvirt and several guests (Debian, Ubuntu, Windows Server 2003) in a bridged network fashion [1,2] I noticed that performing /etc/init.d/networking restart on the host completely cuts off all guests from the network. I have to manually shutdown and restart (virsh shutdown GUEST && virsh start GUEST, a mere reboot doesn't suffice) them to get them onto the network again. Obviously that's not ideal. Is this the expected behaviour? Can I somehow re-establish guest network connectivity without shutting down the guest first? Is my setup somehow wrong or do I expect too much? Any insight, explanation or pointers would be much appreciated! Thanks, Andreas [1] http://wiki.libvirt.org/page/Networking#Debian.2FUbuntu_Bridging [2] http://wiki.libvirt.org/page/Networking#Guest_configuration_2 -- Andreas Ntaflos GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4

14 years, 3 months

4
4
0 / 0

[libvirt-users] Libvirt Compilation on MS Vista

by Development

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 Libvirt 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. Tim McLeod Simulamen Limited Registered in England No: 7133731

14 years, 3 months

1
0
0 / 0

[libvirt-users] Libvirt Compilation on MS Vista

by Tim McLeod

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. Tim McLeod Simulamen Limited Registered in England No: 7133731

14 years, 3 months

1
0
0 / 0

[libvirt-users] That the Linux bridge configuration does not work afer I upgraded the kernel to 2.6.33.2.

by Frank Peng

Hello, When I use a standard Redhat kernel, it's ok. Everything's working right. That the Linux bridge configuration does not work afer I upgraded the kernel to 2.6.33.2. Why? [root@node78 ~]# cat /etc/issue Red Hat Enterprise Linux Server release 5.5 (Tikanga) Kernel \r on an \m [root@node78 ~]# uname -a Linux node78 2.6.33.2 #1 SMP Wed Apr 14 10:10:29 CST 2010 x86_64 x86_64 x86_64 GNU/Linux [root@node78 ~]# cat /etc/sysconfig/selinux # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - SELinux is fully disabled. SELINUX=disabled # SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted [root@node78 ~]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination [root@node78 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 # Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) DEVICE=eth0 HWADDR=00:15:17:11:16:18 BRIDGE=br0 NM_CONTROLLED=no ONBOOT=yes [root@node78 ~]# cat /etc/sysconfig/network-scripts/ifcfg-br0 DEVICE=br0 TYPE=Bridge BOOTPROTO=static BROADCAST=192.168.0.255 IPADDR=192.168.0.78 NETMASK=255.255.255.0 NETWORK=192.168.0.0 DELAY=0 NM_CONTROLLED=no ONBOOT=yes [root@node78 ~]#cd /usr/src/ [root@node78 ~]#tar jxf linux-2.6.33.2.tar.bz2 [root@node78 ~]#ln -s linux-2.6.33.2 linux [root@node78 ~]#cd linux [root@node78 ~]#cp /boot/config-2.6.18-164.el5 /usr/src/linux-2.6.33.2/.config [root@node78 ~]#make menuconfig (add the option "enable deprecated sysfs feathures to support old userspace tools") [root@node78 ~]#make && make modules && make modules_install && make install [root@node78 ~]# ifconfig br0 Link encap:Ethernet HWaddr 00:15:17:11:16:18 inet addr:192.168.0.78 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::215:17ff:fe11:1618/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7217 errors:0 dropped:0 overruns:0 frame:0 TX packets:273 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:738606 (721.2 KiB) TX bytes:36168 (35.3 KiB) eth0 Link encap:Ethernet HWaddr 00:15:17:11:16:18 inet6 addr: fe80::215:17ff:fe11:1618/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7490 errors:0 dropped:0 overruns:0 frame:0 TX packets:304 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:866112 (845.8 KiB) TX bytes:42312 (41.3 KiB) Memory:b8820000-b8840000 eth1 Link encap:Ethernet HWaddr 00:15:17:11:16:19 inet addr:10.0.7.78 Bcast:10.255.255.255 Mask:255.0.0.0 inet6 addr: fe80::215:17ff:fe11:1619/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:59 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1056 (1.0 KiB) TX bytes:10982 (10.7 KiB) Memory:b8800000-b8820000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1831 errors:0 dropped:0 overruns:0 frame:0 TX packets:1831 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3576260 (3.4 MiB) TX bytes:3576260 (3.4 MiB) [root@node78 ~]# ifconfig vmbr0 vmbr0: error fetching interface information: Device not found Best Regards, Frank

14 years, 3 months

1
0
0 / 0

[libvirt-users] STP default behavior for bridged (off) and NAT (on) networking in libvirt

by Francesco Pretto

Hello, when talking about networking in hypervisors, it's easy to distinguish the two classic configurations, NAT and bridged, and the official libvirt wiki does exactly in this way here [1]. NAT networking is already configured by libvirt creating a bridge called libvirt0, while bridged networking have to be configured manually by the user. The libvirt0 bridge for NAT networking is default configured in this way: STP=on MAXWAIT=0 While suggested br0 bridge for bridged networking is configured in this way: STP=off MAXWAIT=5 Please, can you explain me why STP is on for NAT and should be off for bridged networking? It seems much easier to me to create loops when using bridged networking than NAT. Moreover, reading this old debian bug about complaints of MAXWAIT != 0 when STP off, I'm wondering if the suggested configurations aren't actually switched. Thanks, Francesco [1] http://wiki.libvirt.org/page/Networking [2] http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg700924.html

14 years, 3 months

2
4
0 / 0

[libvirt-users] Default network needed?

by Andreas Ntaflos

Hi list, long(ish) time libvirt users, first time poster. Question: Is the default network (192.168.122.0/24, NAT) created by libvirt needed at all when guests are connected to the host's bridge device (and not the default network) I.e. when I have <interface type='bridge'> <source bridge='br0'/> <model type='virtio'/> </interface> in my guest definition is the default network ever even used? Or can I safely remove it? This may be a naive or stupid question but I have not found a definitive answer studying the documentation. Can anybody enlighten me? Thanks, Andreas -- Andreas Ntaflos GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4

14 years, 3 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users April 2010