Cannot boot FreeBSD 9.1 on Proxmox 3.1

B

brigzzy

New Member
Sep 30, 2013
19
0
1
Hi All,

I cannot boot FreeBSD 9.1 on Proxmox 3.1 following the instructions here. I can boot the VM, but it gets to this screen, and just hangs forever. Does anyone know where I would go about troubleshooting this?

Thanks,

Brigzzy
 
Disks must be either ide or Sata unless FreeBSD will see no disks.
You could also download FreeBSD 9.2 which default comes with virtio drivers as part of the installer as well as part of the default kernel modules. In this way you will be able to choose virtio disks and virtio nics.

If you want to be able to do online migration your disks needs to be ide or virtio which kind of narrow down your choice for FreeBSD 9.1;-)
 
mir said:
Disks must be either ide or Sata unless FreeBSD will see no disks.
You could also download FreeBSD 9.2 which default comes with virtio drivers as part of the installer as well as part of the default kernel modules. In this way you will be able to choose virtio disks and virtio nics.

If you want to be able to do online migration your disks needs to be ide or virtio which kind of narrow down your choice for FreeBSD 9.1;-)
Click to expand...

Thanks for the reply, I thought I should stick with FreeBSD 9.1 since it is mentioned on the wiki, but on your suggestion, I tried 9.2. Same problem though, it just froze on the same screen.
 
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)
 
This config works here:
balloon: 512
boot: cdn
bootdisk: sata0
cores: 2
cpu: qemu64
ide0: qnap_nfs:iso/FreeBSD-9.1-RELEASE-amd64-disc1.iso,media=cdrom,size=702014K
memory: 1024
name: freebsd
net0: e1000=92:E0:1D:85:1C:54,bridge=vmbr300
ostype: other
sata0: omnios:vm-110-disk-1,cache=writeback,size=16G
sockets: 1
vga: qxl
 
mir said:
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)
Click to expand...

Here you go:

Code: 
proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve)
pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-7
qemu-server: 3.1-1
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-10
pve-libspice-server1: 0.12.4-1
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2
 
Your proxmox is not latest version, which mine is, so try to update proxmox and the see if your are not able to install FreeBSD after the upgrade. The upgrade contains a lot of bug fixes related to other OS's like *BSD and Solaris.
 
mir said:
Your proxmox is not latest version, which mine is, so try to update proxmox and the see if your are not able to install FreeBSD after the upgrade. The upgrade contains a lot of bug fixes related to other OS's like *BSD and Solaris.
Click to expand...

Okay, I'll give that a try, thanks. Forgive a newbie question, but can you tell me how to update my install? it is as simple as "apt-get update && apt-get upgrade"?
 
mir said:
apt-get update && apt-get dist-upgrade
Click to expand...

Thank you. it returned an error when I was updating, and it says there are no packages to install

Code: 
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://security.debian.org wheezy/updates Release
Hit http://security.debian.org wheezy/updates/main amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib Translation-en
Hit http://security.debian.org wheezy/updates/main Translation-en
Hit http://ftp.ca.debian.org wheezy Release.gpg
Ign https://enterprise.proxmox.com wheezy Release.gpg
Ign https://enterprise.proxmox.com wheezy Release
Hit http://ftp.ca.debian.org wheezy Release
Hit http://ftp.ca.debian.org wheezy/main amd64 Packages
Hit http://ftp.ca.debian.org wheezy/contrib amd64 Packages
Hit http://ftp.ca.debian.org wheezy/contrib Translation-en
Hit http://ftp.ca.debian.org wheezy/main Translation-en
Err https://enterprise.proxmox.com wheezy/pve-enterprise amd64 Packages
  The requested URL returned error: 401
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-en_US
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-en
W: Failed to fetch https://enterprise.proxmox.com/debian/dists/wheezy/pve-enterprise/binary-amd64/Packages  The requested URL returned error: 401


E: Some index files failed to download. They have been ignored, or old ones used instead.
root@prox1:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 
spirit said:
do you have tried with cache=none option for disk?
Click to expand...

cache none is the default for the disk I created, and I kept it that way, but I tried adding that bit to the VM config file too, still no luck.

mir said:
Could paste the contents of /etc/pve/qemu_server/<vmid>.conf
Click to expand...

Here you go:

Code: 
bootdisk: ide0
cores: 2
ide0: local:101/vm-101-disk-1.qcow2,size=32G,cache=none
ide2: ISOs:iso/FreeBSD-9.2-RELEASE-amd64-bootonly.iso,media=cdrom
memory: 2048
name: FreeBSD
net0: virtio=4A:30:CB:1A:25:F1,bridge=vmbr0
ostype: other
sockets: 1
 
mir said:
Could you try changing image format to raw?
Click to expand...

I remade the disk as a RAW image, but the results are the same. Here is the VM config file:

Code: 
bootdisk: ide0
cores: 2
cpu: qemu64
ide0: local:101/vm-101-disk-1.raw,size=32G,cache=none
ide2: ISOs:iso/FreeBSD-9.2-RELEASE-amd64-bootonly.iso,media=cdrom
memory: 2048
name: FreeBSD
net0: virtio=B2:FC:6E:82:C7:17,bridge=vmbr0
ostype: other
sockets: 1
 
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
 
Last edited:
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom