Cannot boot FreeBSD 9.1 on Proxmox 3.1

[trendco]

When you create your VM do you remember to choose 'other' for OS type and qemu64 for CPU?
What version of proxmox do you use exactly? (from proxmox host: pveversion -v)

My Nas4Free VM (9.1.0.1 - Sandstorm/Revision 847 -> FreeBSD-9.1) runs without Problems with "kvm64(default)" CPU.

 

[mir]

What is you host CPU and chipset?

FreeBSD 9.1-RELEASE-p7

FreeBSD 9.2-RELEASE-p0

 

[trendco]

Intel Mainboard "DQ67SW" with "i5-2500T".

The Installation was only possible with Harddisk Type "SCSI".

 

[mir]

Strange;-)
Here: AMD A55 chipset and AMD Phenom II X6 1045T

Installation was possible using all harddisk types except virtio given that I used qemu-64. Later I have installed virtio-kmod package and now both disk and nic uses virtio flawlessly.

 

[brigzzy]

Then there is only two options left:
1) Something is wrong with your proxmox installation
2) The hardware on your proxmox host is either broken or your hardware is not fully supported. You could consider upgrading your BIOS.

What does lspci display on your proxmox host?
CPU?
Motherbord?
Eventuel hardware raid controller or HBA controller?
Disks. SATA, IDE, SCSI, SAS

Thanks for the reply. here is my lspci output:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

 

[ringerl]

Have you guys figured something out?

Facing the same issues as you mentioned: FreeBSD 9.1/2 on kvm64 is a no go for me on proxmox 3.1.
Hardware here is a i5-4570 (Haswell) and a H87 board.

 

[brigzzy]

Have you guys figured something out?

Facing the same issues as you mentioned: FreeBSD 9.1/2 on kvm64 is a no go for me on proxmox 3.1.
Hardware here is a i5-4570 (Haswell) and a H87 board.

Nope, afraid not. I just run my VMs in Ubuntu now, haha. I wonder if it's a Haswell thing, cause that's what I'm running as well.

 

[ogg]

I have the same problem. Out of 4 nodes (three with really old hardware and one with relatively new):

root@vm04:~# for host in vm01 vm02 backup01 vm04; do ssh $host uname -a; ssh $host pveversion; ssh $host cat /proc/cpuinfo | grep model\ name | uniq; echo; done
Linux vm01 2.6.32-26-pve #1 SMP Mon Oct 14 08:22:20 CEST 2013 x86_64 GNU/Linux
pve-manager/3.1-21/93bf03d4 (running kernel: 2.6.32-26-pve)
model name      : Intel(R) Xeon(R) CPU           X5450  @ 3.00GHz


Linux vm02 2.6.32-26-pve #1 SMP Mon Oct 14 08:22:20 CEST 2013 x86_64 GNU/Linux
pve-manager/3.1-21/93bf03d4 (running kernel: 2.6.32-26-pve)
model name      : Intel(R) Xeon(R) CPU           E5410  @ 2.33GHz


Linux backup01 2.6.32-26-pve #1 SMP Mon Oct 14 08:22:20 CEST 2013 x86_64 GNU/Linux
pve-manager/3.1-21/93bf03d4 (running kernel: 2.6.32-26-pve)
model name      : Intel(R) Xeon(R) CPU            5150  @ 2.66GHz


Linux vm04 2.6.32-26-pve #1 SMP Mon Oct 14 08:22:20 CEST 2013 x86_64 GNU/Linux
pve-manager/3.1-21/93bf03d4 (running kernel: 2.6.32-26-pve)
model name      : Intel(R) Xeon(R) CPU E3-1270 V2 @ 3.50GHz

FreeBSD 10 (I've also tried 9.2) runs fine on all nodes except the most modern one (vm04) using the following config:

root@vm04:~# cat /etc/pve/nodes/vm01/qemu-server/137.conf 
bootdisk: virtio0
cores: 2
ide2: none,media=cdrom
keyboard: sv
memory: 2048
name: dbnode02
net0: virtio=XX:XX:XX:XX:XX:XX,bridge=vmbr0
ostype: other
sockets: 1
virtio0: VirtualMachinesNFS:137/vm-137-disk-1.qcow2,format=qcow2,size=12G

Whatever disk type I use dosen't seem to matter, I've tried iSCSI raw instead of qcow2 on NFS and it works the same (fine on all nodes except the one with the Intel(R) Xeon(R) CPU E3-1270 V2 @ 3.50GHz).

I also tried qemu64 vs. kvm64 cpu type.

However, the problem only exist using the amd64 isos, using i386 works fine!

 

[spirit]

Hi,

Maybe could you try to test with pvetest repository ? (with qemu 1.7)

 

[brigzzy]

....

However, the problem only exist using the amd64 isos, using i386 works fine!

Oh wow, I gotta say I'm a little embarrassed with myself for not having thought of this. I just fired up an i386 ISO, and it loaded fine for me. In my case this is a perfectly acceptable workaround, so thanks!

It would be nice to have the amd64 ISOs booting, but it's not a deal breaker for me, haha.

Cheers!

Brigzzy