Hi ))
I have four production servers under bhyve.
Host system - FreeBSD 11.0-RELEASE #0 r306362
But server on Windows Server 2012 R2 when uptime more 17 - 20 days...
At moment when i connect use VNC to server, bhyve(guest OS) coredump
If don't use VNC (fbuf), server uptime 100-200 days and more, it's ok and work very well!!!
script for Windows Server 2012 R2
One time coredump was with FreeBSD 11.0 under bhyve, but uptime was 34 days...
Two times coredump was with Windows 10 under bhyve, uptime was 27 days...
Total info
if use fbuf in config after 15 - 20 days, еhere's a possibility connect to server use VNC, server is down and coredump.
I use usually UltraVNC on Windows and vncviewer under MATE on FreeBSD
Uses fbuf not good idea for a long uptime ?
Please tell me, why this ?
I have four production servers under bhyve.
Host system - FreeBSD 11.0-RELEASE #0 r306362
But server on Windows Server 2012 R2 when uptime more 17 - 20 days...
At moment when i connect use VNC to server, bhyve(guest OS) coredump
If don't use VNC (fbuf), server uptime 100-200 days and more, it's ok and work very well!!!
script for Windows Server 2012 R2
Code:
bhyve -c 4 -s 7,fbuf,tcp=192.168.254.120:5920,wait \
-s 0,hostbridge \
-s 3,ahci-hd,winsrv2012r2.hdd \
-s 4,ahci-cd,null-cd.iso \
-s 5,ahci-hd,data_winsrv2012r2.hdd \
-s 6,ahci-hd,data.700G.winsrv2012r2.hdd \
-s 10,virtio-net,tap3 \
-s 31,lpc -l bootrom,BHYVE_UEFI.fd \
-m 8G -H -w winsrv2012wrk
One time coredump was with FreeBSD 11.0 under bhyve, but uptime was 34 days...
Two times coredump was with Windows 10 under bhyve, uptime was 27 days...
Total info
if use fbuf in config after 15 - 20 days, еhere's a possibility connect to server use VNC, server is down and coredump.
I use usually UltraVNC on Windows and vncviewer under MATE on FreeBSD
Uses fbuf not good idea for a long uptime ?
Please tell me, why this ?