Subcategories

• Management

  VMs, hosts, pools, networks and all other usual management tasks.

  115
  Topics
  851
  Posts

  T

  Hi all,

  I wanted to remove a host from my xen orchestra install. The only vm on this host was xen orchestra itself. I wanted to migrate it to another host. So I used the built-in migrate function in XO.

  For a long time the migrate was stuck on 89%. Later I lose the connection to it. Also a ping is not working. I looked in my router and also there was no arp anymore. So the whole vm is not on the network anymore. What it's state is, I'am not sure.

  When I run:
  xe vm-list on the original host I see the vm still in running state.

  When I run:
  xe vdi-list on the new destination host I don't see the new disk for it

  Then I tried to stop the current vm on the original host with command:
  xe vm-shutdown vm=xen\ orchestra force=true
  I get an error stating:
  The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Object with type VM and id b3b0ba0b-6534-1935-23fa-c512591debd0/config does not exist in xenopsd

  Has anybody an idea how I can recover my xen orchestra vm.

  If possible I want to fix the current vm. If needed, I have full vm backup and xo config backup from the xen orchestra vm. I can restore them but I have created new vm's after the backup. What will happen to the newly created vm's?

• Advanced features

  ACLs, Self-service, Cloud-init, Load balancing...

  40
  Topics
  420
  Posts

  O

  Great!

  @jkissane please open a new thread if you want to continue discussing your issue 🙂

• Backup

  All XO backup features: full and incremental, replication, mirrors...

  119
  Topics
  999
  Posts

  D

  Thanks. Back in Business. I did that but unzipped the file first. That did not work. Dropping the xo-config in as the zip folder, worked as it should. Thanks again.

• REST API

  Everything related to Xen Orchestra's REST API

  22
  Topics
  141
  Posts

  J

  @Rhodderz I'm not able to reproduce the issue on my side.

  I successfully filtered VMs by a /foo tag and was able to filter for it (tags:/^\/foo$/) in the REST API, either by using filter=tags%3A%2F%5E%5C%2Ffoo%24%2F (encoded with encodeURIComponent()) or by using filter=tags:/%5E%5C/foo$/ (encoded using encodeURI() which does not encode / or :).

• Infrastructure as Code

  Terraform, Packer or any tool to do IaC

  13
  Topics
  119
  Posts

  N

  Hello all,

  I'm running into a persistent issue when following the blog steps.

  ansible-inventory -i ./my.xen_orchestra.yaml --list [WARNING]: * Failed to parse /home/cstreb/working/ansible/my.xen_orchestra.yaml with yaml plugin: Plugin configuration YAML file, not YAML inventory [WARNING]: * Failed to parse /home/cstreb/working/ansible/my.xen_orchestra.yaml with ini plugin: Invalid host pattern 'plugin:' supplied, ending in ':' is not allowed, this character is reserved to provide a port. [WARNING]: Unable to parse /home/cstreb/working/ansible/my.xen_orchestra.yaml as an inventory source [WARNING]: No inventory was parsed, only implicit localhost is available

  contents of my.xen-orchestra.yaml file is as follows

  plugin: community.general.xen_orchestra api_host: 192.168.2.203 #(XOA box?) Needs :443? user: <user> password: <pass>

  Other relevant details
  I'm using XO from source running on a different machine then my xcp-ng

  This is my first time trying ansible at all so I may have missed a key step. Any help is appreciated.