XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • M

      Backup Issue: "timeout reached while waiting for OpaqueRef"

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      11
      0 Votes
      11 Posts
      631 Views
      M
      @stevewest15 I believe this issue was resolved when the health check system was changed to detect network connectivity at startup so it did not need to wait for then entire VM to boot. Needs the Xen tools to be installed. I have not had an issue since this change.
    • M

      VM resource usage

      Watching Ignoring Scheduled Pinned Locked Moved Management
      3
      2
      0 Votes
      3 Posts
      166 Views
      P
      @McHenry like @olivierlambert said, keep in mind that a VM with 16 CPUs will be less available than a VM with 4 vCPUs, because it's easier to have 4 vCPUs ready to work than 16 simultaneously beware of this graph, it only graph the first 16 vCPU, but you can have more working ! the visual widget is failing you. think of topology too : if you have two sockets, you can have a topology of 2 sockets with 4 cores for a 8 vCPU VM. If you have only one socket, try to keep the topology to "1 socket xx cores" for your VMs, performance wise.
    • S

      How to force shutdown a specific XCP-ng host without migrating VMs (with HA enabled)

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      3
      0 Votes
      3 Posts
      176 Views
      olivierlambertO
      Host shutdown with force flag should shutdown the VM, IIRC.
    • C

      Upgrade 8.2.1 -> 8.3 failed (manually fixed)

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng
      3
      0 Votes
      3 Posts
      169 Views
      C
      @bleader IIRC I just "tried again". It failed 2 times, then I looked up the logs from other console, removed the file (which shouldn't be of any importance for our instance) and retried without reboot. I copied the whole installer-log to the usb stick before finshing the install. (Could actually be a good hint or even a menu-option for those, where the install fails and won't leave it on the harddrive - e.g. evaluating hardware) [ 128.517356] ata1.00: exception Emask 0x0 SAct 0x800000 SErr 0x0 action 0x0 [ 128.517357] ata1.00: irq_stat 0x40000008 [ 128.517359] ata1.00: failed command: READ FPDMA QUEUED [ 128.517362] ata1.00: cmd 60/80:b8:10:6c:d4/00:00:02:00:00/40 tag 23 ncq dma 65536 in res 41/40:10:80:6c:d4/00:00:02:00:00/00 Emask 0x409 (media error) <F> [ 128.517363] ata1.00: status: { DRDY ERR } [ 128.517364] ata1.00: error: { UNC } [ 128.518008] ata1.00: configured for UDMA/133 [ 128.518018] sd 0:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 128.518020] sd 0:0:0:0: [sda] tag#23 Sense Key : Medium Error [current] [ 128.518021] sd 0:0:0:0: [sda] tag#23 Add. Sense: Unrecovered read error - auto reallocate failed [ 128.518024] sd 0:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 02 d4 6c 10 00 00 80 00 [ 128.518025] print_req_error: I/O error, dev sda, sector 47475840 [ 128.518039] ata1: EH complete [ 128.581286] ata1.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x0 [ 128.581287] ata1.00: irq_stat 0x40000008 [ 128.581288] ata1.00: failed command: READ FPDMA QUEUED [ 128.581291] ata1.00: cmd 60/08:c8:80:6c:d4/00:00:02:00:00/40 tag 25 ncq dma 4096 in res 41/40:08:80:6c:d4/00:00:02:00:00/00 Emask 0x409 (media error) <F> [ 128.581292] ata1.00: status: { DRDY ERR } [ 128.581293] ata1.00: error: { UNC } [ 128.582111] ata1.00: configured for UDMA/133 [ 128.582117] sd 0:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 128.582118] sd 0:0:0:0: [sda] tag#25 Sense Key : Medium Error [current] [ 128.582119] sd 0:0:0:0: [sda] tag#25 Add. Sense: Unrecovered read error - auto reallocate failed [ 128.582121] sd 0:0:0:0: [sda] tag#25 CDB: Read(10) 28 00 02 d4 6c 80 00 00 08 00 [ 128.582122] print_req_error: I/O error, dev sda, sector 47475840 [ 128.582133] ata1: EH complete [ 128.629307] ata1.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x0 [ 128.629309] ata1.00: irq_stat 0x40000008 [ 128.629310] ata1.00: failed command: READ FPDMA QUEUED [ 128.629313] ata1.00: cmd 60/08:48:80:6c:d4/00:00:02:00:00/40 tag 9 ncq dma 4096 in res 41/40:08:80:6c:d4/00:00:02:00:00/00 Emask 0x409 (media error) <F> [ 128.629314] ata1.00: status: { DRDY ERR } [ 128.629315] ata1.00: error: { UNC } [ 128.630068] ata1.00: configured for UDMA/133 [ 128.630074] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 128.630076] sd 0:0:0:0: [sda] tag#9 Sense Key : Medium Error [current] [ 128.630077] sd 0:0:0:0: [sda] tag#9 Add. Sense: Unrecovered read error - auto reallocate failed [ 128.630078] sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 02 d4 6c 80 00 00 08 00 [ 128.630079] print_req_error: I/O error, dev sda, sector 47475840 [ 128.630092] ata1: EH complete Indeed it looks like the SSD should be replaced. 8.3 is running stable on this (and all other hosts, I upgraded) so far. It's a system at a UAS, running various student projects for several years now, coming from XenServer originally. I voluntarily maintain it. Thx for the hint!
    • olivierlambertO

      XOSTOR hyperconvergence preview

      Watching Ignoring Scheduled Pinned Locked Moved XOSTOR
      459
      1
      6 Votes
      459 Posts
      761k Views
      henri9813H
      Hello, I got my whole xostor destroyed, i don't know how precisely. I found some errors in sattelite Error context: An error occurred while processing resource 'Node: 'host', Rsc: 'xcp-volume-e011c043-8751-45e6-be06-4ce9f8807cad'' ErrorContext: Details: Command 'lvcreate --config 'devices { filter=['"'"'a|/dev/md127|'"'"','"'"'a|/dev/md126p3|'"'"','"'"'r|.*|'"'"'] }' --virtualsize 52543488k linstor_primary --thinpool thin_device --name xcp-volume-e011c043-8751-45e6-be06-4ce9f8807cad_00000' returned with exitcode 5. Standard out: Error message: WARNING: Remaining free space in metadata of thin pool linstor_primary/thin_device is too low (98.06% >= 96.30%). Resize is recommended. Cannot create new thin volume, free space in thin pool linstor_primary/thin_device reached threshold. of course, i checked, my SR was not full [image: 1762696853953-aa2774a4-c2d4-4dd1-be52-3c6e418c9083-image-resized.png] And the controller crashed, and i couldn't make it works. Here is the error i got ========== Category: RuntimeException Class name: IllegalStateException Class canonical name: java.lang.IllegalStateException Generated at: Method 'newIllegalStateException', Source file 'DataUtils.java', Line #870 Error message: Reading from nio:/var/lib/linstor/linstordb.mv.db failed; file length 2293760 read length 384 at 2445540 [1.4.197/1] So i deduce the database was fucked-up, i tried to open the file as explained in the documentation, but the linstor schema was "not found" in the file, event if using cat i see data about it. for now, i leave xostor and i'm back to localstorage until we know what to do when this issue occured with a "solution path".
    • F

      XOA and Home Assistant

      Watching Ignoring Scheduled Pinned Locked Moved REST API
      2
      0 Votes
      2 Posts
      14 Views
      P
      @francis-chiew hey, seems very nice. need some screenshots of the dashboards
    • P

      LTR cosmetics in UI

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      2
      1
      1 Votes
      2 Posts
      18 Views
      olivierlambertO
      Adding @florent and @Bastien-Nollet in the loop
    • P

      Sequence scheduled backups and HEALTH CHECKS

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      2
      2
      0 Votes
      2 Posts
      14 Views
      olivierlambertO
      Ping @Bastien-Nollet or @florent (and if it's not clear in our doc, @Team-Documentation-Knowledge-Management )
    • R

      How many guest IRQs is too many?

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      2
      0 Votes
      2 Posts
      80 Views
      olivierlambertO
      Hi, Let me ask @Team-Hypervisor-Kernel
    • C

      XOCE - ISO upload is renamed after upload to ISO SR

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      2
      1 Votes
      2 Posts
      31 Views
      P
      @Chico008 Use a file manager outside of XO, it will keep the name of the iso
    • W

      Intel x710-t2l Problems

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      20
      0 Votes
      20 Posts
      1k Views
      olivierlambertO
      Thank you very much for sharing your findings Adding @Team-Documentation-Knowledge-Management and @Team-OS-Platform-Release to check what's next on our side
    • R

      Boot device: Hard Disk - Success

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng
      2
      0 Votes
      2 Posts
      52 Views
      D
      @rustylh We really need more information to even begin. What version of XCP-ng are you using? What hardware are you using to run XCP-ng? What is the underlying storage where the VM resides on? What OS is the VM running? How are you taking snapshots, XO? How old was the snapshot? Were the guest utilities installed into the VM? You do know snapshots are not backups, right?
    • U

      RTX A4000 GPU passthrough failure on XCP-ng

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      2
      0 Votes
      2 Posts
      48 Views
      olivierlambertO
      Hi, Are you sure your GPU is correctly fed via the power connector?
    • D

      Is it possible yet to select a specific network adapter for Backups?

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      5
      0 Votes
      5 Posts
      511 Views
      olivierlambertO
      Just connect your XOA to your dedicated network and it will flow to it.
    • K

      Self-service and sharing

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      2
      0 Votes
      2 Posts
      62 Views
      olivierlambertO
      Hi, Pinging @pdonias about this
    • P

      Gather CPU utilization of host as variable for prometheus exporter

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      13
      0 Votes
      13 Posts
      3k Views
      S
      Related: https://xcp-ng.org/forum/topic/9160/xen-orchestra-prometheus-backup-metrics/10
    • F

      Xen Orchestra 5.110 V2V not working

      Watching Ignoring Scheduled Pinned Locked Moved Migrate to XCP-ng
      53
      0 Votes
      53 Posts
      4k Views
      D
      @Biz365 Warm migrations from ESXi are ESXi license dependent on what you have/had with ESXi. Otherwise you can replicate the VM using the migration tool and then manually shutdown the VM on ESXi and then power it on XCP-ng.
    • F

      XOSTOR on 8.3?

      Watching Ignoring Scheduled Pinned Locked Moved XOSTOR xostor xcp-ng 8.3
      37
      0 Votes
      37 Posts
      7k Views
      olivierlambertO
      You can manually install XOSTOR yes.
    • lastcmasterL

      Migrating Windows 11 with xcpng-winpv-9.0.9137.0-Release-x64 installed fails to register as running, restart of agent fixes it.

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng rust agent windows tools
      2
      0 Votes
      2 Posts
      57 Views
      D
      @lastcmaster Hi, it's a known issue that guest agent versions are not reported after migration or suspend. Other functionalities (poweroff/reboot, suspend, network change etc.) should continue to work normally.
    • J

      MAP_DUPLICATE_KEY error in XOA backup - VM's wont START now!

      Watching Ignoring Scheduled Pinned Locked Moved Solved Backup
      34
      2
      0 Votes
      34 Posts
      9k Views
      olivierlambertO
      Question for @pierrebrunet I assume