Hi,
i'm using the CVS-checkout from 20090217-1451 including
the patches you refer to (I looked inside the code).
But this error still happen sometimes ..
regards
Danny
> >
> > ** Error1
> > libvir: Remote Fehler : connection already open
> > Fehler: Verbindung zum Hypervisor scheiterte
>
> Thes
"Daniel P. Berrange" wrote:
> We are using DBus from multiple threads in libvirtd. We are not calling
> dbus_threads_init_default(). Very bad things result. Happy-crashy-daemon
>
> This patch fixes that, and also stops DBus messing around with SIGPIPE and
> also stops it calling exit() when the b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel P. Berrange wrote:
> On Tue, Feb 17, 2009 at 04:52:08PM -0500, Daniel J Walsh wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Looks like qemu launched from libvirt wants to create pulseaudito files
>> under /root/.pulse director
On Wed, Feb 18, 2009 at 02:28:27PM +0100, Daniel Schwager wrote:
> > One more: Something, it happens, that a virsh -command on the
> commandline
> > prints out an error message similar to "Can't connect to hypervisor"
> (I can't
> > reproduce it at the moment). Multiple repeating the command works
Hi,
i think something is buggy with the function libvirt-java,
Connect.close()
(closing the connection to the libvirt daemon).
I removed all the close() calls inside my prog and the
JVM will not crash any more. My prog works now like it should...
Maybe a bug ?
Thx
Danny
...
> Instructions: (
When connecting qemu:///session we can autostart the libvirtd daemon.
With the node device APIs present, it can take upto a second to start
up while talking to dbus. The remote driver was only waiting for a
fraction of a second. This changes it to wait for upto 2 seconds, and
also not to spawn mult
We are using DBus from multiple threads in libvirtd. We are not calling
dbus_threads_init_default(). Very bad things result. Happy-crashy-daemon
This patch fixes that, and also stops DBus messing around with SIGPIPE and
also stops it calling exit() when the bus disconnects, so we can actually
see
> One more: Something, it happens, that a virsh -command on the
commandline
> prints out an error message similar to "Can't connect to hypervisor"
(I can't
> reproduce it at the moment). Multiple repeating the command works
well.
> This happens not often - but sometimes..
I got the error again:
Hello, I have a problem for help. I use the libvir library 0.4.2 on
Xen 3.2.0, the host OS is Suse 10.2 . I start a windows domain (windows xp).
I use the function virDomainAttachDevice() to attach an iSCSI device to the
windows domain,but it failed. I can use this function to attach an iSCSI
On Tue, Feb 17, 2009 at 04:52:08PM -0500, Daniel J Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Looks like qemu launched from libvirt wants to create pulseaudito files
> under /root/.pulse directory.
Hmm, that sounds bad - it should not do this.
> Seems strange, and we migh
Cole Robinson wrote:
> This is the second part of the fix for rhbz 479622. If we are generating
> a bridge name for a virtual network, don't collide with any bridge name
> in a defined network. This patch also generates a bridge name at network
> define time, if none was passed in the xml.
>
> The
11 matches
Mail list logo