[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#827044: marked as done (linux-image-4.5.0-1-686-pae: Kernel 4.5.0-1 hangs at boot time on VirtualBox with no hardware virtualization (VT-x))

Your message dated Mon, 10 May 2021 08:19:27 +0200
with message-id <20210510061927.GA25749@lorien.valinor.li>
and subject line Re: Bug#827044: linux-image-4.5.0-1-686-pae: Kernel 4.5.0-1 hangs at boot time on VirtualBox with no hardware virtualization (VT-x)
has caused the Debian Bug report #827044,
regarding linux-image-4.5.0-1-686-pae: Kernel 4.5.0-1 hangs at boot time on VirtualBox with no hardware virtualization (VT-x)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
827044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827044
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-4.5.0-1-686-pae
Severity: normal

Running current testing on virtualbox (windows host and testing as 
client), kernel fails to load and hangs at:

[...] tsc: refined tsc clocksource calibration: 1552.919 MHz
[...] clocksource: tsc: mask: 0xffffffffffffffff max cycles 0x1662692e4fd, max_idle_ns: 440795215416 ns

This only happens when no hardware virtualization is available on host 
machine or it is disabled on purpose on virtualbox machine settings.

Older kernels (e.g., wheezy) just load fine despite the hardware 
virtualization setting in available or not for VBox.

--- End Message ---
--- Begin Message --- 
Hi,

On Mon, May 10, 2021 at 08:14:19AM +0200, Camaleón wrote:
> El 2021-05-09 a las 21:53 +0200, Salvatore Bonaccorso escribió:
> 
> (...)
> 
> > > Is not that just non-pae kernel boots but the last bootable kernel is 
> > > 4.9.0-3, I mean, recent non-pae kernels (4.11, 4.12, 4.13) are unable to 
> > > boot (bad eip value).
> > > 
> > > See attached images for full kernel message.
> > 
> > Is this still reproducible with a current kernel?
> 
> I'm afraid I cannot longer test it because I removed VirtualBox and 
> also virtual machines. This was an old bug report.
> So I guess you can safely close the bug as no other people reported the 
> issue.
> Thanks!

Thanks for reporting back, I guess so and agree, let's close the
issue.

Regards,
Salvatore

--- End Message ---
Reply to: