FreeBSD on kvm

Damien Fleuriot ml at
Fri Jan 6 17:12:33 UTC 2012

On 1/6/12 5:50 PM, Alessandro Baggi wrote:
> On 01/06/2012 05:40 PM, Damien Fleuriot wrote:
>> On 1/6/12 4:18 PM, Alessandro Baggi wrote:
>>> On 01/06/2012 12:50 PM, Damien Fleuriot wrote:
>>>> On 1/6/12 11:43 AM, Alessandro Baggi wrote:
>>>>> Hi list,
>>>>> i've a problem running freebsd as a guest on linux+kvm. The only
>>>>> problem
>>>>> is that sometimes, when I boot the system it dies and this happens
>>>>> also
>>>>> if I run the vm with and without -nographic option. Using the qemu
>>>>> GUI I
>>>>> can see the it stops on the boot loader menu after the countdown
>>>>> and the
>>>>> only mode to resume the system is reboot the vm. I've reduced the
>>>>> autoboot delay to 1 without no result.
>>>>> Someone know something about this problem?
>>>>> Thanks in advance.
>>>> Hi,
>>>> This is exactly how to *not* ask a question.
>>>> Please take the time to read this very informative article:
>>>> For instance, you've omitted important information such as:
>>>> - linux version
>>>> - qemu version
>>>> - freebsd version
>>>> - freebsd error message when "it dies", if any
>>>> - KVM configuration options (disk mode and such)
>>>> We've been running FreeBSD 7 then 8 as a guest in Debian linux/KVM for
>>>> over 3 years now for our pre-production environment and are very happy
>>>> with it.
>>>> Please post some more details, that we might be able to actually help.
>>>> _______________________________________________
>>>> freebsd-questions at  mailing list
>>>> To unsubscribe, send any mail
>>>> to"freebsd-questions-unsubscribe at"
>>> True, I'm sorry, too few informations.
>>> The host system is Slackware64 Linux 13.37
>>> QEMU emulator version 0.14.0 (qemu-kvm-0.14.0), Copyright (c) 2003-2008
>>> Fabrice Bellard
>>> FreeBSD 8.2-RELEASE-p3
>>> kvm option: /usr/bin/qemu-system-x86_64 -pidfile $PIDFILE -cpu host -smp
>>> $NCPU -m $MRAM -k $KB -enable-kvm -drive
>>> file=$IMAGE,media=disk,index=0,cache=writeback -net
>>> nic,model=$NICMODEL,macaddr=$MAC -net
>>> tap,ifname=$TAP,script=no,downscript=no -runas $USER -monitor
>>> unix:$SOCKET,server,nowait -nographic -daemonize
>>> There are not errors. When there is the countdown  it seems to die.For
>>> example it stops to 9 seconds or 6 and stop (die) No boot line, only the
>>> boot loader menu blocked. To avoid this
>>> I want say that freebsd work very well under kvm, the problem is
>>> presented every 2/3 startup of this virtual machine.
>> What disk format do you use, with KVM ?
>> QCOW2, RAW, VirtIO ?
>> We're running with QCOW2 here, emulating IDE drives and we don't have
>> any problem.
>> _______________________________________________
>> freebsd-questions at mailing list
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe at"
> I'm using QCOW2.
> For ide drives do you give -hda?
> Info: if I give Enter during the  countdown, it starts, if i leave the
> countdown to finish, it crash.
> But running with -nographic there isn't sense to give "enter"
> Leaving delay boot to 10 sec, always block. Set delay boot to 1, it give
> me some "crash".
> There is a possibility to run directly the system instead print the
> menu? I must install lilo/grub?
> Thanks in advance.

QEMU emulator version 0.15.0 (qemu-kvm-devel), Copyright (c) 2003-2008
Fabrice Bellard

Find below the resulting command-line used to run a typical FreeBSD KVM
from our Proxmox interface:

/usr/bin/kvm -monitor unix:/var/run/qemu-server/141.mon,server,nowait
-vnc unix:/var/run/qemu-server/141.vnc,password -pidfile
/var/run/qemu-server/ -daemonize -usbdevice tablet -name
yournamehere -smp sockets=2,cores=2 -nodefaults -boot menu=on -vga
cirrus -tdf -k fr -drive
file=/var/lib/vz/images/141/vm-141-disk-1.qcow2,if=ide,index=0 -m 512
-device e1000,romfile=,mac=9E:6C:42:78:98:E2,netdev=vlan18d0 -netdev
-device e1000,romfile=,mac=E6:BA:DA:56:C9:66,netdev=vlan730d0 -netdev
-device e1000,romfile=,mac=8E:B5:8F:30:F2:C1,netdev=vlan731d0 -id 141
-cpuunits 1000

Also find below the contents of the config file for the guest:
-> cat /etc/qemu-server/141.conf
name: [snip]
bootdisk: virtio0
ostype: other
memory: 512
onboot: 1
sockets: 2
ide0: local:141/vm-141-disk-1.qcow2
vlan18: e1000=9E:6C:42:78:98:E2
cores: 2
vlan730: e1000=E6:BA:DA:56:C9:66
vlan731: e1000=8E:B5:8F:30:F2:C1

Do not pay attention to "bootdisk: virtio0", we use "ide0" for other
FreeBSD KVMs just as well.

I'm beginning to think your VM might be crashing while/because it's
actually probing for other devices.

What's the full list of devices you have attached to your VM ?

Do we have any boot stages expert on the list ?

More information about the freebsd-questions mailing list