Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • aports aports
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 736
    • Issues 736
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 358
    • Merge requests 358
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpine
  • aportsaports
  • Issues
  • #11602

Closed
Open
Created Jun 01, 2020 by Fernando Casas Schössow@casasfernando

Libvirt service (libvirtd) not starting correctly since upgrading Alpine from 3.11.6 to 3.12.0

Hi there,

Last weekend I updated two KVM hosts (x86_64) running Alpine 3.11.6 to 3.12.0. Since upgrading libvirt service (libvirtd) is not starting correctly. Two processes of libvirtd are spawned and interaction with libvirt (ie: virsh or remotely over TLS) doesn't work. If you run a virsh command, the command will just hang for a long time until I press ctrl+c to stop it. If I manually kill one of the libvirtd processes, libvirt seems to start working again. I can execute virsh commands without any issues, same with remote access.

I found this other issue that may be related but I'm not really sure: 11361

The problem is not only happening at startup, I'm still investigating but even while libvirt is already running, after sometime a second process is spawned (don't know why yet) and libvirt stops working again. I need to connect to the KVM host, kill the new libvirtd process that was spawned, and operation resumes as usual.

Any ideas?

Thanks.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking