Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Dec 2013 01:57:55 +0000
From:      Michael Berman <michael.berman@tidalscale.com>
To:        Neel Natu <neelnatu@gmail.com>
Cc:        "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
Subject:   Re: break to debugger in bhyve
Message-ID:  <CED4EB1D.1AAF3%michael.berman@tidalscale.com>
In-Reply-To: <CAFgRE9G6eofjPhx-2tNcabj9H83uO7A57bF7zoKiXH6igYJ1qQ@mail.gmail.com>
References:  <CED388F2.1AA90%michael.berman@tidalscale.com> <52AE52DD.6020500@freebsd.org> <03322001-03C7-491F-B97D-64EA2E89BF6C@tidalscale.com> <CAFgRE9G6eofjPhx-2tNcabj9H83uO7A57bF7zoKiXH6igYJ1qQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

Yes, thank you. I had this in my sysctl.conf.
It seems that my problem was in use of ssh in my environment.
=B3~~^B=B2 finally did the trick.
I=B9ve also moved it to boot/loader.conf as this sets it a little earlier i=
n
the boot sequence.

It is still unreliable for me, but it may be my environent.

On 12/16/13, 5:03 PM, "Neel Natu" <neelnatu@gmail.com> wrote:

>Hi Michael,
>
>On Sun, Dec 15, 2013 at 9:00 PM, Michael Berman
><michael.berman@tidalscale.com> wrote:
>>
>> Unfortunately, this does not seem to work with the bhyve /dev/console
>>device.
>>
>
>Works fine for me once I compile with the ALT_BREAK_TO_DEBUGGER config
>option.
>
>root@b2:~ # sysctl -a kern.conftxt | grep ALT_BREAK_TO_DEBUGGER
>options ALT_BREAK_TO_DEBUGGER
>root@b2:~ #
>root@b2:~ # KDB: enter: Break to debugger
>[ thread pid 11 tid 100003 ]
>Stopped at      kdb_alt_break_internal+0x17f:   movq    $0,kdb_why
>db>
>
>best
>Neel
>
>> Sent from my iPhone
>>
>>> On Dec 15, 2013, at 5:10 PM, "Julian Elischer" <julian@freebsd.org>
>>>wrote:
>>>
>>>> On 12/16/13, 8:27 AM, Michael Berman wrote:
>>>> I=B9ve tried the various kernel and sysctl options, and it may be the
>>>>way I am starting bhyve but I can=B9t seem to get a the FreeBSD guest t=
o
>>>>enter the kernel debugger with a hotkey.
>>> it depends of course on which 'console' you are using,,  for serial
>>>console with /dev/nmdm you can use the ALT_BREAK_TO_DEBUGGER
>>> option so that {enter| {~} {^B} will drop you into the debugger.
>>> When I was doing this last I had the console on the first serial port
>>>and the debugger on the second.
>>> (that's why I wrote the nmdm node.)
>>>>
>>>> Michael
>>>>
>>>> _______________________________________________
>>>> freebsd-virtualization@freebsd.org mailing list
>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
>>>> To unsubscribe, send any mail to
>>>>"freebsd-virtualization-unsubscribe@freebsd.org"
>>>
>> _______________________________________________
>> freebsd-virtualization@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
>> To unsubscribe, send any mail to
>>"freebsd-virtualization-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CED4EB1D.1AAF3%michael.berman>