Can't install pfsense on hyper-V
-
hello,
i'm trying to install pfsense on hyper-v
my plan is to install pfsense 2.1 then update to 2.3 but every time i try to install it ige this errorinstall.disklabel.das1
value returned as 1for info :
i'm running hyper-V 2012 r2
i gave the pfsense
virtual hdd: 50gb
ram : 512mb -
my first idea is that you might have your VM setup as Generation 2. pfSense doesn't support Gen 2 VMs. Try creating a new Generation 1 VM and see if that works.
-
@Com:
my first idea is that you might have your VM setup as Generation 2. pfSense doesn't support Gen 2 VMs. Try creating a new Generation 1 VM and see if that works.
sorry but no it's defentlly a setup as a gen 1 VM
i know the installer is correct cause is used it to install my current pfsense (that isn't virtuel)
-
Have you tried downloading the iso for 2.3 and installing into Hyper-V from that?
-
@Com:
Have you tried downloading the iso for 2.3 and installing into Hyper-V from that?
Yes, start from 2.3.1. No point in starting on 2.1 for any reason, and its base OS doesn't support Hyper-V well at all.
-
@cmb:
@Com:
Have you tried downloading the iso for 2.3 and installing into Hyper-V from that?
Yes, start from 2.3.1. No point in starting on 2.1 for any reason, and its base OS doesn't support Hyper-V well at all.
right i've just tried to install 2.3.1 and i'm geting this error
/sbin/bsdlabel -r da0s1 >/tmp/install.disklabel.da0s1
FAILED with return code of 1
may i add this info:
i'm trying to install it onto a vhdx virtual hard drive
i'm for sur using a version 1any suggestions on how to solve this?
should i just plug in another hard drive and install it to the other hard drive ? -
Same issue on a Windows 10 Hyper-V enabled machine. I've already tried installing to a physical drive attached to the guest, no luck. I was using 2.3.1 release iso.
As a test, used VMware player on the same machine, no issues.
-
Same issue on a Windows 10 Hyper-V enabled machine. I've already tried installing to a physical drive attached to the guest, no luck. I was using 2.3.1 release iso.
As a test, used VMware player on the same machine, no issues.
ah so i'm not the only one :)
where you ever able to fix it ?
-
Try installing to a smaller virtual HD. I had all sorts of issues trying to install pfsense 2.2.6 on server 2012 R2 hyper-V, till I specified a 10GB virtual disk. Not sure why that fixed the problem (FreeBSD supports disks larger than 10GB), but it did!
-
I always make them fixed 20gb Larger does seem to have a problem.
-
i shall give that a go tommorow
and can you then make the hard drives bigger after the install?
cause i'd rather have the extra space for the logs seeing that i have to keep them all for at least 1 year ! -
i shall give that a go tommorow
and can you then make the hard drives bigger after the install?
cause i'd rather have the extra space for the logs seeing that i have to keep them all for at least 1 year !update
just tried 10 gb and…. it failled
same error -
Strange, it should work fine. I have tried 2.2 - 2.3 on HyperV 3 (2012 R2) without any problem (apart from spamming the logs with clock drift messages).
Two months ago we've had an HDD failure in our main pfSense box and the quickest "replacement" i came up with was re-creating the router from backups into a HyperV VM. Worked like a charm. It actually worked so well that it took me more than a month to get my butt off the chair and go fix the dead hardware box. :)
The VM is Gen1 (needs to be) and has 2 Gigs of RAM (fixed, dynamic doesn't work), 2 cores, 4 NICs (the new ones, "hn" driver, not the legacy emulated ones) and 16 Gigs of storage. Installed from the standard AMD64 ISO.
Could you post the exact specs of the VM?
-
should be a gen 1
1ram: 1024mb (fixed)
CPO: 1core i3
HDD: 10gb or 50gb (fxrd)
NIC: 2 network cards (dedicated for the pf)
ISO: pfsense-CE-2.3.1-RELEASE-386.iso -
I forgot to mention that the HDD is at IDE interface, not SCSI, so you might check that.
Also, use an AMD64 image, do not use i386. -
I forgot to mention that the HDD is at IDE interface, not SCSI, so you might check that.
Also, use an AMD64 image, do not use i386.even though i've got intel cpu ?
-
AMD64 is a CPU/instruction set architecture that started with AMD and Intel also used it. So the names are just part of history.
The vast majority of 32 bit CPUs made by Intel and AMD are "i386".
The vast majority of 64 bit CPUs made by Intel and AMD are "AMD64". -
AMD64 is a CPU/instruction set architecture that started with AMD and Intel also used it. So the names are just part of history.
The vast majority of 32 bit CPUs made by Intel and AMD are "i386".
The vast majority of 64 bit CPUs made by Intel and AMD are "AMD64".that what i realised (just made self a bit stupid :) )
there a reason as to why they just didn't put 32 or 64 bit ? -
great news it works :D :D
even the bigger hdd -
many thanks for all your help
