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

    OmniOS / Illumos / Solaris as a guest - not working

    Scheduled Pinned Locked Moved
    Compute
    7
    25
    928
    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.
    • M
      mchadley002 @BobTB12
      last edited by

      @BobTB12,

      For what it's worth, I came back to a project I was working on trying to use OpenIndiana in a VM on XCP-ng 8.2 today and serendipitously, that project just released a new version 2024.04 on the same day. I gave the new ISOs a try and was able to boot into the installer and install it and then reboot into OI no problem. I tried both the GUI and text installers without an issue. I don't actually know what the difference is, but the release note does say "New Hardware Support" so I guess whatever that is worked! Not sure about other Illumos based distro; whether this is something later versions of them will pickup as well from their common base or if it's something that OI did specifically 🤷.

      A 1 Reply Last reply Reply Quote 0
      • A
        Andrew Top contributor @mchadley002
        last edited by

        @mchadley002 @BobTB12 Thanks for the info! I concur, it boots now! (XCP 8.2 and 8.3)

        Two important hints: First ENABLE Viridian for the VM. It does not want to boot without it. Second BOOT with UEFI, BIOS does work but disk IO sucks.

        I used the ISO boot image: OI-hipster-minimal-20240426.iso

        B 1 Reply Last reply Reply Quote 1
        • B
          Buckle8711 @Andrew
          last edited by

          Another potential new user here looking to migrate from VMWare and evaluating Proxmox and xcp-ng.
          I was leaning towards xcp-ng until I hit a blocker with laetst OmniOS 151052 and xcp-ng 8.3 that fails to boot in UEFI or BIOS modes. I tried 8.2 as well that also fails.

          any suggestions greatly appreciated.

          SCR-20241111-ojme.png

          B 1 Reply Last reply Reply Quote 0
          • B
            Buckle8711 @Buckle8711
            last edited by

            SCR-20241111-oloe.png Enabling 'Viridian' enables the client to boot but with some errors.

            A 1 Reply Last reply Reply Quote 0
            • A
              Andrew Top contributor @Buckle8711
              last edited by

              @Buckle8711 It boots just fine for me with XCP 8.3... with the same PCI Warning... And the notices are not errors, so it works (I don't have the notices on my VM).

              B 1 Reply Last reply Reply Quote 0
              • B
                Buckle8711 @Andrew
                last edited by

                @Andrew Thanks for confirming, it seems to be working fine so at least I can progress.
                Can I ask what vm guest tools you are running? I dont see Solaris/Illumos/OmniOS listed in the wiki so not sure how to proceed.

                A 1 Reply Last reply Reply Quote 0
                • A
                  Andrew Top contributor @Buckle8711
                  last edited by

                  @Buckle8711 No guest tools.... OpenSolaris does include Xen drivers but I don't know if they have been updated. I don't seem them loading.

                  B 1 Reply Last reply Reply Quote 0
                  • B
                    Buckle8711 @Andrew
                    last edited by

                    I've hit a blocker in my migration to xcp-ng. I'm using OmniOS as a lightweight file server with Napp-it management interface.

                    I reached a point where I needed to add two additional VIF's to support some additional VLANs bring the OmniOS VM total to four. Unfortunately only the first two are mapped to devices in OmniOS. Open to any ideas here.

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      Andrew Top contributor @Buckle8711
                      last edited by

                      @Buckle8711 I see that too. QEMU is only started with two interfaces passed to the guest. I don't know if that's because of the lack of tools or native drivers or some other config issue.

                      @olivierlambert XCP/Xen/Qemu expert question: Why does qemu start with only two interfaces when more are configured in XO?
                      qemu-dm-7 -machine pc-i440fx-2.10,accel=xen ... -device e1000,netdev=tapnet1,mac=5a:7f:c3:ba:04:d6,addr=5,rombar=0 -netdev tap,id=tapnet1,fd=7 -device e1000,netdev=tapnet0,mac=8e:68:02:55:da:c7,addr=4,rombar=0 -netdev tap,id=tapnet0,fd=8 ...
                      Where's the third and fourth? I see other VMs with more. Is it a template or vm-param issue?

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

                        Ping @Teddy-Astie if you know the best person internally to take a look at this

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