similar to: reboot problem with libxl

I was sort of hoping that is was something simple like setting the "do_the_right_thing" flag. The libvirtd kicks out 2014-10-31 11:58:57.111+0000: 8741: error : virRegisterNetworkDriver:549 : driver in virRegisterNetworkDriver must not be NULL 2014-10-31 11:59:29.379+0000: 8840: error : virRegisterNetworkDriver:549 : driver in virRegisterNetworkDriver must not be NULL 2014-10-31

On Fri, Oct 31, 2014 at 08:34:48AM -0400, Alvin Starr wrote: >I was sort of hoping that is was something simple like setting the >"do_the_right_thing" flag. > > >The libvirtd kicks out >2014-10-31 11:58:57.111+0000: 8741: error : virRegisterNetworkDriver:549 >: driver in virRegisterNetworkDriver must not be NULL >2014-10-31 11:59:29.379+0000: 8840: error :

Hello, I have a CentOS 7 client running on a CentOS 7 server.  "virsh --version" reports that 3.9.0 is being used. I'm issuing a "virsh shutdown" command to shutdown the client.  I then confirm that the client has actually shutdown using "virsh list --all". Lately I've been seeing instances where I shutdown the client, turn away to work on something else, and

Hi, Is virsh able to access the VMX config of a virtual machine running on a esxi host? I would like to take backups of my virtual machine configs and the doku section "Converting from VMware VMX config to domain XML config" (http://libvirt.org/drvesx.html) comes close to this - but does not tell how to get access to the vmx file. I would prefer a solution where ssh access to the

Hi, I have encountered problem running virsh as non-root user. I am using eucalyptus software on top of KVM, eucalyptus requires to run virsh as non-root user. I've found that people had similiar issue posted in the list, but I didn't find the solution. I've tried few things. 1) put user eucalyptus in the libvirt group. 2) even changed owner /var/run/libvirt/libvirt-sock to

I'm trying to connect to vbox hypervisor on an Ubuntu 10.04 machine through libvirt java binding (libvirt-java-0.4.6) by simply invoking: Connect conn = new Connect("vbox:///session", false); but I got this exception: libvir: warning : Failed to find the interface: Is the daemon running ? libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock':

Hi all: I create VM on most hypervisors very quickly, about 2 seconds. But some hypervisors are slow, taking more than 10 seconds. I started the debug log for libvirtd and found that some threads had timed out. Thread 95205 has two 5-second timeouts, but I don't know why? Below some information about my hypervisor: [root@node1 datapool]# virsh -v 3.4.0 [root@node1 datapool]# qemu-x86_64

I just built libvirt 0.9.3 from scratch on my Ubuntu 10.10 system. It appeared to build and install correctly. When running a command like 'virsh -c qemu:///session list --all', I get the following: error: Failed to connect socket to '@/home/heath/.libvirt/libvirt-sock': Connection refused error: failed to connect to the hypervisor When looking into it, I realized libvirtd

Did something had chaqnged with spice code or settings. I just compiled latest git of 4.4 unstable and I get is a black screen all I see is the green boot image from server 2012 but I dont get blue windows logo and window does not resize it stays black. I reverted back to older git revision of 4.4 and everything is working fine with. _______________________________________________ Xen-users

I just built libvirt 0.9.3 on my Ubuntu 10.10 box. It appears to have built correctly. When I try "virsh -c qemu:///session list --all" I get the following: error: Failed to connect socket to '@/home/heath/.libvirt/libvirt-sock': Connection refused error: failed to connect to the hypervisor After that, libvirtd isn't running as user heath as it did when I was using

Hello, I recently swapped some components, and rebuilt my system. Changes to the configuration: - Wheezy Beta 1 > Wheezy Beta 2 - Kernel 3.4.9 > Kernel 3.4.11 I have tested the new Xen 4.2 stable, and Xen unstable revision 25777, both are giving me the same error so I do not believe it is related to a change in Xen. The first attempt to pass a PCI device after booting the system

Hello, I am trying to use the libvirt Java bindings (version 0.4.7) with libvirt version 0.9.12 to connect to a XenServer hypervisor. Virsh is able to connect to my XenServer, but when I try to do the same thing in Java, it won't connect. Here is the debug output: 2012-06-26 19:48:52.259+0000: 26051: info : libvirt version: 0.9.12, package: 1.fc16 (Unknown, 2012-06-26-11:43:53, flynx)

When I try to start hvm qemu-xen I get this error It seems that the path my be off. Can someone point me were in source code path to qemu pid is defined .It seems that qeum-xen points to loacation I don''t see were it is defined. xc: detail: elf_load_binary: phdr 0 at 0x0x7f71cac72000 -> 0x0x7f71cad079d5 libxl: error: libxl_dom.c:612:libxl__build_hvm: hvm building failed libxl: error:

I got a very strange problem with call-hold function. For calls that come in from PSTN and route to a SIP extension. If I put the call on hold, I cannot unhold the call after. The caller would be left with hold music forever. A warning message would be shown on the console usually a few seconds after putting the call on hold: WARNING[17428]: chan_sip.c:686 retrans_pkt: Maximum retries

Checked out the latest unstable version of Xen 4.4 but failed to create a PVHVM domU Configured Xen with ./configure --prefix=/usr DomU config file: name = "pvhvm" builder=''hvm'' device_model = ''qemu-xen'' memory = ''512'' vcpus = ''4'' pae=1 acpi=1 apic=1 vif = [ ''mac=00:16:3E:51:20:8C, bridge=xenbr0,

Hi all, Hi have one computer hosting several VM, this particular server is in need of maintenance and has to be shutdown. In order to avoid disrupting the services provided by the VM I intended to migrate the VM to another computer. Computer 1 and 2 do not share any storage. So it is necessary to migrate not only the memory but also any data on the hard-drive. Both computers are running

gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Werror -fno-stack-protector -fno-builtin -msoft-float -I../../../tools/include -I. -c -o hvmloader.o hvmloader.c cc1: warnings being treated as errors

Hello, When destroying a guest (xl destroy <domid>) on NetBSD I get the following error on the log file: Waiting for domain test (domid 1) to die [pid 11675] Domain 1 is dead Unknown shutdown reason code 255. Destroying domain. Action for shutdown reason code 255 is destroy Domain 1 needs to be cleaned up: destroying the domain do_domctl failed: errno 3 libxl: error:

I see that libvirt 1.1.0 should now support virtualbox 4.2, but I'm having problems getting it to work in OSX. I have built it using homebrew, which now has 1.1.0 in its formulae. The error I get when tying to connect is shown below. Any suggestions for where I should look next? The error about "Failed to find user record for uid 'NNNNN'" is odd. libvirtd *is* started

Hi all, this is the tenth version of the patch series to introduce upstream qemu and seabios in the xen-unstable build system. Changes to v9: - rename QEMU_UPSTREAM_TAG to QEMU_UPSTREAM_REVISION: we are going to use it with a branch name by default; - set QEMU_UPSTREAM_REVISION to "master" by default; - set SEABIOS_UPSTREAM_URL to git://xenbits.xen.org/seabios.git by default; - add