KVM guests fail to start

KVM guests fail to start

[David Cunningham]

Apologies if this list is inappropriate, I've failed to come across
anything pertinent via Google. If anyone can suggest a more appropriate
forum please do.

I'm having a problem starting KVM guests since performing a routine
apt-get upgrade on a debian jessie system.

On starting a guest via virt-manager I'm getting the below error.

The same behaviour is seen with existing guests or newly created guests.

Could anyone point me towards a solution, or debug course?

Thanks...


Error starting domain: internal error: QEMU / QMP failed: Failed to open
module: /usr/lib/x86_64-linux-gnu/qemu/block-iscsi.so: undefined symbol:
aio_bh_schedule_oneshot
Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-curl.so:
undefined symbol: aio_bh_schedule_oneshot
Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-rbd.so:
undefined symbol: aio_bh_schedule_oneshot
Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-ssh.so:
undefined symbol: inet_connect_saddr
Could not access KVM kernel module: Permission denied
failed to initialize KVM: Permission denied


Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in
cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 127, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1355, in
startup
    self._backend.create()
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 999, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: QEMU / QMP failed: Failed to open module:
/usr/lib/x86_64-linux-gnu/qemu/block-iscsi.so: undefined symbol:
aio_bh_schedule_oneshot
Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-curl.so:
undefined symbol: aio_bh_schedule_oneshot
Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-rbd.so:
undefined symbol: aio_bh_schedule_oneshot
Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-ssh.so:
undefined symbol: inet_connect_saddr
Could not access KVM kernel module: Permission denied
failed to initialize KVM: Permission denied

Re: KVM guests fail to start

[Stefan Hajnoczi]

[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]

On Thu, Jun 08, 2017 at 08:42:58AM +0100, David Cunningham wrote:
> Apologies if this list is inappropriate, I've failed to come across
> anything pertinent via Google. If anyone can suggest a more appropriate
> forum please do.
> 
> I'm having a problem starting KVM guests since performing a routine
> apt-get upgrade on a debian jessie system.
> 
> On starting a guest via virt-manager I'm getting the below error.
> 
> The same behaviour is seen with existing guests or newly created guests.
> 
> Could anyone point me towards a solution, or debug course?
> 
> Thanks...
> 
> 
> Error starting domain: internal error: QEMU / QMP failed: Failed to open
> module: /usr/lib/x86_64-linux-gnu/qemu/block-iscsi.so: undefined symbol:
> aio_bh_schedule_oneshot
> Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-curl.so:
> undefined symbol: aio_bh_schedule_oneshot
> Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-rbd.so:
> undefined symbol: aio_bh_schedule_oneshot
> Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-ssh.so:
> undefined symbol: inet_connect_saddr

Please make sure your qemu-block-extra and qemu-system-x86 packages are
up-to-date.  They should both have the same version number.

Are you using a backports package for QEMU?

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

Re: [Qemu-devel] KVM guests fail to start

[Stefan Hajnoczi]

[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]

On Thu, Jun 08, 2017 at 08:42:58AM +0100, David Cunningham wrote:
> Apologies if this list is inappropriate, I've failed to come across
> anything pertinent via Google. If anyone can suggest a more appropriate
> forum please do.
> 
> I'm having a problem starting KVM guests since performing a routine
> apt-get upgrade on a debian jessie system.
> 
> On starting a guest via virt-manager I'm getting the below error.
> 
> The same behaviour is seen with existing guests or newly created guests.
> 
> Could anyone point me towards a solution, or debug course?
> 
> Thanks...
> 
> 
> Error starting domain: internal error: QEMU / QMP failed: Failed to open
> module: /usr/lib/x86_64-linux-gnu/qemu/block-iscsi.so: undefined symbol:
> aio_bh_schedule_oneshot
> Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-curl.so:
> undefined symbol: aio_bh_schedule_oneshot
> Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-rbd.so:
> undefined symbol: aio_bh_schedule_oneshot
> Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-ssh.so:
> undefined symbol: inet_connect_saddr

Please make sure your qemu-block-extra and qemu-system-x86 packages are
up-to-date.  They should both have the same version number.

Are you using a backports package for QEMU?

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

Re: KVM guests fail to start

[postmaster]

On 08/06/17 11:02, Stefan Hajnoczi wrote:
>
> Please make sure your qemu-block-extra and qemu-system-x86 packages are
> up-to-date.  They should both have the same version number.
>
> Are you using a backports package for QEMU?
>
Thanks, something along the lines of this does seem to have been the
problem.

I am using the backports package but it seems that the update uprevved
qemu.* modulo qemu-system-x86.

After a bit of fiddling I've got it working again by updating
qemu-system-x86 and then forcing the user/group in
/etc/libvirt/qemu.conf (presumably the conf file was over-written by the
update).

David

Re: [Qemu-devel] KVM guests fail to start

[postmaster]

