Todo #9374
closedUpdate Virtualizing pfSense with Hyper-V recipe with more recent information
100%
Description
Page: https://docs.netgate.com/pfsense/en/latest/recipes/virtualize-hyper-v.html
Feedback:
The Hyper-V tutorial doesn't make a lot of sense. I know there is a generic disclaimer about not looking to hard at it, however the first two steps will probably cause more confusion then less.
Currently it asks you to create an internal network in step one, then immediately change it to a private network in step two. A vswitch cannot be internal and private at the same time, so it might as well just say to create a private interface in step 1, and remove step 2 completely.
Secondly, a private interface isn't a good idea here because it only works on the VM in question. Internal will only work with the other VMs running in Hyper-V. Why not just use external w/ a dedicated NIC as this is what is needed for most if not all real world setups?
Also if you do not turn off the Backup (VSS) integration service for the pfSense VM, it will cause an error when you reboot the host, which causes a hard reset of the pfSense VM instead of a graceful shutdown, which could corrupt data on disk.
pfSense also now works with a Hyper-V Gen2 VM with a little tweaking, so maybe that should be included? Not necessary but still something to consider.
Updated by Jim Pingle over 4 years ago
- Description updated (diff)
- Category changed from Virtualization to Recipes
Updated by Jim Pingle almost 3 years ago
- Tracker changed from Correction to Todo
- Subject changed from Feedback on Virtualization — Virtualizing pfSense with Hyper-V to Update Virtualizing pfSense with Hyper-V recipe with more recent information
Updated by Jim Pingle over 2 years ago
- Status changed from New to In Progress
- Start date deleted (
03/06/2019)
Updated by Jim Pingle over 2 years ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Updated: https://gitlab.netgate.com/docs/pfSense-docs/-/commit/8d7a2654b2d040da94dffc9a3520157406314a88
Should be better and also accounts for the proper settings to use Gen2.
Updated by Jim Pingle about 2 years ago
- Status changed from Feedback to Resolved
I've followed this several times since I updated it and it works fine here. Closing.