virtiofsd issue with fedora 35 and qemu-6.1.0

[rhyas]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID:

Expected behavior

Docker Desktop starts the VM.

Actual behavior

Docker Desktop fails to start the VM.

Information

I found this thread: docker/roadmap#39 and it relates to a bug with virtiofsd, and provides a workaround. The workaround is successful. Without removing the shared directories, the virtiofsd process core dumps in a perpetual loop.

Steps to reproduce the behavior

Get to the current Fedora 35 release.
Install KVM Pre-Requisites. (qemu-common-6.1.0-15.fc35.x86_64)
Install Docker Desktop 4.10.1 (82475)

[aiordache]

Hi @rhyas.
I have installed and run Docker Desktop 4.10.1 (82475) on a Fedora 35 VM with QEMU version 6.1.0 (qemu-6.1.0-5.fc35) and it seemed to run fine.

Would you mind uploading a diagnostics bundle to see if we can find something in the logs?
You can check this page for how to upload diagnostics from the terminal if it cannot be done from the UI.

[p1-0tr]

@rhyas - It looks like the workaround for qemu <-> virtiofsd protocol mismatch we've been shipping is no longer required. I've made a patch to no longer apply the workaround, and will aim to land it in the next release (end of this month). In the meantime here is a link to a dev build with the fix - https://desktop-stage.docker.com/linux/main/amd64/82844/docker-desktop-4.11.0-x86_64.rpm .

[rhyas]

I went with the latest Test build to work around the issue. I can try to make some time to revert and get some logs.

[p1-0tr]

Just following up to say that the fix will be released in 4.12 (end of this month).

[docker-robott]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

[docker-robot]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale