From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] virtualbox woes
Date: Mon, 01 Aug 2022 11:45:11 +0200 [thread overview]
Message-ID: <2643175.mvXUDI8C0e@poseidon> (raw)
In-Reply-To: <BY5PR16MB3473240F4F497D6E84668D38AA9A9@BY5PR16MB3473.namprd16.prod.outlook.com>
On Monday, 1 August 2022 02:46:32 CEST Matthew Sacks wrote:
> The vbox log and screenshot are all I have to go off. Next time I?ll provide
> that upfront. New to these parts (gentoo lists).
>
> It crashes on boot actually to answer your question.
Please stop top-posting. It makes these emails difficult to read.
Did you enable hardware virtualisation (VT) in the BIOS?
What are the VM-settings you use for the VM?
Does your host have sufficient CPU-cores and memory for the Host + the VM?
--
Joost
>
> Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
>
> From: Jack<mailto:ostroffjh@users.sourceforge.net>
> Sent: Sunday, July 31, 2022 7:48 AM
> To: gentoo-user@lists.gentoo.org<mailto:gentoo-user@lists.gentoo.org>
> Subject: Re: [gentoo-user] virtualbox woes
>
> On 7/31/22 09:27, Matthew Sacks wrote:
> I cant get gentoo to run on virtualbox, segfaults or core dumps or
> something.
>
> Please learn how to ask for help. You have provided next to no useful
> information. From the other thread, you provided a log, and the fact that
> you are trying to run a Gentoo guest on a Windows (which version?) host.
> Which version of VB? The latter might matter, as there have been some
> reports of VBox instability, although I believe those are on Linux hosts,
> not guests.
>
> In the other thread, you mention that the crash happens on shutting down.
> How did you shut down? Have you tried other ways? Have you checked the
> virtualbox forums for similar reports?
>
> Jack
prev parent reply other threads:[~2022-08-01 9:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 13:27 [gentoo-user] virtualbox woes Matthew Sacks
2022-07-31 13:30 ` Mark Knecht
2022-07-31 13:40 ` Matthew Sacks
2022-07-31 14:03 ` Mark Knecht
2022-07-31 14:08 ` Matthew Sacks
2022-07-31 14:46 ` Julien Roy
2022-07-31 14:46 ` Mark Knecht
2022-07-31 14:45 ` Jack
2022-07-31 17:58 ` Jack
2022-07-31 21:14 ` Mark Knecht
2022-08-01 0:46 ` Matthew Sacks
2022-08-01 8:17 ` Michael
2022-08-02 1:02 ` Matthew Sacks
2022-08-01 9:45 ` J. Roeleveld [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=2643175.mvXUDI8C0e@poseidon \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.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