XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. adrianvanderwal
    A
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 6
    • Groups 0

    adrianvanderwal

    @adrianvanderwal

    0
    Reputation
    1
    Profile views
    6
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    adrianvanderwal Unfollow Follow

    Latest posts made by adrianvanderwal

    • RE: Unable to attach empty optical drive to VM.

      I've managed to at least solve part of my issue.

      Using this article, I managed to pull together the information I needed in order to remove the Optical Drive from the VM.

      It refereced xe vbd-list. I found the manpage for that command, and noted that I could get the information I needed to remove the drive.

      For future me to reference - because I know I'll somehow do this again in the future.

      1. List all Virtual Block Devices (vbd's) associated to the vm (you can do this by vm-uuid, or vm-label)
      [20:42 xcp-ng-1 ~]# xe vbd-list vm-uuid="3eb63bb4-29d1-f3a7-44a1-37fdb3711454" params="all"
      

      Output should show the following.

      uuid ( RO)                        : 7443c2f0-7c04-ab88-ccfd-29f0831c1aa0
                           vm-uuid ( RO): 3eb63bb4-29d1-f3a7-44a1-37fdb3711454
                     vm-name-label ( RO): veeam01
                          vdi-uuid ( RO): 7821ef6d-4778-4478-8cf4-e950577eaf4f
                    vdi-name-label ( RO): SCSI 2:0:0:0
                allowed-operations (SRO): attach; eject
                current-operations (SRO):
                             empty ( RO): false
                            device ( RO):
                        userdevice ( RW): 3
                          bootable ( RW): false
                              mode ( RW): RO
                              type ( RW): CD
                       unpluggable ( RW): false
                currently-attached ( RO): false
                        attachable ( RO): <expensive field>
                      storage-lock ( RO): false
                       status-code ( RO): 0
                     status-detail ( RO):
                qos_algorithm_type ( RW):
              qos_algorithm_params (MRW):
          qos_supported_algorithms (SRO):
                      other-config (MRW):
                       io_read_kbs ( RO): <expensive field>
                      io_write_kbs ( RO): <expensive field>
      
      
      uuid ( RO)                        : 4d0f16c4-9cf5-5df5-083b-ec1222f97abc
                           vm-uuid ( RO): 3eb63bb4-29d1-f3a7-44a1-37fdb3711454
                     vm-name-label ( RO): veeam01
                          vdi-uuid ( RO): 3f89c727-f471-4ec3-8a7c-f7b7fc478148
                    vdi-name-label ( RO): [ESXI]veeam01-flat.vmdk
                allowed-operations (SRO): attach
                current-operations (SRO):
                             empty ( RO): false
                            device ( RO): xvda
                        userdevice ( RW): 0
                          bootable ( RW): false
                              mode ( RW): RW
                              type ( RW): Disk
                       unpluggable ( RW): false
                currently-attached ( RO): false
                        attachable ( RO): <expensive field>
                      storage-lock ( RO): false
                       status-code ( RO): 0
                     status-detail ( RO):
                qos_algorithm_type ( RW):
              qos_algorithm_params (MRW):
          qos_supported_algorithms (SRO):
                      other-config (MRW): owner:
                       io_read_kbs ( RO): <expensive field>
                      io_write_kbs ( RO): <expensive field>
      
      1. Look for the device with type ( RW): CD. Take that uuid. In this case, the uuid was 7443c2f0-7c04-ab88-ccfd-29f0831c1aa0.
      2. Destroy the vbd:
      xe vbd-destroy uuid="7443c2f0-7c04-ab88-ccfd-29f0831c1aa0"
      

      Once this was done, the vm started without issue.

      posted in XCP-ng
      A
      adrianvanderwal
    • Unable to attach empty optical drive to VM.

      While attempting to attach an ISO to a VM, I have accidently attached the physical optical drive to the VM:
      0307f49c-19e3-4bc9-a2c9-5dbb7f0cfbaa-image.png
      Once this was selected an exclaimation alert appeared, indicating that I could not access the disk until the vm was stopped and started.

      There were no ISO's in the ISO Repository at this stage, however, I added one at this point, and I could not change the selection to an ISO from the list.

      I attempted a reboot from within the vm, it started ok, and the alert persisted. On stop/start, the vm failed to start.

      [23:24 xcp-ng-1 ~]# xe vm-start uuid="3eb63bb4-29d1-f3a7-44a1-37fdb3711454"
      Error code: SR_BACKEND_FAILURE_456
      Error parameters: , Unable to attach empty optical drive to VM.,
      
      1. How do I remove the optical disk so I can boot my vm?
      2. Why couldn't I change the selected ISO?

      Priority is low, as this is not a critical vm.

      Edit:
      Environment information
      XCP-ng Version: v8.3.0

      posted in XCP-ng
      A
      adrianvanderwal
    • RE: Unable to quick deploy XOA on 8.2.1

      Confirmed working with the new version.

      posted in Xen Orchestra
      A
      adrianvanderwal
    • RE: Unable to quick deploy XOA on 8.2.1

      Thanks @olivierlambert.
      I have managed to deploy XOA.

      Again, thanks for the prompt response.

      posted in Xen Orchestra
      A
      adrianvanderwal
    • RE: Unable to quick deploy XOA on 8.2.1

      Not a problem @Danp; thanks for the prompt response.

      posted in Xen Orchestra
      A
      adrianvanderwal
    • Unable to quick deploy XOA on 8.2.1

      I've just completed a clean installation of XCP-NG 8.2.1, and have attempted to quick deploy XOA via the web ui, cli script, and the https://xen-orchestra.com/#!/xoa interface

      All methods result in the following error:

      Importing XOA VM...
      The value given is invalid
      field: bridge
      value: xapi1
      

      452bcd74-159f-4d03-b7fd-9ac082b3d2fb-image.png

      I've attempted to deploy using a static address, as well as using DHCP; both result in the same error.

      Output of xe network-list:

      [11:33 xcp-ng-1 ~]# xe network-list
      uuid ( RO)                : e7c59c08-1eaf-bc2a-9f33-461076a6920b
                name-label ( RW): Pool-wide network associated with eth3
          name-description ( RW):
                    bridge ( RO): xenbr3
      
      
      uuid ( RO)                : b1d3e149-af9b-bd46-7d5d-bb17d0f090ac
                name-label ( RW): Pool-wide network associated with eth2
          name-description ( RW):
                    bridge ( RO): xenbr2
      
      
      uuid ( RO)                : 7af0b5ac-f1c9-98c3-24ca-576c6b713953
                name-label ( RW): Pool-wide network associated with eth0
          name-description ( RW):
                    bridge ( RO): xenbr0
      
      
      uuid ( RO)                : 962de358-592f-c66a-1d35-ef8f5d01db25
                name-label ( RW): Host internal management network
          name-description ( RW): Network on which guests will be assigned a private link-local IP address which can be used to talk XenAPI
                    bridge ( RO): xenapi
      
      
      uuid ( RO)                : 08057bb2-1105-cc3b-d86e-b21f23f8bad3
                name-label ( RW): Pool-wide network associated with eth1
          name-description ( RW):
                    bridge ( RO): xenbr1
      

      Output of ifconfig -a

      [11:34 xcp-ng-1 ~]# ifconfig -a
      eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
              ether 28:80:23:ae:da:d4  txqueuelen 1000  (Ethernet)
              RX packets 0  bytes 0 (0.0 B)
              RX errors 0  dropped 0  overruns 0  frame 0
              TX packets 0  bytes 0 (0.0 B)
              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
              device interrupt 32
      
      eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
              ether 28:80:23:ae:da:d5  txqueuelen 1000  (Ethernet)
              RX packets 1720  bytes 1177484 (1.1 MiB)
              RX errors 0  dropped 0  overruns 0  frame 0
              TX packets 533  bytes 144859 (141.4 KiB)
              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
              device interrupt 36
      
      eth2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
              ether 28:80:23:ae:da:d6  txqueuelen 1000  (Ethernet)
              RX packets 0  bytes 0 (0.0 B)
              RX errors 0  dropped 0  overruns 0  frame 0
              TX packets 0  bytes 0 (0.0 B)
              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
              device interrupt 32
      
      eth3: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
              ether 28:80:23:ae:da:d7  txqueuelen 1000  (Ethernet)
              RX packets 0  bytes 0 (0.0 B)
              RX errors 0  dropped 0  overruns 0  frame 0
              TX packets 0  bytes 0 (0.0 B)
              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
              device interrupt 36
      
      lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
              inet 127.0.0.1  netmask 255.0.0.0
              loop  txqueuelen 1000  (Local Loopback)
              RX packets 192  bytes 161240 (157.4 KiB)
              RX errors 0  dropped 0  overruns 0  frame 0
              TX packets 192  bytes 161240 (157.4 KiB)
              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
      
      ovs-system: flags=4098<BROADCAST,MULTICAST>  mtu 1500
              ether 26:ce:04:47:57:c7  txqueuelen 1000  (Ethernet)
              RX packets 0  bytes 0 (0.0 B)
              RX errors 0  dropped 0  overruns 0  frame 0
              TX packets 0  bytes 0 (0.0 B)
              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
      
      xenbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
              ether 28:80:23:ae:da:d4  txqueuelen 1000  (Ethernet)
              RX packets 0  bytes 0 (0.0 B)
              RX errors 0  dropped 0  overruns 0  frame 0
              TX packets 0  bytes 0 (0.0 B)
              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
      
      xenbr1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
              inet 172.42.10.8  netmask 255.255.255.0  broadcast 172.42.10.255
              ether 28:80:23:ae:da:d5  txqueuelen 1000  (Ethernet)
              RX packets 1423  bytes 1129882 (1.0 MiB)
              RX errors 0  dropped 0  overruns 0  frame 0
              TX packets 515  bytes 145403 (141.9 KiB)
              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
      
      xenbr2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
              ether 28:80:23:ae:da:d6  txqueuelen 1000  (Ethernet)
              RX packets 0  bytes 0 (0.0 B)
              RX errors 0  dropped 0  overruns 0  frame 0
              TX packets 0  bytes 0 (0.0 B)
              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
      
      xenbr3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
              ether 28:80:23:ae:da:d7  txqueuelen 1000  (Ethernet)
              RX packets 0  bytes 0 (0.0 B)
              RX errors 0  dropped 0  overruns 0  frame 0
              TX packets 0  bytes 0 (0.0 B)
              TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
      
      posted in Xen Orchestra
      A
      adrianvanderwal