Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

the installer ISO or the VM image, both in VirtualBox. It should be there right after the panic message. No idea how to take the virtual screen snapshot under VB. Also it might be easier if you configure serial console and catch its output outside VB, but again I have no idea how to do that. You can

VirtualBox: screenshots (was: 14.0-CURRENT panic on boot, i386 VirtualBox client)

On 04/01/2023 10:24, Konstantin Belousov wrote: … No idea how to take the virtual screen snapshot under VB. … For me, it's the Control key to the right + E OpenPGP_signature Description: OpenPGP digital signature

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

ller ISO or the VM image, both in VirtualBox. It should be there right after the panic message. No idea how to take the virtual screen snapshot under VB. Also it might be easier if you configure serial console and catch its output outside VB, but again I have no idea how to do that.

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

On 30/12/2022 01:54, Konstantin Belousov wrote: The backtrace is needed to make a further analysis. Any suggestions for getting a backtrace? I get the panic booting either the installer ISO or the VM image, both in VirtualBox. A+ Paul

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

o enable serial port for the console of the > > guest and capture the output. But I don't know if the default ISO uses > > that and how hard it is to configure VirtualBox to do that properly. > > Hi > > I have used my phone before, and I tried that. > > The last mess

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

that and how hard it is to configure VirtualBox to do that properly. Hi I have used my phone before, and I tried that. The last message with verbose turned on is isa_probe_children: probing PnP devices smist: found supported isa bridge Intel PIX4 ISA bridge panic: td 0x1d94840 stack 0x2424ee8

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

On 12/28/22 17:45, Paul Floyd wrote: Hi For quite a few weeks I've been unable to boot 14.0-CURRENT i386 in a VirtualBox VM. I've tried both booting from iso image and the vmdk image. I get a kernel panic The host is running 13.1-RELEASE-p3 amd64 No problems with 14.0-CURRENT amd64 guests

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

On 28-12-22 18:05, Graham Perrin wrote: If the guest has more than CPU, try reducing to one. A step further: try booting the guest in safe mode. Neither of those changed anything (I was using 2 CPUs) A+ Paul

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

On 28/12/2022 16:45, Paul Floyd wrote: … I haven't been able to see the last message before the panic as it scrolls past too quickly. Any suggestions for a working either how to get more info or what vbox settings to use? If the guest has more than CPU, try reducing to one. A step

14.0-CURRENT panic on boot, i386 VirtualBox client

Hi For quite a few weeks I've been unable to boot 14.0-CURRENT i386 in a VirtualBox VM. I've tried both booting from iso image and the vmdk image. I get a kernel panic The host is running 13.1-RELEASE-p3 amd64 No problems with 14.0-CURRENT amd64 guests. I haven't been able to see the last

Re: FreeBSD-provided .vhd with VirtualBox: gpart I/O errors after resizing the virtual hard disk

On 17/01/2021 18:22, Graham Perrin wrote: VirtualBox 5.2.44 r139111 on FreeBSD-CURRENT. 01. Add FreeBSD-12.2-RELEASE-amd64.vhd to a machine 02. use Virtual Disk Manager to resize it to 2.0 TB … Long story short: it seems that the problem occurs only after resizing to (the maximum) 2.0 TB

Re: VirtualBox 6.1.18⋯, Windows (was: 13.0 RC4 might be delayed)

. They make the almost humorous claim that only Windows and MacOS are adequately secure. At this point I have no idea if the issue is with VirtualBx or FreeBSD, but, after seeing more details of your problem, I doubt mine is related. I really suspect it's VirtualBox, so I will drop out

12.2-RELEASE-p4 and 13.0-RC3 versus VirtualBox

On 26/03/2021 20:36, Graham Perrin wrote: On 26/03/2021 20:01, Graham Perrin wrote: If I'm not mistaken: * 13.0-RC3 seems to be troublesome, as a guest machine, with emulators/virtualbox-ose 6.1.18 as the host … On closer inspection: the problem is not limited 13.0-RC3. If I save

VirtualBox 6.1.18⋯, Windows (was: 13.0 RC4 might be delayed)

