From: gtryujb <gtryujb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] VirtualBox 6.1.36 does not start VMs
Date: Mon, 29 Aug 2022 14:25:24 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38967@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
New issue by gtryujb on void-packages repository
https://github.com/void-linux/void-packages/issues/38967
Description:
### Is this a new report?
Yes
### System Info
Void 5.18.19_1 x86_64 AuthenticAMD uptodate rrFFFFFFFF
### Package(s) Affected
virtualbox-ose-6.1.36_1, virtualbox-ose-dkms-6.1.36_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
VMs start normally.
### Actual behaviour
The VM window briefly appears and disappears, followed by the error window:
```
The VM session was aborted.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
```
This happens for Linux, Windows 7, and Window 10 VMs.
Reverting to 6.1.34 fixes it.
### Steps to reproduce
1. Start VirtualBox
2. Start an existing VM
next reply other threads:[~2022-08-29 12:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 12:25 gtryujb [this message]
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
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38967@inbox.vuxu.org \
--to=gtryujb@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).