- Users - libvirt List Archives

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