From: AngryPhantom <AngryPhantom@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] virtualbox 6.1.34 is broken with Windows guests (please downgrade)
Date: Sun, 17 Jul 2022 23:11:25 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38116@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
New issue by AngryPhantom on void-packages repository
https://github.com/void-linux/void-packages/issues/38116
Description:
### Is this a new report?
Yes
### System Info
Void 5.10.130_1 x86_64 AuthenticAMD uptodate hold rDFFFFF
### Package(s) Affected
virtualbox-ose-6.1.34_1, virtualbox-ose-dkms-6.1.34_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://www.virtualbox.org/ticket/20904
Plus a lot of complaints on other forums and resources, like Debian forums, Stackoverflow etc.
### Expected behaviour
Windows guest should boot normally.
### Actual behaviour
I'm getting an error message:
Error "Failed to load R0 module /usr/lib/virtualbox/VBoxDDR0.r0: Unable to locate imported symbol 'memset' for module 'VBoxDDR0.r0' (VERR_SYMBOL_NOT_FOUND)."
### Steps to reproduce
1. Have some Windows (mine is XP) already installed and running fine on version 6.1.32
2. Upgrade to 6.1.34
3. Boot Windows guest
4. Crash with the above error message
next reply other threads:[~2022-07-17 21:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 21:11 AngryPhantom [this message]
2022-07-18 0:53 ` sgn
2022-07-18 0:57 ` sgn
2022-07-18 1:04 ` slender100
2022-07-18 1:17 ` sgn
2022-07-18 8:18 ` AngryPhantom
2022-07-18 8:19 ` AngryPhantom
2022-07-18 11:32 ` dmarto
2022-07-18 12:57 ` sgn
2022-07-18 13:40 ` dmarto
2022-07-18 15:45 ` AngryPhantom
2022-07-19 0:21 ` sgn
2022-07-20 16:40 ` [ISSUE] [CLOSED] " AngryPhantom
2022-07-20 16:40 ` AngryPhantom
2022-09-06 8:27 ` alekspickle
2022-09-06 8:28 ` alekspickle
2022-09-06 8:29 ` alekspickle
2022-09-06 10:18 ` AngryPhantom
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38116@inbox.vuxu.org \
--to=angryphantom@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).