November 2012 - Users - libvirt List Archives

[libvirt-users] some problem with snapshot by libvirt
by xingxing gao 21 Nov '14

21 Nov '14

Hi,all,i am using libvirt to manage my vm,in these days i am testing the libvirt snapshot ,but meet some problem: the snapshot was created from this command: snapshot-create-as win7 --disk-only --diskspec vda,snapshot=external --diskspec hda,snapshot=no but when i tried to revert from the snapshot which created from the above command ,i got error below: virsh # snapshot-revert win7 1338041515 --force error: unsupported configuration: revert to external disk snapshot not supported yet version: virsh # version Compiled against library: libvir 0.9.4 Using library: libvir 0.9.4 Using API: QEMU 0.9.4 Running hypervisor: QEMU 1.0.93

4 8

[libvirt-users] NWFilter and IPv6
by Guido Winkelmann 05 Dec '12

05 Dec '12

Hi, Libvirt's nwfilter ships a number of useful filter scripts by default, but none to handle IPv6 traffic. Is there a particular reason for that, or is that just because nobody has got around to that yet? One interesting thing about dealing with IPv6 traffic is that hosts often have several auto-configured addresses, usually at least one auto-configured link- local address under fe80::/64 and one auto-configured one from router- advertisements. For writing filter rules, it would be nice to have some function/notation to calculate those auto-configured addresses for the user, so we can write something like this: <rule action='return' direction='out' priority='500'> <ipv6 srcipaddr='ipv6_autoconf($IPV6_PREFIX[@1], $IPV6_MASK[@1], $MAC)'/> </rule> <rule action='return' direction='out' priority='500'> <ipv6 srcipaddr='$IPV6'/> </rule> <rule action='drop' direction='out' priority='1000'/> or maybe more like this: <ipv6 mode='autoconf' field='srcipaddr' prefix='$IPV6_PREFIX[@1]' netmask='$IPV6_MASK[@1]' mac='$MAC)'/> Guido

3 8

[libvirt-users] error: unsupported configuration: block I/O throttling not supported with this QEMU binary
by hzguanqiang 03 Dec '12

03 Dec '12

Hi, guys. I want to change block I/O throttle using 'virsh blkdeviotune' with vm not running, it reported an error: # virsh blkdeviotune instance-000000dc /dev/loop0 --total-bytes-sec 20000000 --total-iops-sec 20 --config error: Unable to change block I/O throttle error: unsupported configuration: block I/O throttling not supported with this QEMU binary I can do this when the vm is running. Is it a bug? How can I fix this problem. BTW,My libvirt version is 0.9.13: # virsh version Compiled against library: libvir 0.9.13 Using library: libvir 0.9.13 Using API: QEMU 0.9.13 Running hypervisor: QEMU 1.1.2 Thanks. 2012-11-28 hzguanqiang

2 5

Re: [libvirt-users] [Freeipa-users] libvirt with vnc freeipa
by Simo Sorce 30 Nov '12

30 Nov '12

Hi Natxo, On Fri, 2012-11-30 at 13:06 +0100, Natxo Asenjo wrote: > hi, > > I'm following the howto on > http://freeipa.org/page/Libvirt_with_VNC_Consoles to authenticate > users voor virsh with ipa. > > I have it mostly working :-) except for the fact that libvirtd is not > respecting the sasl_allowed_username_list parameter. > > If I do not set it, and I have a realm ticket, then I may login virsh > or virtual manager and I get tickets for libvirt/vnc services. > > If I do set it, then it tells me the client is not in the whitelist, > so I cannot log in :-) > > > 2012-11-30 12:00:53.403+0000: 7786: error : > virNetSASLContextCheckIdentity:146 : SASL client admin not allowed in > whitelist > 2012-11-30 12:00:53.403+0000: 7786: error : > virNetSASLContextCheckIdentity:150 : Client's username is not on the > list of allowed clients > 2012-11-30 12:00:53.403+0000: 7786: error : > remoteDispatchAuthSaslStep:2447 : authentication failed: > authentication failed > 2012-11-30 12:00:53.415+0000: 7781: error : virNetSocketReadWire:999 : > End of file while reading data: Input/output error > > Is this a question for the libvirt folks or is it ok to post it here? Seem more like a libvirt or maybe even a cyrus-sasl question but I would be interested in knowing what is going on. Have you used a full principal name including the realm in the list, or just the bare user names ? CCing libvirt-users. Simo. -- Simo Sorce * Red Hat, Inc * New York

