Hyper-V

heper

any error messages in the logs? any info to help the devs to improve the alpha builds would be good.

peterclark4

Whats the status for Hyper-V support with this lastest 2.2 snapshot. I have tried with both the synthetic and legacy nic options, both lead to not receiving an IP from modem. I have used the following commands just incase to try to get an ip
ifconfig ### down
ifconfig ### up
dhclient ###

Still a no go. Something I am missing?

Try enabling spoofing of MAC addresses on the network adapter in the VM settings.

evil5826

Thanks.
Ill try that when i get home and post what log information I can find. Not to noob it but where in shell are the logs kept? Or will system logs understatus on the webui have helpful data needed?

charliem

@evil5826:

Not to noob it but where in shell are the logs kept? Or will system logs understatus on the webui have helpful data needed?

Logs are circular logs, and live in /var/log. Use clog to view them (ie, "clog ipsec.log |less" for example). Everything you need should be logged in the webui though, but some prefer this way.

evil5826

Tried the same thing again today fresh install. Mac spoofing didn't get it to work. Which logs are needed for dev's when it comes to getting an IP address from modem or that part of the process? Just the system log or something else?

salida

@evil5826:

Tried the same thing again today fresh install. Mac spoofing didn't get it to work. Which logs are needed for dev's when it comes to getting an IP address from modem or that part of the process? Just the system log or something else?

hey evil5826, i am running pfsense since 1.2 version in hyper-v nearly 4 years if i remember correctly .
I have created the proper virtual switches in hyper-v (Virtual switch manager) and i am using legacy network adapters in pfsense vm. I used to have the same problem with the lan interface using the ifconfig lan down , ifconfig lan up made it work. but it has been long ago since it last troubled me …

what windows server edition are you using ?

msi

I haven't had the chance to check out neither FreeBSD 10 or pfSense 2.2 snapshots but have access to Hyper-V boxes.
Technically the modules should be present as that's what was announced with FreeBSD 10.0-RELEASE.

As salida wrote: Technically lots of OS run on Hyper-V without the paravirt drivers, however the performance is very low.
1 vCPU, 100 MBit emulated NICs, only 4 emulated (slow) IDE drives, in order to correctly run on Hyper-V the guest needs paravirt drivers.

It would be interesting to know what version of Hyper-V you are on, there are quite significant differences between i.e. 2008 R2 which I maintain some stuff on (quite some Linux)
and am currently in process to move a setup over to Server 2012 (R2) base. It would be good idea to check if paravirtualized NICs are at least working with fixed IPs.

(I may repeat myself but I remember the first Linux beta drivers that were just unstable that I even bricked one filesystem this way on a test VM)

evil5826

@salida:

@evil5826:

Tried the same thing again today fresh install. Mac spoofing didn't get it to work. Which logs are needed for dev's when it comes to getting an IP address from modem or that part of the process? Just the system log or something else?

hey evil5826, i am running pfsense since 1.2 version in hyper-v nearly 4 years if i remember correctly .
I have created the proper virtual switches in hyper-v (Virtual switch manager) and i am using legacy network adapters in pfsense vm. I used to have the same problem with the lan interface using the ifconfig lan down , ifconfig lan up made it work. but it has been long ago since it last troubled me …

what windows server edition are you using ?

Windows Server 2012

salida

Windows Server 2012

me too, are you using external adapters for the virtual switch in hyper-v ?

MikeyTT

I'm running 2012R2 Hyper-V with pfSense 2.2 (27/5). 3 physical NICs and one virtual for my set-up and it's running as well as it ever did on my old ESXi set-up. Well almost as well, I have an Open VPN issue, but I think that's me and not pfSense.

I tried with 2.1 but I had issues with the NICs even when they were legacy ones. I'm now using the standard network adapter, install off live CD just sailed through.

I only transfer traffic bound for the web through the router, but performance wise I have seen no dropoff under Hyper-V.

I get an odd "calcu: runtime went backwards" error, but I've not had chance to look at what that might be yet. Doesn't seem to impact the stability or performance, well over the 2 days it's been running.

eri--

Try setting kern.hz to 100 or run a proper time server synchronization.

salida

@MikeyTT:

I get an odd "calcu: runtime went backwards" error, but I've not had chance to look at what that might be yet. Doesn't seem to impact the stability or performance, well over the 2 days it's been running.

@ermal:

Try setting kern.hz to 100 or run a proper time server synchronization.

True dat , calcu is common problem related to manu things as bios clock settings, kern.hz speed and time server..

susamlicubuk

pfSense on hyper-v ethernet problem (Windows hyper-v server 2008,2008r2,2012,2012r2)
solution.
1- add legacy network adapter
2- Create a Startup Script
/usr/local/etc/rc.d/startup.sh
ifconfig de0 down
ifconfig de1 up
ifconfig de1 down
ifconfig de1 up

and startup.sh properties chmod 0755 or
command chmod +x /usr/local/etc/rc.d/startup.sh
pfsense reboot.

msi

Do you have the possibility to compare it with native FreeBSD? It sometimes helped me in nailing things down.

Since pfSense 2.2 is based on 10.0-STABLE as of writing you might want to compare things with a regular 10.0-R and a current snapshot of 10-STABLE.
Snapshots can be found here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/

Spaghetti

@susamlicubuk:

pfSense on hyper-v ethernet problem (Windows hyper-v server 2008,2008r2,2012,2012r2)
solution.
1- add legacy network adapter

You don't need to use legacy adapters and that startup script with version 2.2 if you use the synthetic network adapters. Or you can install the drivers on 2.1 for the faster adapter.