julien-f 0k, is there a specific rule on the format of this identifier?

When I create a backup, I set an email address for reporting but that address or notification setting) is not present in the JSON, why and how can I set it ?

For rolling snapshots, the content is 0k (same identifier in both settings and schedule):

{
  "name": "rolling snapshots",
  "mode": "full",
  "schedules": {
    "gbkk1mbemhg": {
      "cron": "15 12 * * *",
      "enabled": true,
      "name": "daily rolling snapshots",
      "timezone": "Europe/Rome"
    }
  },
  "settings": {
    "": {
      "concurrency": 2,
      "nRetriesVmBackupFailures": 3,
      "timeout": 7200000,
      "offlineSnapshot": false,
      "checkpointSnapshot": true
    },
    "gbkk1mbemhg": {
      "healthCheckSr": "ac595bf5-ca14-586e-6f89-9e4e884043eb",
      "healthCheckVmsWithTags": [],
      "snapshotRetention": 2
    }
  },
  "vms": {
    "id": {
      "__or": [
        "64adb2e9-e0f3-9e70-b08f-7c8653415053",
        "aaf9e807-3ee9-37ff-05ec-cf782ba74d56",
        "7cd276ae-b7df-06d8-3da8-48262750051d",
        "9ccfcd0c-a35e-7f45-a0d2-19db678291f1",
        "42afaaea-ada4-fb7f-dc55-f62a51a6997a",
        "54b97ba5-9858-a563-e02f-89b0a6c450a1",
        "9524834a-3577-4445-54c6-1c786775749d"
      ]
    }
  }
}

Ok for the VM backup using:
{
  "name": "vm backups",
  "mode": "full",
  "compression": "zstd",
  "schedules": {
    "fdi73l44ewf": {
      "cron": "40 12 * * 6",
      "enabled": true,
      "name": "weekly vm backups",
      "timezone": "Europe/Rome"
    }
  },
  "settings": {
    "": {
      "concurrency": 2,
      "nRetriesVmBackupFailures": 3,
      "timeout": 7200000,
      "offlineSnapshot": false,
      "checkpointSnapshot": true
    },
    "fdi73l44ewf": {
      "exportRetention": 1,
      "healthCheckSr": "ac595bf5-ca14-586e-6f89-9e4e884043eb",
      "healthCheckVmsWithTags": []
    }
  },
  "remotes": {
    "id": "40e5ecde-f12f-43c7-befd-c1f0a76e8a25"
  },
  "vms": {
    "id": {
      "__or": [
        "64adb2e9-e0f3-9e70-b08f-7c8653415053",
        "aaf9e807-3ee9-37ff-05ec-cf782ba74d56",
        "7cd276ae-b7df-06d8-3da8-48262750051d",
        "9ccfcd0c-a35e-7f45-a0d2-19db678291f1",
        "42afaaea-ada4-fb7f-dc55-f62a51a6997a",
        "54b97ba5-9858-a563-e02f-89b0a6c450a1",
        "9524834a-3577-4445-54c6-1c786775749d"
      ]
    }
  }
}

julien-f Hi Julien, I've just tested to create a backup job for metadata and got this debugging information.
For schedule and settings, what is the meaning of the key: 'bavyvq5rapl' ?
See the details below.
Thanks for your support.

{
  "name": "metadata backup",
  "pools": {
    "id": "c50afa00-46e5-aa4a-9299-31e3315591b5"
  },
  "remotes": {
    "id": "40e5ecde-f12f-43c7-befd-c1f0a76e8a25"
  },
  "schedules": {
    "bavyvq5rapl": {
      "cron": "0 12 * * *",
      "name": "daily metadata backup",
      "timezone": "Europe/Rome"
    }
  },
  "settings": {
    "bavyvq5rapl": {
      "retentionPoolMetadata": 2,
      "retentionXoMetadata": 2
    }
  },
  "xoMetadata": true
}

julien-f Merci, I'll try and let you know.

julien-f Thanks Julien, I didn't know that.
0k, if I understand correctly, the debug mode will show the rest methods not the calls ro the xo-cli, is that correct? Maybe the parameters are identical?

Best regards,
davide

olivierlambert merci Olivier

Hi,

I'm trying to use xo-cli to create jobs and schedules but without succes due to a lack of documentation.

