similar to: OSX: trying to use libvirt 1.1.0 with VirtualBox 4.2

I have freshly installed Virtualbox (5.04) and have installed libvirt (1.2.19) using brew. When i attempt to run virsh it does not work with the following outputs. # virsh -c vbox:///session error: failed to connect to the hypervisor error: internal error: unable to initialize VirtualBox driver API Any pointers on what to try next or where to investigate to get more info. Has anyone got virsh

Hi, When I want to start a VM by virsh, report error: virsh start vm1 2013-09-18 05:52:06.809+0000: 12324: info : libvirt version: 1.1.1, package: 1.mcp8_0.1 (Koji, 2013-08-09-07:55:01, lnxmcp1) 2013-09-18 05:52:06.809+0000: 12324: debug : virLogParseOutputs:1334 : outputs=1:file:/var/log/virsh.log error: Failed to start domain vm1 error: End of file while reading data: Input/output error

Hi All, I am trying to compile libvirt tools from source on RHEL 4. I could get the sources compiled, but when I try to connect to libvirtd using QEMU+SSH I get the following error: error: failed to connect to the hypervisor error: authentication failed: unsupported authentication type 2 With root as the user, I could login, rest other users get the error. All authentication related settings

On 04/20/2015 09:28 PM, Matthew Schumacher wrote: > > On 04/20/2015 05:12 PM, Laine Stump wrote: >> On 04/20/2015 08:45 PM, Matthew Schumacher wrote: >>> List, >>> >>> I was under the impression that I could restart libvirtd without it >>> destroying my VMs, but am not finding that to be true. >> If not, then something is wrong. >> >

Hi I was trying out the libxl backend of xen 4.3 with libvirt, but I found it very unstable and unusable. I'm in xen 4.3 dom0 and starting: 1. xen stuff: echo "Starting Xen..." /etc/init.d/xencommons start #/etc/init.d/xend start . /etc/rc.d/rc.xen_bridge start /etc/init.d/xendomains start #libvirtd -l -d hsflowd 2. Starting libvirt -v to see what is going on. After that

On 04/20/2015 05:12 PM, Laine Stump wrote: > On 04/20/2015 08:45 PM, Matthew Schumacher wrote: >> List, >> >> I was under the impression that I could restart libvirtd without it >> destroying my VMs, but am not finding that to be true. > If not, then something is wrong. > Here are the logs from the vm: 2015-04-20 23:50:20.387+0000: shutting down qemu:

libvirt 1.3.3 seems to have introduced some kind of issue on CentOS 6 (no systemd). After upgrading, libvirt would take an incredibly long time to get to a state where it would actually respond to a simple 'virsh list' command. Looking at verbose output showed this repeating at exactly 30s intervals 2016-04-12 19:40:57.142+0000: 14929: info : virEventPollDispatchHandles:507 :

Hello all, I have been trying to get libvirtd to work but when I connect to it with virsh, I get "error : virNetMessageDecodeLength:131 : Unable to decode message length" This happens with libvirt 6.1.0, libtirpc 1.2.6, rpcsvc-proto 1.4.1. I have tried with other versions, but I still get the same error. If anybody has any tip on what to try next, that would be helpful. Thank you

Hi, I tried to build and run libvirt-1.0.1 on FSL PowerPC platform. The connection to '/var/run/libvirt/libvirt-sock' is always refused. # libvirtd -d # export LIBVIRT_DEBUG=1 # export LIBVIRT_LOG_OUTPUTS="1:file:virsh.log" # virsh -c qemu:///system list 2013-01-10 04:55:20.409+0000: 2574: info : libvirt version: 1.0.1 2013-01-10 04:55:20.409+0000: 2574: debug :

Hi all: It takes more than 10 seconds to create a vm on a Dell R830 machine, but it takes less than 2 seconds on other machines. This is not normal, so I turned on the debug log for libvirtd. I analyzed the log and found that the time was spent on libvirtd calling qemu. Thread 95225 calls the qemuProcessLaunch interface at 14:22:30.129 and then builds the emulator command line, but the

Dear Michal After I fix the local libvirt master branch follow your patch, and build rpm for CentOS 7.4. virDomainUpdateDeviceFlags as bellow: ================================================ 2018-02-27 09:27:43.782+0000: 16656: debug : virDomainUpdateDeviceFlags:8326 : dom=0x7f2084000c50, (VM: name=6ec499397d594e f2a64fcfc938f38225, uuid=6ec49939-7d59-4ef2-a64f-cfc938f38225), xml=<disk

Hi Folks, Using libvirt python bindings we are creating an lxc container.Here is the problem that we see sometimes (say 20 % of the time) when we create a new container. 1.container gets created, and also starts.However the we are not able to enter the namepace of the container.It throws an error initPid not available.We see that the using netstat command , socket connection is closed. 2.To

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

Hello everybody, i oberserve a strange behavior of libvirtd. I have an xen vm (HVM, windows xp) that i restore from an statefile. If i do so, it works. But if i do that in an loop, where i restore the vm, let it run 60 seconds, destroy it, wait 30 second, and then i restore again, it runs 91 times and then libvirt crashed and the give me in the syslog logs the messages after "from

On Tue, Apr 17, 2018 at 07:54:14PM +0900, Matt wrote: > 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

Hi Michal, Looking in the logs, it looks like the libvirt process sent a sigkill to the qemu process: 2013-10-11 19:59:22.132+0000: 10212: debug : virLockManagerAcquire:358 : lock=0x7f6bc80de170 state='(null)' flags=3 action=0 fd=0x7f6bdf3bf074 2013-10-11 19:59:22.132+0000: 10212: debug : virLockManagerFree:395 : lock=0x7f6bc80de170 2013-10-11 19:59:22.132+0000: 10212: debug :

List, I was under the impression that I could restart libvirtd without it destroying my VMs, but am not finding that to be true. When I killall libvirtd then my VM's keep running, but then when I start libvirtd it calls qemuDomainObjEndJob:1542 : Stopping job: modify (async=none vm=0x7fb8cc0d8510 name=test) and my domain gets whacked. Any way to disable this behavior? Also, while I'm

Hi, I have installed libvirt 4.9. libvirtd 4.9 takes a long time to come up. I enabled debug prints and also put my own prints Logs are below 2019-02-06 05:55:49.082+0000: 377: info : libvirt version: 4.9.0 2019-02-06 05:55:49.082+0000: 377: info : hostname: draco 2019-02-06 05:55:49.082+0000: 377: info : virObjectNew:248 : OBJECT_NEW: obj=0x558e782d8bb0 classname=virAccessManager

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

On 14.10.2013 17:38, Francois Gaudreault wrote: > Hi Michal, > > Looking in the logs, it looks like the libvirt process sent a sigkill to > the qemu process: > 2013-10-11 19:59:22.132+0000: 10212: debug : virLockManagerAcquire:358 : > lock=0x7f6bc80de170 state='(null)' flags=3 action=0 fd=0x7f6bdf3bf074 > 2013-10-11 19:59:22.132+0000: 10212: debug :