4 11

[libvirt-users] error: argument unsupported: unable to handle disk requests in snapshot
by 于长江 30 Nov '12

30 Nov '12

Hello, a problem occurred during making a snapshot for a guest, ask for help... 1. the xml for snapshotdomain like this: # cat deployment.1 <domainsnapshot> <name>a</name> <disks> <disk name='/home/qcow2/disk.0'> <driver type='qcow2'/> <source file='/home/qcow2/disk.3'/> </disk> </disks> </domainsnapshot> 2. when i execute the command , a mistake occurred: # virsh snapshot-create qcow2 deployment.1 error: argument unsupported: unable to handle disk requests in snapshot 3. i add the parameter '--disk-only', another mistake occurred: # virsh snapshot-create qcow2 deployment.1 --disk-only error: Failed to take snapshot: unknown command: 'snapshot_blkdev' 4. my libvirtd version is 0.9.4 , i update to 1.0.0 , also had this problem # libvirtd --version libvirtd (libvirt) 1.0.0 5. this is my guest below: # ls -l -rw-r--r-- 1 oneadmin oneadmin 1540 2012-11-27 15:27 deployment.0 -rw-r--r-- 1 root root 204 2012-11-27 21:28 deployment.1 -rw-r--r-- 1 root root 5772345344 2012-11-28 17:42 disk.0 -rw-r--r-- 1 root root 459264 2012-11-27 21:02 disk.1 -rw-r--r-- 1 root root 372736 2012-11-27 15:25 disk.2 # virsh list Id 名� �� ---------------------------------------------------- 1 qcow2 running # qemu-img info disk.0 image: disk.0 file format: qcow2 virtual size: 20G (21474836480 bytes) disk size: 5.4G cluster_size: 65536 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 1354019482 142M 2012-11-27 20:31:22 00:00:08.971 is there anyone has the same problem with me ? 于长江 | 东软 --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. ---------------------------------------------------------------------------------------------------

2 2

[libvirt-users] error when configuring management access via PolicyKit
by Arindam Choudhury 28 Nov '12

28 Nov '12

Hi, Libvirtd is in listen mode. /etc/libvirt/libvirtd.conf listen_tls = 0 listen_tcp = 1 auth_tcp = "sasl" my trying to setup polkit authentication using http://wiki.libvirt.org/page/SSHPolicyKitSetup [root@aopcach ~]# cat /etc/polkit-1/localauthority/50-local.d/50-org.arindam-libvirt-remote-access.pkla [Remote libvirt SSH access] Identity=unix-user:arindam Action=org.libvirt.unix.manage ResultAny=yes ResultInactive=yes ResultActive=yes but it fails with: [arindam@aopcach ~]$ virsh -c qemu+ssh:///system arindam@localhost's password: error: authentication failed: polkit\56retains_authorization_after_challenge=1 Authorization requires authentication but no agent is available. error: failed to connect to the hypervisor

1 0

[libvirt-users] How to passthru a block device from host to the quest os in kvm?
by Dennis Chen 27 Nov '12

27 Nov '12

Hi, Is there any APIs or some XML scheme can passthru a local block device of the host, eg, /dev/sda1 to its running guest OS? Specifically, say there is a block device /dev/sda1 in the host, mount it: mount /dev/sda1 /mnt; ls /mnt: a.file, b.file After passthru, the same /dev/sda1 can be used by the quest os(maybe the dev name is changed): mount /dev/sda1 /mnt; ls /mnt: a.file, b.file. BRs, Dennis

1 0

[libvirt-users] Live migration with non-shared storage leads to corrupted file system
by Xinglong Wu 27 Nov '12

27 Nov '12

Hi, We have the following environment for live-migration with non-shared stroage between two nodes, Host OS: RHEL 6.3 Kernel: 2.6.32-279.el6.x86_64 Qemu-kvm: 1.2.0 libvirt: 0.10.1 and use "virsh" to do the job as virsh -c 'qemu:///system' migrate --live --persistent --copy-storage-all <guest-name> qemu+ssh://<target-node>/system The above command itself returns no error, and the migrated domain in the destination node starts fine. But when I log into the migrated domain, some commands failed immediately. And if I shutdown the domain, it won't boot up any more, complaining about the corrupted file system. Furthermore, I can confirm that the domain before migration works flawlessly after thorough test. The log file in /var/log/libvirt/qemu looks fine without any warnings or errors. And the only error message I can observe is found at /var/log/libvirt/libvirtd.log 2012-11-25 10:00:55.001+0000: 15398: warning : qemuDomainObjBeginJobInternal:838 : Cannot start job (query, none) for domain testVM; current job is (async nested, migration out) owned by (15397, 15397) 2012-11-25 10:00:55.001+0000: 15398: error : qemuDomainObjBeginJobInternal:842 : Timed out during operation: cannot acquire state change lock 2012-11-25 10:00:57.009+0000: 15393: error : virNetSocketReadWire:1184 : End of file while reading data: Input/output error I also noticed that the raw image file used by the migrated domain has the different sizes (reported by "du") before and after the migration. Is there anybody having the similiar experience with live migration on non-shared storage? It apparently leads to failed migrations in libvirt but no cirtical errors ever reported. Brett

5 5

[libvirt-users] IPV6 configuration
by Patrick Chemla 26 Nov '12

26 Nov '12

Hi, I am running package libvirt-0.9.11.6-1.fc17.x86_64 on a kernel-3.6.5-1.fc17.x86_64 Fedora 17. I have set up the host with an IPv6 address, and I made some successfull tests transferring in IPv6 mode to/from other hosts. I want to set up libvirt to get an IPv6 address for his local network interface, same for the guests. I want the guests to be able to communicate directly on the internet through this ipv6 address. I have had a <ip family="ipv6" address="2001:xxxxxxx" /> line to the /etc/libvirtd/qemu/network/default.xml file but when I restart the host, this line disappears and no ipv6 address is added to the libvirt interface. I have added an ipv6 address to the guest in the same range of the host address. I can ping6 the address locally on the guest, but can't access the host. Is there somewhere a howto-libvirt-ipv6 to understand how to set up the whole stuff? Thanks for help Patrick

2 1

[libvirt-users] Block device IO limits
by Davide Guerri 26 Nov '12

26 Nov '12

Hi all, is there a way to limit the throughput (or the number of operations per seconds) of a block device? I ask because I've a couple of misconfigured VMs that are performing a lot of disk activity (swapping I'd bet but I haven't access to their OS). Since their storage is on a NFS share they are slowing down other VMs on the same share. Thank you. Davide.

2 1

[libvirt-users] image transfer incompletely in live migration
by yli＠cloudiya.com 25 Nov '12

25 Nov '12

