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

CD drive not completely installed in XOA

Scheduled Pinned Locked Moved Xen Orchestra
16 Posts 3 Posters 2.8k 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.
  • A
    ashinobi
    last edited by 1 Mar 2022, 23:22

    Hi, Everyone.

    Please help me with an issue I encounter when running my first VM in XCP-NG & XOA. The iso repository is located in a SMB share. I found this forum post “Unable to start newly created VM; cd drive not completely installed warning message | XCP-ng and XO forum” that should be fixing this issue. I have successfully mounted the CIFS share in XCP-NG. I have mounted this using the option “Attach existing Storage Repository” in XCP-NG. My question is how can I find where it is mounted so I can check the permissions configured on each iso. I tried checking “/mnt”, “/media” and checking “/etc/fstab” but I didn’t find any information where it is mounted. Hope you guys can help me.

    1 Reply Last reply Reply Quote 0
    • O
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by 2 Mar 2022, 08:50

      Hi,

      I'm not sure to understand everything. Do you see the ISO SR in the list of SR? Are you using an official client to manage XCP-ng?

      A 1 Reply Last reply 2 Mar 2022, 10:58 Reply Quote 0
      • A
        ashinobi @olivierlambert
        last edited by ashinobi 3 Feb 2022, 12:00 2 Mar 2022, 10:58

        @olivierlambert

        Thank you for responding. My apologies for not stating my issue clearly. I'll try my best to explain my issue. I am still new with XCP-NG this is my first venture try.

        1. As of this moment I can see the iso files and was able to select ubuntu iso but beside it says "CD drive not completely installed"

        firefox_Npp3kB9Dyi.png

        1. I removed the SMB mount from XOA then followed the instruction in this forum post, where the responder connected the SMB share via XCP-NG configuration:

        https://xcp-ng.org/forum/topic/4118/unable-to-start-newly-created-vm-cd-drive-not-completely-installed-warning-message?_=1646217980911

        1. On the post as well it indicated that he change the permission so this is where my question is. I cannot find where xcp-ng mounted the share. My apologies if this a very noob question.
        1 Reply Last reply Reply Quote 0
        • O
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by 2 Mar 2022, 15:30

          1. This is normal until you got your first boot done 🙂 It shouldn't cause any harm 🙂 Consider this alert useless
          2. So it seems you have your ISO SR correctly working
          3. It should be mounted in /run/sr-mount/<SR UUID>. But ISO SR can be in read only, that's fine 🙂

          So in the end, can you boot the VM with Ubuntu ISO?

          A 1 Reply Last reply 2 Mar 2022, 19:15 Reply Quote 0
          • A
            ashinobi @olivierlambert
            last edited by ashinobi 3 Feb 2022, 21:04 2 Mar 2022, 19:15

            @olivierlambert

            Thanks for the information. In regards to your question the answer is no, if I ran VMGuest I get this error message:

            NO_HOSTS_AVAILABLE()

            This is a XenServer/XCP-ng error

            That is why I thought the issue is the CD is not properly mounted. I only have 1 hypervisor and this is my first VMGuest.

            Also, I am not sure if this will make any difference. I have the XOA installed on my desktop as a vmguest in my vmware workstation. Once I have finished setting up XCP-NG, I will create new image and move the XOA as vmguest of XCP-NG.

            1 Reply Last reply Reply Quote 0
            • O
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by 2 Mar 2022, 20:24

              NO_HOSTS_AVAILABLE() means there's no host able to start the VM. Can be for various reasons. Can you try to do a xe vm-start uuid=<VM UUID> from the host?

              A 1 Reply Last reply 2 Mar 2022, 20:41 Reply Quote 1
              • A
                ashinobi @olivierlambert
                last edited by ashinobi 3 Feb 2022, 21:48 2 Mar 2022, 20:41

                @olivierlambert

                Thank you so much for the help.

                Running the command the command "xe vm-start uuid=<VM UUID>" it indicated the following: "home-hypervisor: Cannot start here [Not enough free memory]

                After seeing this I have double check my VMGuest configuration, and it is set to 4TiB instead of 4GiB. I have corrected this and the VM started running. Again thank you so much for responding.

                1 Reply Last reply Reply Quote 0
                • O
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by 2 Mar 2022, 21:08

                  Good news then 🙂 I'd love to get the error message coming in XO, but I'm not sure why we can't have the details.

                  Ping @julien-f on this: why NO_HOSTS_AVAILABLE() is just coming without any more content in XO? Is it a XAPI limitation? Why we have more info in xe?

                  J 1 Reply Last reply 2 Mar 2022, 21:12 Reply Quote 0
                  • J
                    julien-f Vates 🪐 Co-Founder XO Team @olivierlambert
                    last edited by 2 Mar 2022, 21:12

                    @olivierlambert No idea without investigating, all that I can tell is that this error comes straight from the XAPI without any more info.

                    J 1 Reply Last reply 2 Mar 2022, 21:16 Reply Quote 0
                    • J
                      julien-f Vates 🪐 Co-Founder XO Team @julien-f
                      last edited by 2 Mar 2022, 21:16

                      I just did a quick test and neither VM.start(ref, false, false) nor Async.VM.start(ref, false, false) (which creates a task) gives any more info.

                      1 Reply Last reply Reply Quote 0
                      • O
                        olivierlambert Vates 🪐 Co-Founder CEO
                        last edited by olivierlambert 3 Feb 2022, 22:22 2 Mar 2022, 21:22

                        Got it @julien-f

                        If xe fails to boot the VM, it will call an extra function, doing a VM.assert_can_boot_here, and catching the failure to display it.

                        See https://github.com/xapi-project/xen-api/blob/47fae74032aa6ade0fc12e867c530eaf2a96bf75/ocaml/xapi-cli-server/cli_operations.ml#L3212 and https://github.com/xapi-project/xen-api/blob/47fae74032aa6ade0fc12e867c530eaf2a96bf75/ocaml/xapi-cli-server/cli_operations.ml#L2105

                        That would be an interesting XO feature 🙂

                        J 1 Reply Last reply 2 Mar 2022, 21:24 Reply Quote 1
                        • J
                          julien-f Vates 🪐 Co-Founder XO Team @olivierlambert
                          last edited by 2 Mar 2022, 21:24

                          @olivierlambert Nice, should be pretty easy to add! The only think I'm wondering is which host is it choosing to pass to assert_can_boot_here in case of a simple start on a multiple hosts pool. 🤔

                          J 1 Reply Last reply 2 Mar 2022, 21:25 Reply Quote 0
                          • O
                            olivierlambert Vates 🪐 Co-Founder CEO
                            last edited by 2 Mar 2022, 21:25

                            I had the exact same reaction 😄

                            1 Reply Last reply Reply Quote 0
                            • J
                              julien-f Vates 🪐 Co-Founder XO Team @julien-f
                              last edited by julien-f 3 Feb 2022, 22:26 2 Mar 2022, 21:25

                              From what I understand it appears to do it on all the hosts, which makes sense 👍

                              1 Reply Last reply Reply Quote 0
                              • O
                                olivierlambert Vates 🪐 Co-Founder CEO
                                last edited by 2 Mar 2022, 21:27

                                Indeed. So it's a pretty nice feature to have to enrich our logs. Is it possible to simply chain that in XO so we got the error with more details?

                                J 1 Reply Last reply 2 Mar 2022, 21:54 Reply Quote 0
                                • J
                                  julien-f Vates 🪐 Co-Founder XO Team @olivierlambert
                                  last edited by julien-f 3 Feb 2022, 22:59 2 Mar 2022, 21:54

                                  @olivierlambert Done: https://github.com/vatesfr/xen-orchestra/commit/33b45d2eda2ce6d8071541da246bdcfd06b133b8

                                  It's not perfect but that should help 🙂

                                  Example:

                                  vm.start
                                  {
                                    "id": "123e4f2b-498e-d0af-15ae-f835a1e9f59f",
                                    "bypassMacAddressesCheck": false,
                                    "force": false
                                  }
                                  {
                                    "errors": [
                                      "R620-L3: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)",
                                      "R620-L1: HOST_NOT_ENOUGH_FREE_MEMORY(216430280704, 18778341376)",
                                      "R620-L2: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)"
                                    ],
                                    "message": "",
                                    "name": "Error",
                                    "stack": "Error: 
                                      at Xapi._startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1358:15)
                                      at Xapi.startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1393:7)
                                      at Api.callApiMethod (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:307:20)"
                                  }
                                  
                                  2 julien-f committed 2 Mar 2022, 21:51 to vatesfr/xen-orchestra
                                  feat(xo-server): better info when failing to start a VM
                                  
                                  Fixes https://xcp-ng.org/forum/post/47329
                                  1 Reply Last reply Reply Quote 3
                                  3 out of 16
                                  • First post
                                    3/16
                                    Last post