Github messages for voidlinux
 help / color / mirror / Atom feed
From: Calandracas606 <Calandracas606@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: WIP: New package: muvm-0.1.3
Date: Thu, 31 Oct 2024 18:17:47 +0100	[thread overview]
Message-ID: <20241031171747.3C65730D0B@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52736@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

New comment by Calandracas606 on void-packages repository

https://github.com/void-linux/void-packages/pull/52736#issuecomment-2450377687

Comment:
@dkwo could you please try testing this again? Make sure your user is in the kvm group.

eg: `muvm -- sh`

I get stuck on:

```
Error: Failed to set up user, bailing out

Caused by:
    0: Failed to read directory `/dev/dri`
    1: No such file or directory (os error 2)
```

I think that this is possibly because eudev doesn't setup /dev/dri in the vm, but I could be wrong.

When I patch out the check to open `/dev/dri`, i'm able to successfully launch sh in the vm

As aforementioned, it works on my install with systemd, although I'm not confident that its because of systemd that it works, its very possible that some other configuration difference between the systems is at play.


  parent reply	other threads:[~2024-10-31 17:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22  7:34 [PR PATCH] " Calandracas606
2024-10-22  7:38 ` [PR PATCH] [Updated] " Calandracas606
2024-10-24 13:44 ` dkwo
2024-10-27 12:41 ` Calandracas606
2024-10-27 23:51 ` dkwo
2024-10-28 13:41 ` dkwo
2024-10-28 13:45 ` dkwo
2024-10-31  1:47 ` [PR PATCH] [Updated] " Calandracas606
2024-10-31  1:51 ` Calandracas606
2024-10-31  2:07 ` [PR PATCH] [Updated] " Calandracas606
2024-10-31  2:21 ` Calandracas606
2024-10-31 15:52 ` Calandracas606
2024-10-31 15:58 ` Calandracas606
2024-10-31 16:02 ` Calandracas606
2024-10-31 16:03 ` [PR PATCH] [Updated] " Calandracas606
2024-10-31 16:24 ` Calandracas606
2024-10-31 16:44 ` [PR PATCH] [Updated] " Calandracas606
2024-10-31 16:55 ` Calandracas606
2024-10-31 16:58 ` Calandracas606
2024-10-31 17:12 ` Calandracas606
2024-10-31 17:17 ` Calandracas606
2024-10-31 17:17 ` Calandracas606 [this message]
2024-10-31 17:41 ` [PR PATCH] [Updated] " Calandracas606
2024-10-31 17:43 ` Calandracas606
2024-11-02 20:21 ` dkwo
2025-02-01  2:00 ` github-actions
2025-02-06 23:26 ` Calandracas606
2025-02-17 22:03 ` [PR PATCH] [Updated] " Calandracas606
2025-02-17 22:21 ` Calandracas606
2025-05-19  2:13 ` github-actions
2025-06-02  2:14 ` [PR PATCH] [Closed]: " github-actions
2025-06-25 17:04 ` dkwo

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=20241031171747.3C65730D0B@inbox.vuxu.org \
    --to=calandracas606@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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 NNTP newsgroup(s).