Hi all, I am using libvirt version 0.10.1 and qemu-kvm version 1.2.0 with RHEL 6.3 When I use libvirt API to make block migrate with a VM, it failed frequently. I check the migrated VM and found that the filesystem damaged. But sometimes it works very fine, I don't know why, it seems to be random. All failed tests have the same condition, image transfer incompletely in live migration. The image I used is 10GB size, after a failed migration it has only about 400MB to 3GB in remote host. Here is the code: import libvirt from xml.dom import minidom name = "vm-01" host = libvirt.open("qemu:///system") vm = host.lookupByNmae(name) vm_xml_file = "/etc/libvirt/qemu/%s.xml" % name vm_xml = minidom.parse(vm_xml_file).documentElement.toxml() remote_host = "qemu+ssh://host02/system" remote = libvirt.open(remote_host) try: vm.migrate2(remote, vm_xml, 89, name, None, 0) except Exception,e: print str(e) Before run the code I have already create a image for migration in remote host 'host02'. Path, size, and privilege all OK. Here is the related log: in source host 'host01': 2012-11-24 05:14:40.001+0000: 24888: warning : qemuDomainObjBeginJobInternal:838 : Cannot start job (query, none) for domain wrksp-776; current job is (async nested, migration out) owned by (24890, 24890) 2012-11-24 05:16:16.398+0000: 24888: error : qemuDomainObjBeginJobInternal:842 : Timed out during operation: cannot acquire state change lock 2012-11-24 05:16:21.317+0000: 24887: error : virNetSocketReadWire:1184 : End of file while reading data: Input/output error in remote host 'host02': 2012-11-24 05:14:00.776+0000: 11065: warning : qemuDomainObjEnterMonitorInternal:993 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous 2012-11-24 05:14:01.196+0000: 11065: warning : qemuDomainObjEnterMonitorInternal:993 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous 2012-11-24 05:14:01.198+0000: 11065: warning : qemuDomainObjEnterMonitorInternal:993 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous 2012-11-24 05:14:01.208+0000: 11065: warning : qemuDomainObjEnterMonitorInternal:993 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous 2012-11-24 05:14:01.211+0000: 11065: warning : qemuDomainObjEnterMonitorInternal:993 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous I try to use command "virsh migrate vm-01 --live --copy-storage-all --persistent --undefinesource qemu+ssh://host02/system --verbose", the test results have no change, common but not regular. Even after my once successful test, it will certainly fail when I try to make a second migrate with the same VM. How can I solve this problem？ Anything is helpful. Thanks.

1 0

[libvirt-users] how can i get rid of the password for accessing the console in virt-manager ?
by Lentes, Bernd 22 Nov '12

22 Nov '12

Hi, i'm using virt-manager to manage serveral guests on a sles 11 host. For one guest, i configured a password to enter the console via virt-manager (not via VNC). How can i get rid of it ? Thanks in advance. Bernd -- Bernd Lentes Systemadministration Institut für Entwicklungsgenetik Gebäude 35.34 - Raum 208 HelmholtzZentrum münchen bernd.lentes(a)helmholtz-muenchen.de phone: +49 89 3187 1241 fax: +49 89 3187 2294 http://www.helmholtz-muenchen.de/idg Wir sollten nicht den Tod fürchten, sondern das schlechte Leben Helmholtz Zentrum München Deutsches Forschungszentrum für Gesundheit und Umwelt (GmbH) Ingolstädter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Aufsichtsratsvorsitzende: MinDir´in Bärbel Brumme-Bothe Geschäftsführer: Prof. Dr. Günther Wess und Dr. Nikolaus Blum Registergericht: Amtsgericht München HRB 6466 USt-IdNr: DE 129521671

1 0

[libvirt-users] About IBM PowerVM hypervisor support
by Dennis Chen 22 Nov '12

22 Nov '12

Hi, I noticed that libvirt support the following hypervisors currently: * The KVM/QEMU <http://libvirt.org/drvqemu.html> Linux hypervisor * The Xen <http://libvirt.org/drvxen.html> hypervisor on Linux and Solaris hosts. * The LXC <http://libvirt.org/drvlxc.html> Linux container system * The OpenVZ <http://libvirt.org/drvopenvz.html> Linux container system * The User Mode Linux <http://libvirt.org/drvuml.html> paravirtualized kernel * The VirtualBox <http://libvirt.org/drvvbox.html> hypervisor * The VMware ESX and GSX <http://libvirt.org/drvesx.html> hypervisors * The VMware Workstation and Player <http://libvirt.org/drvvmware.html> hypervisors * The Microsoft Hyper-V <http://libvirt.org/drvhyperv.html> hypervisor /"the goal of libvirt: *to provide a common and stable layer sufficient to securely manage domains on a node, possibly remote*."/ My question is, does redhat's libvirt team have the plan to support IBM PowerVM hypervisor? If the answer is NO, what's the reason to make the support for IBM PowerVM hypervisor doesn't make sense... BRs, Dennis

5 17

[libvirt-users] add disk problems for domain
by zhijun liu 21 Nov '12

21 Nov '12

hi,all I use Java api `domain.attachDeviceFlags(xml, 0);` to add a disk for domain. the xml file like this: <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/dev/sp1353486595267/v1353488096262'/> <target dev='vdb' bus='virtio'/> </disk> then I use command `virsh detach-disk $domain vdb` to remove the disk. what I said above have no any errors.but the problem is when I restart this vm ,the disk still exist,because I see it from the command `virsh dumpxml $domain` ,how to remove the disk from this domain persistently. thanks in advance. >zhijun

2 1

[libvirt-users] Virtualbox support - documentation
by Brian Candler 21 Nov '12

21 Nov '12

At http://libvirt.org/drvvbox.html it says: "The libvirt VirtualBox driver can manage any VirtualBox version from version 2.2 onwards" However it looks like 4.2 is yet implemented. Perhaps the page could be updated? Thanks, Brian Candler. P.S. I see work is ongoing in this area: http://www.redhat.com/archives/libvir-list/2012-October/msg00038.html http://www.redhat.com/archives/libvir-list/2012-November/msg00575.html

1 0

[libvirt-users] Disk/volume hot-add question
by Harish Patil 21 Nov '12

21 Nov '12

Hello Why is the disk hot-add operation use PCI hotplug ? Below is the hot plugged device using info pci monitor cmd. > Bus 192, device 10, function 0: > SCSI controller: PCI device 1af4:1001 > IRQ 0. > BAR0: I/O at 0xc400 [0xc43f]. > BAR1: 32 bit memory at 0xf0101000 [0xf0101fff]. > id "mydisk" Could someone pls provide all the steps involved upto the point it appears in the guest kernel? Thx >harish

1 0

[libvirt-users] libvir: Domain Config error : internal error malformed uuid element
by huancong deng 19 Nov '12

19 Nov '12

what about this error ??? thanks a lot . -- personal blog : denghuancong.com facebook: facebook.com/denghuancong twitter : twitter.com/denghuancong

2 1

[libvirt-users] Fwd: unable to ping from guests in virbr0 to guests in virbr1 network
by Marwan Tanager 19 Nov '12

19 Nov '12

---------- Forwarded message ---------- From: mallapadi niranjan <niranjan.ashok(a)gmail.com> Date: Mon, Nov 19, 2012 at 7:30 PM Subject: Re: [libvirt-users] unable to ping from guests in virbr0 to guests in virbr1 network To: Marwan Tanager <marwan.tngr(a)gmail.com> On Mon, Nov 19, 2012 at 7:51 PM, Marwan Tanager <marwan.tngr(a)gmail.com>wrote: > On Mon, Nov 19, 2012 at 12:09:53PM +0530, mallapadi niranjan wrote: > > Hi all, > > > > I have 3 guests (2-RHEL4 and 1 RHEL6) and have some issues regarding > > networking between them. The 2 RHEL4 system's use default bridge virbr0 > and > > get ip's of range 192.168.122.0/24 (192.168.122.207, 192.168.122.167) > > > > I created another bridge (virbr1) with NAT forwarding (no dhcp). The > > network i choose was 192.168.100.0/24. And the third system (RHEL6) was > > assigned static ip-addres 192.168.100.101, > > > > >>From the RHEL6 system which uses virbr1 is able to ping systems in > > 192.168.122.0/24 series , but guest systems in 192.168.122.0/24 are not > > able to ping RHEL6 system (in virbr1) network. > > > > >>From the RHEL4 guests i am able to ping the gateway ip's > (192.168.122.1, > > 192.168.100.1) , but not the RHEL6 system > > > > > > Versions: > > Fedora release 16 (Verne) > > libvirt-0.9.6.3-1.fc16.x86_64 > > qemu-kvm-0.15.1-8.fc16.x86_64 > > > > Any hints on what could be the problem > > The problem is caused by the relative order of the iptables rules for > those two > networks. > > When libvirt created virbr1 for the network 192.168.100.0/24 it inserted a > couple of iptables rules on the FORWARDING chain for this interface, but it > added them before the rules of virbr0 on the same chain. Those rules > basically > are ordered as follows (at least on my system which I suspect is different > from > yours since I also had the same problem): > > 1. Forward packets destined for the interface that are part of an > established > connection. > 2. Forward packets coming from the interface. > 3. Forward packets coming from and destined to the same interface > (loopback). > 4. Reject forwarding anything else to the interface. > 5. Reject forwarding anything else from the interface. > okay that seems to be the behaviour: hain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- 0.0.0.0/0 192.168.100.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.100.0/24 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable ACCEPT all -- 0.0.0.0/0 192.168.200.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.200.0/24 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable ACCEPT all -- 0.0.0.0/0 192.168.122.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.122.0/24 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited I can ping from 192.168.100.0/24 -> 192.168.122.0/24 (but not the viceversa) > > Since those rules are inserted for every interface libvirt adds in this > order, > you can only ping from one interface to another if the set of rules for the > interface you are pinging from comes before that of the one you're pinging > to. > Otherwise, rule number 4 of the destination interface will get in the way > since > iptables matches the packets against the rules in a chain according to > their > order on it. > > A possible workaround: > > iptables-save >/path/to/iptables/dump/file > > then, edit the file to move all relevant rules that REJECT things on the > FORWARDING chain to the end of the chain. > > then put this command in your rc.local script: > > cat /path/to/iptables/dump/file | iptables-restore > > This solution is not reliable though because you will need to update the > file > containing the rules every time you add a new virtual network or update the > iptables rules for some other reason. > Right , > > Also, I hinted before at this problem on the list and someone pointed me > that > it's a bug, but nobody confirmed. Read my message on this topic with the > subject: Inconsistent iptables forwarding rules for virtual networks, to > get a > clearer picture. > > Okay, will look in to that mail > > Marwan >