Someone can help me on writing commands for:

• metadataBackup.createJob
• backupNg.createJob
  I'll use these commands with a specific remote and a retention to backup metadata, do snapshots and full vm backups.

The job is created with a schedules parameters, do I need to create a schedule before ? What I understood is that the schedule.create method requires a jobId parameter.

Thanks a lot.

Finally, I follow an existing topic and configure nut-server on the hypervisor to access the ups via usb.
I know that Olivier is not fully aligned with the fact that the host is modified but IMO it is an acceptable change on my XCP-NG host.

infodavid Finally, I follow an existing topic and configure nut-server on the hypervisor to access the ups via usb.
I know that Olivier is not fully aligned with the fact that the host is modified but IMO it is an acceptable change on my XCP-NG host.

manilx 0k. The device is an ups so I'll try first to install a server software on the hypervisor. I'm not very enthusiastic about adding another system just to plug that ups.

manilx so, solutions are:

• use a client / server solution perhaps on another system,
• Install some software directly on the hypervisor.

manilx did you try to install the server part on the hypervisor? Is there a free plan for the software?

uwood Smart workaround. Unfortunately you have to pay for VirtualHere and use another system to connect the device. It will be nice to have the USB devices working on the hypervisor.

krakers Thanks for your answer. The behavior is very strange, the device is attached on start of the vm but status changed to 'not attached' after boot of the vm, few seconds later.

