From: virtiofs-bot@sinrega.org
To: virtio-fs@redhat.com
Subject: [Virtio-fs] [virtiofsd] Issue closed: Cannot copy files / crash on Windows 11 22H2, Server 2019, Server 2022
Date: Tue, 27 Sep 2022 16:09:33 +0000 (UTC) [thread overview]
Message-ID: <24382.122092712093001487@us-mta-402.us.mimecast.lan> (raw)
While trying to copy any file from the virtio-fs drive into the local disk, `virtiofs.exe` crashed with:
```
Faulting application name: virtiofs.exe, version: 0.0.0.0, time stamp: 0x62887e76
Faulting module name: virtiofs.exe, version: 0.0.0.0, time stamp: 0x62887e76
Exception code: 0xc0000005
Fault offset: 0x0000000000008f70
Faulting process id: 0x0x10CC
Faulting application start time: 0x0x1D8D1CAF5E62D04
Faulting application path: C:\Program Files\Virtio-Win\VioFS\virtiofs.exe
Faulting module path: C:\Program Files\Virtio-Win\VioFS\virtiofs.exe
Report Id: 6d921400-ca34-4501-b33e-6d9d8ab87909
Faulting package full name:
Faulting package-relative application ID:
```
I'm using:
1. the drivers bundled in https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.221-1/virtio-win-0.1.221.iso (only `viofs.sys` had a version string. and it is `100.91.104.22100`)
2. winfsp 1.11.22176
3. Windows 11 22H2 guest, Windows Server 2019 or 2022 guest.
4. Ubuntu 22.04 host with packages:
1. libvirt 8.0.0-1ubuntu7.1
2. qemu-system-x86 6.2+dfsg-2ubuntu6.3
5. the libvirt virtiofs configuration snippet:
```xml
<filesystem type="mount" accessmode="passthrough">
<driver type="virtiofs"/>
<binary path="/usr/lib/qemu/virtiofsd"/>
<source dir="/home/vagrant/Projects/windows-vagrant/example"/>
<target dir="9ee5aaf7cf944b385ee3e99881442aa"/>
<alias name="fs0"/>
<address type="pci" domain="0x0000" bus="0x07" slot="0x00" function="0x0"/>
</filesystem>
```
6. the libvirt shared memory configuration snippet:
```xml
<memoryBacking>
<source type="memfd"/>
<access mode="shared"/>
</memoryBacking>
```
BTW, It would be useful to include some kind of version information in the `virtiofs.exe` file as its currently reporting its version as `0.0.0.0`.
---
https://gitlab.com/virtio-fs/virtiofsd/-/issues/57
reply other threads:[~2022-09-27 16:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24382.122092712093001487@us-mta-402.us.mimecast.lan \
--to=virtiofs-bot@sinrega.org \
--cc=virtio-fs@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).