1 0

[libvirt-users] unable to ping from guests in virbr0 to guests in virbr1 network
by mallapadi niranjan 19 Nov '12

19 Nov '12

Hi all, I have 3 guests (2-RHEL4 and 1 RHEL6) and have some issues regarding networking between them. The 2 RHEL4 system's use default bridge virbr0 and get ip's of range 192.168.122.0/24 (192.168.122.207, 192.168.122.167) I created another bridge (virbr1) with NAT forwarding (no dhcp). The network i choose was 192.168.100.0/24. And the third system (RHEL6) was assigned static ip-addres 192.168.100.101, >From the RHEL6 system which uses virbr1 is able to ping systems in 192.168.122.0/24 series , but guest systems in 192.168.122.0/24 are not able to ping RHEL6 system (in virbr1) network. >From the RHEL4 guests i am able to ping the gateway ip's (192.168.122.1, 192.168.100.1) , but not the RHEL6 system Versions: Fedora release 16 (Verne) libvirt-0.9.6.3-1.fc16.x86_64 qemu-kvm-0.15.1-8.fc16.x86_64 Any hints on what could be the problem Regards Niranjan

3 4

[libvirt-users] how to make the volume's format to qcow2 when creating volume
by zhijun liu 19 Nov '12

19 Nov '12

hi,all the following are files of pool and volume. storage pool is based on logical(LVM) and iscsi,now I create volume specified the format to "qcow2" *pool.xml* <pool type='logical'> <name>pool_190</name> <source> <device path='/dev/disk/by-path/ip-192.168.0.190:3260-iscsi-iqn.2012-11.com.cloudking:server.target1-lun-1'/> </source> <target> <path>/dev/pool_190</path> </target> </pool> *volume.xml* <?xml version="1.0" encoding="UTF-8" ?> <volume> <name>volume1</name> <capacity unit="GB">1</capacity> <target> <format type="qcow2" /> </target> </volume> *the problmes is :when the volume created successfully,However, the volume's format is 'raw'* like this image: /dev/pool_190/volume1 *file format: raw* virtual size: 1.0G (1073741824 bytes) disk size: 0 how to resolve this troublesome. libvirt :0.9.8 os:ubuntu12.04 many thanks for any reply....

2 1

Re: [libvirt-users] Failed to build libvirt-1.0.0-1.fc17.src.rpm on a CentOS 6.3 system
by Abbas 16 Nov '12

16 Nov '12