For information, herunder are the parameters of the vm:

                        name-label ( RW): xoa
                  name-description ( RW): Xen Orchestra virtual Appliance compiled with full features
                      user-version ( RW): 2
                     is-a-template ( RW): false
               is-default-template ( RW): false
                     is-a-snapshot ( RO): false
                       snapshot-of ( RO): <not in database>
                         snapshots ( RO): 
                     snapshot-time ( RO): 19700101T00:00:00Z
                     snapshot-info ( RO): 
                            parent ( RO): <not in database>
                          children ( RO): 
                 is-control-domain ( RO): false
                       power-state ( RO): running
                     memory-actual ( RO): 2469601280
                     memory-target ( RO): 2469605376
                   memory-overhead ( RO): 24117248
                 memory-static-max ( RW): 2469606195
                memory-dynamic-max ( RW): 2469606195
                memory-dynamic-min ( RW): 644245094
                 memory-static-min ( RW): 268435456
                  suspend-VDI-uuid ( RW): <not in database>
                   suspend-SR-uuid ( RW): ac595bf5-ca14-586e-6f89-9e4e884043eb
                      VCPUs-params (MRW): weight: 256
                         VCPUs-max ( RW): 2
                  VCPUs-at-startup ( RW): 2
            actions-after-shutdown ( RW): Destroy
              actions-after-reboot ( RW): Restart
               actions-after-crash ( RW): Restart
                     console-uuids (SRO): a4f59f75-2a3e-9bab-ba21-84919893a448
                               hvm ( RO): true
                          platform (MRW): timeoffset: -30; usb: True; device-model: qemu-upstream-compat; vga: cirrus; secureboot: false; videoram: 8; hpet: true; nx: true; pae: true; apic: true; viridian: false; acpi: 1; device_id: 0001
                allowed-operations (SRO): changing_dynamic_range; changing_VCPUs_live; hard_reboot; hard_shutdown; clean_reboot; clean_shutdown; pause
                current-operations (SRO): 
                blocked-operations (MRW): destroy: true
               allowed-VBD-devices (SRO): 2; 4; 5; 6; 7; 8; 9; 10; 11; 12; 13; 14; 15; 16; 17; 18; 19; 20; 21; 22; 23; 24; 25; 26; 27; 28; 29; 30; 31; 32; 33; 34; 35; 36; 37; 38; 39; 40; 41; 42; 43; 44; 45; 46; 47; 48; 49; 50; 51; 52; 53; 54; 55; 56; 57; 58; 59; 60; 61; 62; 63; 64; 65; 66; 67; 68; 69; 70; 71; 72; 73; 74; 75; 76; 77; 78; 79; 80; 81; 82; 83; 84; 85; 86; 87; 88; 89; 90; 91; 92; 93; 94; 95; 96; 97; 98; 99; 100; 101; 102; 103; 104; 105; 106; 107; 108; 109; 110; 111; 112; 113; 114; 115; 116; 117; 118; 119; 120; 121; 122; 123; 124; 125; 126; 127; 128; 129; 130; 131; 132; 133; 134; 135; 136; 137; 138; 139; 140; 141; 142; 143; 144; 145; 146; 147; 148; 149; 150; 151; 152; 153; 154; 155; 156; 157; 158; 159; 160; 161; 162; 163; 164; 165; 166; 167; 168; 169; 170; 171; 172; 173; 174; 175; 176; 177; 178; 179; 180; 181; 182; 183; 184; 185; 186; 187; 188; 189; 190; 191; 192; 193; 194; 195; 196; 197; 198; 199; 200; 201; 202; 203; 204; 205; 206; 207; 208; 209; 210; 211; 212; 213; 214; 215; 216; 217; 218; 219; 220; 221; 222; 223; 224; 225; 226; 227; 228; 229; 230; 231; 232; 233; 234; 235; 236; 237; 238; 239; 240; 241; 242; 243; 244; 245; 246; 247; 248; 249; 250; 251; 252; 253; 254
               allowed-VIF-devices (SRO): 1; 2; 3; 4; 5; 6
                    possible-hosts ( RO): 8daf76e4-32ac-4941-bb6b-cf189fbacf80
                       domain-type ( RW): hvm
               current-domain-type ( RO): hvm
                   HVM-boot-policy ( RW): BIOS order
                   HVM-boot-params (MRW): order: c
             HVM-shadow-multiplier ( RW): 1.000
                         PV-kernel ( RW): 
                        PV-ramdisk ( RW): 
                           PV-args ( RW): 
                    PV-legacy-args ( RW): 
                     PV-bootloader ( RW): 
                PV-bootloader-args ( RW): 
               last-boot-CPU-flags ( RO): vendor: GenuineIntel; features: 1fcbfbff-f7fa3223-2c100800-00000021-00000001-000007ab-00000000-00000000-00001000-9c000400-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000
                  last-boot-record ( RO): '{"platformdata":{"timeoffset":"-6","featureset":"1fcbfbff-f7fa3223-2c100800-00000021-00000001-000007ab-00000000-00000000-00001000-9c000400-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000-00000000","usb":"true","usb_tablet":"true","device-model":"qemu-upstream-compat","secureboot":"false","videoram":"8","hpet":"true","vga":"std","nx":"true","pae":"true","apic":"true","viridian":"false","acpi":"1","device_id":"0001"},"xen_platform":[1,2],"pv_drivers_detected":true,"pci_power_mgmt":false,"pci_msitranslate":true,"qemu_vifs":[],"qemu_vbds":[],"suspend_memory_bytes":2365575168,"original_profile":"Qemu_upstream_compat","profile":"Qemu_upstream_compat","nested_virt":false,"nomigrate":false,"domain_config":["X86",{"emulation_flags":["X86_EMU_LAPIC","X86_EMU_HPET","X86_EMU_PM","X86_EMU_RTC","X86_EMU_IOAPIC","X86_EMU_PIC","X86_EMU_VGA","X86_EMU_IOMMU","X86_EMU_PIT","X86_EMU_USE_PIRQ"]}],"last_start_time":1705855427.314935,"ty":["HVM",{"firmware":"Bios","qemu_stubdom":false,"qemu_disk_cmdline":false,"boot_order":"c","pci_passthrough":false,"pci_emulations":[],"serial":"pty","acpi":true,"video":"Standard_VGA","video_mib":8,"timeoffset":"-6","shadow_multiplier":1.0,"hap":true}],"build_info":{"has_hard_affinity":false,"priv":["BuildHVM",{"video_mib":8,"shadow_multiplier":1.0}],"vcpus":2,"kernel":"/usr/libexec/xen/boot/hvmloader","memory_target":2310144,"memory_max":2310144},"version":2}'
                       resident-on ( RO): 8daf76e4-32ac-4941-bb6b-cf189fbacf80
                          affinity ( RW): 8daf76e4-32ac-4941-bb6b-cf189fbacf80
                      other-config (MRW): pci: ; auto_poweron: true; import_task: OpaqueRef:b7132b4e-f996-4f14-8d58-a80047832de6; mac_seed: bef9b129-fb94-b59f-1e38-5d27b2fc03a9; vgpu_pci: ; base_template_name: Debian Stretch 9.0; install-methods: cdrom,nfs,http,ftp; linux_template: true
                            dom-id ( RO): 2
                   recommendations ( RO): <restrictions><restriction field="memory-static-max" max="1649267441664"/><restriction field="vcpus-max" max="32"/><restriction field="has-vendor-device" value="false"/><restriction field="allow-gpu-passthrough" value="1"/><restriction field="allow-vgpu" value="1"/><restriction max="255" property="number-of-vbds"/><restriction max="7" property="number-of-vifs"/></restrictions>
                     xenstore-data (MRW): vm-data/mmio-hole-size: 268435456; vm-data: 
        ha-always-run ( RW) [DEPRECATED]: false
               ha-restart-priority ( RW): 
                             blobs ( RO): 
                        start-time ( RO): 20240322T11:22:49Z
                      install-time ( RO): 20240113T12:10:36Z
                      VCPUs-number ( RO): 2
                 VCPUs-utilisation (MRO): 0: 0.006; 1: 0.001
                        os-version (MRO): name: Debian GNU/Linux 12 (bookworm); uname: 6.1.0-18-amd64; distro: debian; major: 12; minor: 12
                PV-drivers-version (MRO): major: 7; minor: 30; micro: 0; build: 11
