virtio-fs.lists.linux.dev archive mirror
 help / color / mirror / Atom feed

From: Ewen Chan <alpha754293@hotmail.com>
To: "virtio-fs@redhat.com" <virtio-fs@redhat.com>
Subject: [Virtio-fs] [virtio-fs] Windows 10 VirtioFS Service error - The service did not respond to the start or control request in a timely fashion
Date: Wed, 1 Mar 2023 12:05:10 +0000	[thread overview]
Message-ID: <SA1P221MB1018AA58757048B93CFB3437B5AD9@SA1P221MB1018.NAMP221.PROD.OUTLOOK.COM> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2851 bytes --]

To Whom It May Concern:

I am trying to use Virtiofs inside a Windows 10 VM under Proxmox 7.3-3.

Previously, I was able to do it, but now, for some reason, whenever I try to start the service, this is the error message that I get:

[cid:15c9698d-d741-416c-aa69-31d60be10227]

I tried a fresh install of Windows 10 Pro x64 and then installed the virtio Windows drivers (virtio-win-0.1.229.iso) this error is still popping up.

I have a script which daemonizes the virtiofsd daemon:

      # cat launch-virtio-daemon.sh
#!/usr/bin/bash


function launch() {

    nohup /usr/lib/kvm/virtiofsd --syslog --daemonize --socket-path=/var/run/shared-fs.sock -o source=/export/myfs/ -o cache=always &> /dev/null  &
    return 0
}

launch

And in my Proxmox VM, I have called the launch-virtio-daemon.sh via a Proxmox hookscript:

qm set 101 --hookscript local:snippets/virtiofs.pl

and this is what's in the virtiofs.pl file:

# cat /var/lib/vz/snippets/virtiofs.pl
#!/usr/bin/perl

# Exmple hook script for PVE guests (hookscript config option)
# You can set this via pct/qm with
# pct set <vmid> -hookscript <volume-id>
# qm set <vmid> -hookscript <volume-id>
# where <volume-id> has to be an executable file in the snippets folder
# of any storage with directories e.g.:
# qm set 100 -hookscript local:snippets/hookscript.pl

use strict;
use warnings;

print "GUEST HOOK: " . join(' ', @ARGV). "\n";

# First argument is the vmid

my $vmid = shift;

# Second argument is the phase

my $phase = shift;

if ($phase eq 'pre-start') {

    # First phase 'pre-start' will be executed before the guest
    # ist started. Exiting with a code != 0 will abort the start

    print "$vmid is starting, doing preparations.\n";

    system('/var/lib/vz/snippets/launch-virtio-daemon.sh');

    # print "preparations failed, aborting."
    # exit(1);

} elsif ($phase eq 'post-start') {

    # Second phase 'post-start' will be executed after the guest
    # successfully started.

    print "$vmid started successfully.\n";

} elsif ($phase eq 'pre-stop') {

    # Third phase 'pre-stop' will be executed before stopping the guest
    # via the API. Will not be executed if the guest is stopped from
    # within e.g., with a 'poweroff'

    print "$vmid will be stopped.\n";

} elsif ($phase eq 'post-stop') {

    # Last phase 'post-stop' will be executed after the guest stopped.
    # This should even be executed in case the guest crashes or stopped
    # unexpectedly.

    print "$vmid stopped. Doing cleanup.\n";

} else {
    die "got unknown phase '$phase'\n";
}

exit(0);


This was working before and now I don't really know nor understand why it isn't working anymore.

Your help would be greatly appreciated.

Thank you.

Sincerely,
Ewen Chan

[-- Attachment #1.2: Type: text/html, Size: 15345 bytes --]

[-- Attachment #2: Capture.PNG --]
[-- Type: image/png, Size: 6810 bytes --]

next             reply	other threads:[~2023-03-01 12:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 12:05 Ewen Chan [this message]
2023-03-03  2:08 ` [Virtio-fs] [virtio-fs] Windows 10 VirtioFS Service error - The service did not respond to the start or control request in a timely fashion Xiaoling Gao
2023-03-03  4:09   ` Ewen Chan
2023-03-03  7:24     ` Xiaoling Gao
2023-03-03 13:07       ` Ewen Chan

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=SA1P221MB1018AA58757048B93CFB3437B5AD9@SA1P221MB1018.NAMP221.PROD.OUTLOOK.COM \
    --to=alpha754293@hotmail.com \
    --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

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).