similar to: virConnectOpen question.

hi All, I'm new to this list and also not a professional libvirt user:) I'm trying to use it for running a container. This is my config: <domain type='lxc'> <name>test</name> <uuid>d3667da2-061a-7b20-a29c-3afc798a257e</uuid> <memory>500000</memory> <currentMemory>500000</currentMemory> <vcpu>1</vcpu> <os>

On Mon, Jun 05, 2017 at 07:52:58PM -0400, Michael C Cambria wrote: > > >On 06/05/2017 10:46 AM, Martin Kletzander wrote: >> On Sun, Jun 04, 2017 at 06:42:39PM -0400, Michael C Cambria wrote: >>> I've upgraded from Fedora 20; probably missed a merge of rpmnew with >>> existing .conf; permission problem, some other mistake along the way to >>> Fedora 25.

I have a CIM provider that just calls virConnectOpen("qemu:///system"); and virConnectClose(). When cimom unloads this provider segfaults - #0 0x000000305b420cd0 in ?? () (gdb) bt #0 0x000000305b420cd0 in ?? () #1 0x00000031a3e05ad9 in __nptl_deallocate_tsd () from /lib64/libpthread.so.0 #2 0x00000031a3e0674b in start_thread () from /lib64/libpthread.so.0 #3 0x00000031a32d3d1d in

On Sat, Jun 03, 2017 at 05:20:47PM -0400, Michael C Cambria wrote: >I also tried stopping libvirtd, renaming both qemu-system-i386 and >qemu-system-x86_64, start libvirtd. Things get further along; dnsmasq >log messages show up. > >$ sudo systemctl status libvirtd.service >● libvirtd.service - Virtualization daemon > Loaded: loaded

Hello, I am trying to execute virsh commands on a host but it is giving errors due to failure in acquiring lock. root at kvm01:~# virsh suspend blindone error: Failed to suspend domain blindone error: Timed out during operation: cannot acquire state change lock Any suggestions how can we figure out possible reasons. -- Jatin -------------- next part -------------- An HTML attachment was

Following xml file was used to create storage pool using 'virsh pool-create <xml>' <pool type='dir'> <name>my-diskpool</name> <uuid>2fbc894e-7619-6cda-a33c-b27fae5fbe8b</uuid> <capacity>136024670208</capacity> <allocation>11416657920</allocation> <available>124608012288</available> <source>

On Sun, Jun 04, 2017 at 06:42:39PM -0400, Michael C Cambria wrote: >I've upgraded from Fedora 20; probably missed a merge of rpmnew with >existing .conf; permission problem, some other mistake along the way to >Fedora 25. > Yeah, probably some 'rpm -qV' (or whatever the command to verify all packages is) could help as well. >Is there a "how to" similar to [1]

I followed the wiki[1] to create a KVM virtual machine using bridged network on CentOS 6.5. It seemed to work fine on initial setup. (FWIW I'm trying to run a MythBuntu guest.) However, after a reboot, it doesn't auto-start the VMs. Shortly after boot, if I go into "virsh", then do a "list", it just hangs. Likewise, if I go into "virt manager", it just

Hi, I have a host with 6 VMs set to autostart. When this host reboots, it starts libvirtd, pegasus cimom and libvirt-cim. It also restarts the VMs. Intermittently we noticed a core during start up that points to the last call made by libvirt-cim to "virInitialize". I am thinking that it is a timing issue where virInitialize is called while libvirt is trying to autostart the VMs.

On Sat, Jun 03, 2017 at 08:27:08PM -0400, Michael C Cambria wrote: > > >On 06/03/2017 05:47 PM, Martin Kletzander wrote: >> On Sat, Jun 03, 2017 at 05:20:47PM -0400, Michael C Cambria wrote: >>> I also tried stopping libvirtd, renaming both qemu-system-i386 and >>> qemu-system-x86_64, start libvirtd. Things get further along; dnsmasq >>> log messages show

One of my team mate investigated the issue where libvirt-cim was segfaulting when unloading providers. More info on this issue is at https://www.redhat.com/archives/libvirt-users/2011-August/msg00069.html Here is the gist of his investigation - I've looked into the libvirt source code and the reason for issues with the unload of libvirt-cim providers is there (and cimprovider -r forces an

*Hello,* * * *My environment is "Xen3.1 in Fedora8" with "libvirt0.3 & python2.5". When I ran the following * *commands as a non-root user "nimbus":* $python >>> import libvirt >>> libvirt.open("xen:///") --------- Console --------- [nimbus at localhost-120 ~]$ python Python 2.5.1 (r251:54863, Oct 30 2007, 13:54:11) [GCC 4.1.2

----- On Jun 5, 2019, at 4:49 PM, Peter Krempa pkrempa@redhat.com wrote: > On Wed, Jun 05, 2019 at 13:33:49 +0200, Lentes, Bernd wrote: >> Hi Peter, >> >> thanks for your help. >> >> ----- On Jun 5, 2019, at 9:27 AM, Peter Krempa pkrempa@redhat.com wrote: > > [...] > >> >> > >> > So that's interresting. Usually assertion

ear All, I configured Postfix 2.3.3-2 on CentOS 5.2 using SASL Dovecot authentication put I am facing the problem to receive mails . My postconf -n result is: [root at mails ~]# postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2

I am trying to make Qemu agent work with libvirt thanks to https://github.com/NixOS/nixops/pull/922 with libvirt 4.1.0. I've been trying to make it work for quite some time but I still haven't the slightest idea of what is wrong, I keep seeing "Guest agent is not responding: QEMU guest agent is not connected" as the program I use (nixops) calls the libvirt python API. I

Thanks, Daniel, I can see virsh nodeinfo (custom) passes now, but I still get the same error: when running under my user account: PASS: virshtest confdata/fc4.conf OK PASS: test_conf.sh First virConnectOpen() failed FAIL: reconnect when running as root: PASS: virshtest confdata/fc4.conf OK PASS: test_conf.sh First

Using libvirt under openstack I encounter a problem when launching a VM with multiple partitions (2 G image) , While a single partition can be launched successfully . The launch is done with Openstack. We are using in libvirtd.conf log_level=1 and log_outputs="1:file:/var/log/libvirt/libvirtd.log" we can see that in /var/log/libvirt/libvirtd.log appear the following error

With libvirt 6.9.0, qemu 5.1.0, and following configurations: libvirt: key_file = "/etc/ssl/libvirt/server.lan.key" cert_file = "/etc/ssl/libvirt/server.lan.crt" ca_file = "/etc/ssl/libvirt/ca.crt" log_filters="3:remote 4:event 3:util.json 3:rpc 1:*" log_outputs="1:file:/var/log/libvirt/libvirtd.log" qemu: default_tls_x509_cert_dir =

Hi there I am using libvirt+lxc on fedora I just upgraded a couple boxes from f29 to f31 i am running into rather puzzling glitches on one of the boxes, and am having a hard time trying to figure what exactly is going wrong symptom being that on the faulty box, my 3 containers startup correctly, but all of them stop after some random time shortly after (approx. in the 5-10 minutes) in some

Eric, I have a RHEL6.0 machine running libvirt 0.8.7-18. I am running into issue mentioned in one of the previous posting. https://www.redhat.com/archives/libvirt-users/2011-December/msg00059.html # virsh start <domain> error: Failed to start domain <domain> error: operation failed: failed to read qemu header # od -N 128 -tx1z /path/to/domain.save 0000000 The workaroud to run