Re: Is it me or does FreeBSD (12.1 amd64) hang when I manually snapshot it in VSphere 6.7?

2020-05-21 Thread Doug McIntyre
On Fri, May 22, 2020 at 12:31:29AM +0200, rai...@ultra-secure.de wrote:
> subject says it all, basically.
> 
> The system becomes totally unresponsive and has to be power-cycled.


Not just you.

Specificly, the behavior I see comes about only when Snapshot with a
copy of the virtual machine's memory is done. With this box unchecked,
there are no problems.

I suspect some interaction with the kernel and the openvm-tool set.

open-vm-tools-nox11-11.0.1_3,2

I'll upgrade to the latest

open-vm-tools-nox11-11.1.0,2

and see if it does it.

No change with that version (after a reboot).

$ freebsd-version -kru
12.1-RELEASE-p5
12.1-RELEASE-p5
12.1-RELEASE-p5

vCenter server = 6.7U3g
I think I'm a little behind on the hypervisor
VMware ESXi, 6.7.0, 15160138


So, workaround I guess is to not snapshot the memory, just the disk snap.
But still, it shouldn't do that.





___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Is it me or does FreeBSD (12.1 amd64) hang when I manually snapshot it in VSphere 6.7?

2020-05-21 Thread rainer

Hi,


subject says it all, basically.

The system becomes totally unresponsive and has to be power-cycled.

da0 at mpt0 bus 0 scbus2 target 0 lun 0
da0:  Fixed Direct Access SCSI-2 device
da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit)
da0: Command Queueing enabled
da0: 40960MB (83886080 512 byte sectors)
da0: quirks=0x140


This is a bit of a problem here, to say the least.


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


watch(4) and [USB] serial

2020-05-21 Thread O'Connor, Daniel via freebsd-stable
Hi,
I have noticed that watch(4) does not pick up traffic coming from the USB 
serial port - it sees traffic going out but not the reverse.

I tested a pty and it sees traffic in both directions, this computer has a 
'real' serial port but I don't have anything to plug into it right now.

I think this is a bug but I am not sure how the snp stuff is hooked up to find 
the cause, any one know?

Thanks.

--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
 -- Andrew Tanenbaum


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"