@olivierlambert said in Increase simultaneous snapshot download from 2:

In /etc/xo-server/config.toml. Don't forget to restart xo-server after the modification

Awesome. Do changes in /etc/xo-server/config.toml persist when XOA upgrades itself?

@julien-f said in Increase simultaneous snapshot download from 2:

@nodesocket You can override this setting in your config file: https://github.com/vatesfr/xen-orchestra/blob/c4d96fbc492c86d7d0365efcbe13bd0b6dd2f9a0/packages/xo-server/config.toml#L132

If I am using the managed XOA appliance, how do I modify this value?

I've noticed when I go to export VM snapshots in Xen Orchestra, I can only seem to queue up two simultaneous snapshot downloads in Chrome. Further snapshot downloads seem to block and eventually fail with:

404

Cannot GET /api/VTX6gssNxuwfkRMQm43CLHcFMVgGkU9d_iuWD6p9FTU/20200819T234722Z%20-%20kube-worker-nmAsp.xva

Is this a setting or intentional behavior? Would be nice to be able to download 3,4, or 5 simultaneous snapshot exports in one go in Chrome.

Note: I am using the free version, not sure if the paid version has a better way to do this.

Nevermind I got it back up. Somehow the disk boot was turned off in boot order. Either I made an error when I changed it and turned off disk instead of network, or perhaps some sort of UI bug in XOA. The most likely thing is that I made an error and toggled off disk instead of network.

Thank you so much for the help and assistance, I really appreciate it.

@olivierlambert said in Turned off network boot for XOA in advanced and now broken:

curl -sS https://xoa.io/deploy | bash

I was able to create a fresh new xoa instance using the web interface installer. When I tried to start my existing (broken) xoa again it tries to start, but then went to halted. I went into the console and see:

Any ideas now?

So sorry, but how do I deploy another XOA? The web form https://xen-orchestra.com/#!/xoa won't work as I don't expose XCP-NG to the public. Is there a command to deploy another XOA from the dom0 host of XCP-NG?

I have triedd running:

xe vm-start uuid=e44ffb7e-334d-06e7-dd88-c25b580a69ae

The command, completes and I see the following for a little bit:

[11:55 localhost ~]# xe vm-list uuid=e44ffb7e-334d-06e7-dd88-c25b580a69ae
uuid ( RO)           : e44ffb7e-334d-06e7-dd88-c25b580a69ae
     name-label ( RW): XOA
    power-state ( RO): running

However after about 15 seconds, it reverts to:

[11:55 localhost ~]# xe vm-list uuid=e44ffb7e-334d-06e7-dd88-c25b580a69ae
uuid ( RO)           : e44ffb7e-334d-06e7-dd88-c25b580a69ae
     name-label ( RW): XOA
    power-state ( RO): halted

Is there a way to view the logs and inspect what is causing this? The reason I suspect it's the network boot toggle, is this is the only setting I changed. XOA has been running fine for nearly 6 months before this.

It appears that I broke Xen Orchestra by toggling off "Network Boot" in the advanced options of the VM. I have restarted the entire host multiple times and all the VM's come up except Xen Orchestra (xoa).

I am able to ssh into root @ dom0. What file or command can I modify to re-enable network boot for the Xen Orchesta VM?

uuid ( RO)           : e44ffb7e-334d-06e7-dd88-c25b580a69ae
     name-label ( RW): xoa
    power-state ( RO): halted

Ah, the problem is the command is xe vbd-destroy uuid=7dbe255d-8b76-04fe-e5ba-a97523e0445e.

After running it though, it seems to have deleted all the disks from the VM.

xe vm-disk-list uuid=4aef7b34-2e7e-53c5-62e3-331be8151287

Shows 0 disks now.

@olivierlambert said in Imported VM fails to start with VDI_MISSING:

xe vdb-destroy uuid=

Humm, getting unknown command vdb-destroy.

[23:10 localhost ~]# xe vm-disk-list uuid=4aef7b34-2e7e-53c5-62e3-331be8151287
Disk 0 VBD:
uuid ( RO)             : 7dbe255d-8b76-04fe-e5ba-a97523e0445e
    vm-name-label ( RO): Ubuntu server 18.04-2 base
       userdevice ( RW): 0


Disk 0 VDI:
uuid ( RO)             : 193f9105-e23c-4fe7-a8ae-40bed37ede4e
       name-label ( RW): base
    sr-name-label ( RO): Local storage
     virtual-size ( RO): 10737418240


[23:11 localhost ~]# xe vdb-destroy uuid=7dbe255d-8b76-04fe-e5ba-a97523e0445e
Unknown command: vdb-destroy
For usage run: 'xe help'