Re: Trying to run an older head in a recent Bhyve.
Hi Willem, I'm trying to run one of my older VM's and get the crash below in the VM when trying to boot... This happens both on an older BSD: FreeBSD 11.0-CURRENT (FREETEST) #1 r273066M: Sun Oct 19 00:59:06 CEST 2014 As well as on a very recent: FreeBSD 11.0-CURRENT (BHYVE00) #0 r274490M: Fri Nov 14 02:42:43 CET 2014 The older 10.0 VM's do boot normally Any suggestions on what this might be, and/or how to debug this.. Did the disk image backing file change by any chance ? e.g. from file to zvol ? What's the version of the VM that has the issue ? later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Trying to run an older head in a recent Bhyve.
Hi, I'm trying to run one of my older VM's and get the crash below in the VM when trying to boot... This happens both on an older BSD: FreeBSD 11.0-CURRENT (FREETEST) #1 r273066M: Sun Oct 19 00:59:06 CEST 2014 As well as on a very recent: FreeBSD 11.0-CURRENT (BHYVE00) #0 r274490M: Fri Nov 14 02:42:43 CET 2014 The older 10.0 VM's do boot normally Any suggestions on what this might be, and/or how to debug this.. --WjW DHCPDISCOVER on vtnet0 to 255.255.255.255 port 67 interval 3 DHCPOFFER from 192.168.10.75 DHCPREQUEST on vtnet0 to 255.255.255.255 port 67 DHCPACK from 192.168.10.75 panic: ffs_write: type 0xf8000565dce8 0 (0,62) cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe00975374d0 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe0097537580 vpanic() at vpanic+0x126/frame 0xfe00975375c0 panic() at panic+0x43/frame 0xfe0097537620 ffs_write() at ffs_write+0x68b/frame 0xfe00975376c0 VOP_WRITE_APV() at VOP_WRITE_APV+0x16f/frame 0xfe00975377d0 vn_write() at vn_write+0x2f3/frame 0xfe0097537860 vn_io_fault() at vn_io_fault+0x17b/frame 0xfe00975379f0 dofilewrite() at dofilewrite+0x88/frame 0xfe0097537a40 kern_writev() at kern_writev+0x68/frame 0xfe0097537a90 sys_write() at sys_write+0x63/frame 0xfe0097537ae0 amd64_syscall() at amd64_syscall+0x25a/frame 0xfe0097537bf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe0097537bf0 --- syscall (4, FreeBSD ELF64, sys_write), rip = 0x800de9b4a, rsp = 0x7fffd4c8, rbp = 0x7fffd510 --- KDB: enter: panic [ thread pid 551 tid 100057 ] Stopped at kdb_enter+0x3e: movq$0,kdb_why ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve remote kgdb does not support kernel modules...
Julian Elischer wrote this message on Sun, Nov 16, 2014 at 00:23 +0800: > On 11/15/14, 5:43 PM, John-Mark Gurney wrote: > >John-Mark Gurney wrote this message on Sat, Nov 15, 2014 at 01:37 -0800: > >>So, I got remote kgdb working w/ bhyve, but kernel modules aren't > >>loaded... > >> > >>I'm getting: > >>(kgdb) bt > >>#0 kdb_enter (why=0x8102ee88 "panic", msg=) > >> at ../../../kern/subr_kdb.c:444 > >>#1 0x8094aa79 in vpanic (fmt=, > >> ap=) at ../../../kern/kern_shutdown.c:739 > >>#2 0x8094a8c9 in kassert_panic (fmt=) > >> at ../../../kern/kern_shutdown.c:634 > >>#3 0x8093583c in __mtx_lock_flags (c=0xf80002919720, opts=0, > >> file=0x81c3f0fa > >> > >> "/usr/home/jmg/freebsd.p4/opencrypto/sys/modules/aesni/../../crypto/aesni/aesni.c", > >> line=442) at ../../../kern/kern_mutex.c:217 > >>#4 0x81c3e3a7 in ?? () > >>#5 0xf80002a474a0 in ?? () > >>#6 0xf80002919720 in ?? () > >> > >>Where those should be in the aesni.ko module... If I run kgdb on a > >>local machine, it properly finds the kernel modules... Any hits on > >>how to fix this? > > works for me.. > the modules I'm debugging are not compiled in. > you have to have the modules in the standard place ONE THE GDB HOST. > I make a chroot with an image of the machine being debugged, PLUS the > sources. > and then run kgdb from inside that chroot. Ahh, that's right, kgdb isn't smart enough to know when you've pointed it to the kernel build dir whereh the modules are... :( Thanks for the reminder... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve remote kgdb does not support kernel modules...
On 11/15/14, 5:43 PM, John-Mark Gurney wrote: John-Mark Gurney wrote this message on Sat, Nov 15, 2014 at 01:37 -0800: So, I got remote kgdb working w/ bhyve, but kernel modules aren't loaded... I'm getting: (kgdb) bt #0 kdb_enter (why=0x8102ee88 "panic", msg=) at ../../../kern/subr_kdb.c:444 #1 0x8094aa79 in vpanic (fmt=, ap=) at ../../../kern/kern_shutdown.c:739 #2 0x8094a8c9 in kassert_panic (fmt=) at ../../../kern/kern_shutdown.c:634 #3 0x8093583c in __mtx_lock_flags (c=0xf80002919720, opts=0, file=0x81c3f0fa "/usr/home/jmg/freebsd.p4/opencrypto/sys/modules/aesni/../../crypto/aesni/aesni.c", line=442) at ../../../kern/kern_mutex.c:217 #4 0x81c3e3a7 in ?? () #5 0xf80002a474a0 in ?? () #6 0xf80002919720 in ?? () Where those should be in the aesni.ko module... If I run kgdb on a local machine, it properly finds the kernel modules... Any hits on how to fix this? works for me.. the modules I'm debugging are not compiled in. you have to have the modules in the standard place ONE THE GDB HOST. I make a chroot with an image of the machine being debugged, PLUS the sources. and then run kgdb from inside that chroot. Also, any plans to support the Z2 write-watchpoint packet? (kgdb) watch *(char *)0xf80002919708 Hardware watchpoint 1: *(char *) 18446735277659625224 (kgdb) c Continuing. Can't clear hardware watchpoints without the 'Z2' (write-watchpoint) packet ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: VIMAGE and VirtualBox networking question
On 11/11/14 00:39, Peter Ross wrote:
Nikos Vassiliadis wrote:
On 11/05/14 00:29, Manas Bhatnagar wrote:
Install ports tree in a temporary location (another computer or
something), grab the required folder and move it to the computer that
you want to install the port on and do 'make install clean' ?
probably won't work like that, you would need to make sure the
directories for dependencies are there too :o)
Tried to do this with a full ports tree and I stopped it after gcc
started to build.
BTW: You need /usr/src available for the creation of the package.
Preferably matching the kernel you want to install it..
I do this regularly (but without VIMAGE) in a jail where I build all my
packages. ("make install" and "pkg create" in a script)
I do all updates from source. I only update kernel, user land and ports
when security is at risk. Usually independent from each other.
But VirtualBox is an exception. I update kernel and VirtualBox at the
same time.
I was not brave enough to enable VIMAGE and VirtualBox on the same
server. But I may do that soon. I plan a major reconfiguration ca. end
of the year. I hope it is stable enough.
Hi,
Just want to add that everything works as expected with VIMAGE and VBox.
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve remote kgdb does not support kernel modules...
John-Mark Gurney wrote this message on Sat, Nov 15, 2014 at 01:37 -0800: > So, I got remote kgdb working w/ bhyve, but kernel modules aren't > loaded... > > I'm getting: > (kgdb) bt > #0 kdb_enter (why=0x8102ee88 "panic", msg=) > at ../../../kern/subr_kdb.c:444 > #1 0x8094aa79 in vpanic (fmt=, > ap=) at ../../../kern/kern_shutdown.c:739 > #2 0x8094a8c9 in kassert_panic (fmt=) > at ../../../kern/kern_shutdown.c:634 > #3 0x8093583c in __mtx_lock_flags (c=0xf80002919720, opts=0, > file=0x81c3f0fa > "/usr/home/jmg/freebsd.p4/opencrypto/sys/modules/aesni/../../crypto/aesni/aesni.c", > line=442) at ../../../kern/kern_mutex.c:217 > #4 0x81c3e3a7 in ?? () > #5 0xf80002a474a0 in ?? () > #6 0xf80002919720 in ?? () > > Where those should be in the aesni.ko module... If I run kgdb on a > local machine, it properly finds the kernel modules... Any hits on > how to fix this? Also, any plans to support the Z2 write-watchpoint packet? (kgdb) watch *(char *)0xf80002919708 Hardware watchpoint 1: *(char *) 18446735277659625224 (kgdb) c Continuing. Can't clear hardware watchpoints without the 'Z2' (write-watchpoint) packet -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
bhyve remote kgdb does not support kernel modules...
So, I got remote kgdb working w/ bhyve, but kernel modules aren't loaded... I'm getting: (kgdb) bt #0 kdb_enter (why=0x8102ee88 "panic", msg=) at ../../../kern/subr_kdb.c:444 #1 0x8094aa79 in vpanic (fmt=, ap=) at ../../../kern/kern_shutdown.c:739 #2 0x8094a8c9 in kassert_panic (fmt=) at ../../../kern/kern_shutdown.c:634 #3 0x8093583c in __mtx_lock_flags (c=0xf80002919720, opts=0, file=0x81c3f0fa "/usr/home/jmg/freebsd.p4/opencrypto/sys/modules/aesni/../../crypto/aesni/aesni.c", line=442) at ../../../kern/kern_mutex.c:217 #4 0x81c3e3a7 in ?? () #5 0xf80002a474a0 in ?? () #6 0xf80002919720 in ?? () Where those should be in the aesni.ko module... If I run kgdb on a local machine, it properly finds the kernel modules... Any hits on how to fix this? Thanks. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
