- Users - libvirt List Archives

[libvirt-users] libvirt: error : internal error: cannot apply process capabilities -1
by Santhosh Kokala 11 Apr '14

11 Apr '14

Hi All, I am running libvirt-1.1.2 on Scientific Linux release 6.1 (Carbon). I compiled the libvirtd rpms and installed them on to my system. I see this error 2014-04-11 05:37:42.351+0000: 12378: error : virCommandWait:2348 : internal error: Child process (LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/libexec/qemu-kvm -help) unexpected exit status 1: libvirt: error : internal error: cannot apply process capabilities -1 Whenever libvirtd restarts. Because of this error I also cannot create a domain with os_type set to "hvm". Virsh capabilities also does not list this os_type. Can someone let me if I am missing something obvious? Santhosh

2 1

[libvirt-users] Help with understanding and solving snapshot problem
by rolf 11 Apr '14

11 Apr '14

Hello Fairly new to libvirt. I’m hoping to both solve a problem with this question as well as learn more detail about how libvirt works. Using RHEL 6.4 and libvirt version is 0.10.2 and qemu-img version is 0.12.1.2 Using virt-manager I created a VM. Nothing unusual as far as I can see. I then added a disk. So I have a second virtio based volume which the guest then mounts as a separate filesystem. At some stage after that I created a snapshot of the system. I can’t delete the snapshot. The end result is I’d like to create a snapshot that excludes the second (much larger) disk - that is backed up via conventional backup systems. But the issue is first deleting the snapshot and my understanding of what its saying. So here is some basic info: # virsh snapshot-list host1 Name Creation Time State ------------------------------------------------------------ snap1-host1 2014-01-19 16:59:10 +1100 shutoff # # virsh snapshot-info host1 --current Name: snap1-host1 Domain: host1 Current: yes State: shutoff Location: internal Parent: - Children: 0 Descendants: 0 Metadata: yes So I try and delete it: # virsh snapshot-delete host1 --current error: Failed to delete snapshot snap1-host1 error: unsupported configuration: deletion of 1 external disk snapshots not supported yet Why does it say “external” in the above error, when the snapshot-info says its Location is internal? Are they not related ideas? The img file /var/lib/libvirt/images/host1.img is not being used by KVM. the snapshot files are in use instead: # virsh domblklist host1 Target Source ------------------------------------------------ vda /var/lib/libvirt/snap1-host1.qcow2 vdb /var/lib/libvirt/snap1-host1-db.qcow2 hdc - Querying them: # qemu-img info /var/lib/libvirt/snap1-host1.qcow2 image: /var/lib/libvirt/snap1-host1.qcow2 file format: qcow2 virtual size: 24G (25769803776 bytes) disk size: 3.5G cluster_size: 65536 [root@cocoa libvirt]# qemu-img info /var/lib/libvirt/snap1-host1-db.qcow2 image: /var/lib/libvirt/snap1-host1-db.qcow2 file format: qcow2 virtual size: 1.6T (1800279089664 bytes) disk size: 325G cluster_size: 65536 What have I done wrong and how can I correct this so I can discard the existing snapshot and have a snapshot of the system excluding the second disk (and optionally which I can re-take at intervals and discard old ones)? Many thanks, rolf.

2 4

[libvirt-users] Windows 2008r2 guest tcp retransmit hangs
by Dennis Jacobfeuerborn 11 Apr '14

11 Apr '14

Hi, I'm currently investigating a problem with our windows 2008r2 guest on centos 6 hosts. The issue is that the windows system sometimes sees a SYN packet for a tcp connection but doesn't respond. Three seconds later the retransmitted packet arrives and this time windows decides to proceed normally with the connection. This is with the virtio drivers but I have now switched to the e1000 driver where the problem also occurs but not quite as badly as with virtio which leads me to speculate that the driver isn't really the problem but only affects whatever the real issue is. Also this does not happen when the systems primary IP is addressed directly but only when an IP on the loopback device is addressed through a load-balancer. I've also provisioned a linux guest on the same host and put that into the load balancer as well but there everything is fine. Has anyone run into this and can provide a pointer in the right direction? Regards, Dennis

2 1

[libvirt-users] passthrough filesystem (9p) permissions issues on Fedora 20
by David Mansfield 11 Apr '14

11 Apr '14

Hello All: I've gotten a passthrough filesystem to work (as in, to mount) in my vm (guest F20, host F20), but due to the fact that the qemu-kvm process runs as "qemu" user, I cannot access "my" files from the share. Both the guest and the host are running SSSD so the user/group mapping is identical. Other than putting 'user = "root"' it /etc/libvirt/qemu.conf, is there a way to get this to work without trashing all of the file permissions on the directory? Even if I do put the user=root, I imagine selinux will become a major headache anyway. So is there a roadmap for how to get this working? -- Thanks, David Mansfield Cobite, INC.

1 0

[libvirt-users] disk iotune
by Doron Fediuck 10 Apr '14

10 Apr '14

Hi, reading the below[1] on blkdeviotune made me wonder if we can dynamically change the values after the VM is already running using iotune. Is it supported? Thanks, Doron [1] https://fedoraproject.org/wiki/QA:Testcase_Virtualization_IO_Throttling

2 2

[libvirt-users] Passing non-standard Options through Libvirt to QEMU
by Asadullah Hussain 10 Apr '14

10 Apr '14

Hello, I have a custom QEMU which requires some non-standard command line arguments to launch a VM. e.g., "--proc-type=secondary" option is always required to launch a QEMU VM. To launch the VM through libvirt (virsh) "How do I specify these non-standard options in XML? OR if thats not possible ,Can you guide me at which point (code file) libvirt converts the XML to QEMU command (so that I can insert the option there). Regards -- Asadullah Hussain

2 3

[libvirt-users] method for communication between containers
by WANG Cheng D 09 Apr '14

09 Apr '14

Dear all, In my system, two containers need to exchange data as quick as possible and the two containers are hosted by the same physical machine, I wonder if socket is the only method for communication between containers? Thank you. Cheng Wang

2 6

[libvirt-users] Question regarding ssh and lxc
by Schulz, Arno 09 Apr '14

09 Apr '14

I'm trying to narrow down the source of a bug where a docker container sshd closes the connection after a successful authentication (https://bugzilla.redhat.com/show_bug.cgi?id=1085081) - filed with libvirt as there's no docker-io component for RHEL 6.5 in bugzilla. One of the steps I'm taking is to reproduce a similar setup using LXC but while it seemed to have worked I'm not sure I've properly reproduced the setup I would have with docker. I've based myself on the RHEL 7b Linux Container Guide 1. Created a HelloWorld containe based on the sample config file <domain type='lxc'> <name>test-container</name> <memory>102400</memory> <os> <type>exe</type> <init>/bin/sh</init> </os> <devices> <console type='pty'/> </devices> </domain> 2. Defined, started and connected to it using virsh 3. Obtained the ip and started sshd 4. And when I logged in via sshd I got the bash from the host Any assistance would be appreciated. Arno -------------------- Confidentiality Statement - The contents of this e-mail, including its attachment, are intended for the exclusive use of the recipient and may contain confidential or privileged information. If you are not the intended recipient, you are strictly prohibited from reading, using, disclosing, copying, or distributing this e-mail or any of its contents. If you received this e-mail in error, please notify the sender by reply e-mail immediately or the Privacy Office (privacy(a)ottawahospital.on.ca ) and permanently delete this e-mail and its attachments, along with any copies thereof. Thank you. Avis de confidentialit� � Ce courriel, y compris ses pi�ces jointes, s�adresse au destinataire uniquement et pourrait contenir des renseignements confidentiels. Si vous n��tes pas le bon destinataire, il est strictement interdit de lire, d�utiliser, de divulguer, de copier ou de diffuser ce courriel ou son contenu, en partie ou en entier. Si vous avez re�u ce courriel par erreur, veuillez en informer imm�diatement l�exp�diteur ou le bureau de la Protection des renseignements personnels (info.privee(a)hopitalottawa.on.ca) puis effacez le courriel ainsi que les pi�ces jointes et toute autre copie. Merci. --------------------

2 1

[libvirt-users] Not able to start a VM - Xen and libvirt
by Aravindhan Dhanasekaran 09 Apr '14

09 Apr '14

Hello, I've installed Xen 4.3.1 on a machine with x86 based 64-bit Intel processor running Fedora 20 (Linux 3.11) and libvirt 1.0.1. I'm not able to start a VM. It's failing with the below mentioned error. What am I doing wrong? If this is documented somewhere, a pointer to that would be great. I did a "generic" search, but in vain, before posting to this list and I couldn't find an easier way to search through the mailman archives of this mailing list. Thanks for your time. Aravind Error starting domain: internal error: libxenlight failed to create new domain 'vm1' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 127, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1355, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 708, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error: libxenlight failed to create new domain 'vm1'

1 0

[libvirt-users] Issue with 1.2.3 and lxcCheckNetNsSupport
by Thierry Parmentelat 09 Apr '14

09 Apr '14

Hi there I’ve just moved to libvirt-1.2.3 from 1.2.1; we use it for dealing with lxc containers I just wanted to report that everything went well for us with this new release, except for one little glitch At some point the lxc drivers seems to check that the kernel indeed has the netns feature built in Well in our environment this checks miserably fails; I haven’t been able to tell exactly why, but could find this post that might be related Bug 1050210 – lxcCheckNetNsSupport fails to detect NETNS As a quick workaround I have this patch below in place, with which everything else seems to be working fine; at least all our system tests are passing.. It feels like the way the 1.2.3 code checks for the presence of netns is clearly not exactly right (in our case selinux is disabled), and I wish a more reliable solution can be found in the future :) Hope this helps — Thanks in any case

2 2