Bhyve: panic: "Unregistered use of FPU in kernel" when starting guest

[sree.openwrk]

Hey Neel
Thanks for the fix.
Will let you know if the fix solves the issue I reported earlier.

On Thu, Oct 25, 2012 at 8:16 PM, Neel Natu <neelnatu at gmail.com> wrote:

> Hi svas,
>
> I just submitted a fix for this:
> http://svnweb.freebsd.org/base?view=revision&revision=242122
>
> Please let me know if this fixes the panic you reported.
>
> best
> Neel
>
> On Sun, Oct 7, 2012 at 11:12 AM, sree.openwrk <sree.openwrk at gmail.com>
> wrote:
> > Hey Neel
> > Sure. I will reproduce the issue and try to narrow down the problem.
> > Will update you, if I am able to narrow down the problem.
> >
> > Thanks
> >
> >
> > On Thu, Oct 4, 2012 at 9:07 PM, Neel Natu <neelnatu at gmail.com> wrote:
> >>
> >> Hi svas,
> >>
> >> On Thu, Oct 4, 2012 at 5:58 PM, sree.openwrk <sree.openwrk at gmail.com>
> >> wrote:
> >> > Hi
> >> > I am seeing frequent kernel panic when I try to run the guest OS. I
> have
> >> > the
> >> > latest Freebsd (I compiled the latest code from
> >> > svn://svn.freebsd.org/base/projects/bhyve and installed it in my
> >> > machine).
> >> > While trying to run the pre-built guest provided at
> >> > http://people.freebsd.org/~neel/bhyve/vm1.tar.gz I get the kernel
> panic
> >> > (panic: Unregistered use of FPU in kernel)
> >> > I am attaching the core.txt.
> >> > I also want to mention that I was successfully able to boot in to the
> >> > guest
> >> > OS couple of times. But around 7/10 times I get thsi host kernel
> panic.
> >> >
> >> > stack trace:
> >> > vm_run() at vm_run+0xec
> >> > vmmdev_ioctl() at vmmdev_ioctl+0x4ea
> >> > devfs_ioctl_f() at devfs_ioctl_f+0x7a
> >> > kern_ioctl() at kern_ioctl+0xcd
> >> > sys_ioctl() at sys_ioctl+0xfd
> >> > amd64_syscall() at amd64_syscall+0x304
> >> > Xfast_syscall() at Xfast_syscall+0xf7
> >> >
> >>
> >> I am seeing this too but nowhere as frequently as you are. I hit this
> >> last night for the first time and not since.
> >>
> >> There hasn't been any change in this part of the code for quite some
> time
> >> now.
> >>
> >> Since you can trigger this much more frequently that me, would it be
> >> possible for you to narrow down which change caused this? It would be
> >> hugely helpful.
> >>
> >> best
> >> Neel
> >>
> >> >
> >> > regards
> >> > svas
> >> >
> >> >
> >
> >
>