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

      Nested Virtualization of Windows Hyper-V on XCP-ng

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      133
      1
      0 Votes
      133 Posts
      120k Views
      C
      Thanks for that information. I will make this message short because @stormi is busy but I want to say thanks to Vates and XCP-ng for all their work done to support Windows on the Xen platform. This includes TPM2 and secure boot support and Microsoft-signed pv drivers. Well done!
    • J

      Ran into a new auth issue with xostor?

      Watching Ignoring Scheduled Pinned Locked Moved XOSTOR
      4
      3
      0 Votes
      4 Posts
      60 Views
      M
      Hi @jonathon, If that happens again, could you show me the results of the command linstor n l (listing the nodes and their status) along with the version of each node? When restarting the controller, did you do it with a systemctl restart linstor-controller or with a systemctl stop linstor-controller, letting drbd-reactor elect a new node? You mentioned updating all of your nodes but you also mentioned rebooting only one node, is this correct? Depending on the version you were before the update it's possible that you got a version mismatch between your nodes (the satellites of each node + the controller needing to be rebooted so that they all get to the same version). The node appearing offline is due to a bug when updating from < linstor-server v1.32.0 to >= linstor-server v1.32.0 which makes the node with a different version appear as offline (the auth error is a symptom of that).
    • olivierlambertO

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

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      220
      7 Votes
      220 Posts
      31k Views
      C
      @julienXOvates @julienXOvates said: @colomb said: I really miss the description column XO5 has in the default/home view. I understand space is limited for the tree view, but maybe it could appear when a host is selected in the tree view? In XO6, you will see it if you click on the eye at the end of the row, then on the right panel. Is this OK ? I noticed that. Unfortunately, for our use case, clicking on each vm to see the description is a little onerous. Ideally, you'd allow the user to customize the visible columns in the VMs page/tab. The fact that search includes description does help. Ultimately, it was convenient that XO5 would allow us to quickly identify vms by the description from the "Home" page.
    • M

      XCP-NG 8.3 PCI Passthrough Trials and Tribulations

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      9
      0 Votes
      9 Posts
      2k Views
      olivierlambertO
      Nice!! Thanks for the feedback @mattrc , it's really cool to see that you can fully enjoy your machine
    • R

      Date format on web interface: Only US format available?

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      7
      1 Votes
      7 Posts
      221 Views
      julienXOvatesJ
      @robbie-c Very clear, thanks. We will change this !
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      509
      1 Votes
      509 Posts
      219k Views
      O
      I get this in dmesg after the latest updates : [ 54.673443] python3[3691]: segfault at 200000 ip 00007f16eb8eca9f sp 00007ffd b84e9ff0 error 4 in libpython3.6m.so.1.0[7f16eb804000+28d000] [ 54.673450] Code: 01 00 00 8d 5f ff 48 8d 2d de 3a 3c 00 c1 eb 03 44 8d 24 1b 4e 8b 44 e5 00 49 8b 70 10 49 39 f0 74 5f 49 8b 40 08 41 83 00 01 <48> 8b 38 48 85 ff 49 89 78 08 74 0d 48 83 c4 10 5b 5d 41 5c c3 0f [ 84.587661] xapi[3697]: segfault at 7f28cacaea40 ip 00007f28c6df0ec2 sp 00007 f289a5b8af0 error 6 in libjemalloc.so.2[7f28c6d85000+85000] [ 84.587669] Code: 48 2b 73 08 44 8b 4d 84 ba 01 00 00 00 49 83 c2 01 49 0f af f1 4c 8d 0d ac 72 42 00 48 89 f1 48 c1 ee 26 48 c1 e9 20 48 d3 e2 <48> 31 54 f3 40 48 8b 8d 58 ff ff ff 48 8b 33 48 8d be 00 00 00 10
    • K

      Old VM:s shows up

      Watching Ignoring Scheduled Pinned Locked Moved Management
      2
      1
      0 Votes
      2 Posts
      60 Views
      poddingueP
      Hi! I think what you're seeing may be stale entries in the XAPI database, ghost records that can survive upgrades or host reconfigurations. From what I've read, xe vm-destroy uuid=<vm-uuid> removes the record without touching any storage, which seems like what you need here; the xe CLI reference confirms storage is left intact. I think you can get the UUID first with xe vm-list name-label="Before Ubuntu Update" (replacing the name with whichever one you're after). I'm not entirely sure why xsconsole would show them but XO wouldn't, so if the VMs don't turn up in xe vm-list, it might be worth a mention to Team-XAPI-Network, they'll know the right way to dig into XAPI state.
    • P

      visual bug in backup data

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      4
      3
      0 Votes
      4 Posts
      124 Views
      P
      @pierrebrunet @poddingue the size is really 2.17Tb, but showing last incremental size on the key I'll wait for the patch, this is really a visual bug, backup is working okay.