XCP-ng

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. vmpr
    3. Posts
    V
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 18
    • Best 2
    • Controversial 0
    • Groups 0

    Posts made by vmpr

    • RE: Hub Template Debian 11 cloud init network configuration

      @fohdeesha thanks for the information, I've added the following to my cloud-init template:

      runcmd:
        # disable dhcp for eth0
        - [ sh, -c, sed -e '/iface eth0 inet dhcp/s/^/#/g' -i /etc/network/interfaces ]
      

      at the end of the installation I have a reboot of the machine anyway so I don't restart the network in between:

      power_state:
       delay: "+2" # minutes
       mode: reboot
       message: rebooting system after cloud-init configurations are finished
       timeout: 120 # seconds
      

      cheers and keep up the good work!
      Ringo

      posted in Xen Orchestra
      V
      vmpr
    • Hub Template Debian 11 cloud init network configuration

      Hi Team! thanks for your great work 🙂
      I have a question regarding the debian11 hub cloud-init template. maybe @fohdeesha is the right person?

      I am using this network configuration for deployment:

      network:
        version: 1
        config:
          - type: physical
            name: eth0
            subnets:
              - type: static
                address: 172.16.232.93/26
                gateway: 172.16.232.65
                dns_nameservers:
                  - 172.16.232.65
                dns_search:
                  - xx.xxxxxx.xx
      

      The Machine boots and gets an IP from DHCP and installs how it should, but it never changes to the configured IP address until I reboot the machine, but then it comes up with two IP-addresses:

      2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
          link/ether aa:90:ca:c4:15:c2 brd ff:ff:ff:ff:ff:ff
          inet 172.16.232.93/26 brd 172.16.232.127 scope global eth0
             valid_lft forever preferred_lft forever
          inet 172.16.232.121/26 brd 172.16.232.127 scope global secondary dynamic eth0
             valid_lft 541041sec preferred_lft 541041sec
          inet6 fe80::a890:caff:fec4:15c2/64 scope link
             valid_lft forever preferred_lft forever
      

      the one I configured with the YAML and also the DHCP IP address from the first boot.

      I can see these configurations:
      cloud-init network configuration file from YAML config

      root@XXX:~ cat /etc/network/interfaces.d/50-cloud-init
      # This file is generated from information provided by the datasource.  Changes
      # to it will not persist across an instance reboot.  To disable cloud-init's
      # network configuration capabilities, write a file
      # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
      # network: {config: disabled}
      auto lo
      iface lo inet loopback
      
      auto eth0
      iface eth0 inet static
          address 172.16.232.93/26
          dns-nameservers 172.16.232.65
          dns-search qa.oneserv.de
          gateway 172.16.232.65
      

      Debian standard network config file with DHCP enabled:

      root@XXX:~ cat /etc/network/interfaces
      # This file describes the network interfaces available on your system
      # and how to activate them. For more information, see interfaces(5).
      
      source /etc/network/interfaces.d/*
      
      # The loopback network interface
      auto lo
      iface lo inet loopback
      
      # The primary network interface
      allow-hotplug eth0
      iface eth0 inet dhcp
      

      Does anyone know what I have to do to get rid off the DHCP assigned IP address and how I can apply the configured network config instantly without having the DHCP assigned one or without rebooting after the installation?

      And what is the default user password for the debian or root user? i deploy keys so I can access the machine normally but if I have problems with network or sshd then I would like to login via xoa-console but don't have a pw 😞

      cheers, Ringo

      posted in Xen Orchestra
      V
      vmpr
    • RE: New Smart Backup failure

      great job guys on a saturday! I am just updating my xo but your response times are great, keep up the good work!

      posted in Xen Orchestra
      V
      vmpr
    • RE: New Smart Backup failure

      I've got the same error for a delta job since the 11th of March. cheers Ringo

      posted in Xen Orchestra
      V
      vmpr
    • RE: Updates announcements and testing

      @benjireis today I tested it but didn't reboot the host, was working after a toolstack restart. please integrate it into 8.2 LTS, a very useful feature, and we want to stay at 8.2 LTS. 👍

      posted in News
      V
      vmpr
    • RE: Backup error: "no writers left"

      @julien-f any ideas how to debug that?

      posted in Xen Orchestra
      V
      vmpr
    • RE: Backup error: "no writers left"

      @julien-f its a NFS remote

      posted in Xen Orchestra
      V
      vmpr
    • Backup error: "no writers left"

      Hi everyone, I've got the first time today an error with my backup:

      • 5 vms were successfully backuped
      • 2 didn't and failed with: Error: no writers left
      • I restarted those two vms and one finished successful but the other didn't, this is the log:
      {
        "data": {
          "mode": "delta",
          "reportWhen": "failure"
        },
        "id": "1621848907079",
        "jobId": "d3ada465-98aa-4f30-bf53-289d00249d17",
        "jobName": "delta_all",
        "message": "backup",
        "scheduleId": "5b2e2c96-2919-496f-9a4d-7db06fd28634",
        "start": 1621848907079,
        "status": "failure",
        "infos": [
          {
            "data": {
              "vms": [
                "61673574-80c8-ae18-c379-562cc38a7eaf",
                "1d2b0597-69c3-9a07-34ea-f45a801affad"
              ]
            },
            "message": "vms"
          }
        ],
        "tasks": [
          {
            "data": {
              "type": "VM",
              "id": "61673574-80c8-ae18-c379-562cc38a7eaf"
            },
            "id": "1621848910981",
            "message": "backup VM",
            "start": 1621848910981,
            "status": "failure",
            "tasks": [
              {
                "id": "1621848913457",
                "message": "snapshot",
                "start": 1621848913457,
                "status": "success",
                "end": 1621848918206,
                "result": "6053c653-1c21-12f6-6a4d-56419373bf9c"
              },
              {
                "data": {
                  "id": "f34266e4-aaf7-4e70-88d1-ae1b811b7e55",
                  "isFull": true,
                  "type": "remote"
                },
                "id": "1621848918208",
                "message": "export",
                "start": 1621848918208,
                "status": "failure",
                "tasks": [
                  {
                    "id": "1621848918254",
                    "message": "transfer",
                    "start": 1621848918254,
                    "status": "failure",
                    "end": 1621851676334,
                    "result": {
                      "errno": -122,
                      "code": "Unknown system error -122",
                      "syscall": "write",
                      "message": "Unknown system error -122: Unknown system error -122, write",
                      "name": "Error",
                      "stack": "Error: Unknown system error -122: Unknown system error -122, write"
                    }
                  }
                ],
                "end": 1621851676344,
                "result": {
                  "errno": -122,
                  "code": "Unknown system error -122",
                  "syscall": "write",
                  "message": "Unknown system error -122: Unknown system error -122, write",
                  "name": "Error",
                  "stack": "Error: Unknown system error -122: Unknown system error -122, write"
                }
              }
            ],
            "end": 1621851678754,
            "result": {
              "message": "no writers left",
              "name": "Error",
              "stack": "Error: no writers left\n    at VmBackup._callWriters (/opt/xo/xo-builds/xen-orchestra-202105071253/@xen-orchestra/backups/_VmBackup.js:118:13)\n    at async VmBackup._copyDelta (/opt/xo/xo-builds/xen-orchestra-202105071253/@xen-orchestra/backups/_VmBackup.js:190:5)\n    at async VmBackup.run (/opt/xo/xo-builds/xen-orchestra-202105071253/@xen-orchestra/backups/_VmBackup.js:371:9)"
            }
          },
      

      any ideas what this error means, what could be the root cause? I've googled and searched in the forum for it, but couldn't find anything 😞

      cheers, Ringo

      posted in Xen Orchestra
      V
      vmpr
    • RE: Error on Delta Backup - cannot read property "length" of undefined

      @olivierlambert yes I thought the same so I updated the code from the master again yesterday but didn't help 😞

      posted in Xen Orchestra
      V
      vmpr
    • RE: Error on Delta Backup - cannot read property "length" of undefined

      I had the same problem in my homelab - xo from sources, installed it the official way from the documentation. updated via git pull --ff-only 3 days ago. the backups are failing with the error message:

        "tasks": [
          {
            "data": {
              "type": "VM",
              "id": "abc2c07e-33e8-97e2-6724-3e69f837d0f7"
            },
            "id": "1617691268721:0",
            "message": "backup VM",
            "start": 1617691268721,
            "status": "failure",
            "tasks": [
              {
                "id": "1617691271853",
                "message": "snapshot",
                "start": 1617691271853,
                "status": "success",
                "end": 1617691328127,
                "result": "74c58079-3e89-53db-a770-6f3b936833b2"
              },
              {
                "id": "1617691328128",
                "message": "merge",
                "start": 1617691328128,
                "status": "failure",
                "end": 1617691328128,
                "result": {
                  "message": "Cannot read property 'length' of undefined",
                  "name": "TypeError",
                  "stack": "TypeError: Cannot read property 'length' of undefined\n    at /home/toor/xen-orchestra/@xen-orchestra/backups/_DeltaBackupWriter.js:114:31\n    at Zone.run (/home/toor/xen-orchestra/node_modules/node-zone/index.js:80:23)\n    at /home/toor/xen-orchestra/node_modules/node-zone/index.js:89:19\n    at Function.fromFunction (/home/toor/xen-orchestra/@xen-orchestra/backups/_syncThenable.js:20:27)\n    at SyncThenable.fulfilledThen [as then] (/home/toor/xen-orchestra/@xen-orchestra/backups/_syncThenable.js:2:50)\n    at TaskLogger.run (/home/toor/xen-orchestra/@xen-orchestra/backups/Task.js:77:10)\n    at Object.run (/home/toor/xen-orchestra/@xen-orchestra/backups/Task.js:157:17)\n    at DeltaBackupWriter._deleteOldEntries (/home/toor/xen-orchestra/@xen-orchestra/backups/_DeltaBackupWriter.js:108:17)\n    at Array.<anonymous> (/home/toor/xen-orchestra/@xen-orchestra/backups/_VmBackup.js:150:70)\n    at Function.from (<anonymous>)"
                }
              }
            ],
            "end": 1617691344109,
            "result": {
              "message": "Cannot read property 'length' of undefined",
              "name": "TypeError",
              "stack": "TypeError: Cannot read property 'length' of undefined\n    at /home/toor/xen-orchestra/@xen-orchestra/backups/_DeltaBackupWriter.js:114:31\n    at Zone.run (/home/toor/xen-orchestra/node_modules/node-zone/index.js:80:23)\n    at /home/toor/xen-orchestra/node_modules/node-zone/index.js:89:19\n    at Function.fromFunction (/home/toor/xen-orchestra/@xen-orchestra/backups/_syncThenable.js:20:27)\n    at SyncThenable.fulfilledThen [as then] (/home/toor/xen-orchestra/@xen-orchestra/backups/_syncThenable.js:2:50)\n    at TaskLogger.run (/home/toor/xen-orchestra/@xen-orchestra/backups/Task.js:77:10)\n    at Object.run (/home/toor/xen-orchestra/@xen-orchestra/backups/Task.js:157:17)\n    at DeltaBackupWriter._deleteOldEntries (/home/toor/xen-orchestra/@xen-orchestra/backups/_DeltaBackupWriter.js:108:17)\n    at Array.<anonymous> (/home/toor/xen-orchestra/@xen-orchestra/backups/_VmBackup.js:150:70)\n    at Function.from (<anonymous>)"
            }
          },
      

      I created a new delta backup job and it works now, deleted the old one - but its not the best solution, maybe something is incompatible with the last releases in the master branch to old backup jobs?

      hope to help other people with a quick workaround, but hopefully the xoa guys can look into that - great job btw!

      cheers, Ringo

      posted in Xen Orchestra
      V
      vmpr
    • RE: XO CE migrate fails for VM - "Internal Error"

      @olivierlambert any idea what could be the problem?

      posted in Xen Orchestra
      V
      vmpr
    • RE: XO CE migrate fails for VM - "Internal Error"

      thanks @gn_ro - but Nah that's not the problem, its a 6TB storage and 1TB ist used ... 5TB space should be enough. I am also moving three vms at the same time via xcp-ng centre and cli, as XOA does ... that's the limit of how many VMS you can move simultaneous from local storage to local storage.

      posted in Xen Orchestra
      V
      vmpr
    • RE: XO CE migrate fails for VM - "Internal Error"

      I could do that sure, is there a way to use the xoa ce for that support tunnel?
      I dug deeper into the problem and tested a little bit:

      • removed all the snapshots from the above-mentioned VM and wow - no you can migrate it via XOA from local storage to local storage
      • I removed all snapshots from my other VMS, besides the one from the nightly xoa backup job
        • didn't work -> every VM logged the same error 😞
      • I removed all snapshots from all VMs
        • 👍 now it works to migrate all the VMs via XOA 👎 but that is not really a solution, because xoa backup runs every night and i don't want to remove all snapshots from the VMs every time I move them to the other host

      It also doesn't explain why the move works with snapshots via XCP-ng Center and CLI 😞

      any thoughts from your side?
      thanks, guys! Ringo

      posted in Xen Orchestra
      V
      vmpr
    • RE: XO CE migrate fails for VM - "Internal Error"

      yes it has three normal snapshots

      posted in Xen Orchestra
      V
      vmpr
    • RE: XO CE migrate fails for VM - "Internal Error"

      thy for the reply Olivier - just checked, no cd inserted or DVD drive connected to VM - its the same VM every time for all different migrate methods

      posted in Xen Orchestra
      V
      vmpr
    • XO CE migrate fails for VM - "Internal Error"

      Re: XO CE migrate fails for WinServer 2019 VM - "Internal Error"

      Hi everyone, I have a similar problem like the earlier thread. My xcp-ng 8.0 pool has two members and the VMs are on local storage. so every time I update ich have to migrate all the VMS from one server to the other. with XOA it should be no problem with some clicks, but it doesn't work 😞

      when I move a VM via xoa I can see how it moves data from one host to the other and then I get this error:

      vm.migrate
      {
        "mapVdisSrs": {
          "5c9b25da-b5a1-4050-b8ed-4b261cbb0339": "c34046c7-658d-66c2-fdec-292d29a0681c",
          "be0a7dfd-6950-4fef-9965-342a05a06093": "c34046c7-658d-66c2-fdec-292d29a0681c"
        },
        "migrationNetwork": "0a6c51c6-93d9-d9f9-2a76-e8c2330c4448",
        "targetHost": "cc689219-af8a-44e0-b096-23da85534502",
        "vm": "acef4db1-2087-58c2-f5ee-6d48beb34fb1"
      }
      {
        "code": 21,
        "data": {
          "objectId": "acef4db1-2087-58c2-f5ee-6d48beb34fb1",
          "code": "INTERNAL_ERROR"
        },
        "message": "operation failed",
        "name": "XoError",
        "stack": "XoError: operation failed
          at factory (/home/toor/xen-orchestra/packages/xo-common/src/api-errors.js:21:32)
          at /home/toor/xen-orchestra/packages/xo-server/src/api/vm.js:520:15
          at runMicrotasks (<anonymous>)
          at processTicksAndRejections (internal/process/task_queues.js:97:5)
          at Object.migrate (/home/toor/xen-orchestra/packages/xo-server/src/api/vm.js:509:3)
          at Api.callApiMethod (/home/toor/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:291:20)"
      }
      

      in XCP-ng Center it shows this error for that move:

      "Failed","Migrating VM 'it-dd-prx'
      Internal error: Storage_error ([S(Vdi_does_not_exist);S(57b54124-67fe-4a86-9e5c-f2a1e1bb49c1)])
      Time: 00:04:14","amy","Aug 3, 2020 5:36 AM"
      

      If I do the same move via XCP-ng Center, it works without problems - but you can't move more than three VMs at the same time, so that's not really an option.

      When I do the migrate via CLI command it also works without any problems:
      [07:31 sheldon ~]# xe vm-migrate vm=it-dd-prx host=amy remote-master=10.13.38.200 remote-username=root remote-password=*************

      I guess there is something wrong with the API call from XOA to migrate the VMs from local storage to local storage - if you need more informations please let me know!

      thanks, Ringo

      posted in Xen Orchestra
      V
      vmpr
    • RE: [Beta Release] XCP-ng Windows Client tools 8.2.1-beta1

      @olivierlambert thanks for your reply, but after refresh and disconnect/connect its still the same 😞

      posted in Development
      V
      vmpr
    • RE: [Beta Release] XCP-ng Windows Client tools 8.2.1-beta1

      @borzel thanks for the hint, now it works also fine for me, in xcp-ng center it says:

      IO optimized
      Management Agent installed

      but in XenOrchestra it still says: "Xen tools version Not installed"

      what should we do to get this fixed?

      cheers, Ringo

      posted in Development
      V
      vmpr