FreeBSD 11.x won't boot

werter

Well-Known Member
Dec 10, 2017
81
9
48
39
Hi.

I have latest updated Proxmox VE.

FreeBSD 11.x won't boot as VM if I'm select host as Processor.
Just freezing boot process.

I'm try to change hdd type, network type, disable\enable ACPI etc. - but nothing :(

Package versions :
proxmox-ve: 5.1-35 (running kernel: 4.13.13-4-pve)
pve-manager: 5.1-42 (running version: 5.1-42/724a6cb3)
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.13.13-2-pve: 4.13.13-33
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-19
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-16
pve-qemu-kvm: 2.9.1-5
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9
openvswitch-switch: 2.7.0-2

Thx for your help, guys.
 

Attachments

  • hardware.png
    hardware.png
    12.8 KB · Views: 28
  • freebsd_11.1_bios.png
    freebsd_11.1_bios.png
    20.5 KB · Views: 24
  • freebsd_11.1_uefi.png
    freebsd_11.1_uefi.png
    15.4 KB · Views: 25
The freebsd kernel may not support the CPU flags presented, when set to host.
 
Hi.

No.
Freebsd 10.x working fine with host CPU as Processor in VM settings.
 
I just installed FreeBSD-11.1-RELEASE-amd64-disc1.iso with the following settings, no issue here.

proxmox-ve: 5.1-36 (running kernel: 4.13.13-5-pve)
pve-manager: 5.1-43 (running version: 5.1-43/bdb08029)
pve-kernel-4.13.13-5-pve: 4.13.13-36
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-20
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-16
pve-qemu-kvm: 2.9.1-6
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9

bootdisk: scsi0
cores: 1
cpu: host
ide2: iso-templates:iso/FreeBSD-11.1-RELEASE-amd64-disc1.iso,media=cdrom
memory: 2048
name: freebsd11-1
net0: virtio=46:D5:F8:02:4C:B0,bridge=vmbr0
numa: 0
ostype: l26
scsi0: zfs:vm-106-disk-1,size=32G
scsihw: virtio-scsi-pci
smbios1: uuid=36c77351-497a-425d-8e9a-192eabf7f825
sockets: 1

I run a Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
 
Same with AMD A8 Socket AM4 :(

Guys, is it BUG ?
Proxmox Team can you add this to your bug tracker to solve it in near future release ?
Tnx.
 
Does it work with other CPU types?
 
Yes.
Only with host CPU type. Troubles only with latest AMD A10, A8 , A6 (maybe) Socket AM4 processors.

And you can reproduce that. Is it not difficult, really ?
 
... And you can reproduce that. Is it not difficult, really ?

As I do not have such a hardware, I cannot test it.
 
Hi.
Guys, can you add this serious BUG in your plans to fix it \ add to bugtracker ?
Thx.
 
Try to set in the vmid.conf 'cpu: max', this might help. To have the cpu type host working, AMD needs to jump in and add the cpu type to KVM.
 

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!