virtio-win / kvm-guest-drivers-windows

Windows paravirtualized drivers for QEMU\KVM
https://www.linux-kvm.org/page/WindowsGuestDrivers
BSD 3-Clause "New" or "Revised" License
1.94k stars 379 forks source link

VirtioFs MS Office saving/locking problem #781

Closed exteon closed 10 months ago

exteon commented 2 years ago

Describe the bug When saving a macro-enabled spreadsheet in Excel 2019, I get "The document was saved successfully, but Excel cannot re-open it because of a sharing violation". This doesn't happen on block device mounts.

Host:

VM:

viktor-prutyanov commented 2 years ago

Hi @exteon

0.1.215 is too old, could you please try last version?

exteon commented 2 years ago

I would, except .217 doesn't install on win 11. It's a known issue but I'm on mobile and can't look it up just now.

exteon commented 2 years ago

I can now confirm the problem persists with .217

Daniel-Trevitz commented 2 years ago

I could not duplicate this on my win10 install with office 2016. :(

@exteon,

exteon commented 2 years ago

I tried to do some more testing today; would have helped greatly if I could create multiple VirtioFs mounts (I was trying to see how the problem reproduces depending on different mount source media/fs). But even if I added more virtiofs mounts, only one is created as Z:... is this a know problem? Am I doing something wrong?

YanVugenfirer commented 2 years ago

@exteon Yes, multi-mount support is a known issue.

https://bugzilla.redhat.com/show_bug.cgi?id=2042247

exteon commented 2 years ago

Ok, I'll try one at a time then and see how it goes...

xiagao commented 1 year ago

I also can't reproduce this issue on Win11 guest installed with MSFT office 2019. No matter coping the xlsm file from block device to virtiofs drive nor saving the xlsm file in virtiofs drive, no error pop up.

Btw,I'm using virtiofsd rust version which is a replacement of qemu-virtiofsd,here are some description from virtiofsd project. +There is a new Rust implementation of virtiofs at +https://gitlab.com/virtio-fs/virtiofsd; +since this is now marked stable, new development should be done on that +rather than the existing C version in the QEMU tree. +The C version will still accept fixes and patches that +are already in development for the moment.

Thanks, Xiaoling