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

    Hyper-V: Upgrade from 22.05 to 23.01.b.20221217.1429 fails to boot

    Scheduled Pinned Locked Moved
    Plus 23.01 Development Snapshots (Retired)
    3
    11
    1.3k
    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.
    • A
      andrew_241
      last edited by

      Hello!

      This is what I'm getting after trying to upgrade from 22.05 to the 23.01 beta:

      pfsense2301.png

      This freeze happens after the system has rebooted. This will also happen with a clean default configuration.

      My pfSense install is running in a Hyper-V VM on Windows Server 2022. Is there anything else I can provide that would be helpful?

      Thanks!

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

        @andrew_241 Mine is working fine and is looking like this.

        Screenshot 2022-12-19 101429.png

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

          Make sure you use all of the recommended settings mentioned in the docs:

          https://docs.netgate.com/pfsense/en/latest/recipes/virtualize-hyper-v.html

          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!

          A 1 Reply Last reply Reply Quote 0
          • A
            andrew_241 @jimp
            last edited by

            @jimp

            I'm using the recommended settings (with more RAM and CPU cores), except that the virtual LAN switch is set to 'External' so pfSense can communicate through to my local network. The management operating system shares the virtual LAN switch. The virtual WAN switch is connected to a different physical port and is dedicated, and that virtual switch is not shared with the management operating system.

            Upgrades from 2.6.0 to 22.01 to 22.05 have gone fine.

            Thanks again!

            A 1 Reply Last reply Reply Quote 0
            • A
              andrew_241 @andrew_241
              last edited by

              I'm not sure what the problem is, but playing with the boot environments using option 8 on the boot screen got me booting up and continuing the upgrade. However, rebooting the system results in the same hang unless I use option 8 again, and in that menu, toggling option 2 once between the two options. Then I can resume boot by pressing Enter.

              Do I have a problem with my pfSense configuration, and can I change something so that booting does not require additional user intervention?

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

                @andrew_241 I did noticed that the font in the console changed for me with the upgrade, yours looks the same as always... just an observation.

                Clipboard01.png

                A 1 Reply Last reply Reply Quote 0
                • A
                  andrew_241 @Bob.Dig
                  last edited by

                  @bob-dig

                  I did notice that the font had changed when I was able to boot 23.01. I've reverted to 22.05, because I need to have a system that can boot without user interaction. This could be some sort of bug in either Hyper-V, or FreeBSD.

                  Are you using ZFS? I'm on Windows Server 2022.

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

                    @andrew_241 I am using ZFS and VM is on Server 2022. Do you use DDA? This can be problematic although I am using it right now.

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      andrew_241 @Bob.Dig
                      last edited by

                      @bob-dig

                      I'm not using DDA. Is your configuration version at 10.0? I'm still getting the same problem with the latest beta build.

                      A Bob.DigB 2 Replies Last reply Reply Quote 0
                      • A
                        andrew_241 @andrew_241
                        last edited by

                        I just tried to run CE 2.7.0-DEVELOPMENT using the same Hyper-V configuration and settings, and it boots just fine.

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

                          @andrew_241 said in Hyper-V: Upgrade from 22.05 to 23.01.b.20221217.1429 fails to boot:

                          Is your configuration version at 10.0?

                          Yep.

                          1 Reply Last reply Reply Quote 0
                          • V vbjp referenced this topic on
                          • T ttmcmurry referenced this topic on
                          • First post
                            Last post