similar to: Remote connection. Get URI

Hi, when I try to use such API: virDomainPtr <http://www.libvirt.org/html/libvirt-libvirt.html#virDomainPtr> virDomainMigrate (virDomainPtr <http://www.libvirt.org/html/libvirt-libvirt.html#virDomainPtr> domain, virConnectPtr <http://www.libvirt.org/html/libvirt-libvirt.html#virConnectPtr> dconn, unsigned long flags, const char * dname, const char * uri,

Hi In my program , When libvirtd restart , the old libvirtd connection(virConnectPtr) has to reconnect, Before usr old virConnectPtr , I call virConnectIsAlive. but when I restart libvirtd , virConnectIsAlive return 1, and I continue other operate use the old virConnectPtr, program will receive signal pipe. I use libvirt event. before any api use, I call virEventRegisterDefaultImpl, and

Dell Customer Communication Hi All, I am using Compiled against library: libvirt 1.2.9 Using library: libvirt 1.2.9 Using API: QEMU 1.2.9 Running hypervisor: QEMU 2.1.2 I want user to provide username and password authentication to virConnectPtr virConnectOpenAuth(const char *name, virConnectAuthPtr auth, unsigned int flags) to login remotely for the qemu

libvirtd will lock if for example kill programm which established connection, only sigkill + restart helps., to reproduce: virConnectPtr libvirt_connection = virConnectOpen("qemu:///system"); if(libvirt_connection == NULL) { std::cout<<"failed to connect to qemu:///system\n"; exit(-1); } exit(0);

Hi, I am using python libvirt api to get domain information. When using a uri without specifying the socket path, an error occurs. uri = "qemu+ssh://myuser@some.kvm.host/system" conn = libvirt.open(uri) This results in the following: libvirt: XML-RPC error : internal error: received hangup event on socket If I append the socket path to the URI, it works. e.g.

Hi My libvirt version is 3.4.0,host system is centos 7.4 ,kernel is 3.10.0-693.el7.x86_64 , when I shutdown domain in virtual system, My program call virDomainMemoryStats, My program blocked in this api. the call stack is #0 0x00007ff242d78a3d in poll () from /lib64/libc.so.6 #1 0x00007ff243755ce8 in virNetClientIOEventLoop () from /lib64/libvirt.so.0 #2 0x00007ff24375654b in

Migration without --p2p works just fine, ie. the below works: $ virsh migrate --verbose --copy-storage-all \ --live cvm1 qemu+ssh://kashyapc@devstack3/system Migration: [100 %] Result: - On the source host, the guest is shut off - On the destination host, the guest is live migratied successfully Migration with "--p2p" fails, a simple test below:

Hello Community, I am installing a domU image via virt-install. However, it seems that a driver needs to be installed for the connection as I saw an error while running the command. Can anyone give any hints about this error? Here is the running script: # virt-install --connect=xen:/// -p -d Thu, 15 Mar 2012 10:17:55 DEBUG Launched with command line: /usr/bin/virt-install --connect=xen:///

Hello Community, I am installing a domU image via virt-install. However, it seems that a driver needs to be installed for the connection as I saw an error while running the command. Can anyone give any hints about this error? Here is the running script: # virt-install --connect=xen:/// -p -d Thu, 15 Mar 2012 10:17:55 DEBUG Launched with command line: /usr/bin/virt-install --connect=xen:///

On Fri, Apr 03, 2015 at 10:13:38AM +0200, Kashyap Chamarthy wrote: > On Fri, Apr 03, 2015 at 10:08:21AM +0200, Kashyap Chamarthy wrote: > > Migration without --p2p works just fine, ie. the below works: > > > > > > $ virsh migrate --verbose --copy-storage-all \ > > --live cvm1 qemu+ssh://kashyapc@devstack3/system > > Migration: [100 %] >

I want to run libvirtd as a special user, and allowing users that belong to a special group to connect via qemu+unix:///system (eg: unix socket). I did everything necessary to do so: created a libvirt user and group, added the libvirt user to the kvm group, added my normal user to the libvirt group, and made sure the socket is owned by libvirt:libvirt with permissions set to 770. libvirtd starts

On 29/04/2019 22.01, Michal Privoznik wrote: > On 4/29/19 1:06 PM, lameventanas@gmail.com wrote: >> I want to run libvirtd as a special user, and allowing users that belong >> to a special group to connect via qemu+unix:///system (eg: unix socket). >> >> I did everything necessary to do so: created a libvirt user and group, >> added the libvirt user to the kvm

В письме от Вторник, 25-июн-2013 11:47:10 пользователь Michal Privoznik написал: > On 24.06.2013 11:36, Александр wrote: > > libvirtd will lock if for example kill programm which established > > connection,> > > only sigkill + restart helps., to reproduce: > > virConnectPtr libvirt_connection = virConnectOpen("qemu:///system"); > >

A disk of type 'volume' is stored as <source pool='pool_name' volume='volume_name'/> and its real location is inside the 'volume_name', as 'pool_name': in this case, query libvirt for the actual path of the specified volume in the specified pool. Adjust the code so that: - for_each_disk gets the virConnectPtr, needed to do operations with libvirt

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 21.08.2013 12:58, Alexandr пишет: > 21.08.2013 12:39, Daniel P. Berrange пишет: >> On Wed, Aug 21, 2013 at 12:36:06PM +0300, Alexandr wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>> >>> 21.08.2013 09:46, Alexandr пишет: >>>> 21.08.2013 09:32, Martin Kletzander пишет: >>>>> On

Hi, When I use 'virConnectOpenAuth' function to connect to '192.168.1.102' libvirtd with ssh, Code below, the screen print the dialog "root at 192.168.1.102's password:" , and only After I type the password, the connection can be created. How can I connect to libvirtd with ssh automatically? No need to type the password manually. char *au[2] = {"root",

On Wed, Aug 21, 2013 at 12:36:06PM +0300, Alexandr wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > 21.08.2013 09:46, Alexandr пишет: > > 21.08.2013 09:32, Martin Kletzander пишет: > >> On Wed 21 Aug 2013 01:03:37 AM CEST, Alexandr wrote: > >>> > >>> good day. i trying to make callback function for > >>>

A disk of type 'volume' is stored as <source pool='pool_name' volume='volume_name'/> and its real location is inside the 'volume_name', as 'pool_name': in this case, query libvirt for the actual path of the specified volume in the specified pool. Adjust the code so that: - for_each_disk gets the virConnectPtr, needed to do operations with libvirt

Hey, Over in KubeVirt we're investigating a use case where we'd like to perform a live migration within a network namespace that does not provide libvirtd with network access. In this scenario we would like to perform a live migration by proxying the migration through a unix socket to a process in another network namespace that does have network access. That external process would live

On Tue, 30 Apr 2019 at 10:40, Michal Privoznik <mprivozn@redhat.com> wrote: > Is there any problem running libvirtd as root? > > Yes, in the regulated environment in which I work! I have to do far more thorough threat analysis than I would do if I knew which capabilities it had. So far, we've accepted the extra work; but it would be wonderful to be able to run a locked-down