0

I virtualized a Windows server with libvirtd that uses an additional image on a smb share.

The host system was Fedora Server 30 and everything worked fine. Now I have upgraded the host to Fedora Server 31 and I get the following error:

# virsh start <domain-name>
error: Failed to start domain <domain-name>
error: internal error: process exited while connecting to monitor: 2020-01-29T07:35:45.682701Z qemu-system-x86_64: -drive file=<image file on smb share>,format=qcow2,if=none,id=drive-virtio-disk1: Failed to get "write" lock
Is another process using the image [<image file on smb share>]?

With lslocks or lsof the image file is not mentioned - so no other process is using the file.

The share is mounted correctly:

# mount -t cifs
//<server>/<share> on <mount point> type cifs (rw,noexec,relatime,vers=2.0,cache=strict,username=virtual,uid=107,forceuid,gid=984,forcegid,addr=<ip>,file_mode=0755,dir_mode=0775,soft,nounix,serverino,mapposix,rsize=65536,wsize=65536,bsize=1048576,echo_interval=60,actimeo=1)

So what changed from Fedora Server 30 to 31?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.