On 08/06/17 11:02, Stefan Hajnoczi wrote:
>
> Please make sure your qemu-block-extra and qemu-system-x86 packages are
> up-to-date.  They should both have the same version number.
>
> Are you using a backports package for QEMU?
>
Thanks, something along the lines of this does seem to have been the
problem.

I am using the backports package but it seems that the update uprevved
qemu.* modulo qemu-system-x86.

After a bit of fiddling I've got it working again by updating
qemu-system-x86 and then forcing the user/group in
/etc/libvirt/qemu.conf (presumably the conf file was over-written by the
update).

David

Re: KVM guests fail to start

[Michael Tokarev]

08.06.2017 13:02, Stefan Hajnoczi wrote:
> On Thu, Jun 08, 2017 at 08:42:58AM +0100, David Cunningham wrote:
>> Apologies if this list is inappropriate, I've failed to come across
>> anything pertinent via Google. If anyone can suggest a more appropriate
>> forum please do.
>>
>> I'm having a problem starting KVM guests since performing a routine
>> apt-get upgrade on a debian jessie system.
>>
>> On starting a guest via virt-manager I'm getting the below error.
>>
>> The same behaviour is seen with existing guests or newly created guests.
>>
>> Could anyone point me towards a solution, or debug course?
>>
>> Thanks...
>>
>>
>> Error starting domain: internal error: QEMU / QMP failed: Failed to open
>> module: /usr/lib/x86_64-linux-gnu/qemu/block-iscsi.so: undefined symbol:
>> aio_bh_schedule_oneshot
>> Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-curl.so:
>> undefined symbol: aio_bh_schedule_oneshot
>> Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-rbd.so:
>> undefined symbol: aio_bh_schedule_oneshot
>> Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-ssh.so:
>> undefined symbol: inet_connect_saddr
> 
> Please make sure your qemu-block-extra and qemu-system-x86 packages are
> up-to-date.  They should both have the same version number.

The up-to-date thing isn't a requiriment, you can use any version of
your choice if it suits your needs.

The problem here is the version MISMATCH - qemu-system-x86 package
is from one version, while qemu-block-extra is from another.

qemu-block-extra package contains less-often-used block modules,
and in order to work, should be of the same version as corresponding
qemu-system-* package. I especially didn't use strong versioned
depencency here, in order to keep ability to try other versions of
qemu-system if some problem is found.

However, it seems like when qemu tries to load "wrong-versioned"
modules, it fails to _start_, which should not really happen.
It should ignore the wrong modules and continue, _unless_ you
actually use one of the block drivers in this package (only
in that case it should fail to start telling it didn't find
the requested block device).

Please for now ensure qemu-system-* and qemu-block-extra are
of the same version. We'll see what can be done to avoid this
prob in the future.

Thanks!

/mjt

Re: [Qemu-devel] KVM guests fail to start

[Michael Tokarev]

08.06.2017 13:02, Stefan Hajnoczi wrote:
> On Thu, Jun 08, 2017 at 08:42:58AM +0100, David Cunningham wrote:
>> Apologies if this list is inappropriate, I've failed to come across
>> anything pertinent via Google. If anyone can suggest a more appropriate
>> forum please do.
>>
>> I'm having a problem starting KVM guests since performing a routine
>> apt-get upgrade on a debian jessie system.
>>
>> On starting a guest via virt-manager I'm getting the below error.
>>
>> The same behaviour is seen with existing guests or newly created guests.
>>
>> Could anyone point me towards a solution, or debug course?
>>
>> Thanks...
>>
>>
>> Error starting domain: internal error: QEMU / QMP failed: Failed to open
>> module: /usr/lib/x86_64-linux-gnu/qemu/block-iscsi.so: undefined symbol:
>> aio_bh_schedule_oneshot
>> Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-curl.so:
>> undefined symbol: aio_bh_schedule_oneshot
>> Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-rbd.so:
>> undefined symbol: aio_bh_schedule_oneshot
>> Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/block-ssh.so:
>> undefined symbol: inet_connect_saddr
> 
> Please make sure your qemu-block-extra and qemu-system-x86 packages are
> up-to-date.  They should both have the same version number.

The up-to-date thing isn't a requiriment, you can use any version of
your choice if it suits your needs.

The problem here is the version MISMATCH - qemu-system-x86 package
is from one version, while qemu-block-extra is from another.

qemu-block-extra package contains less-often-used block modules,
and in order to work, should be of the same version as corresponding
qemu-system-* package. I especially didn't use strong versioned
depencency here, in order to keep ability to try other versions of
qemu-system if some problem is found.

However, it seems like when qemu tries to load "wrong-versioned"
modules, it fails to _start_, which should not really happen.
It should ignore the wrong modules and continue, _unless_ you
actually use one of the block drivers in this package (only
in that case it should fail to start telling it didn't find
the requested block device).

Please for now ensure qemu-system-* and qemu-block-extra are
of the same version. We'll see what can be done to avoid this
prob in the future.

Thanks!

/mjt