From: AngryPhantom <AngryPhantom@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: virtualbox 6.1.34 is broken with Windows guests (please downgrade)
Date: Tue, 06 Sep 2022 12:18:38 +0200 [thread overview]
Message-ID: <20220906101838.3Sx1LN4ld0Yz_8awbexo6u4eexQqUSfzFWx1luR19qg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38116@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 532 bytes --]
New comment by AngryPhantom on void-packages repository
https://github.com/void-linux/void-packages/issues/38116#issuecomment-1237955145
Comment:
The bug is still here with version 6.1.36. It is even NOT fixed in 6.1.38. And it's not the Void's fault.
The problem is that no one can confirm this since the virtual machine **had to be created several versions ago**. And after that, upon upgrading VirtualBox itself, the issue appears. There is **no problem** if you create a **new virtual machine** with a **new version of VB**.
prev parent reply other threads:[~2022-09-06 10:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 21:11 [ISSUE] " AngryPhantom
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 [this message]
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=20220906101838.3Sx1LN4ld0Yz_8awbexo6u4eexQqUSfzFWx1luR19qg@z \
--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).