Fell back to legacy (v5) and will try again shortly to see if it's any better. Windows 7 guest or host? For me, Windows 10 20H2 guest is rock solid. % pkg info -x virtualbox virtualbox-ose-6.1.18 virtualbox-ose-kmod-6.1.18_1 % freebsd-version -kru 14.0-CURRENT 14.0-CURRENT 14.0-CURRENT % uname -

12.2-RELEASE-p4 versus VirtualBox (was: 13.0 RC4 might be delayed)

On 26/03/2021 20:01, Graham Perrin wrote: If I'm not mistaken: * 13.0-RC3 seems to be troublesome, as a guest machine, with emulators/virtualbox-ose 6.1.18 as the host * no such trouble with 12.0-RELEASE-p5 as a guest. On closer inspection: the problem is not limited 13.0-RC3. If I save

Re: FreeBSD-provided .vhd with VirtualBox: gpart I/O errors after resizing the virtual hard disk

Graham Perrin grahamperrin at gmail.com wrote on Mon Jan 25 22:08:53 UTC 2021 : . . . omitted material, including steps 01..13 . . . Your steps 01..13 make no mention of involving growfs as indicated in "man 8 growfs". I'd guess that the growfs step would be after step 8 (recover) and before 10

Re: problem building virtualbox-ose-kmod

On 26/01/21 13:29, Dima Panov wrote: Moin! Stefan, please add check for __FreeBSD_version and fill PR or commit it directly with ports-secteam approval. There's a bug report for this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252675 And another one which is marked as a duplicate

Re: problem building virtualbox-ose-kmod

o:s...@freebsd.org)> wrote: > Am 26.01.21 um 07:34 schrieb monochrome: > > having this issue building virtualbox-ose-kmod, its been like this for a > > while but I deinstalled and forgot, for quite a while now, maybe over a > > month. now that I've moved from 13-current to stab

Re: problem building virtualbox-ose-kmod

Am 26.01.21 um 07:34 schrieb monochrome: having this issue building virtualbox-ose-kmod, its been like this for a while but I deinstalled and forgot, for quite a while now, maybe over a month. now that I've moved from 13-current to stable/13 I thought I would try to put it back, but it still

Re: problem building virtualbox-ose-kmod

On 1/26/21 9:13 AM, Mark Millard via freebsd-current wrote: monochrome monochrome at twcny.rr.com wrote on Tue Jan 26 06:34:23 UTC 2021 : . . . for quite a while now, maybe over a month . . . --- memobj-r0drv-freebsd.o --- /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-5.2.44/out

Re: problem building virtualbox-ose-kmod

monochrome monochrome at twcny.rr.com wrote on Tue Jan 26 06:34:23 UTC 2021 : > . . . for quite a while now, maybe over a month . . . > --- memobj-r0drv-freebsd.o --- > /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-5.2.44/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freeb

problem building virtualbox-ose-kmod

having this issue building virtualbox-ose-kmod, its been like this for a while but I deinstalled and forgot, for quite a while now, maybe over a month. now that I've moved from 13-current to stable/13 I thought I would try to put it back, but it still wont build. I haven't seen anyone else

Re: FreeBSD-provided .vhd with VirtualBox: gpart I/O errors after resizing the virtual hard disk

On 17/01/2021 18:22, Graham Perrin wrote: VirtualBox 5.2.44 r139111 on FreeBSD-CURRENT. 01. Add FreeBSD-12.2-RELEASE-amd64.vhd to a machine 02. use Virtual Disk Manager to resize it to 2.0 TB 03. apply, close 04. boot single user 05. gpart show /dev/ada0 07. observe reported corruption 08

FreeBSD-provided .vhd with VirtualBox: gpart I/O errors after resizing the virtual hard disk

VirtualBox 5.2.44 r139111 on FreeBSD-CURRENT. 01. Add FreeBSD-12.2-RELEASE-amd64.vhd to a machine 02. use Virtual Disk Manager to resize it to 2.0 TB 03. apply, close 04. boot single user 05. gpart show /dev/ada0 07. observe reported corruption 08. gpart recover /dev/ada0 09. I/O error <ht

Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

On 20/12/2020 00:31, Graham Perrin wrote: … With the boot maintenance manager of VirtualBox, I <https://imgur.com/BTsj4zS> navigated to loader.efi, added it as a boot option (I lazily named it 'loader.efi') then set it as primary <https://imgur.com/FYnHynr> after which: * n

Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