PV-drivers-up-to-date ( RO) [DEPRECATED]: true
                            memory (MRO): 
                             disks (MRO): 
                              VBDs (SRO): c024771a-1641-a1a6-e600-378aca992622; 2768d04a-a755-9e6f-6770-7807eb8fd8df; c18600a6-d7e6-f6ba-82ba-0339da98dd67
                          networks (MRO): 0/ip: 192.168.1.227; 0/ipv4/0: 192.168.1.227; 0/ipv6/0: fe80::a02e:e1ff:fe58:4e95
               PV-drivers-detected ( RO): true
                             other (MRO): platform-feature-xs_reset_watches: 1; platform-feature-multiprocessor-suspend: 1; has-vendor-device: 0; feature-vcpu-hotplug: 1; feature-suspend: 1; feature-reboot: 1; feature-poweroff: 1; feature-balloon: 1
                              live ( RO): true
        guest-metrics-last-updated ( RO): 20240322T11:23:32Z
               can-use-hotplug-vbd ( RO): unspecified
               can-use-hotplug-vif ( RO): unspecified
          cooperative ( RO) [DEPRECATED]: true
                              tags (SRW): XOA, 2021.08
                         appliance ( RW): <not in database>
                 snapshot-schedule ( RW): <not in database>
                  is-vmss-snapshot ( RO): false
                       start-delay ( RW): 0
                    shutdown-delay ( RW): 0
                             order ( RW): 0
                           version ( RO): 0
                     generation-id ( RO): 
         hardware-platform-version ( RO): 0
                 has-vendor-device ( RW): false
                   requires-reboot ( RO): false
                   reference-label ( RO): debian-9
                      bios-strings (MRO): bios-vendor: Xen; bios-version: ; system-manufacturer: Xen; system-product-name: HVM domU; system-version: ; system-serial-number: ; hp-rombios: ; oem-1: Xen; oem-2: MS_VM_CERT/SHA1/bdbeb6e0a816d43fa6d3fe8aaef04c2bad9d3e3d

Hi, I have a similar issue the lsusb command on the vm shows a different product than the real one shown on the host for an USB pass-through device. I've followed all the steps for USB pass-through, the device is seen as the real device in XenCenter too but not on the Debian vm.

The device is listed as: 0409:55aa NEC Corp. Hub
At the start of the vm it is marked as 'attached' but after boot, few seconds later, it's marked 'not attached'.

How can I fix this behavior ?

For information, the USB controller is on a PCIe card and I've tried to use this card using PCI pass-through without success (Operation not permitted on start of the vm) as plan B.

Thanks for your help.

krakers Hi, I have a similar issue the lsusb command on the vm shows a different product than the real one shown on the host for an USB pass-through device. I've followed all the steps for USB pass-through, the device is seen as the real device in XenCenter too but not on the Debian vm.

How can I fix this behavior ?

For information, the USB controller is on a PCIe card and I've tried to use this card using PCI pass-through without success (Operation not permitted on start of the vm) as plan B.

Thanks for your help.