On Monday, 10 February 2025 15:12:05 CET Turritopsis Dohrnii Teo En Ming wrote: > It appears to be too difficult for me to understand.
Not gonna lie, Hyper-V is anything but easy to work with, at least initially. It was in response to this thread that I realized that I don't even remember and never documented how I made that network stack work, which I find concerning. The only thing I do remember is that it could be done in Powershell. If I had to choose between Hyper-V, Virtualbox and VMware, I would say that Virtualbox and VMware are easier to work with, while Hyper-V gives better OS integration at the cost of complexity. Against something like QEMU meanwhile, they all create vendor lock-in. But QEMU on Windows comes with less than stellar performance, and there is something to be said about qcow2 being just as locked in of a storage format as the rest. Whichever option you choose in the end, I wish you good luck :) Best regards, Michael -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
