Date: Mon, 10 Aug 2020 10:40:27 +0200 From: rainer@ultra-secure.de To: Daniel Braniss <danny@cs.huji.ac.il> Cc: freebsd-virtualization@freebsd.org, stable@freebsd.org Subject: Re: vmware/vmx causing problems Message-ID: <f3628d36402c06b7b61ab28391051dfa@ultra-secure.de> In-Reply-To: <1615B87D-90B9-4680-B240-CB802B359628@cs.huji.ac.il> References: <C7C433B0-CF89-48C2-A2C1-05D44A489463@cs.huji.ac.il> <4A968FF0-35A2-4EBA-8752-A38992BDFAEC@ultra-secure.de> <1615B87D-90B9-4680-B240-CB802B359628@cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 2020-08-10 09:03, schrieb Daniel Braniss: >> On 10 Aug 2020, at 09:46, Rainer Duffner <rainer@ultra-secure.de> >> wrote: >> >> >> >>> Am 10.08.2020 um 07:27 schrieb Daniel Braniss <danny@cs.huji.ac.il>: >>> >>> hi, >>> suspend/resume/migrate works fine up to 11.3, >>> in 12.1 it usually becomes very unresponsive, ping can take several >>> minutes after a suspend/migrate. >>> switching to em works fine. >>> >>> any ideas on how to save this? >>> >> >> >> You need to disable snapshotting the memory. > > who is snapshotting the memory? and how can I stop it? Well, if you manually do a snapshot, there's a checkbox which is usually checked to snapshot the VMs memory. I guess when VEEAM does a backup, it doesn't snapshot the memory and thus the bug never triggers. I asked about this on stable a while back, too and got this answer. Not sure about migrations. I haven't had any problems.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f3628d36402c06b7b61ab28391051dfa>