Date: Wed, 03 Oct 2012 21:17:35 +0200 From: Marek Salwerowicz <marek_sal@wp.pl> To: lev@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection Message-ID: <506C8F4F.3040703@wp.pl> In-Reply-To: <80840563.20120920002200@serebryakov.spb.ru> References: <80840563.20120920002200@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
W dniu 2012-09-19 22:22, Lev Serebryakov pisze: > Hello, Freebsd-current. > > I've upgraded my FreeBSD-CURRENT Virtual machine, which I use to > build router's NanoBSD image, to today's morning (MSK time, GMT+4) > revision. Unfortunately, I cannot provide exact version, as sources > are in this unbootable VM too :) > > Kernel is GENERIC. > > VBox configuration is rather stander: 2 CPUs, ICH9, 2GB of RAM. > Host is Windows 7/64bit. > > Booting hangs after (new?) line: > > atrtc0: <AT realtime clock> port 0x70-0x71 on acpi0 > Hi, still the same in my environment, running FreeBSD 9.1 under ESXi5.1 host Do you have any solution? Regards, -- Marek Salwerowicz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?506C8F4F.3040703>