Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Hyper-V problem

I'm virtualizing Sophos xg firewall and I have a problem with it. The problem also happens with Sophos utm 9.3. The speed for the internet connection is at about 100mbs but my connection is 1000mbs. I connected using ssh and tried to change the speed with ethtool but the only option I have is link autonegociation. Also in hyper-v console I get a message that says integration services upgrade is required. Also I'm using the synthetic network adapter, not the legacy one. Can anyone help?

Thank you.



This thread was automatically locked due to age.
Parents
  • Would you mind sharing your infrastructure topology? Sounds like you are being limited by a 10/100 switch, or dare I say even a damaged patch cable... Regarding the degraded message, that is because Hyper-V does not detect (probably because the Hyper-V virtual release doesn't have it) the Linux Integration Services installed. While I was reviewing this message that is what I came up with. But when I used the legacy network on the VM the status was OK. Although Legacy is unsupported, what I read in the documentation for Hyper-V support is that Hyper-V 2008 is the supported version not 2012 R2. Which is apparent because I had to use Gen 1 as the VM version. So when using Legacy NIC in 2012 R2 - is it referring to Hyper-V 2008 ? :)

    I have not performed any tests on speeds since I was messing with configuration options within the firewall, but if requested I could test it out tonight.
Reply
  • Would you mind sharing your infrastructure topology? Sounds like you are being limited by a 10/100 switch, or dare I say even a damaged patch cable... Regarding the degraded message, that is because Hyper-V does not detect (probably because the Hyper-V virtual release doesn't have it) the Linux Integration Services installed. While I was reviewing this message that is what I came up with. But when I used the legacy network on the VM the status was OK. Although Legacy is unsupported, what I read in the documentation for Hyper-V support is that Hyper-V 2008 is the supported version not 2012 R2. Which is apparent because I had to use Gen 1 as the VM version. So when using Legacy NIC in 2012 R2 - is it referring to Hyper-V 2008 ? :)

    I have not performed any tests on speeds since I was messing with configuration options within the firewall, but if requested I could test it out tonight.
Children
No Data