Crashing and Windows server 2016
The Doctor
doctor at doctor.nl2k.ab.ca
Sat Dec 31 22:24:41 UTC 2016
On Sat, Dec 31, 2016 at 01:41:48PM -0700, The Doctor wrote:
> 1) recently it seems that bhyve is crashing. Anyone else experiencing this?
>
Just doing a gdb
gdb /usr/sbin/bhyve ~doctor/vm/bhyve.core
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...
Core was generated by `bhyve'.
Program terminated with signal 6, Aborted.
Reading symbols from /usr/lib/libvmmapi.so.5...Reading symbols from /usr/lib/debug//usr/lib/libvmmapi.so.5.debug...done.
done.
Loaded symbols for /usr/lib/libvmmapi.so.5
Reading symbols from /lib/libmd.so.6...Reading symbols from /usr/lib/debug//lib/libmd.so.6.debug...done.
done.
Loaded symbols for /lib/libmd.so.6
Reading symbols from /lib/libz.so.6...Reading symbols from /usr/lib/debug//lib/libz.so.6.debug...done.
done.
Loaded symbols for /lib/libz.so.6
Reading symbols from /lib/libthr.so.3...Reading symbols from /usr/lib/debug//lib/libthr.so.3.debug...done.
done.
Loaded symbols for /lib/libthr.so.3
Reading symbols from /lib/libc.so.7...Reading symbols from /usr/lib/debug//lib/libc.so.7.debug...done.
done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /lib/libutil.so.9...Reading symbols from /usr/lib/debug//lib/libutil.so.9.debug...done.
done.
Loaded symbols for /lib/libutil.so.9
Reading symbols from /libexec/ld-elf.so.1...Reading symbols from /usr/lib/debug//libexec/ld-elf.so.1.debug...done.
done.
Loaded symbols for /libexec/ld-elf.so.1
#0 0x000000080119755a in thr_kill () from /lib/libc.so.7
[New Thread 801a1b200 (LWP 101785/<unknown>)]
[New Thread 801a1ad00 (LWP 101784/<unknown>)]
[New Thread 801a1a800 (LWP 101783/<unknown>)]
[New Thread 801a1a300 (LWP 101782/<unknown>)]
[New Thread 801a19e00 (LWP 101781/<unknown>)]
[New Thread 801a19900 (LWP 101780/<unknown>)]
[New Thread 801a19400 (LWP 101779/<unknown>)]
[New Thread 801a18f00 (LWP 101778/<unknown>)]
[New Thread 801a18a00 (LWP 101324/<unknown>)]
[New Thread 801a18500 (LWP 101323/<unknown>)]
[New Thread 801a18000 (LWP 100837/<unknown>)]
(gdb) data
Undefined command: "data". Try "help".
(gdb) help
List of classes of commands:
aliases -- Aliases of other commands
breakpoints -- Making program stop at certain points
data -- Examining data
files -- Specifying and examining files
internals -- Maintenance commands
obscure -- Obscure features
running -- Running the program
stack -- Examining the stack
status -- Status inquiries
support -- Support facilities
tracepoints -- Tracing of program execution without stopping the program
user-defined -- User-defined commands
Type "help" followed by a class name for a list of commands in that class.
Type "help" followed by command name for full documentation.
Command name abbreviations are allowed if unambiguous.
(gdb) stack
Undefined command: "stack". Try "help".
(gdb) help stack
Examining the stack.
The stack is made up of stack frames. Gdb assigns numbers to stack frames
counting from zero for the innermost (currently executing) frame.
At any time gdb identifies one frame as the "selected" frame.
Variable lookups are done with respect to the selected frame.
When the program being debugged stops, gdb selects the innermost frame.
The commands below can be used to select other frames by number or address.
List of commands:
backtrace -- Print backtrace of all stack frames
bt -- Print backtrace of all stack frames
down -- Select and print stack frame called by this one
frame -- Select and print a stack frame
return -- Make selected stack frame return to its caller
select-frame -- Select a stack frame without printing anything
up -- Select and print stack frame that called this one
Type "help" followed by command name for full documentation.
Command name abbreviations are allowed if unambiguous.
(gdb) bt
#0 0x000000080119755a in thr_kill () from /lib/libc.so.7
#1 0x000000080119752b in __raise (s=6) at /usr/src/lib/libc/gen/raise.c:52
#2 0x0000000801197499 in abort () at /usr/src/lib/libc/stdlib/abort.c:65
#3 0x000000000040affc in vm_loop (ctx=0x801a1d040, vcpu=0, startrip=0)
at /usr/src/usr.sbin/bhyve/bhyverun.c:634
#4 0x0000000000409e81 in fbsdrun_start_thread (param=0x859b10)
at /usr/src/usr.sbin/bhyve/bhyverun.c:244
#5 0x0000000800eb1b55 in thread_start (curthread=<value optimized out>)
at /usr/src/lib/libthr/thread/thr_create.c:289
#6 0x0000000000000000 in ?? ()
(gdb) help data
Examining data.
List of commands:
append -- Append target code/data to a local file
call -- Call a function in the program
delete display -- Cancel some expressions to be displayed when program stops
delete mem -- Delete memory region
disable display -- Disable some expressions to be displayed when program stops
disable mem -- Disable memory region
disassemble -- Disassemble a specified section of memory
display -- Print value of expression EXP each time the program stops
dump -- Dump target code/data to a local file
enable display -- Enable some expressions to be displayed when program stops
enable mem -- Enable memory region
inspect -- Same as "print" command
mem -- Define attributes for memory region
output -- Like "print" but don't put in value history and don't print newline
print -- Print value of expression EXP
print-object -- Ask an Objective-C object to print itself
printf -- Printf "printf format string"
ptype -- Print definition of type TYPE
restore -- Restore the contents of FILE to target memory
set -- Evaluate expression EXP and assign result to variable VAR
set variable -- Evaluate expression EXP and assign result to variable VAR
undisplay -- Cancel some expressions to be displayed when program stops
whatis -- Print data type of expression EXP
x -- Examine memory: x/FMT ADDRESS
Type "help" followed by command name for full documentation.
Command name abbreviations are allowed if unambiguous.
(gdb) call thr_kill
$1 = {<text variable, no debug info>} 0x80066afe0 <thr_kill>
(gdb) call abort
$2 = {void (void)} 0x801197450 <abort>
(gdb) call vm_loop
$3 = {void (struct vmctx *, int, uint64_t)} 0x40adb0 <vm_loop>
> 2) Widnows 2016 server runs on FreeBSD expcept that apart from hyper-v
> Remote Desktop is acting strange! I have set up the ability to
> get RDP going, however attampting to log in gives me an error
> using the correct credentials.
>
> Any explanation.
>
> 3) any move afoot to get nested virtualisation into bhyve?
>
> --
> Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
> God,Queen and country!Never Satan President Republic!Beware AntiChrist rising!
> http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism
> Merry Christmas 2016 and Happy New Year 2017
> _______________________________________________
> freebsd-virtualization at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe at freebsd.org"
--
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
God,Queen and country!Never Satan President Republic!Beware AntiChrist rising!
http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism
Merry Christmas 2016 and Happy New Year 2017
More information about the freebsd-virtualization
mailing list