Error pfsense freebsd

FreeBSD-9.1-RELEASE-amd64-disc1.iso runs without any problems here (on 2.3).

FreeBSD-8.3-RELEASE-amd64-bootonly.iso failed.
So Proxmox VE 2.3 works with FreeBSD-9.1 but not 8.3...
 
I have this problem too - all the freeBSD VMs on my test machine are throwing this error (pfSense, FreeNAS, NAS4Free etc).
All worked fine with Proxmox 2.2. Hardware is HP Proliant Microserver (AMD).
 
Hi, you may disable the atkbd module via hint.atkbd.0.disabled="1" in /boot/loader.conf.

To get the FreeBSD VM boot use the console, enter the boot loader, then:
set hint.atkbd.
0.disabled="1"
boot


Beware that this disables the keyboard emulation in the console!
You may also try some flags (see man atkbd), but at least "0x8" didn't work for me.

 
Hi, you may disable the atkbd module via hint.atkbd.0.disabled="1" in /boot/loader.conf.

To get the FreeBSD VM boot use the console, enter the boot loader, then:
set hint.atkbd.
0.disabled="1"
boot


Beware that this disables the keyboard emulation in the console!
You may also try some flags (see man atkbd), but at least "0x8" didn't work for me.



I have the same problem... I had the three virtual machines with qemu in proxmox 2.2 . I updated proxmox 2.2 to 2.3 and pfsense not boot, the error is this:

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00

I think the problem is the updated proxmox...

Now, I installed the monowall based in freebsd and no problem in boot...

I think the problem is version freebsd with proxmox 2.3 drivers cpu??
 
Hi, you may disable the atkbd module via hint.atkbd.0.disabled="1" in /boot/loader.conf.

To get the FreeBSD VM boot use the console, enter the boot loader, then:
set hint.atkbd.
0.disabled="1"
boot


Beware that this disables the keyboard emulation in the console!
You may also try some flags (see man atkbd), but at least "0x8" didn't work for me.


thank you... solved after the boot with the hint i've added from ssh

echo "hint.atkbd.0.disabled=1" >> /boot/loader.conf.local

to make permanent the change (/boot/loader.conf i think will be rewritten in case of update)

it works... but I hope I do not need to access the console :)
 
thank you... solved after the boot with the hint i've added from ssh

echo "hint.atkbd.0.disabled=1" >> /boot/loader.conf.local

to make permanent the change (/boot/loader.conf i think will be rewritten in case of update)

it works... but I hope I do not need to access the console :)


How I access the ssh?? pfsense not boot... Could try boot from systemrescuecd and add:

echo "hint.atkbd.0.disabled=1" >> /boot/loader.conf.local

??

And I need install pfsense from origin??

Thanks in advanced.
 
How I access the ssh?? pfsense not boot... Could try boot from systemrescuecd and add:

echo "hint.atkbd.0.disabled=1" >> /boot/loader.conf.local

??

And I need install pfsense from origin??

Thanks in advanced.

no you can use your existing VM

start the pfSense VM and enter in the console, then hit 7 from the boot menu (in pfSense 2.0.2) and type:
set hint.atkbd.0.disabled="1"
boot

note: if the boot of pfSense is faster than the console to connect, when pfSense will stop with the error message, simply leave the console opened and type
reboot
at the db> prompt

the VM should start correctly, so you can access via ssh and enter:

echo "hint.atkbd.0.disabled=1" >> /boot/loader.conf.local

reboot and it should work, but as said Raptor:
Beware that this disables the keyboard emulation in the console!
 
thank you... solved after the boot with the hint i've added from ssh

echo "hint.atkbd.0.disabled=1" >> /boot/loader.conf.local

to make permanent the change (/boot/loader.conf i think will be rewritten in case of update)

it works... but I hope I do not need to access the console :)

This may be a temporary solution.
However, the console is still required in some occassion.
(ssh server is disabled by default in the new install of pfsense, remember?)

What's wrong with atkbd and the new pve?
 
This may be a temporary solution.
However, the console is still required in some occassion.
(ssh server is disabled by default in the new install of pfsense, remember?)

What's wrong with atkbd and the new pve?


I solved this fix. Works for me.

Thanks for all. I wait resolved this bug.
 
Same problem. With pfSense v2.02 i368 and pfSense v2.01 x64
AMD Phenom II X6 1075T host machine

FreeBSD 8.1-Release, FreeBSD 8.3-Release AND FreeBSD 9.1-Release won't install.
VM Machine has 1 (Default) KVM64 processor, 2 cores
4096Mb static memory

adding: set hw.mca.enabled=0 and boot will cause the kernel to crash later on.
adding: set hint.atkbd.0.disabled=1 and boot will cause the cpu to crash (error 9 on i368 and 12 on x64)
adding: args: -machine pc-1.0 to vm config -> Same problems

I have used FreeBSD from Proxmox v1.8->v2.2 without noticible problems (AMD 383 errata, but this was fixed).
 
option 7

hint.atkbd.0.disabled="1"
boot

Then ssh'd into the VM

echo "hint.atkbd.0.disabled=1" >> /boot/loader.conf.local

This solved my issue as well, downside this disable console keyboard
 
Same problem. With pfSense v2.02 i368 and pfSense v2.01 x64
AMD Phenom II X6 1075T host machine

FreeBSD 8.1-Release, FreeBSD 8.3-Release AND FreeBSD 9.1-Release won't install.
VM Machine has 1 (Default) KVM64 processor, 2 cores
4096Mb static memory

adding: set hw.mca.enabled=0 and boot will cause the kernel to crash later on.
adding: set hint.atkbd.0.disabled=1 and boot will cause the cpu to crash (error 9 on i368 and 12 on x64)
adding: args: -machine pc-1.0 to vm config -> Same problems

I have used FreeBSD from Proxmox v1.8->v2.2 without noticible problems (AMD 383 errata, but this was fixed).

Same problem here.
I am using AMD Phenom(tm) II X6 1055T Processor.
Well, so the problem only occurs on AMD Phenom?
 
from richard1963

pfsense 2.0.2-RELEASE (i386)
built on Fri Dec 7 16:30:38 EST 2012
FreeBSD 8.1-RELEASE-p13
host intel core2quad


+1 This solved my issue as well, downside this disable console keyboard

hint.atkbd.0.disabled="1"
boot
ssh'd into the VM
echo "hint.atkbd.0.disabled=1" >> /boot/loader.conf.local
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!