On 11/17/2012 02:47 AM, Frank Shi wrote: > Thanks much Abbas for your prompt response. Right, I have fixed all the > dependency issues. It compiled but failed during running test cases. I > prefer building from src-rpm is because I need to install the package onto > other machines. Building from src-rpm can generate rpm so it makes > future deploy easier. Then the start off point will be CentOS' srpms. You might still need to do some patchwork and testing before you get a working rpm (a reason why there's no third party repo for latest kvm and libvirt). Installing on multiple machines sounds like you tend towards stability and Fedora's packages won't do that job anyway! > Anyway, follow your recommendation, I downloaded the source tar and tried > to compile it from source. This time I am seeing following problems. What > could be the problem? > > Thanks, Frank > > =============== > $ tar xvf libvirt-1.0.0-rc1.tar.gz > $ libvirt-1.0.0 > $ ./configure Try using the supplied autogen script first. > libxl/libxl_conf.c:471: error: 'libxl_domain_build_info' It's a missing dep error. Quick time-savers for latest KVM and Libvirt (on latest CentOS 6.3): # qemu-kvm deps yum install gcc pkgconfig SDL-devel zlib-devel alsa-lib-devel pciutils-devel gnutls-devel glib glib2-devel ./configure --prefix=/usr --sysconfdir=/etc make && make install # libvirt deps yum install git python-devel libtool patch libxml2 libxml2-devel yajl-devel device-mapper-devel libnl-devel ./autogen-sh --system make && make install # packages to remove qemu-img qemu-kvm libvirt libvirt-client virt-top The kvm_intel manually loaded of course! ------ bassu

1 0

[libvirt-users] Failed to build libvirt-1.0.0-1.fc17.src.rpm on a CentOS 6.3 system
by Frank Shi 16 Nov '12

16 Nov '12

Hi, List, I am seeing following problems when building libvirt-1.0.0-1.fc17.src.rpm. The first failed test case is xml2sexprtest as you can see below. $ sudo rpmbuild -ba SPECS/libvirt.spec + make check TEST: virshtest ........................................ 40 ........... 51 OK TEST: sockettest ...................................... 38 OK TEST: virbuftest .... 4 OK TEST: commandtest ..................... 21 OK TEST: virhashtest .............. 14 OK TEST: virnetmessagetest ..... 5 OK TEST: virnetsockettest ............... 15 OK TEST: viratomictest .. 2 OK TEST: utiltest ... 3 OK TEST: virnettlscontexttest ........................................ 40 ........ 48 OK TEST: shunloadtest . 1 OK TEST: virtimetest ............... 15 OK TEST: viruritest .................. 18 OK TEST: virkeyfiletest . 1 OK TEST: virauthconfigtest ...... 6 OK TEST: virbitmaptest ...... 6 OK TEST: virlockspacetest ....... 7 OK TEST: securityselinuxtest TEST: virdrivermoduletest ....... 7 OK TEST: xml2sexprtest .!.!!.....................!..!!!!.!!!!!! 40 !!!!!!!!!!... 53 FAIL TEST: sexpr2xmltest ........................................ 40 ........... 51 OK TEST: xmconfigtest ..............!.!.!.!.!.!.!.!.!.!.!.!.!. 40 !.!.!.!.!.!.!.!.!...!.!.!. 66 FAIL TEST: xencapstest .......... 10 OK TEST: statstest TEST: reconnect TEST: qemuxml2argvtest ........................................ 40 ........................................ 80 ........................................ 120 ........................................ 160 ........................................ 200 ........................................ 240 ...... 246 OK TEST: qemuxml2xmltest ........................................ 40 ........................................ 80 ................................... 115 OK TEST: qemuxmlnstest ....... 7 OK TEST: qemuargv2xmltest ........................................ 40 ................................... 75 OK TEST: qemuhelptest ................ 16 OK TEST: domainsnapshotxml2xmltest ....... 7 OK TEST: qemumonitortest .. 2 OK TEST: qemumonitorjsontest !!!!! 5 FAIL TEST: esxutilstest .... 4 OK TEST: vmx2xmltest ........................................ 40 .......... 50 OK TEST: xml2vmxtest ........................................ 40 ..... 45 OK TEST: networkxml2xmltest ................ 16 OK TEST: networkxml2argvtest ......... 9 OK TEST: nwfilterxml2xmltest ........................................ 40 . 41 OK TEST: storagevolxml2xmltest ....... 7 OK TEST: storagepoolxml2xmltest ............. 13 OK TEST: nodedevxml2xmltest ............. 13 OK TEST: interfacexml2xmltest ................... 19 OK TEST: cputest ........................................ 40 .......................... 66 OK TEST: eventtest ............... 15 OK TEST: libvirtdconftest ....................................... 39 OK make[1]: *** [check-TESTS] Error 1 make: *** [check-am] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.E2o2Vs (%check) Bad exit status from /var/tmp/rpm-tmp.E2o2Vs (%check) Not sure whether the failures are related to xml. Anyway, following is a list of xml packages installed, python-lxml-2.2.3-1.1.el6.x86_64 xmldb-api-sdk-0.1-0.4.20011111cvs.1.5.el6.noarch xmlto-0.0.23-3.el6.x86_64 xmlrpc-c-1.16.24-1209.1840.el6.x86_64 xml-commons-resolver-1.1-4.18.el6.x86_64 xmlrpc-c-client-1.16.24-1209.1840.el6.x86_64 xmldb-api-0.1-0.4.20011111cvs.1.5.el6.noarch xmlrpc3-client-3.0-4.15.el6.noarch xmlgraphics-commons-1.3.1-1.1.el6.noarch libxml2-devel-2.7.6-4.el6_2.4.x86_64 libxml2-2.7.6-4.el6_2.4.x86_64 xml-common-0.6.3-32.el6.noarch perl-libxml-perl-0.08-10.el6.noarch libxml2-python-2.7.6-4.el6_2.4.x86_64 xml-commons-apis-1.3.04-3.6.el6.x86_64 # cat /proc/version Linux version 2.6.32-279.el6.x86_64 (mockbuild(a)c6b9.bsys.dev.centos.org) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Fri Jun 22 12:19:21 UTC 2012 Thanks, Frank