> On 19. Dec 2020, at 23:21, Graham Perrin wrote: > > With VirtualBox on an r368589 host I installed the latest (17th December) > snapshot of 13.0-CURRENT in a guest machine. I set the guest to EFI before > installation, and chose GPT (UEFI) during installation. > >

Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

On 19/12/2020 23:20, Warner Losh wrote: On Sat, Dec 19, 2020 at 2:21 PM Graham Perrin <mailto:grahamper...@gmail.com>> wrote: With VirtualBox on an r368589 host I installed the latest (17th December) snapshot of 13.0-CURRENT in a guest machine. I set the guest to E

Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

On Sat, Dec 19, 2020 at 2:21 PM Graham Perrin wrote: > With VirtualBox on an r368589 host I installed the latest (17th > December) snapshot of 13.0-CURRENT in a guest machine. I set the guest > to EFI before installation, and chose GPT (UEFI) during installation. > > After instal

FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

With VirtualBox on an r368589 host I installed the latest (17th December) snapshot of 13.0-CURRENT in a guest machine. I set the guest to EFI before installation, and chose GPT (UEFI) during installation. After installing KDE Plasma etc., the guest worked for a short while but then failed

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

On 6/22/2020 6:18 PM, Warner Losh wrote: On Mon, Jun 22, 2020 at 6:18 PM Rebecca Cran > wrote: On 6/22/2020 10:12 AM, Warner Losh wrote: > I believe so. However, I've not dived deeply enough into this problem to > understand if it is a bug in our

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

On Mon, Jun 22, 2020 at 6:18 PM Rebecca Cran wrote: > On 6/22/2020 10:12 AM, Warner Losh wrote: > > I believe so. However, I've not dived deeply enough into this problem to > > understand if it is a bug in our code or theirs.freebsd.org" > > > As I've said before, at least under bhyve it's a bug

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

On 6/22/2020 10:12 AM, Warner Losh wrote: I believe so. However, I've not dived deeply enough into this problem to understand if it is a bug in our code or theirs.freebsd.org" As I've said before, at least under bhyve it's a bug in the UEFI firmware that we currently use. -- Rebecca Cran

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

From: Warner Losh Subject: Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot Date: Mon, 22 Jun 2020 10:12:47 -0600 > I believe so. However, I've not dived deeply enough into this problem to > understand if it is a bug in our code or theirs. I got it. Thank you for

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

On Mon, Jun 22, 2020 at 9:40 AM Yasuhiro KIMURA wrote: > From: Warner Losh > Subject: Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot > Date: Mon, 22 Jun 2020 08:57:24 -0600 > > > Does setting the tunable hw.efi.poweroff=0 help you? > > I add

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

From: Warner Losh Subject: Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot Date: Mon, 22 Jun 2020 08:57:24 -0600 > Does setting the tunable hw.efi.poweroff=0 help you? I add it to /boot/loader.conf and then `shutdown -p now` successfully powers off system. Does existe

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

> On 22. Jun 2020, at 16:57, Warner Losh wrote: > > On Mon, Jun 22, 2020 at 4:14 AM Yasuhiro KIMURA wrote: > >> From: Yasuhiro KIMURA >> Subject: Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot >> Date: Mon, 22 Jun 2020 16:45:23 +0900 (JST) &g

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

On Mon, Jun 22, 2020 at 4:14 AM Yasuhiro KIMURA wrote: > From: Yasuhiro KIMURA > Subject: Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot > Date: Mon, 22 Jun 2020 16:45:23 +0900 (JST) > > > I tried bisect and found this problem happens with r342108 and

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

From: Yasuhiro KIMURA Subject: Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot Date: Mon, 22 Jun 2020 16:45:23 +0900 (JST) > I tried bisect and found this problem happens with r342108 and > after. Commit message of r342108 says as following. > > yasu@rolling-vm-f

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

From: Yasuhiro KIMURA Subject: `shutdown -p now` fails to power off with VirtualBox UEFI boot Date: Fri, 19 Jun 2020 05:23:48 +0900 (JST) > I have VirtualBox VM running 13-CURRENT. In order to switch from > legacy BIOS to UEFI I reinstalled OS by using > FreeBSD-13.0-CURRENT-amd64

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

