- Users - libvirt List Archives

[libvirt-users] Clone disk image common ancestry/branching.
by Mestnik, Michael J - Eagan, MN - Contractor 05 Dec '12

05 Dec '12

Hello, I was wondering if it was possible to support or easily extent libvirt to perform steps like the following when cloning: # Any existing VMs must be paused or better. ln $currentimg backing-store.img qemu-img create -o backing-store.img $currentimg.tmp qemu-img create -o backing-store.img $newimg # Get any existing VM using $currentimg.tmp mv $currentimg.tmp $currentimg The idea being to create branches of an installs ancestry rather than simply duplicating the install. Cheers. Mike Mestnik, Michael J The ESM Tools Enterprise Systems Monitoring United States Postal Service O: (651) 406-2048 Michael.J.Mestnik(a)usps.gov ITEnterpriseSystemsMonitoring(a)usps.gov

1 0

[libvirt-users] Strange QoS behavior
by Davide Guerri 04 Dec '12

04 Dec '12

Hi, I'm having some weird problem with the setup of the QoS on a bridged network. As the docs states, outbound/inbound average speed should be expressed in KBps (KBytes per second) but in order to get a maximum speed of 10Mbps (megabits per second) surprising enough I have to use 2560 on the guest (not 1280 as expected). Using 1280 units I get a speed og 5Mbps. I'm aware of peak and burst parameters but even with them I'm seeing the same (long-term) behavior. Here follows my configuration. Thank you in advance for any help you can provide. Domain definition (relevant part only) virsh # dumpxml mydomain <domain type='kvm' id='45'> [...] <devices> [...] <interface type='network'> <mac address='52:54:00:xx:xx:xx'/> <source network='br909'/> <target dev='vnet43'/> <model type='virtio'/> <bandwidth> <inbound average='2560'/> <outbound average='2560'/> </bandwidth> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> [...] </devices> </domain> The network definition: virsh # net-dumpxml br909 <network> <name>br909</name> <uuid>07319380-2025-cdcc-924a-149cd0370b56</uuid> <forward mode='bridge'/> <bridge name='br909' /> </network> And iperf result (client and server are on the same vlan and they are running on the same host) [ 5] local xx.xx.xx.xx port 5001 connected with xx.xx.xx.yy port 18396 [ 5] 0.0-30.1 sec 35.4 MBytes 9.87 Mbits/sec

3 4

[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

[libvirt-users] iSCSI storage pool autostart
by rh ev 03 Dec '12

03 Dec '12

Hello everyone, I have recently installed libvirt 1.0.0 and am having a problem with my iSCSI storage pool's autostarting. They are just going to an inactive state right after a reboot of the host. However once the startup is complete I can manually start the pool without problem. I am getting the following errors in the libvirtd.log file but they don't really give me much as to what could be causing this. I also looked in the messages log file but didn't find anything that looked useful. *2012-11-27 20:06:50.845+0000: 1358: error : virCommandWait:2287 : internal error Child process (/sbin/iscsiadm –mode session) unexpected exit status 21 * *2012-11-27 20:06:50.890+0000: 1358: error : virCommandWait:2287 : internal error Child process (/sbin/iscsiadm –mode session) unexpected exit status 21 * *2012-11-27 20:07:10.159+0000: 1358: error : virCommandWait:2287 : internal error Child process (/sbin/iscsiadm –mode discovery –type sendtargets –portal 192.168.220.50:3260,1) unexpected exit status 4* *2012-11-27 20:07:10.159+0000: 1358: error : storageDriverAutostart:101 : Failed to autostart storage pool ‘stoPool01′: internal error Child process (/sbin/iscsiadm –mode discovery –type sendtargets –portal 192.168.220.50:3260,1) unexpected exit status 4* If anyone has any ideas what is causing this it would be a great help. If you need more information let me know. Thanks, Darcy

3 3

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

01 Dec '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 于长江 01 Dec '12

01 Dec '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 29 Nov '12

29 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 27 Nov '12

27 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