2 1

[libvirt-users] authentication failed, but why?
by huancong deng 16 Nov '12

16 Nov '12

I set the me into the group libvirt and write the config for libvirtd: ================================================== listen_tls = 0 listen_tcp = 0 auth_tcp = "none" mdns_adv = 0 unix_sock_group = "libvirt" unix_sock_ro_perms = "0770" unix_sock_rw_perms = "0770" unix_sock_dir = "/var/run/libvirt" log_filters = "1:libvirt 1:util 1:qemu" log_output = "1:file:/var/log/libvirt/libvirtd.log" max_clients = 500 min_workers = 10 max_workers = 50 max_requests = 50 max_client_requests = 8 =========================================== but I can't login the libvirt: [xxxxxx@u70 ~]$ virsh error : authentication failed: Authorization requires authentication but no agent is available. who can tell me why? thanks a lot. :)

1 0

[libvirt-users] Handling connection closes in (older) Sys::Virt
by Henrik Ahlgren 14 Nov '12

14 Nov '12

I hope this is the correct mailing list for discussing the Sys::Virt Perl module. It appears that the most recent version has a new method called register_close_callback that, I believe, can be used to catch errors when the connection to libvirt is closed, e.g. due to libvirt restart or a network related issue. (I've been testing this simply by killing the the SSH process in the libvirt server.) However, Debian still ships libvirt 0.9.12 in stable backports and testing, as probably do many other mainstream distributions. The latest Perl bindings that can be installed from CPAN is thus 0.9.12 and it does not have support for close callbacks. Not only that, when a Perl program loses the (ssh) connection to libvirt, Perl just crashes: Program received signal SIGPIPE, Broken pipe. 0x00007ffff73de0d0 in __write_nocancel () from /lib/libpthread.so.0 Setting a $SIG{PIPE} handler does not seem to help. Is there any possibility of a Perl program surviving and gracefully handling a closed libvirt connection with libvirt version 0.9.12 or older? Henrik

2 4

[libvirt-users] Virt-io Kernels for older RHEL/CentOS versions
by Chandana De Silva 14 Nov '12

14 Nov '12

All, I need to run a number of guests which user older distributions of RHEL and CentOS on an RHEL 6.3 host. The versions are; 4.8 - i386 5.1 - i386 5.2 - x86_64 5.3 - i386 Currently I am running these with the E1000 network driver and the IDE driver. Where can I find kernels (or modules) for virtio for these OS's ? Thanks in advance Chandana

2 2