Olivier Cochard-Labbé wrote: On Thu, Jun 18, 2020 at 10:26 PM Yasuhiro KIMURA wrote: I have VirtualBox VM running 13-CURRENT. In order to switch from legacy BIOS to UEFI I reinstalled OS by using FreeBSD-13.0-CURRENT-amd64-20200611-r362037-disc1.iso. After that `shutdow -p now` (or select

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

On 6/21/20 12:37 AM, Olivier Cochard-Labbé wrote: Same problem using FreeBSD current UEFI guests with bhyve, so it should happen in any kind of hypervisor. It is an old regression (in the sense of -current, so older than 6 months). My idea was to generate very light UEFI VM images (because the

Re: `shutdown -p now` fails to power off with VirtualBox UEFI boot

On Thu, Jun 18, 2020 at 10:26 PM Yasuhiro KIMURA wrote: > I have VirtualBox VM running 13-CURRENT. In order to switch from > legacy BIOS to UEFI I reinstalled OS by using > FreeBSD-13.0-CURRENT-amd64-20200611-r362037-disc1.iso. After that > `shutdow -p now` (or select 'ACPI shutdown

`shutdown -p now` fails to power off with VirtualBox UEFI boot

I have VirtualBox VM running 13-CURRENT. In order to switch from legacy BIOS to UEFI I reinstalled OS by using FreeBSD-13.0-CURRENT-amd64-20200611-r362037-disc1.iso. After that `shutdow -p now` (or select 'ACPI shutdown' in VM menu) fails to power off. Shutdown itself completes successfully

Re: emulators/virtualbox-ose 5.2.34_4 will not start with r361769

On 08/06/2020 15:24, Graham Perrin wrote: grahamperrin@momh167-gjp4-8570p:~ % virtualbox VirtualBox: Error -610 in supR3HardenedMainInitRuntime! VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed: /usr/local/lib/libcurl.so.4: Undefined symbol "SSLv3_client_metho

emulators/virtualbox-ose 5.2.34_4 will not start with r361769

grahamperrin@momh167-gjp4-8570p:~ % virtualbox VirtualBox: Error -610 in supR3HardenedMainInitRuntime! VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed: /usr/local/lib/libcurl.so.4: Undefined symbol "SSLv3_client_method@OPENSSL_1_1_0" VirtualBox: Tip! It m

VirtualBox segmentation fault, 5.2.34_2 on FreeBSD-CURRENT r359628

estigating it, then we'll see if they're related or requires yet another PR. Re: <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244847#c13> and the landing described at comment 15 Now with FreeBSD-CURRENT r359628 I (re)installed virtualbox-ose 5.2.34_2. Still no go: root@momh167-gjp4-8570

VirtualBox segmentation fault, 5.2.34_1 on FreeBSD-CURRENT r359249

gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG grahamperrin@momh167-gjp4-8570p:~ % virtualbox Segmentation fault grahamperrin@momh167-gjp4-8570p:~ % pkg query '%o %v %R' virtualbox-ose virtualbox-ose-kmod emulators/virtualbox-ose 5.2.34_1 poudriere emulators/virtualbox-ose-kmod 5.2.34

Re: VirtualBox segmentation fault, FreeBSD-CURRENT r359068

On Thu, Mar 19, 2020 at 12:11 PM Graham Perrin wrote: > > Is this maybe related to > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244847 or should I > make a separate bug report? > Please throw a tentative "Me too" on that PR; I'm investigating it, then we'll see if they're related or

Re: Panic with latest CURRENT amd64 as Virtualbox guest

kernel panic also with Freebsd currrent on virtualbox on a mac. > > > > My latetst build is 356985 > > > > > > > > Op wo 22 jan. 2020 14:14 schreef Rares Aioanei : > >> > >> I updated my system today, by issuing "svn up; mak

Re: Panic with latest CURRENT amd64 as Virtualbox guest

My bad, here's the link : https://imgur.com/45He1iy On Wed, Jan 22, 2020 at 8:04 PM Johan Hendriks wrote: > > These is no file attached. I think the mailing list stripped it off. > But i had an kernel panic also with Freebsd currrent on virtualbox on a mac. > > My latetst

Re: Panic with latest CURRENT amd64 as Virtualbox guest

These is no file attached. I think the mailing list stripped it off. But i had an kernel panic also with Freebsd currrent on virtualbox on a mac. My latetst build is 356985 Op wo 22 jan. 2020 14:14 schreef Rares Aioanei : > I updated my system today, by issuing "svn up; make buildowr

Panic with latest CURRENT amd64 as Virtualbox guest

I updated my system today, by issuing "svn up; make buildowrld; make kernel; reboot" and I got the output as seen in the attached file. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To

FreeBSD CURRENT buildworld in virtualbox guest crashes FreeBSD host

Please forgive the crosspost, I don't know where the problem actually belongs. For the last several months I've had a problem where doing a buildworld on FreeBSD CURRENT running as a virtualbox guest is crashing a the FreeBSD current host. This doesn't always happen, but there is a pattern

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On 19 Oct, Matthew D. Fuller wrote: > On Fri, Oct 19, 2018 at 03:47:40PM -0700 I heard the voice of > Don Lewis, and lo! it spake thus: >> >> The first is that when I attempt to start a Virtualbox VM, the >> system panics. > > Perhaps https://bugs.freebsd.org/b

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On Fri, Oct 19, 2018 at 03:47:40PM -0700 I heard the voice of Don Lewis, and lo! it spake thus: > > The first is that when I attempt to start a Virtualbox VM, the > system panics. Perhaps https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230460 -- Matthew Fuller (MF4839) | full

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On 19 Oct, Don Lewis wrote: > On 20 Oct, Graham Perrin wrote: >> On 19/10/2018 23:47, Don Lewis wrote: >> >>> … when I attempt to start a Virtualbox VM, the system panics. … (guest) >>> Windows 7 with >> networking configured as > NAT and the underly

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On 20 Oct, Graham Perrin wrote: > On 19/10/2018 23:47, Don Lewis wrote: > >> … when I attempt to start a Virtualbox VM, the system panics. … (guest) >> Windows 7 with > networking configured as > NAT and the underlying adapter being Intel PRO/1000 > MT Desktop (82540EM

Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

On 19/10/2018 23:47, Don Lewis wrote: > … when I attempt to start a Virtualbox VM, the system panics. … (guest) > Windows 7 with networking configured as > NAT and the underlying adapter being Intel PRO/1000 MT Desktop (82540EM). … No panic here. 32-bit Windows 7 guest with the sam

virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432

It looks like there are a couple of problems here. The first is that when I attempt to start a Virtualbox VM, the system panics. The DDB backtrace seems to indicate that the panic is occuring inside the ng_ether module, which was being called due to a virtualbox doing an ioctl call. The VM

Re: Fatal trap 9 when rebooting after installkernel on VirtualBox VM

From: Yasuhiro KIMURA Subject: Fatal trap 9 when rebooting after installkernel on VirtualBox VM Date: Sun, 02 Sep 2018 23:51:45 +0900 (JST) > I'm tracking head with VirtualBox VM. Everytime new snapshot is > released I update to same revision. So buildworld, buildkernel and > inst

Fatal trap 9 when rebooting after installkernel on VirtualBox VM

Hello. I'm tracking head with VirtualBox VM. Everytime new snapshot is released I update to same revision. So buildworld, buildkernel and installkernel always completes sucsessfully. But when rebooting system always crashes with 'Fatal trap 9: general protection fault while in kernel mode

Error occurs in the VirtualBox VM installed from the vmdk image when "close" is pressed on the VM window

I installed this VMDK image https://download.freebsd.org/ftp/snapshots/VM-IMAGES/12.0-CURRENT/amd64/Latest/FreeBSD-12.0-CURRENT-amd64.vmdk.xz rom Jul 26. Once it boots, pressing "close" causes the error. Yuri ___ freebsd-current@freebsd.org

Re: emulators/virtualbox-ose-additions-nox11 fails to build in poudriere-devel for amd64 context: fails CTASSERT(sizeof(struct pcpu) == UMA_PCPU_ALLOC_SIZE)

[The build got to emulators/virtualbox-ose-additions and it also failed this way. The PAGE_SIZE warning did not occur. More notes added after the quoted history.] On 2018-Jul-15, at 7:49 AM, Mark Millard wrote: > The failure: > > kBuild: Compiling VBoxGuestR0Lib - > /wrkdi

emulators/virtualbox-ose-additions-nox11 fails to build in poudriere-devel for amd64 context: fails CTASSERT(sizeof(struct pcpu) == UMA_PCPU_ALLOC_SIZE)

The failure: kBuild: Compiling VBoxGuestR0Lib - /wrkdirs/usr/ports/emulators/virtualbox-ose-additions-nox11/work/VirtualBox-5.2.14/src/VBox/Additions/common/VBoxGuest/lib/VBoxGuestR0LibPhysHeap.cpp In file included from /wrkdirs/usr/ports/emulators/virtualbox-ose-additions-nox11/work/VirtualBox

Current fails to install in virtualbox: Distribution extract failed

This ISO image: FreeBSD-12.0-CURRENT-amd64-20180322-r331345-disc1.iso Differences with default: I chose ZFS root fs and only left "ports" checked in "Distribution Select". Yuri ___ freebsd-current@freebsd.org mailing list

Re: head -r325997: Fatal trap 12: page fault while in kernel mode (during a buildworld, virtualbox guest context) [2nd example]

> > Correction to original:frame 0xfe01aeb28a70 > (new is the same) > >> fork_exit() at fork_exit+0x82/frame 0xfe01aeb28ab0 >> fork_trampoline() at fork_trampoline+0xe/frame 0xfe01aeb28ab0 >> --- trap 0, rip = 0, rsp = 0, rpb = 0 --- >>

head -r325997: Fatal trap 12: page fault while in kernel mode (during a buildworld, virtualbox guest context)

dworld buildkernel had completed fine. Until yesterday, I'd been running -r325700 or before and had not seen such an issue ever before. I'd been using the virtualbox version for a while before this as well. === Mark Millard markmi at dsl-only.net ___ f

Re: emulators/virtualbox-kmod: turn on VIMAGE by default for FreeBSD 12+

24 окт. 2017 г. 0:38 пользователь "Oleg Ginzburg" <olev...@olevole.ru> написал: Hello, With this change: https://svnweb.freebsd.org/base?view=revision=324810 I think should also set VIMAGE options by default in emulators/virtualbox-kmod port for FreeBSD 12+ via .if ${O

emulators/virtualbox-kmod: turn on VIMAGE by default for FreeBSD 12+

Hello, With this change: https://svnweb.freebsd.org/base?view=revision=324810 I think should also set VIMAGE options by default in emulators/virtualbox-kmod port for FreeBSD 12+ via .if ${OPSYS} == FreeBSD && ${OSVERSION} >= 1200051 or by separated meta port ( FLAVOR can help

Re: r320183 (rpc.lockd cleanup) breaks virtualbox-ose build

o match. When I went to >> build packages, the virtualbox-ose build failed due to ar segfaulting. > > Can you give the patch in https://reviews.freebsd.org/D11687 a try? I still see ar segfault. I'm also really curious about how the rpc.lockd change can trigger the bug. __

Re: r320183 (rpc.lockd cleanup) breaks virtualbox-ose build

On 11 July 2017 at 12:44, Don Lewis <truck...@freebsd.org> wrote: > This is a really strange problem ... > > Last week I upgraded my 12.0-CURRENT package build box from r318774 to > r320570. I also upgraded the poudriere jail to match. When I went to > build packages, the

r320183 (rpc.lockd cleanup) breaks virtualbox-ose build

This is a really strange problem ... Last week I upgraded my 12.0-CURRENT package build box from r318774 to r320570. I also upgraded the poudriere jail to match. When I went to build packages, the virtualbox-ose build failed due to ar segfaulting. To debug I created a new 12.0-CURRENT

FYI: Going from head -r313864 to -r313999 I had to rebuild virtualbox-ose-additions 5.1.14

For amd64 I run FreeBSD under VirtualBox on macOS. So I use emulators/virtualbox-ose-additions in the FreeBSD instance. I've been using virtualbox-ose-additions-5.1.14 for some time under -r313864 (and some prior versions), no problems, no need to rebuild virtualbox-ose-additions-5.1.14 along

Re: kernel panic caused by virtualbox(?)

hursday, August 04, 2016 05:10:29 PM Don Lewis wrote: > >> >>>>>> Reposted to -current to get some more eyes on this ... > >> >>>>>> > >> >>>>>> I just got a kernel panic when I started up a CentOS 7 VM in > >> >>>>>> virtu

Re: kernel panic caused by virtualbox(?)

get some more eyes on this ... >> >>>>>> >> >>>>>> I just got a kernel panic when I started up a CentOS 7 VM in >> >>>>>> virtualbox. >> >>>>>> The host is: >> >>>>>> FreeBSD 12.0-CURRENT #17

Re: kernel panic caused by virtualbox(?)

t;>> On Mon, Aug 08, 2016 at 10:22:44AM -0700, John Baldwin wrote: > >>>>> On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote: > >>>>>> Reposted to -current to get some more eyes on this ... > >>>>>> > >>>>>> I

Re: kernel panic caused by virtualbox(?)

> On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote: >>>>>> Reposted to -current to get some more eyes on this ... >>>>>> >>>>>> I just got a kernel panic when I started up a CentOS 7 VM in virtualbox. >>>>>> The hos

Re: kernel panic caused by virtualbox(?)

on Lewis wrote: >>>>> Reposted to -current to get some more eyes on this ... >>>>> >>>>> I just got a kernel panic when I started up a CentOS 7 VM in virtualbox. >>>>> The host is: >>>>> FreeBSD 12.0-CURRENT #17 r302500

Re: kernel panic caused by virtualbox(?)

-current to get some more eyes on this ... > >> > > >> > I just got a kernel panic when I started up a CentOS 7 VM in virtualbox. > >> > The host is: > >> > FreeBSD 12.0-CURRENT #17 r302500 GENERIC amd64 > >> > The virtualbox version is: > >

Re: kernel panic caused by virtualbox(?)

anic when I started up a CentOS 7 VM in virtualbox. >> > The host is: >> >FreeBSD 12.0-CURRENT #17 r302500 GENERIC amd64 >> > The virtualbox version is: >> >virtualbox-ose-5.0.26 >> >virtualbox-ose-kmod-5.0.26_1 >> > >> > The p

Re: kernel panic caused by virtualbox(?)

anic when I started up a CentOS 7 VM in virtualbox. >> > The host is: >> >FreeBSD 12.0-CURRENT #17 r302500 GENERIC amd64 >> > The virtualbox version is: >> >virtualbox-ose-5.0.26 >> >virtualbox-ose-kmod-5.0.26_1 >> > >> > The p

Re: kernel panic caused by virtualbox(?)

On 8 Aug, John Baldwin wrote: > On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote: >> Reposted to -current to get some more eyes on this ... >> >> I just got a kernel panic when I started up a CentOS 7 VM in virtualbox. >> The host is: >> FreeBSD

Re: kernel panic caused by virtualbox(?)

On Mon, Aug 08, 2016 at 10:22:44AM -0700, John Baldwin wrote: > On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote: > > Reposted to -current to get some more eyes on this ... > > > > I just got a kernel panic when I started up a CentOS 7 VM in virtualbox. > > T

Re: kernel panic caused by virtualbox(?)

On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote: > Reposted to -current to get some more eyes on this ... > > I just got a kernel panic when I started up a CentOS 7 VM in virtualbox. > The host is: > FreeBSD 12.0-CURRENT #17 r302500 GENERIC amd64 > The

kernel panic caused by virtualbox(?)

Reposted to -current to get some more eyes on this ... I just got a kernel panic when I started up a CentOS 7 VM in virtualbox. The host is: FreeBSD 12.0-CURRENT #17 r302500 GENERIC amd64 The virtualbox version is: virtualbox-ose-5.0.26 virtualbox-ose-kmod-5.0.26_1

11.0 under virtualbox: Going from -r302180 to -r302331 required emulators/virtualbox-ose-additions rebuild despite 1100120 being unchanged

[The ports had recently been updated to -r417989 and a "portupgrade -Wa" had run to completion before the following FreeBSD 11.0 -r302180 to -r302331 upgrade was started.] On Mac OS X 10.11.5 using FreeBSD 11.0 -r302331 under VirtualBox 5.0.24 r108355 after upgrading from FreeBSD 11.

Re: Virtualbox kernel module on 11-CURRENT

On 8/06/2016 5:13 AM, Kevin Oberman wrote: On Tue, Jun 7, 2016 at 1:04 AM, Guido Falsi <m...@madpilot.net> wrote: On 06/07/16 02:23, Rafael Rodrigues Nakano wrote: Hello, I tried installing virtualbox from packages, building it from sources, trying the GENERIC kernel but everytime I

Fwd: Virtualbox kernel module on 11-CURRENT

Thanks for the replies, Is there a specific option which needs to be enabled in the kernel config file to make softwares like virtualbox run properly? I installed a new kernel before building and installing virtualbox-ose (and -kmod), which I enabled very few things (only hardware that I have

Re: Virtualbox kernel module on 11-CURRENT

On 06/07/16 23:13, Kevin Oberman wrote: > On Tue, Jun 7, 2016 at 1:04 AM, Guido Falsi <m...@madpilot.net > <mailto:m...@madpilot.net>> wrote: > > On 06/07/16 02:23, Rafael Rodrigues Nakano wrote: > > Hello, > > > > I tried installing

Re: Virtualbox kernel module on 11-CURRENT

On Tue, Jun 7, 2016 at 1:04 AM, Guido Falsi <m...@madpilot.net> wrote: > On 06/07/16 02:23, Rafael Rodrigues Nakano wrote: > > Hello, > > > > I tried installing virtualbox from packages, building it from sources, > > trying the GENERIC kernel but everytim

Re: Virtualbox kernel module on 11-CURRENT

> On Jun 7, 2016, at 01:04, Guido Falsi <m...@madpilot.net> wrote: > >> On 06/07/16 02:23, Rafael Rodrigues Nakano wrote: >> Hello, >> >> I tried installing virtualbox from packages, building it from sources, >> trying the GENERIC kernel but everytime I

Re: Virtualbox kernel module on 11-CURRENT

On 06/07/16 02:23, Rafael Rodrigues Nakano wrote: > Hello, > > I tried installing virtualbox from packages, building it from sources, > trying the GENERIC kernel but everytime I can't start the kernel module > 'vboxdrv', it says: > "KLD vboxdrv.ko: depends on kernel - n

Virtualbox kernel module on 11-CURRENT

Hello, I tried installing virtualbox from packages, building it from sources, trying the GENERIC kernel but everytime I can't start the kernel module 'vboxdrv', it says: "KLD vboxdrv.ko: depends on kernel - not available or version mismatch. linker_load_file: Unsupported file type"

Re: VirtualBox network connectivity broken on recent -CURRENT

om> wrote > >> > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: > >> > > It looks like something changed in -CURRENT to break network > >> > > connectivity to VirtualBox guests. This was last known to work > >> > > w

Re: VirtualBox network connectivity broken on recent -CURRENT

;> > > It looks like something changed in -CURRENT to break network >> > > connectivity to VirtualBox guests. This was last known to work >> > > with r299139 (May 6th) and is definitely broken with r301229. >> > >> > I've been having Virtual

Re: VirtualBox network connectivity broken on recent -CURRENT

On 5 Jun, Otacílio wrote: > Em 04/06/2016 23:04, Randy Westlund escreveu: >> On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: >>> It looks like something changed in -CURRENT to break network >>> connectivity to VirtualBox guests. This was last known to wor

Re: VirtualBox network connectivity broken on recent -CURRENT

o break network > > > connectivity to VirtualBox guests. This was last known to work > > > with r299139 (May 6th) and is definitely broken with r301229. > > > > I've been having VirtualBox networking problems as well. I can't > > get my VMs on the network recently,

Re: VirtualBox network connectivity broken on recent -CURRENT

Em 04/06/2016 23:04, Randy Westlund escreveu: On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: It looks like something changed in -CURRENT to break network connectivity to VirtualBox guests. This was last known to work with r299139 (May 6th) and is definitely broken with r301229

Re: VirtualBox network connectivity broken on recent -CURRENT

On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund <rwest...@gmail.com> wrote > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: > > It looks like something changed in -CURRENT to break network > > connectivity to VirtualBox guests. This w

Re: VirtualBox network connectivity broken on recent -CURRENT

On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: > It looks like something changed in -CURRENT to break network > connectivity to VirtualBox guests. This was last known to work with > r299139 (May 6th) and is definitely broken with r301229. I've been having VirtualBox n

  1   2   3   4   >