Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Boottime on Hyper-V still slow on 2.4.5-RELEASE-p1

    Scheduled Pinned Locked Moved Virtualization
    15 Posts 3 Posters 1.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Bob.DigB
      Bob.Dig LAYER 8 @Gertjan
      last edited by Bob.Dig

      @Gertjan I have almost the same setup, it is my only router at home, although with a nvme SSD. But I don't let start Windows my VM, because I had problems with that in the past. Maybe I have to re-check that. But there is now way it would be up and running if I would let it start at boottime.
      I also use the default config of hyper-v with win10, all devises are virtual, nothing is passed-through into the vm itself.

      Capturex.JPG

      1 Reply Last reply Reply Quote 0
      • Bob.DigB
        Bob.Dig LAYER 8 @Gertjan
        last edited by

        @Gertjan said in Boottime on Hyper-V still slow on 2.4.5-RELEASE-p1:

        Don't know what "gen1 hyper-v vm" is, I just accepted default Hyper stuff.

        Would be nice if you could take a look, which generation you are running.

        1 Reply Last reply Reply Quote 0
        • GertjanG
          Gertjan
          last edited by

          The lowest one .... I'm sure (have to check at @home this evening).

          Also, I'm using just one processor core, as it's already more then enough (a big fat I7) for my needs. (and rendered impossible another issue that others have seen)

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

          Bob.DigB 1 Reply Last reply Reply Quote 1
          • Bob.DigB
            Bob.Dig LAYER 8 @Gertjan
            last edited by

            @Gertjan Ok, thanks, then I will try that next time I make a VM. One core didn't fix that problem.

            1 Reply Last reply Reply Quote 0
            • Bob.DigB
              Bob.Dig LAYER 8
              last edited by

              I did some fresh installs and compared boot-times afterwards.

              Gen1 pfSense 245p1 57 Seconds
              Gen1 pfSense 25D   50 Seconds
              Gen2 pfSense 245p1 73 Seconds
              Gen2 pfSense 25D   44 Seconds
              
              1 Reply Last reply Reply Quote 0
              • Bob.DigB
                Bob.Dig LAYER 8
                last edited by Bob.Dig

                So I made a gen1 machine and tried going with the xml the first time, but it was an unpleasant experience. In the end, after the third try, I had to install the packages manually.
                when I am booting, I still see some problems related to openVPN.

                gdsrf.png

                GertjanG 1 Reply Last reply Reply Quote 0
                • GertjanG
                  Gertjan @Bob.Dig
                  last edited by

                  @Bob-Dig said in Boottime on Hyper-V still slow on 2.4.5-RELEASE-p1:

                  problems related to openVPN.

                  Deleting them will make pfSense start faster ?
                  Make the OpenVPN settings 'better', or delete OpenVPN.

                  I've a OpenVPN client present, but not runninh, and a OpenVPN server running on boot. Boots fast enough - no visible delays.

                  No "help me" PM's please. Use the forum, the community will thank you.
                  Edit : and where are the logs ??

                  Bob.DigB 1 Reply Last reply Reply Quote 0
                  • Bob.DigB
                    Bob.Dig LAYER 8 @Gertjan
                    last edited by Bob.Dig

                    @Gertjan I need my OpenVPN-Server, use it everyday. Switching to gen1 almost did for me, it is only some seconds over the default reboot-time... So yes, I will make a new OVPN-Server.
                    Edit: Had no luck with that, still problematic at boot time.

                    Bob.DigB 1 Reply Last reply Reply Quote 0
                    • Bob.DigB
                      Bob.Dig LAYER 8 @Bob.Dig
                      last edited by Bob.Dig

                      @Bob-Dig said in Boottime on Hyper-V still slow on 2.4.5-RELEASE-p1:

                      Edit: Had no luck with that, still problematic at boot time.

                      The problem might be, that I route all traffic from the OVPNServer to a OVPNClient, which isn't connected at boottime? But I can't change this, because it is wanted. So Boot is still slow.

                      GertjanG 1 Reply Last reply Reply Quote 0
                      • jimpJ
                        jimp Rebel Alliance Developer Netgate
                        last edited by

                        I noticed this as well, at least for me it gets stuck for ~30s at "Mounting filesystems" and hitting ^T it prints that it's stuck doing something in newfs. Only thing I can think of that would be doing that at the time would be a RAM disk (even if you don't have RAM disks enabled for /var and /tmp, /var/run is always a RAM disk). Though I couldn't find any explanation for why it was happening.

                        Unlikely we can do anything about that one since it appears to be a Hyper-V/Filesystem type issue.

                        Might help if someone could reproduce it on plain FreeBSD, and if so, report it upstream.

                        Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                        Need help fast? Netgate Global Support!

                        Do not Chat/PM for help!

                        Bob.DigB 1 Reply Last reply Reply Quote 1
                        • Bob.DigB
                          Bob.Dig LAYER 8 @jimp
                          last edited by

                          @jimp Hello Jim, have you seen my comparison? I don't know what the bare metal boottime of pfsense is, but it now would be ok, if OVPN wouldn't also slow things down a bit.

                          1 Reply Last reply Reply Quote 0
                          • jimpJ
                            jimp Rebel Alliance Developer Netgate
                            last edited by

                            Boot time varies widely depending on hardware so it's tough to get a proper basis for comparison there.

                            30-40 seconds on each boot is so little it is barely worth throwing resources at to debug, though. Reboots are rare and when they do happen, nothing is so critical that 40s would mean a huge difference.

                            If it were several minutes, then it would be more of a problem.

                            Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                            Need help fast? Netgate Global Support!

                            Do not Chat/PM for help!

                            1 Reply Last reply Reply Quote 0
                            • GertjanG
                              Gertjan @Bob.Dig
                              last edited by

                              @Bob-Dig said in Boottime on Hyper-V still slow on 2.4.5-RELEASE-p1:

                              that I route all traffic from the OVPNServer to a OVPNClient

                              The OpenVPN client tunnel isn't up at that moment, but the OpenVPN server daemon is already starting, using 'route's to the OpenVPN client. This might explain the 'route' messages.

                              What happens if you de activate the OpenVPN client - and activate it manually, after the system booted ?
                              Does it boot faster this way ?

                              Maybe you could start the OpenVPN client with a cron command that start a serveice (OpenVPN Client) 30 seconds after booting ?
                              And have it killed before you shut down, so it gets marked as "non running" and won't start during the next boot.

                              We have the "earlyshellcmd" commands. Let's invent the "lateshellcmd" ;)

                              No "help me" PM's please. Use the forum, the community will thank you.
                              Edit : and where are the logs ??

                              1 Reply Last reply Reply Quote 1
                              • First post
                                Last post
                              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.