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

    OmniOS / Illumos / Solaris as a guest - not working

    Scheduled Pinned Locked Moved Compute
    30 Posts 8 Posters 2.6k 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.
    • 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?

                TeddyAstieT 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
                  • TeddyAstieT
                    TeddyAstie Vates 🪐 XCP-ng Team @Andrew
                    last edited by TeddyAstie

                    @Andrew said in OmniOS / Illumos / Solaris as a guest - not working:

                    @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?

                    These are the same "interfaces" just plugged differently to the guest (e.g tapnet0 exposed as e1000 and "tap" and tapnet1 exposed as e1000 and "tap" too).

                    You have 4 interfaces configured ?

                    A B 2 Replies Last reply Reply Quote 0
                    • A
                      Andrew Top contributor @TeddyAstie
                      last edited by

                      @Teddy-Astie Yes...
                      xcp-oi-interfaces.jpg

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

                        @TeddyAstie thanks for looking into this. Do you have any updates here? Any workarounds or bug reports I can follow for updates?

                        TeddyAstieT 1 Reply Last reply Reply Quote 0
                        • TeddyAstieT
                          TeddyAstie Vates 🪐 XCP-ng Team @Buckle8711
                          last edited by TeddyAstie

                          @Buckle8711 Hello,

                          I took a look but unfortunately, I haven't found a workaround for this.
                          I suspect the Illumos/OmniOS Xen PV drivers to be too old to work in current Xen, but we currently don't have a way to prevent those drivers from loading (e.g HVM-only (non-PVHVM) domains).

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

                            @TeddyAstie thank you for investigating.

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