similar to: SOLVED: failed to connect to the hypervisor

When I try, I get this: root@kilo-VirtualBoxHost:~# virsh -c vbox:///session error: failed to connect to the hypervisor error: internal error: nsIEventQueue object is null ---------------------------------- The part that puzzles me is that it *used* to work, but no longer. "virsh -V" shows me running libvirt 1.2.2, with VirtualBox enabled. I'm running stock Ubuntu VirtualBox v.

On 04.03.2016 16:24, Predrag Ivanovic wrote: > Hi. > > Since the update to libvirt-1.3.2, virsh keeps disconnecting from qemu:///session. > Weirdly enough, qemu:///session works fine for root, and qemu:///system works for both the user and the root. > With the same configuration(tarball with files from /etc/libvirt attached), libvirt-1.3.1 works without problems. > > From

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

Hi. Since the update to libvirt-1.3.2, virsh keeps disconnecting from qemu:///session. Weirdly enough, qemu:///session works fine for root, and qemu:///system works for both the user and the root. With the same configuration(tarball with files from /etc/libvirt attached), libvirt-1.3.1 works without problems. From the virsh debug log(attached): --- grep error virsh.log.1.3.2 2016-03-03

What are the standard reasons for this to fail? virNetSocketReadWire:1791 : End of file while reading data: Input/output error -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20230307/7b318c84/attachment.htm>

On Tue, Mar 07, 2023 at 01:57:24PM +0000, Simon Fairweather wrote: > What are the standard reasons for this to fail? > > virNetSocketReadWire:1791 : End of file while reading data: Input/output > error The socket connection to libvirtd / other daemons was abruptly closed. Essentially you can almost always ignore this error message as being mostly harmless. With regards, Daniel --

Hi, I'm running OpenStack on CentOS 6.3 to manage lxc instances. And running into series of problem relating libvirt and lxc interaction. For example, libvirt_lxc segfault ( https://bugzilla.redhat.com/show_bug.cgi?id=874549) which has an upstream fix. And another bugs such as fail to start when SELinux disabled. Finally, I decides to adopt libvirt 0.10.2, self compiled from

Ján Tomko wrote 2018-01-18 14:27: > On Thu, Jan 18, 2018 at 11:30:16AM +0700, Artem Likhachev wrote: >> # strace -p 5786 >> read(53, "\0\0\0\34", 4) = 4 >> read(53, "keep\0\0\0\1\0\0\0\2\0\0\0\2\0\0\0\0\0\0\0\0", 24) = 24 >> poll([{fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=12, >> events=POLLIN}, {fd=13, events=POLLIN},

Hi Michal, Am 17.01.2012 09:19, schrieb Michal Privoznik: On 16.01.2012 23:04, Marko Weber wrote: Hi Michal, i cant say the USEFLAGS, cause i removed at end the package, heres a cut of logfile /var/log/libvirt/libvirt.log 2012-01-15 19:48:11.960+0000: 21586: error : virCommandWait:2192 : Interner Fehler Child process (/sbin/iptables --table mangle --insert POSTROUTING --out-interface virbr0

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The CentOS Cloud SIG ( https://wiki.centos.org/SpecialInterestGroup/Cloud ) is releasing a new OpenStack metadata package called centos-release-openstack-kilo that replaces centos-release-openstack. Metadata packages in CentOS are used to setup the repositories used by the package manager ( yum ) and the signing keys used to validate content

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

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

Hi Natxo, On Fri, 2012-11-30 at 13:06 +0100, Natxo Asenjo wrote: > hi, > > I'm following the howto on > http://freeipa.org/page/Libvirt_with_VNC_Consoles to authenticate > users voor virsh with ipa. > > I have it mostly working :-) except for the fact that libvirtd is not > respecting the sasl_allowed_username_list parameter. > > If I do not set it, and I have

On 17/07/16 09:35, kendell clark wrote: > hi > Ok, this is odd. Samba now works. I went to smb://blackfang, samba > prompted me for my user name and password, and then connected. There was > an smbclient update, and that must've fixed it because before that it > wouldn't work. My final question is printer sharing. Is it simple to set > up printer sharing where a printer

> > The demo page is up, but when I click on "Compile source code" I get: > > Not Found > > The requested URL /demo/test.cgi was not found on this server. > Weird - I noticed this bug a few weeks ago. I assume Tanya must've left some local/test changes in when she was updating the patch with my color diagnostic changes a few weeks ago. The test.cgi was up on

Hi Rick, I had the same problem last week I understand that I didn't initialized target. Cheers, Manuele Il 08/01/2013 16:08, Rick Mann ha scritto: > I wrote a little OS X app to assemble some LLVM (human-readable) code and run it. Unfortunately, my ExecutionEngine won't create. Just comes back NULL. > > This is the code that builds it: > > http://pastebin.com/8cexgPj7

Hi, Discard this request , I was investigating on the wrong compute node. It works fine. Sorry for incovenience. Regards, J.P. De : Jean-Pierre Ribeauville Envoyé : mercredi 20 janvier 2016 16:18 À : 'libvirt-users@redhat.com' Objet : channel device "state" value missing within OpenStack Kilo version Hi, I've installed a OpenStack KILO all-in-one . For private

Hi all! We are using 1 Samba PDC and 2 bdc (Version 3.0.15pre3-SVN-build-UNKNOWN-PS-SuSE) with openldap2-2.2.6-37.38 on SLES 9. New users setup ok and first logon password change works. Because of HIPAA we need the passwords to change every 30 days however this isn't happening. I thought that I had this working once upon a time while I was testing and getting ready for production but

I wrote a little OS X app to assemble some LLVM (human-readable) code and run it. Unfortunately, my ExecutionEngine won't create. Just comes back NULL. This is the code that builds it: http://pastebin.com/8cexgPj7 This is the code it seems to successfully assemble, but it can't build the ExecutionEngine. You can see I tried several different ways of building it.

Hi, I've installed a OpenStack KILO all-in-one . For private need , I've to add a channel device to all my GUESTS on my compute node. It works fine (e.g. via a virsh command). Problem is that , in the xml describing the Guest , this 'state' value : <target type='virtio' name='agent' state='disconnected'/> showing if the channel is connected