Comments for The Server Side Technology

Comment on The little virtual machine that is crashing Hyper-V on AMD by admin

admin — Tue, 07 Mar 2023 12:21:16 +0000

Hello,
thank you for your experience. In the end we solved this issue by using a small Intel-based Hyper-V hosts also to address the chance that this issue might happen again. To be honest, since then we migrated everything back to AMD but that specific machine has been decommissioned before the moving so we can’t tell you if moving to a different AMD CPU would have fixed the issue. However, that’s really an exception for us, in all senses! 😀 We basically ran thousands of VMs without issues. That was our very rare issue in thousands of deployments.

Hopefully we won’t need to use your trick but we will attempt to do that, if ever. Though reattaching the VHDX to a new machine usually requires re-configuring the guest OS, which is something we usually want to avoid.

Thanks!

Comment on The little virtual machine that is crashing Hyper-V on AMD by The Virtual Machine That Crashes Hyper-V on AMD | NotWeasel

The Virtual Machine That Crashes Hyper-V on AMD | NotWeasel — Fri, 03 Mar 2023 15:47:49 +0000

[…] With this new knowledge, I did some more searching and found I’m not the first one to have this happen. There’s a detailed story here about someone in a very similar situation, migrating a VM from an Intel based server to an AMD one and then having random crashes: https://www.theserverside.technology/2020/03/22/the-little-virtual-machine-that-is-crashing-hyper-v-… […]

Comment on The little virtual machine that is crashing Hyper-V on AMD by NotWeasel

NotWeasel — Wed, 01 Mar 2023 02:25:48 +0000

Hot damn! Am I ever happy to read this!
I’ve just done a migration from an old Intel based system to a new AMD based system running Hyper-V server and have spent the past few days trying to figure out what part of my hardware might be bad.
So far as I can tell, it’s all fine… and I’ve got a problem VM that’s somehow crashing the host with a hardware error showing on the motherboard.
I can reproduce it at will. Everything is fine no matter what I do until I start up that one VM. Then it crashes within a minute or so and the motherboard says 8, which was useless when trying to search out the issue.
Now I know this is a couple years ago for you, but here’s what fixed it for me. I created a new VM, attached the original VHDX to it, and it runs just fine. I have no idea what it is about the migrated VM that’s so destructive, but it seems my problem is solved now.

Comment on How to containerize Windows Admin Center by Vladimir Knobel

Vladimir Knobel — Tue, 23 Feb 2021 00:10:00 +0000

Thanks for the guide very interesting indeed, just a couple of questions:
– Can you control and monitor the host server running the container? I see that mostly all information is correct but the disk space is way smaller, probably only the container disk space.
– Have you successfully setup azure monitor on an instance like this?
– Do you have a working Dockerfile for this setup?
Best regards!

Comment on Juniper scopre codice non autorizzato su alcuni firewall. Backdoor governative ? by Dettagli sulle backdoor nei firewall Juniper | The Server Side Technology

Dettagli sulle backdoor nei firewall Juniper | The Server Side Technology — Thu, 25 Aug 2016 11:13:16 +0000

[…] usare PHP 7 versione 32 o 64bit con i servizi di Cloud Hosting e Windows… Must Read:Juniper scopre codice non autorizzato su alcuni firewall. Backdoor governative ? Il […]