From: Alec Ten Harmsel <alec@alectenharmsel.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Anyone using kernel 4.1.8 in a virtualbox guest machine?
Date: Sun, 4 Oct 2015 20:59:01 -0400 [thread overview]
Message-ID: <20151005005901.GB6134@greenbeast> (raw)
In-Reply-To: <20151004174737.639750e0@a6>
On Sun, Oct 04, 2015 at 05:47:37PM -0700, walt wrote:
> (I'm asking this question only because I'm curious about the problem I'm
> about to describe. I've already worked around it.)
>
> I updated the kernel in my gentoo virtualbox guest machine to 4.1.8 and
> got a kernel panic after rebooting the guest. (The panic was in the
> guest machine, not the host machine. Has anyone noticed how ambiguous
> our English language is?)
>
> Anyway, I rebooted the guest machine with vmlinuz.old (3.18.21) and
> then updated the guest to vanilla-sources-4.2.3 with no problems.
>
> (I omit several hours of confused reconfiguring/recompiling/rebooting
> because you really don't want to hear about them.)
>
> So, what is different or strange about kernel 4.1.8? Anyone have any
> problems with it on real hardware, or in other virtual environments
> like qemu, vmware, xen, etc?
>
I am running 4.1.8 on all my machines without any problems. Without
seeing the stack trace and/or other output from the kernel panic, I
would have no idea how to figure out what the problem was. I am also not
a kernel wizard, so I probably wouldn't be much help anyways.
Alec
next prev parent reply other threads:[~2015-10-05 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 0:47 [gentoo-user] Anyone using kernel 4.1.8 in a virtualbox guest machine? walt
2015-10-05 0:59 ` Alec Ten Harmsel [this message]
2015-10-06 0:56 ` [gentoo-user] " walt
2015-10-06 12:13 ` [gentoo-user] Re: Anyone using kernel 4.1.8 in a virtualbox guest machine? [SOLVED] walt
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=20151005005901.GB6134@greenbeast \
--to=alec@alectenharmsel.com \
--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