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
    • C

      HA causes reboot of xcp-ng nodes

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Management
      9
      0 Votes
      9 Posts
      264 Views
      tjkreidlT
      @carloum70 Sorry, that option was deprecated. You may need to be more specific in the reset, something like the following with is just an example: xe-reset-networking -m IP_of_Master --device=eth0 --mode=static --ip=192.168.1.50 --netmask=255.255.255.0 --gateway=192.168.1.1 --dns=192.168.1.254 Check the options and see which ones you actually need in your case. Worst case, you could possibly dissolve the bond, redo the PMI and then re-create the bond. WHy eth4 shows up is hard to guess. I have seen before that on some hosts in a pool that the NIC order was not the same, even though the hardware and OS versions were identical. In that case, you have to shut down the NICs and use interface-rename to reassign specific NIC names to the corresponding MAC addresses.
    • P

      Why are transfer sizes different between XO5 & XO6?

      Watching Ignoring Scheduled Pinned Locked Moved Solved Backup
      17
      2
      0 Votes
      17 Posts
      341 Views
      JorisKJ
      Wonderful !
    • J

      V2V migrated VMs don't autostart

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Migrate to XCP-ng
      1
      1 Votes
      1 Posts
      15 Views
      No one has replied
    • K

      Slow VM migration on Linstor SR

      Watching Ignoring Scheduled Pinned Locked Moved XOSTOR
      1
      0 Votes
      1 Posts
      34 Views
      No one has replied
    • J

      Reducing vCPU isn't done live on Windows

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved XCP-ng
      1
      0 Votes
      1 Posts
      34 Views
      No one has replied
    • johnnezeroJ

      Tag-Based Automation Plugin: Tag-Based VM Performance & Permission Management via assigned tag(s)

      Watching Ignoring Scheduled Pinned Locked Moved Management
      19
      1
      0 Votes
      19 Posts
      2k Views
      johnnezeroJ
      @fohdeesha Hi all, I apologize that it's taken a while to get all the issues sorted, fixed and properly verified. I have pushed the corrected version up to my GitHub, and everything seems to be working much better (thanks to the efforts of everyone here)! A big shout out to all of you, as this is exactly how open source is supposed to work! Let me know if there are any other issues that arrise - and Happy Day to one and All!
    • J

      DRBD reactor metrics in k8s

      Watching Ignoring Scheduled Pinned Locked Moved XOSTOR
      5
      3
      0 Votes
      5 Posts
      210 Views
      J
      Wonder if these are just issues that will be fixed and not come back by manually cleaning it up. Held off at first cause I did not want to manually clean up, and then have it happen again. Will post in a bit when it finishes and will monitor this one for a few. [18:45 ovbh-pprod-xen02 ~]# drbdadm status xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 --verbose --statistics drbdsetup status xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 --verbose --statistics xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 node-id:1 role:Primary suspended:no force-io-failures:no write-ordering:flush volume:0 minor:1013 disk:UpToDate backing_dev:/dev/linstor_group/xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1_00000 quorum:yes open:yes size:315195168 read:296465702 written:1319196709 al-writes:790653 bm-writes:361 upper-pending:1 lower-pending:1 al-suspended:no blocked:no ovbh-pprod-xen01 node-id:0 connection:Connected role:Secondary tls:no congested:no ap-in-flight:0 rs-in-flight:0 volume:0 replication:Established peer-disk:UpToDate resync-suspended:no received:0 sent:1319197101 out-of-sync:0 pending:1 unacked:0 ovbh-pprod-xen05 node-id:2 connection:Connected role:Secondary tls:no congested:no ap-in-flight:8 rs-in-flight:0 volume:0 replication:Established peer-disk:UpToDate resync-suspended:no received:0 sent:1292149931 out-of-sync:0 pending:1 unacked:0 [18:45 ovbh-pprod-xen02 ~]# drbdadm invalidate-remote xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 [18:45 ovbh-pprod-xen02 ~]# drbdadm status xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 --verbose --statistics drbdsetup status xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 --verbose --statistics xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 node-id:1 role:Primary suspended:no force-io-failures:no write-ordering:flush volume:0 minor:1013 disk:UpToDate backing_dev:/dev/linstor_group/xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1_00000 quorum:yes open:yes size:315195168 read:300587646 written:1319298558 al-writes:790664 bm-writes:15389 upper-pending:0 lower-pending:1 al-suspended:no blocked:no ovbh-pprod-xen01 node-id:0 connection:Connected role:Secondary tls:no congested:no ap-in-flight:0 rs-in-flight:0 volume:0 replication:SyncSource peer-disk:Inconsistent done:0.69 resync-suspended:no received:0 sent:1321387882 out-of-sync:313023380 pending:0 unacked:1 dbdt1:35.66 eta:8573 ovbh-pprod-xen05 node-id:2 connection:Connected role:Secondary tls:no congested:no ap-in-flight:0 rs-in-flight:0 volume:0 replication:SyncSource peer-disk:Inconsistent done:0.65 resync-suspended:no received:0 sent:1294222956 out-of-sync:313141144 pending:0 unacked:0 dbdt1:30.42 eta:10052 jonathon@jonathon-framework:~$ linstor --controllers=10.2.0.10,10.2.0.11,10.2.0.12,10.2.0.13,10.2.0.14 r l | grep xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ ovbh-pprod-xen01 │ DRBD,STORAGE │ Unused │ Ok │ UpToDate │ Yes │ │ xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ ovbh-pprod-xen02 │ DRBD,STORAGE │ InUse │ Ok │ UpToDate │ Yes │ │ xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ ovbh-pprod-xen05 │ DRBD,STORAGE │ Unused │ Ok │ UpToDate │ Yes │ jonathon@jonathon-framework:~$ linstor --controllers=10.2.0.10,10.2.0.11,10.2.0.12,10.2.0.13,10.2.0.14 r l | grep xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ ovbh-pprod-xen01 │ DRBD,STORAGE │ Unused │ Ok │ SyncTarget(0.04%) │ Yes │ │ xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ ovbh-pprod-xen02 │ DRBD,STORAGE │ InUse │ Ok │ UpToDate │ Yes │ │ xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ ovbh-pprod-xen05 │ DRBD,STORAGE │ Unused │ Ok │ Inconsistent │ Yes │ jonathon@jonathon-framework:~$ linstor --controllers=10.2.0.10,10.2.0.11,10.2.0.12,10.2.0.13,10.2.0.14 r l | grep xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ ovbh-pprod-xen01 │ DRBD,STORAGE │ Unused │ Ok │ SyncTarget(0.64%) │ Yes │ │ xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ ovbh-pprod-xen02 │ DRBD,STORAGE │ InUse │ Ok │ UpToDate │ Yes │ │ xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ ovbh-pprod-xen05 │ DRBD,STORAGE │ Unused │ Ok │ SyncTarget(0.61%) │ Yes │ jonathon@jonathon-framework:~$ linstor --controllers=10.2.0.10,10.2.0.11,10.2.0.12,10.2.0.13,10.2.0.14 r l | grep xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ ovbh-pprod-xen01 │ DRBD,STORAGE │ Unused │ Ok │ SyncTarget(1.00%) │ Yes │ │ xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ ovbh-pprod-xen02 │ DRBD,STORAGE │ InUse │ Ok │ UpToDate │ Yes │ │ xcp-volume-6a8544e8-f17f-49c8-b725-54c5e3213ae1 │ ovbh-pprod-xen05 │ DRBD,STORAGE │ Unused │ Ok │ SyncTarget(0.96%) │ Yes │
    • J

      Piraeus operator 2.12.0 does not work on current xostor version

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved XOSTOR
      3
      3
      0 Votes
      3 Posts
      64 Views
      J
      Got a response Yes, sorry, this was not properly pointed out in the release message. This comes from using https://github.com/piraeusdatastore/linstor-csi/releases/tag/v1.13.0 So you can still use the new operator, but you have to downgrade the LINSTOR CSI version until you upgrade the cluster. So doing that for now with the following helm values --- operator: resources: requests: cpu: 250m memory: 500Mi limits: memory: 1Gi installCRDs: true imageConfigOverride: - base: quay.io/piraeusdatastore components: linstor-satellite: image: piraeus-server tag: v1.33.1 linstor-csi: image: piraeus-csi tag: v1.12.0 tls: certManagerIssuerRef: name: pp-step-issuer kind: StepClusterIssuer group: certmanager.step.sm
    • olivierlambertO

      🛰️ XO 6: dedicated thread for all your feedback!

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      279
      7 Votes
      279 Posts
      132k Views
      julienXOvatesJ
      @jacob.becker said: Hi! In XO-5 you can see clearly if a host is in maintenace mode" or not. I'm missing a similar thing to the little green/gray dot from XO-5 in the XO6 treeview. You can see it in the System- Tab under General Information, but only if the host is already selected. I personally find it difficult to distinct between hosts and VMs in the treeview if a large amount entries are shown. Especially while scrolling. Hi @jacob.becker, this is going to be fixed in XO 6.9 (ie. the Disable state for a host). I share your point of view about hosts & VM icons, we should also change them. Thanks !