XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Stuck on boot : Hard Disk - Success

    Scheduled Pinned Locked Moved Compute
    19 Posts 6 Posters 3.0k Views 5 Watching
    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.
    • alpenliebeanjA Offline
      alpenliebeanj @olivierlambert
      last edited by

      @olivierlambert Hello, there is already another istance with Win10 and works properly without problems, but this second istance not working, showing this error

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        Can you answer my question?

        alpenliebeanjA 1 Reply Last reply Reply Quote 0
        • alpenliebeanjA Offline
          alpenliebeanj @olivierlambert
          last edited by

          @olivierlambert Im sorry, i think i gave to you a reply, i have used a ISO immage of debian 11 and i did all full install process, after the reboot to boot the local hard disk this is showed

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            Do you have enough memory?

            alpenliebeanjA 1 Reply Last reply Reply Quote 0
            • alpenliebeanjA Offline
              alpenliebeanj @olivierlambert
              last edited by

              @olivierlambert 2gb and 2 core, also i have tryied to run this machine with the otherone Win10 off, still same issue

              1 Reply Last reply Reply Quote 0
              • olivierlambertO Offline
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                Can you try to boot with 4GiB RAM in case?

                Also, it's a regular Debian 11 install, anything specific?

                alpenliebeanjA 1 Reply Last reply Reply Quote 0
                • alpenliebeanjA Offline
                  alpenliebeanj @olivierlambert
                  last edited by

                  @olivierlambert Selected 4gb and 2core, forced reboot still stuck in this view

                  1 Reply Last reply Reply Quote 0
                  • DanpD Offline
                    Danp Pro Support Team
                    last edited by

                    Could this be a BIOS vs UEFI issue.

                    alpenliebeanjA 1 Reply Last reply Reply Quote 0
                    • alpenliebeanjA Offline
                      alpenliebeanj @Danp
                      last edited by

                      @Danp during the boot we cant select UEFI bios for debian, it's as default selection unselected... so

                      DanpD 1 Reply Last reply Reply Quote 0
                      • DanpD Offline
                        Danp Pro Support Team @alpenliebeanj
                        last edited by

                        @alpenliebeanj This setting can be viewed / changed from the VM's Advanced tab in XO.

                        alpenliebeanjA 1 Reply Last reply Reply Quote 0
                        • alpenliebeanjA Offline
                          alpenliebeanj @Danp
                          last edited by

                          @Danp You mean to try to allow UEFI bios during the boot for this istance of Debian11?

                          D 1 Reply Last reply Reply Quote 0
                          • D Offline
                            dejavju @alpenliebeanj
                            last edited by

                            @alpenliebeanj did you find a solution? Having the same issue after moving from KVM and following the migration guide https://xcp-ng.org/docs/migratetoxcpng.html#from-kvm-libvirt.

                            Tried changing to UEFI aswell but no luck

                            Bios:
                            347c9106-4a56-4151-bfa6-709ba8aec106-image.png

                            UEFI:
                            1607556c-63e6-4184-89d9-8d29bbc90eb3-image.png

                            D 1 Reply Last reply Reply Quote 0
                            • D Offline
                              dejavju @dejavju
                              last edited by

                              @dejavju FYI Converted the qcow disk to vhd again and tried and this time it booted, so something perhaps went wrong in the conversion. All is good now.

                              1 Reply Last reply Reply Quote 1
                              • olivierlambertO Offline
                                olivierlambert Vates 🪐 Co-Founder CEO
                                last edited by

                                Ah good to know, thanks for your feedback @dejavju 🙂

                                1 Reply Last reply Reply Quote 0
                                • E Offline
                                  erik.lukes
                                  last edited by

                                  This post is deleted!
                                  D 1 Reply Last reply Reply Quote 0
                                  • D Offline
                                    dejavju @erik.lukes
                                    last edited by

                                    This post is deleted!
                                    1 Reply Last reply Reply Quote 0
                                    • A Offline
                                      akoala
                                      last edited by

                                      @alpenliebeanj

                                      I know you resolved this a different way but what I did when migrating P2V from a bare metal debian system to xcpng is using clonezilla I transferred the image via the network to the VM which was booted to clonezilla as well. Then I changed the boot option to UEFI in advanced, pressed escape on startup and then proceeded to add a boot menu entry for grub of the Debian system. I would assume the process would have been similar in your case as well to resolve.

                                      1 Reply Last reply Reply Quote 0
                                      • First post
                                        Last post