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

    Scrambled display booting Clonezilla (and linux) ISOs under Win10 template

    Scheduled Pinned Locked Moved Compute
    18 Posts 6 Posters 7.2k Views 2 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.
    • Z Offline
      Zevgeny
      last edited by Zevgeny

      Edit 2: Thanks to jaayb, if you use the Debian-based 686 build, it just works without any messing around required at all!

      The version I used was:
      clonezilla-live-3.0.1-8-i686.iso


      Edit: Here's a workaround that works for me:

      @zevgeny said in Scrambled display booting Clonezilla (and linux) ISOs under Win10 template:

      After working with XCP support, it turns out that the culprit is the "nomodeset" parameter in Clonezilla boot options. (This is also in the "safe graphics mode" of a Ubuntu boot etc.)

      Some problem in the Xen EFI VGA virtual adaptor causes this mode to not display properly.

      Also, the W10 template has a parameter "platform:device_id=0002" which needs to be set to 0001 for Linuxes such as Clonezilla to work properly.

      So, in order to boot to CZ from a W10 template machine, we do the following.

      1. In the console for the VM host, run the command:

      xe vm-param-set uuid=<UUID of your VM goes here, no brackets> platform:device_id=0001

      1. Select KVM mode from the CZ startup menu.
        Boot Clonezilla and press "e" at the starting menu to get to the boot options. Remove "nomodeset" and press F10 to boot.

      2. When you are finished using CZ, run the command from step 1, but with "device_id=0002", to make it work with windows again.

      Original post:

      Hi, I'm running XCP-NG 8.1 (Build date 2020-03-30). I'm running into issues trying to deploy a W10 image to a new VM.

      • Create VM with template "Windows 10 64bit."

      • Set ISO to Clonezilla 20200703-focal

      • After booting, I can see the CZ initial menu screen:
        VM01.png

      • However, regardless of which option I choose (normal mode, failsafe mode, failsafe graphics, etc), the display is scrambled afterwards:
        VM02.png

      • The previous version of Clonezilla, eoan, does not exhibit this issue. (However, I can't use it anymore because suddenly it's exhibiting a different issue where it cannot find a network card.)

      • I've tried both settings of "VGA" in VM advanced properties, and every setting of Video RAM.

      • I've tried both UEFI and BIOS boot.

      • I've tried using XCP-ng Centre.

      • I've tried the Debian based Clonezilla, 2.6.7-28, and also Kubuntu 20.04.01. I've also tried the testing version of Clonezilla, "groovy."

      • Everything I've tried listed above exhibits the scrambled display issue. Clonezilla Eoan does not.

      • If I boot Clonezilla with an Ubuntu template, it works fine. But ultimately I'll be running Windows 10 under that template, after I deploy my image. Olivier says I risk running into problems if I do so.

      Does anyone else have this problem? Is there any troubleshooting, log files, etc that I can do to provide further information?

      Thanks!

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates πŸͺ Co-Founder CEO
        last edited by

        I think the issue might be related to some properties of W10 template, made to run on… Windows. But obviously, Clonezilla isn't Windows based.

        I'll test on my side if I an reproduce this. Have you tried with, let's say, a Windows Server template?

        Z 2 Replies Last reply Reply Quote 0
        • Z Offline
          Zevgeny @olivierlambert
          last edited by

          @olivierlambert I just tried the WS2019 template, with various display modes in CZ. It still has this issue.

          I also just tried the "Other Install Media" template, and it does NOT have the display issue. However, shortly after choosing any boot menu option, CZ dies and resets.

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates πŸͺ Co-Founder CEO
            last edited by

            And it works with Ubuntu template?

            Z 1 Reply Last reply Reply Quote 0
            • Z Offline
              Zevgeny @olivierlambert
              last edited by

              @olivierlambert Yes, if I use the Ubuntu 18.04 template CZ works fine. I used the default boot menu option. I haven't tried any other Ubuntu templates.

              1 Reply Last reply Reply Quote 0
              • Z Offline
                Zevgeny @olivierlambert
                last edited by

                @olivierlambert Hi, have you managed to test? Were you able to reproduce the issue?

                1 Reply Last reply Reply Quote 0
                • olivierlambertO Offline
                  olivierlambert Vates πŸͺ Co-Founder CEO
                  last edited by

                  Sorry I didn't have time, I'll try ASAP πŸ™‚

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO Offline
                    olivierlambert Vates πŸͺ Co-Founder CEO
                    last edited by

                    So I can reproduce and I'm almost sure it's a problem between UEFI and console resolution/refresh rate.

                    Maybe you can try latest testing version to see if it's the same issue.

                    1 Reply Last reply Reply Quote 0
                    • G Offline
                      gn_ro
                      last edited by

                      Fast solution is to use Clonezilla on a vm template where it works, then move the disk to a Windows 10 vm. The boot mode of the Windows vm is not important, as Clonezilla does copy the disk respecting the source format (UEFI or Bios).

                      Z 1 Reply Last reply Reply Quote 1
                      • Z Offline
                        Zevgeny @gn_ro
                        last edited by

                        @gn_ro Thanks, I'll give it a try.

                        1 Reply Last reply Reply Quote 0
                        • P Offline
                          PhantomTypist
                          last edited by

                          Unfortunately I'm running into this bug as well on the latest version of XCP-ng. Regardless if running the console from XCP-ng Center or Xen Orchestra. It's a Windows Server 2019 VM (used Windows template) and I'm trying to boot from a Linux ISO in the virtual optical drive mounted to the Windows VM. I've tried using Ubuntu Desktop, Clonezilla and Rescuezilla. Same scrambled screen/console.

                          Z 1 Reply Last reply Reply Quote 0
                          • T Offline
                            tmllc
                            last edited by

                            I dont get the scrambled image, but nothing i do allows it to detect the network

                            Z 1 Reply Last reply Reply Quote 0
                            • Z Offline
                              Zevgeny
                              last edited by Zevgeny

                              After working with XCP support, it turns out that the culprit is the "nomodeset" parameter in Clonezilla boot options. (This is also in the "safe graphics mode" of a Ubuntu boot etc.)

                              Some problem in the Xen EFI VGA virtual adaptor causes this mode to not display properly.

                              Also, the W10 template has a parameter "platform:device_id=0002" which needs to be set to 0001 for Linuxes such as Clonezilla to work properly.

                              So, in order to boot to CZ from a W10 template machine, we do the following.

                              1. In the console for the VM host, run the command:

                              xe vm-param-set uuid=<UUID of your VM goes here, no brackets> platform:device_id=0001

                              1. Select KVM mode from the CZ startup menu.
                                Boot Clonezilla and press "e" at the starting menu to get to the boot options. Remove "nomodeset" and press F10 to boot.

                              2. When you are finished using CZ, run the command from step 1, but with "device_id=0002", to make it work with windows again.

                              1 Reply Last reply Reply Quote 0
                              • Z Offline
                                Zevgeny @tmllc
                                last edited by

                                @tmllc I had that problem with an older version of Clonezilla. Are you using the latest Ubuntu based one? See my recent reply to this topic, there's a workaround that works for me.

                                T 1 Reply Last reply Reply Quote 0
                                • Z Offline
                                  Zevgeny @PhantomTypist
                                  last edited by

                                  @phantomtypist Hi, see my latest reply or my edit to the OP for a workaround.

                                  1 Reply Last reply Reply Quote 0
                                  • T Offline
                                    tmllc @Zevgeny
                                    last edited by

                                    @zevgeny I used several different versions. I finally used the ubunto template, and then it booted as a windows 10 machine. So far, no issues.

                                    J 1 Reply Last reply Reply Quote 0
                                    • J Offline
                                      jaayb @tmllc
                                      last edited by

                                      @tmllc After trying several builds of the amd64 version without success I tried the 686 version and had no issues with the screen or the nic and hard drive. I previously tried the kms option with the amd64 version which doesn't include the vga and nomodetest flags which worked for the video but got messages that it couldn't find the nic or hard drive.

                                      Z 1 Reply Last reply Reply Quote 0
                                      • Z Offline
                                        Zevgeny @jaayb
                                        last edited by

                                        @jaayb Amazing, TYSM!

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