Bhyve - Host kernel panic after running 'kldload vmm'
sree.openwrk
sree.openwrk at gmail.com
Thu Jul 19 23:55:13 UTC 2012
Hi
I have hit another road block while trying to run the guest using bhyve.
These are the steps I followed. I have used
http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt as the
reference for preparing and running guest.
1. As posted in my previous e-mail, I installed FreeBSD 9 and then checked
out /projects/bhyve and installed the world and kernel from that. Later I
am going to use the same kernel, (built from /projects/bhyve, thats used to
update from Freebsd-9 to latest in /projects/bhyve) for the guest in step
9. Also the virtio kernel modules I use in step 9 are from the ones built
from /projects/bhyve.
2. I have 8gb ram and I have set aside 4gb for the vms.
sysctl -a | grep hw.physmem
hw.physmem: 3185541120
3. I have successfully performed upto step 7 in
http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt.
4. Skipped step 8, as I plan to use virtio built from the latest code from
/projects/bhyve (As part of updating the host freebsd to the latest source
in /projects/bhyve, as mentioned above, I also made the virtio modules.)
5. Created vm1 directory in /usr/share and created all its sub-directories
and their contents. I copied only the mdroot file from
http://people.freebsd.org/~neel/bhyve/vm1.tar.gz. (remember that I copied
/boot/kernel (i.e. host kernel) as the guest kernel)
6. Then cd to /usr/share/vm1 and execute './vmrun.sh vm1'. After the
freebsd boot loader prompy comes up for the guest, after I hit enter, I get
segfaulted with core.
I am attaching herewith the backtrace of the core. Also I am pasting below
the loader.conf file witihn /usr/share/vm1/boot. Any idea what is
happening? Also is there any easy way to configure and run the guest, after
building the host kernel with bhyve hypervisor?
loader.conf
-------------------
kernel="/kernel"
virtio_load="YES"
if_vtnet_load="YES"
virtio_pci_load="YES"
virtio_blk_load="YES"
kern.hz="100"
hw.pci.enable_msix="0"
hw.pci.honor_msi_blacklist="0"
bootverbose="1"
mfsroot_load="YES"
mfsroot_type="mfs_root"
mfsroot_name="mdroot"
Thanks
On Wed, Jul 18, 2012 at 11:17 AM, sree.openwrk <sree.openwrk at gmail.com>wrote:
> Hey Neel
> Thanks for the immediate reply.
> I found that the BIOS did not have vm-x and vt-d enabled and luckily
> enabling them fixed the issue.
> Now I am able to load the vmm module and its not throwing any error as of
> now.
>
> Thanks
>
>
> On Tue, Jul 17, 2012 at 10:07 PM, Neel Natu <neelnatu at gmail.com> wrote:
>
>> Hi,
>>
>> On Tue, Jul 17, 2012 at 9:12 PM, s vas <sree.openwrk at gmail.com> wrote:
>> > Hi
>> > I have a kernel panic when loading bhyve hypervisor kernel module.
>> > These are the steps I followed
>> > 1. First I installed Freebsd 9 on my machine which has Intel-x86_64 and
>> 8Gb
>> > Ram
>> > 2. The following output from dmesg.boot confirm that vmx is enabled in
>> the
>> > machine.
>> > PU: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (2394.06-MHz
>> K8-class
>> > CPU)
>> > Origin = "GenuineIntel" Id = 0x20655 Family = 6 Model = 25
>> Stepping =
>> > 5
>> >
>> >
>> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
>> >
>> >
>> Features2=0x29ae3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AESNI>
>> > AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
>> > AMD Features2=0x1<LAHF>
>> > TSC: P-state invariant, performance statistics
>> >
>> > 3. Then I checked out the latest code from svn://
>> > svn.freebsd.org/base/projects/bhyve/
>> > a) I built world and kernel
>> > b) Followed the steps in
>> >
>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
>> > (25.7.1
>> > The Canonical Way to Update Your System) to install the new kernel and
>> to
>> > install the new world.
>> > c) Rebooted to the newly built kernel.
>> > 4. I wanted to give 4gb to the host kernel and the remaining memory for
>> the
>> > guest. So I set hw.physmem to "0x100000000".
>> > 5. Rebooted the host so that hw.physmem takes effect (Following
>> > http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt)
>> > a) This is the sysctl output
>> > sysctl -a | grep hw.physmem
>> > hw.physmem: 3185545216
>> > cat /boot/loader.conf
>> > hw.physmem="0x100000000"
>> > 6. Then executed 'kldload vmm'. Got kernel panic with the following
>> trace
>> >
>> > -----
>> > #0 - #8 is panic related call trace....
>> > ........
>>
>> Could you provide the stack frames above vmx_enable()?
>>
>> It is unclear from the subset of stack frames provided here as to what
>> the cause of the panic is.
>>
>> best
>> Neel
>>
>> > #9 0xffffffff8189b91f in vmx_enable (arg=Variable "arg" is not
>> available.
>> > ) at vmx_cpufunc.h:65
>> > #10 0xffffffff808b9e5d in smp_rendezvous_action ()
>> > at /media/fbsd_part2/bhyve/bhyve/
>> > sys/kern/subr_smp.c:381
>> > #11 0xffffffff80b5f0c5 in Xrendezvous () at apic_vector.S:342
>> > #12 0xffffffff80b58e86 in acpi_cpu_c1 ()
>> > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/acpica/acpi_machdep.c:97
>> > #13 0xffffffff803467ce in acpi_cpu_idle ()
>> > at /media/fbsd_part2/bhyve/bhyve/sys/dev/acpica/acpi_cpu.c:967
>> > #14 0xffffffff80b622b5 in cpu_idle_acpi (busy=Variable "busy" is not
>> > available.
>> > )
>> > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/machdep.c:689
>> > #15 0xffffffff80b64ab8 in cpu_idle (busy=0)
>> > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/machdep.c:843
>> > #16 0xffffffff8089ed21 in sched_idletd (dummy=Variable "dummy" is not
>> > available.
>> > )
>> > at /media/fbsd_part2/bhyve/bhyve/sys/kern/sched_ule.c:2583
>> > #17 0xffffffff80846835 in fork_exit (
>> > callout=0xffffffff8089eae0 <sched_idletd>, arg=0x0,
>> > frame=0xffffff800023cc40)
>> > at /media/fbsd_part2/bhyve/bhyve/sys/kern/kern_fork.c:992
>> > #18 0xffffffff80b5e55e in fork_trampoline ()
>> > at /media/fbsd_part2/bhyve/bhyve/sys/amd64/amd64/exception.S:602
>> >
>> > I am attaching herewith the text core as well as the info. Can someone
>> tell
>> > me whats happening?
>> >
>> > _______________________________________________
>> > freebsd-virtualization at freebsd.org mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
>> > To unsubscribe, send any mail to "
>> freebsd-virtualization-unsubscribe at freebsd.org"
>> >
>>
>
>
-------------- next part --------------
#0 0x00000008318135af in ficlExecC () from /boot/userboot.so
#1 0x000000083181b1f1 in ficlTick () from /boot/userboot.so
#2 0x00000008318135c1 in ficlExecC () from /boot/userboot.so
#3 0x0000000831806be9 in bf_run () from /boot/userboot.so
#4 0x000000083180bd68 in include () from /boot/userboot.so
#5 0x000000083180bf5b in interact () from /boot/userboot.so
#6 0x000000083180bb38 in loader_main () from /boot/userboot.so
#7 0x0000000000401622 in ?? ()
#8 0x000000000040114e in ?? ()
#9 0x000000080061c000 in ?? ()
#10 0x0000000000000000 in ?? ()
#11 0x0000000000000000 in ?? ()
#12 0x0000000000000008 in ?? ()
#13 0x00007fffffffde18 in ?? ()
#14 0x00007fffffffde2c in ?? ()
#15 0x00007fffffffde2f in ?? ()
#16 0x00007fffffffde33 in ?? ()
#17 0x00007fffffffde36 in ?? ()
#18 0x00007fffffffde3b in ?? ()
#19 0x00007fffffffde3e in ?? ()
#20 0x00007fffffffde4d in ?? ()
#21 0x0000000000000000 in ?? ()
#22 0x00007fffffffde51 in ?? ()
#23 0x00007fffffffde5e in ?? ()
#24 0x00007fffffffde69 in ?? ()
#25 0x00007fffffffde7e in ?? ()
#26 0x00007fffffffde92 in ?? ()
#27 0x00007fffffffdee9 in ?? ()
#28 0x00007fffffffdefb in ?? ()
#29 0x00007fffffffdf0e in ?? ()
#30 0x00007fffffffdf1b in ?? ()
#31 0x00007fffffffdf26 in ?? ()
#32 0x00007fffffffdf31 in ?? ()
#33 0x00007fffffffdf3b in ?? ()
#34 0x00007fffffffdf55 in ?? ()
#35 0x00007fffffffdf61 in ?? ()
#36 0x0000000000000000 in ?? ()
#37 0x0000000000000003 in ?? ()
#38 0x0000000000400040 in ?? ()
#39 0x0000000000000004 in ?? ()
#40 0x0000000000000038 in ?? ()
#41 0x0000000000000005 in ?? ()
#42 0x0000000000000008 in ?? ()
#43 0x0000000000000006 in ?? ()
#44 0x0000000000001000 in ?? ()
#45 0x0000000000000008 in ?? ()
#46 0x0000000000000000 in ?? ()
#47 0x0000000000000009 in ?? ()
#48 0x00000000004010c0 in ?? ()
#49 0x0000000000000007 in ?? ()
#50 0x0000000800602000 in ?? ()
#51 0x000000000000000f in ?? ()
#52 <signal handler called>
#53 0x0000000000000000 in ?? ()
Previous frame inner to this frame (corrupt stack?)
More information about the freebsd-virtualization
mailing list