From: imiric <imiric@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: VirtualBox 6.1.36 does not start VMs
Date: Tue, 31 Jan 2023 15:14:07 +0100 [thread overview]
Message-ID: <20230131141407.-Wew6cOIyxxfgUkTNLmezU4s8tAMWF6Zrq45WUfcfoY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38967@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
New comment by imiric on void-packages repository
https://github.com/void-linux/void-packages/issues/38967#issuecomment-1410432803
Comment:
Please reopen this issue, as it still happens after upgrading to 7.0.4. None of my VMs start, with the same segfault error mentioned above. I'm on Linux 6.1.7.
@gtryujb Just because it suddenly works for you, it doesn't mean that it works for others, as you can see from this thread. Also, sharing what you did to fix the issue would be helpful...
Downgrading to VirtualBox 6.1.36 now shows a driver version mismatch, even though DKMS seems to have built the module when downgrading. Running `xbps-reconfigure -f virtualbox-ose-dkms` does nothing.
There's no `/sbin/vboxconfig` binary, nor anywhere else on my system. :sweat:
Please advise. This is a major issue that shouldn't go unnoticed.
next prev parent reply other threads:[~2023-01-31 14:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 12:25 [ISSUE] " gtryujb
2022-08-29 13:18 ` Duncaen
2022-08-29 13:59 ` gtryujb
2022-08-31 9:51 ` rapha8l
2022-09-11 9:22 ` egorenar
2022-09-11 9:23 ` egorenar
2022-10-16 15:25 ` nezos
2022-10-16 16:52 ` gtryujb
2022-10-17 7:43 ` rapha8l
2023-01-11 23:33 ` ar-jan
2023-01-11 23:33 ` ar-jan
2023-01-16 15:07 ` gtryujb
2023-01-16 15:07 ` [ISSUE] [CLOSED] " gtryujb
2023-01-31 14:14 ` imiric [this message]
2023-02-01 11:41 ` ar-jan
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=20230131141407.-Wew6cOIyxxfgUkTNLmezU4s8tAMWF6Zrq45WUfcfoY@z \
--to=imiric@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).