Hello, I recently upgraded to libvirt 0.8.3 and qemu 0.12.5 and I'm seeing
these messages in syslog:
libvirtd: 09:52:34.591: warning : virStorageBackendQEMUImgBackingFormat:623
: Unexpected exit status '1', qemu probably failed
libvirtd: 09:52:34.746: warning : qemudParsePCIDeviceStrs:1422 : Unexp
2010/9/3 Matthias Bolte :
> 2010/9/3 Daniel P. Berrange :
>> On Fri, Sep 03, 2010 at 01:02:09PM +0200, Matthias Bolte wrote:
>>> Ah, okay, now I understand what you want to say.
>>>
>>> You have two threads A and B. When A runs on its own then it's just
>>> fine, but when you add B (that triggers a
2010/9/3 Daniel P. Berrange :
> On Fri, Sep 03, 2010 at 01:02:09PM +0200, Matthias Bolte wrote:
>> Ah, okay, now I understand what you want to say.
>>
>> You have two threads A and B. When A runs on its own then it's just
>> fine, but when you add B (that triggers an exception on purpose and
>> ign
2010/9/3 Daniel P. Berrange :
> On Fri, Sep 03, 2010 at 01:02:09PM +0200, Matthias Bolte wrote:
>> Ah, okay, now I understand what you want to say.
>>
>> You have two threads A and B. When A runs on its own then it's just
>> fine, but when you add B (that triggers an exception on purpose and
>> ign
On Fri, Sep 03, 2010 at 01:02:09PM +0200, Matthias Bolte wrote:
> Ah, okay, now I understand what you want to say.
>
> You have two threads A and B. When A runs on its own then it's just
> fine, but when you add B (that triggers an exception on purpose and
> ignores it) then A picks it up and repo
On Fri, Sep 03, 2010 at 01:02:09PM +0200, Matthias Bolte wrote:
> Ah, okay, now I understand what you want to say.
>
> You have two threads A and B. When A runs on its own then it's just
> fine, but when you add B (that triggers an exception on purpose and
> ignores it) then A picks it up and repo
Ah, okay, now I understand what you want to say.
You have two threads A and B. When A runs on its own then it's just
fine, but when you add B (that triggers an exception on purpose and
ignores it) then A picks it up and reports it. This is the point where
thread safety comes to mind.
libvirt stor
here is the stacktrace:
org.libvirt.LibvirtException: invalid argument in cannot pin vcpus on an
inactive domain
at org.libvirt.ErrorHandler.processError(Unknown Source)
at org.libvirt.Connect.processError(Unknown Source)
at org.libvirt.Connect.storagePoolLookupByName(Unkn
Well, if the domain is not running then I get this exception with
libvirt 0.6.3 and libvirt-java 0.4.2:
org.libvirt.LibvirtException: invalid argument in cannot pin vcpus on
an inactive domain
at org.libvirt.ErrorHandler.processError(Unknown Source)
at org.libvirt.Connect.processEr
