On 26/10/24 15:28, Mark Johnston wrote:
On Fri, Oct 25, 2024 at 11:12:48PM +0200, Guido Falsi wrote:
On 25/10/24 22:49, Mark Johnston wrote:
On Fri, Oct 25, 2024 at 09:24:13PM +0200, Guido Falsi wrote:
Hi,
I've recently updated my current machines to git commit
525a177c165740fc697df3de5b92e58
On 26/10/24 15:28, Mark Johnston wrote:
On Fri, Oct 25, 2024 at 11:12:48PM +0200, Guido Falsi wrote:
On 25/10/24 22:49, Mark Johnston wrote:
On Fri, Oct 25, 2024 at 09:24:13PM +0200, Guido Falsi wrote:
Hi,
I've recently updated my current machines to git commit
525a177c165740fc697df3de5b92e58
On Fri, Oct 25, 2024 at 11:12:48PM +0200, Guido Falsi wrote:
> On 25/10/24 22:49, Mark Johnston wrote:
> > On Fri, Oct 25, 2024 at 09:24:13PM +0200, Guido Falsi wrote:
> > > Hi,
> > >
> > > I've recently updated my current machines to git commit
> > > 525a177c165740fc697df3de5b92e58b3b41477c (Sun
On 25/10/24 22:49, Mark Johnston wrote:
On Fri, Oct 25, 2024 at 09:24:13PM +0200, Guido Falsi wrote:
Hi,
I've recently updated my current machines to git commit
525a177c165740fc697df3de5b92e58b3b41477c (Sun Oct 20 22:43:41 2024 -0800)
and just have Windows 10 VMs fail to start in bhyve with the
On Fri, Oct 25, 2024 at 09:24:13PM +0200, Guido Falsi wrote:
> Hi,
>
> I've recently updated my current machines to git commit
> 525a177c165740fc697df3de5b92e58b3b41477c (Sun Oct 20 22:43:41 2024 -0800)
> and just have Windows 10 VMs fail to start in bhyve with the error in the
> subject.
>
> I'v
Hi,
I've recently updated my current machines to git commit
525a177c165740fc697df3de5b92e58b3b41477c (Sun Oct 20 22:43:41 2024
-0800) and just have Windows 10 VMs fail to start in bhyve with the
error in the subject.
I've been unable to recover them with usual tricks (automatic recovery,
ch
