Description of problem:
As we have FreeBSD9.2 in VM Operation Systems list, the boot of FreeBSD9.2 should work. However it freezes right after start of installation after boot menu:
FreeBSD/x86 bootstrap loader, Revision 1.1
(firstname.lastname@example.org, Fri Sep 27 03:22:55 UTC 2013)
pxe_open: server addr: *****************
pxe_open: server path: /
pxe_open: gateway ip: ***************
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. try to install FreeBSD9.2 into VM
Installation stuck after bootmenu
FreeBSD9.2 should be functional as we support it in VM Operation Systems
what is the status of the vm in the webadmin?
please attach engine+vdsm+libvirt+qemu logs
what about virtio console setting in Edit VM?
status of VM: Powering Up -> Up
adding vdsm, qemu, libvirt, engine logs
VM options, standard VM without any change in options (except name, disk, network) -> Virtio Console Disabled
Created attachment 924862 [details]
Created attachment 924863 [details]
Created attachment 924864 [details]
qemu log of test01 vm
Created attachment 924865 [details]
after conversation with dev
1. PXE boot
2. 32bit iso (instead of Vinzenzs 64bit)
Lukas please check whether or not you could figure out if this is a problem of the PXE boot. From what I can tell, there's no indication that this is a problem of devices or any settings we can tune. It rather seems to be a problem of PXE boot.
So please test if your PXE boot setup for FreeBSD works with a VM created for instance with Virt Manager.
@Lukas: please update your investigation results here:
Tried PXE boot on local machine / Virtual via virt-manager
Seems the problem is in PXE boot of FreeBSD 9.2.
Also tried booting from iso via iso domain and it works for 32 and 64bit system.
PXE boot cfg:
menu label ^FreeBSD9.2-i386
Closing since this is not a issue of RHEV and seems to be a problem specific to the PXE boost code used in fbsd
seems the bug is on FreeBSD side and is being investigated
It would be cool if you can add this information to the freebsd bug report
because it looks like it will get closed otherwise.
There is information that this is indeed a bug in ISC-DHCP?