On Sun, Jan 15, 2017 at 10:16:33PM -0500, Jeremy Faulkner wrote:
>
>
> On 2017-01-15 5:45 PM, The Doctor wrote:
> >>> 2) Windows 2016 and bhyve
> >>>
> >>>
> >>> Why can Widnows 2016 rpc not work with bhyve?
> >>
> >> Can you describe the case that isn't working ? (to get a repro)
> >
> >
On 2017-01-15 5:45 PM, The Doctor wrote:
2) Windows 2016 and bhyve
Why can Widnows 2016 rpc not work with bhyve?
Can you describe the case that isn't working ? (to get a repro)
Under VNC you can log in but not under rpc.
Anyone else running Win 2016 in FreeBSD 11 bhyve?
You are
On Sun, 15 Jan 2017 16:45:41 -0600, The Doctor
wrote:
Under VNC you can log in but not under rpc.
Anyone else running Win 2016 in FreeBSD 11 bhyve?
I'm running FreeBSD 12-CURRENT, just like another user who has responded.
I put Windows Server 2016 x64 eval on
On Mon, Jan 16, 2017 at 11:55:52AM +1100, Jason Tubnor wrote:
> On 16 January 2017 at 09:45, The Doctor wrote:
>
> > > > Seems that yes 6 Vms are running and are crashing at the same time.
> > > >
> > > > 2) Windows 2016 and bhyve
> > > >
> > > >
> > > > Why can
On 16 January 2017 at 09:45, The Doctor wrote:
> > > Seems that yes 6 Vms are running and are crashing at the same time.
> > >
> > > 2) Windows 2016 and bhyve
> > >
> > >
> > > Why can Widnows 2016 rpc not work with bhyve?
> >
> > Can you describe the case that isn't
On Mon, Jan 16, 2017 at 12:45:16AM +, Dustin Marquess wrote:
> I'm running 2016 (both Standard and Essentials) under 12-CURRENT bhyve
> without any obvious issues other than it's acting a lot slower than it should
> be. However I'm not entirely sure that it's a bhyve issue.
>
> -Dustin
>
>
I'm running 2016 (both Standard and Essentials) under 12-CURRENT bhyve without
any obvious issues other than it's acting a lot slower than it should be.
However I'm not entirely sure that it's a bhyve issue.
-Dustin
On Sun, Jan 15, 2017 at 4:46 PM -0600, "The Doctor"
On Sun, Jan 15, 2017 at 12:14:19PM -0800, Peter Grehan wrote:
> Hi,
>
> > 1) What do I need to send a bhyve crashing report?
>
> This list is fine, or you can file a PR against FreeBSD (you need to
> create an account for that, https://bugs.freebsd.org/bugzilla/enter_bug.cgi)
Using gdb,
> Some screens attached (hopefully not too heavy).
> Didn't have time to do better. Select your favourite ones.
>
> I upgraded Linux to newer version (Ubuntu 16.10, kernel 4.8),
> and it broke the driver. OpenCL does not work at all anymore.
> The screens were made on newer system -- nothing
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
Hi,
1) What do I need to send a bhyve crashing report?
This list is fine, or you can file a PR against FreeBSD (you need to
create an account for that, https://bugs.freebsd.org/bugzilla/enter_bug.cgi)
Seems that yes 6 Vms are running and are crashing at the same time.
2) Windows 2016
> When `glxgears` is run in fullscreen mode, what's on screen depends
> on each run. Framerate varies from run to run, is mostly stable within
> one run but can change abruptly by 100's of FPS. When the screen is
> blank, the framerate is slowest (750~1500 FPS). When only parts of
> gears are
12 matches
Mail list logo