• Live migrate of Rocky Linux 8.8 VM crashes/reboots VM

    Solved
    20
    0 Votes
    20 Posts
    2k Views
    W

    @KFC-Netearth

    The Rocky Linux bugtracker indeed mentions it's mostly fixed, but there are still some kernel errors present: https://bugs.rockylinux.org/view.php?id=3565#c4293

  • PCI Nvidia GPU Passthrough boot delay

    Solved
    11
    0 Votes
    11 Posts
    2k Views
    olivierlambertO

    Probably (ideally) before the end of 2024, but it's really hard to make any promises (it might be -at that point- an ever more recent version)

  • New Server HP 350 gen 10 hang

    1
    0 Votes
    1 Posts
    100 Views
    No one has replied
  • RunX as podman

    1
    1 Votes
    1 Posts
    237 Views
    No one has replied
  • NUC compatibility

    5
    0 Votes
    5 Posts
    884 Views
    tjkreidlT

    @nhoty Sadly, it has been announced that the NUC will be discontinued by Intel, but ASUS is evidently licensing them and will likely keep making similar products. https://www.theverge.com/2023/7/19/23800006/intel-nuc-computers-asus-license-support

  • PCPU assumed down

    Moved
    6
    0 Votes
    6 Posts
    146 Views
    shaddowS

    @Andrew
    At the moment I can not find why or what could be running at 21:30 but have a few thoughts into it, Including possible outside hack attempts, as I am on a Fixed IPv4 & IPv6 and the modem is bridged mode to one NIC.

    But on the VM I have running Pfsense2.6, Plex (Debian10), (Emails, dns, web) Freebsd12, Unifi (debain10), Asterisk (debian10), XenOrchestra7.4CE (Debian10).
    Not running but can be spun up, Winxp64, XenOrchestra(Paid Version)

    I have a replacement Nic in the mail and hope this will fix the problem, but wondering if I need to disable the onboard ones to stop the crash even if I force all to use the new ones, but hope this replacement card fixes the problems.

  • slow vm with high steal

    11
    0 Votes
    11 Posts
    863 Views
    olivierlambertO

    It sounds really slow to install on this hardware (even if it's not crazy fast, it shouldn't be that long). I would take a look at usual logs (like dmesg) to see if there's a problem on the hardware. I would also check to have latest BIOS and firmware installed on that machine.

  • lost access to vm

    3
    0 Votes
    3 Posts
    212 Views
    B

    Ok, I was able to fix this. I migrated it to the pool master on the cli. I don't think this was necessary in hindsight but I just wanted to be sure I knew where it was running. I then brought up xo-lite in Chrome on the pool master. At that point I could view the VM in the embedded console. It turned out that the root partition had errors on it and was stuck in Initramfs waiting for fsck to be run. Once I repaired the errors with fsck, the VM booted and I'm back in business.

  • Update doc'n for xe-guest-utils installation for Ubuntu

    8
    1 Votes
    8 Posts
    985 Views
    J

    @gsrfan01

    As near as I can tell the apt version does not install the xe-linux-distribution.service and run it, and therefore the various daemons won't load.

    You can read more about my plight here: https://xcp-ng.org/forum/topic/7494/ubuntu-22-04lts-guest-utiilities?_=1688263726663

  • qemu-img formats

    2
    0 Votes
    2 Posts
    901 Views
    AtaxyaNetworkA

    @pavkamlc Hi !

    Usually I convert my qcow2 file to VHD directly on Proxmox.

    As far as I remember, when I crashed my Proxmox in the school lab, I didn't succeed to convert the image directly on a Linux box.

    I found a workaround, but it's pretty messy:

    Install a Debian VM Install the proxmox-ve package (you'll need the Proxmox repository) Mount your shared storage directly on your new VM (with NFS for example). Then, you can convert

    Let me know if it's working !

  • vTPM support requirements

    4
    0 Votes
    4 Posts
    1k Views
    jeffmetalJ

    @stormi said in vTPM support requirements:

    The TPM device is emulated in the controller domain, so it's all software. No need for hardware TPM.

    thanks, That's great to hear. Makes getting windows 11 machines working much easier.

  • How many VM can be created per host CPU core?

    Moved
    7
    0 Votes
    7 Posts
    680 Views
    D

    Thank you so much @olivierlambert,

    That helps me alot with clarification.

  • What is xo-server-log?

    18
    0 Votes
    18 Posts
    943 Views
    ronivayR

    That script has a shebang pointing to node (first line), so no need to define it separately, just execute the script directly.

  • Lost access to all servers

    36
    0 Votes
    36 Posts
    9k Views
    J

    @ronan-a My pool is mostly working now, though I'm still seeing some quirks. I believe the problems I've seen thus far is due to the hardware instability of one of my hosts, as noted before. While frustrating, it has given me the opportunity to work through some host and SR recovery processes. That's the silver lining. šŸ™‚

    The main issue that I'm still seeing is when I attempt to load a specific stopped VM on a specific host (xcp-ng3). The VM will fail to start and throw this error:

    SR_BACKEND_FAILURE_46(, The VDI is not available [opterr=VDI a9d53abc-f492-4826-b659-744ee87d4d94 not detached cleanly], )

    This VM will start without issue on the other two hosts. XO is not showing any other issues with this VM and is not showing any orphaned VDIs.

    I am also seeing these errors in the /var/log/linstor-controller directory:

    Host xcp-ng1:

    ERROR REPORT 648FDBE6-00000-000000 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 00:39:06 Node: xcp-ng1 ============================================================ Reported error: =============== Category: Exception Class name: SocketException Class canonical name: java.net.SocketException Generated at: Method 'bind0', Source file 'Net.java, Unknown line number Error message: Protocol family unavailable Call backtrace: Method Native Class:Line number bind0 Y sun.nio.ch.Net:unknown bind N sun.nio.ch.Net:461 bind N sun.nio.ch.Net:453 bind N sun.nio.ch.ServerSocketChannelImpl:222 bind N sun.nio.ch.ServerSocketAdaptor:85 bindToChannelAndAddress N org.glassfish.grizzly.nio.transport.TCPNIOBindingHandler:107 bind N org.glassfish.grizzly.nio.transport.TCPNIOBindingHandler:64 bind N org.glassfish.grizzly.nio.transport.TCPNIOTransport:215 bind N org.glassfish.grizzly.nio.transport.TCPNIOTransport:195 bind N org.glassfish.grizzly.nio.transport.TCPNIOTransport:186 start N org.glassfish.grizzly.http.server.NetworkListener:711 start N org.glassfish.grizzly.http.server.HttpServer:256 start N com.linbit.linstor.api.rest.v1.config.GrizzlyHttpService:314 initialize N com.linbit.linstor.systemstarter.GrizzlyInitializer:88 startSystemServices N com.linbit.linstor.core.ApplicationLifecycleManager:87 start N com.linbit.linstor.core.Controller:365 main N com.linbit.linstor.core.Controller:613 END OF ERROR REPORT.

    Host xcp-ng2 (each truncated for post limit):

    ERROR REPORT 648E4932-00000-000012 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 00:38:51 Node: xcp-ng2 Peer: Node: 'xcp-ng1' ============================================================ Reported error: =============== Category: RuntimeException Class name: TransactionException Class canonical name: com.linbit.linstor.transaction.TransactionException Generated at: Method 'startTransaction', Source file 'ControllerSQLTransactionMgrGenerator.java', Line #32 Error message: Failed to start transaction Error context: Failed to start transaction Asynchronous stage backtrace: Error has been observed at the following site(s): |_ checkpoint ā‡¢ Execute single-stage API UpdateFreeCapacity |_ checkpoint ā‡¢ Fallback error handling wrapper Stack trace: Call backtrace: Method Native Class:Line number startTransaction N com.linbit.linstor.transaction.manager.ControllerSQLTransactionMgrGenerator:32 ERROR REPORT 648E4932-00000-000013 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 00:38:51 Node: xcp-ng2 Peer: Node: 'xcp-ng3' ============================================================ Reported error: =============== Category: RuntimeException Class name: ErrorCallbackNotImplemented Class canonical name: reactor.core.Exceptions.ErrorCallbackNotImplemented Generated at: <UNKNOWN> Error message: com.linbit.linstor.transaction.TransactionException: Failed to start transaction Call backtrace: Method Native Class:Line number ERROR REPORT 648E4932-00000-000014 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 00:38:51 Node: xcp-ng2 Peer: RestClient(127.0.0.1; 'PythonLinstor/1.15.1 (API1.0.4): Client 1.15.1') ============================================================ Reported error: =============== Category: RuntimeException Class name: TransactionException Class canonical name: com.linbit.linstor.transaction.TransactionException Generated at: Method 'startTransaction', Source file 'ControllerSQLTransactionMgrGenerator.java', Line #32 Error message: Failed to start transaction Error context: Modification of node 'xcp-ng1' failed due to an unknown exception. Asynchronous stage backtrace: Error has been observed at the following site(s): |_ checkpoint ā‡¢ Auto-Quorum and -Tiebreaker after node create |_ checkpoint ā‡¢ Reconnect node(s) Stack trace: Call backtrace: Method Native Class:Line number startTransaction N com.linbit.linstor.transaction.manager.ControllerSQLTransactionMgrGenerator:32 ERROR REPORT 648E4932-00000-000015 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 00:38:51 Node: xcp-ng2 Peer: Node: 'xcp-ng2' ============================================================ Reported error: =============== Category: RuntimeException Class name: TransactionException Class canonical name: com.linbit.linstor.transaction.TransactionException Generated at: Method 'startTransaction', Source file 'ControllerSQLTransactionMgrGenerator.java', Line #32 Error message: Failed to start transaction Error context: Failed to start transaction Asynchronous stage backtrace: Error has been observed at the following site(s): |_ checkpoint ā‡¢ Execute single-stage API ApplyPropsFromStlt |_ checkpoint ā‡¢ Fallback error handling wrapper Stack trace: Call backtrace: Method Native Class:Line number startTransaction N com.linbit.linstor.transaction.manager.ControllerSQLTransactionMgrGenerator:32 ERROR REPORT 648E4932-00000-000016 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 00:38:51 Node: xcp-ng2 Peer: RestClient(127.0.0.1; 'PythonLinstor/1.15.1 (API1.0.4): Client 1.15.1') ============================================================ Reported error: =============== Category: RuntimeException Class name: TransactionException Class canonical name: com.linbit.linstor.transaction.TransactionException Generated at: Method 'startTransaction', Source file 'ControllerSQLTransactionMgrGenerator.java', Line #32 Error message: Failed to start transaction Error context: Modification of node 'xcp-ng1' failed due to an unknown exception. Asynchronous stage backtrace: Error has been observed at the following site(s): |_ checkpoint ā‡¢ Reconnect node(s) Stack trace: Call backtrace: Method Native Class:Line number startTransaction N com.linbit.linstor.transaction.manager.ControllerSQLTransactionMgrGenerator:32 ERROR REPORT 648E4932-00000-000017 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 00:38:51 Node: xcp-ng2 ============================================================ Reported error: =============== Category: RuntimeException Class name: ErrorCallbackNotImplemented Class canonical name: reactor.core.Exceptions.ErrorCallbackNotImplemented Generated at: <UNKNOWN> Error message: com.linbit.linstor.transaction.TransactionException: Failed to start transaction Error context: Exception thrown by connection observer when outbound connection established Call backtrace: Method Native Class:Line number ERROR REPORT 648E4932-00000-000018 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 00:38:51 Node: xcp-ng2 Peer: Node: 'xcp-ng1' ============================================================ Reported error: =============== Category: RuntimeException Class name: IllegalStateException Class canonical name: java.lang.IllegalStateException Generated at: Method 'assertOpen', Source file 'BaseGenericObjectPool.java', Line #759 Error message: Pool not open Asynchronous stage backtrace: Error has been observed at the following site(s): |_ checkpoint ā‡¢ Execute single-stage API NotifyDevMgrRunCompleted |_ checkpoint ā‡¢ Fallback error handling wrapper Stack trace: Call backtrace: Method Native Class:Line number assertOpen N org.apache.commons.pool2.impl.BaseGenericObjectPool:759 ERROR REPORT 648E4932-00000-000019 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 00:38:51 Node: xcp-ng2 ============================================================ Reported error: =============== Category: RuntimeException Class name: TransactionException Class canonical name: com.linbit.linstor.transaction.TransactionException Generated at: Method 'startTransaction', Source file 'ControllerSQLTransactionMgrGenerator.java', Line #32 Error message: Failed to start transaction Asynchronous stage backtrace: Error has been observed at the following site(s): |_ checkpoint ā‡¢ Restore node Stack trace: Call backtrace: Method Native Class:Line number startTransaction N com.linbit.linstor.transaction.manager.ControllerSQLTransactionMgrGenerator:32 ERROR REPORT 648E4932-00000-000020 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 00:38:51 Node: xcp-ng2 ============================================================ Reported error: =============== Category: RuntimeException Class name: TransactionException Class canonical name: com.linbit.linstor.transaction.TransactionException Generated at: Method 'startTransaction', Source file 'ControllerSQLTransactionMgrGenerator.java', Line #32 Error message: Failed to start transaction Asynchronous stage backtrace: Error has been observed at the following site(s): |_ checkpoint ā‡¢ Fetch thin capacity info Stack trace: Call backtrace: Method Native Class:Line number startTransaction N com.linbit.linstor.transaction.manager.ControllerSQLTransactionMgrGenerator:32 ERROR REPORT 648E4932-00000-000021 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 00:38:51 Node: xcp-ng2 ============================================================ Reported error: =============== Category: RuntimeException Class name: TransactionException Class canonical name: com.linbit.linstor.transaction.TransactionException Generated at: Method 'startTransaction', Source file 'ControllerSQLTransactionMgrGenerator.java', Line #32 Error message: Failed to start transaction Asynchronous stage backtrace: Error has been observed at the following site(s): |_ checkpoint ā‡¢ Fetch thin capacity info Stack trace: Call backtrace: Method Native Class:Line number startTransaction N com.linbit.linstor.transaction.manager.ControllerSQLTransactionMgrGenerator:32 ERROR REPORT 648E4932-00000-000023 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 00:38:51 Node: xcp-ng2 Peer: RestClient(127.0.0.1; 'PythonLinstor/1.15.1 (API1.0.4): Client 1.15.1') ============================================================ Reported error: =============== Category: RuntimeException Class name: TransactionException Class canonical name: com.linbit.linstor.transaction.TransactionException Generated at: Method 'startTransaction', Source file 'ControllerSQLTransactionMgrGenerator.java', Line #32 Error message: Failed to start transaction Error context: Modification of node 'xcp-ng1' failed due to an unknown exception. Asynchronous stage backtrace: Error has been observed at the following site(s): |_ checkpoint ā‡¢ Reconnect node(s) Stack trace: Call backtrace: Method Native Class:Line number startTransaction N com.linbit.linstor.transaction.manager.ControllerSQLTransactionMgrGenerator:32 ERROR REPORT 648E4932-00000-000024 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 00:38:51 Node: xcp-ng2 ============================================================ Reported error: =============== Category: RuntimeException Class name: TransactionException Class canonical name: com.linbit.linstor.transaction.TransactionException Generated at: Method 'startTransaction', Source file 'ControllerSQLTransactionMgrGenerator.java', Line #32 Error message: Failed to start transaction Asynchronous stage backtrace: Error has been observed at the following site(s): |_ checkpoint ā‡¢ Fetch thin capacity info Stack trace: Call backtrace: Method Native Class:Line number startTransaction N com.linbit.linstor.transaction.manager.ControllerSQLTransactionMgrGenerator:32

    Host xcp-ng3:

    ERROR REPORT 64905A1B-00000-000000 ============================================================ Application: LINBITĀ® LINSTOR Module: Controller Version: 1.21.1 Build ID: a677db312062add13e9b230b8b902d43a69caf13 Build time: 2023-03-22T14:05:41+00:00 Error time: 2023-06-19 09:37:36 Node: xcp-ng3 ============================================================ Reported error: =============== Category: Exception Class name: SocketException Class canonical name: java.net.SocketException Generated at: Method 'bind0', Source file 'Net.java, Unknown line number Error message: Protocol family unavailable Call backtrace: Method Native Class:Line number bind0 Y sun.nio.ch.Net:unknown bind N sun.nio.ch.Net:461 bind N sun.nio.ch.Net:453 bind N sun.nio.ch.ServerSocketChannelImpl:222 bind N sun.nio.ch.ServerSocketAdaptor:85 bindToChannelAndAddress N org.glassfish.grizzly.nio.transport.TCPNIOBindingHandler:107 bind N org.glassfish.grizzly.nio.transport.TCPNIOBindingHandler:64 bind N org.glassfish.grizzly.nio.transport.TCPNIOTransport:215 bind N org.glassfish.grizzly.nio.transport.TCPNIOTransport:195 bind N org.glassfish.grizzly.nio.transport.TCPNIOTransport:186 start N org.glassfish.grizzly.http.server.NetworkListener:711 start N org.glassfish.grizzly.http.server.HttpServer:256 start N com.linbit.linstor.api.rest.v1.config.GrizzlyHttpService:314 initialize N com.linbit.linstor.systemstarter.GrizzlyInitializer:88 startSystemServices N com.linbit.linstor.core.ApplicationLifecycleManager:87 start N com.linbit.linstor.core.Controller:365 main N com.linbit.linstor.core.Controller:613 END OF ERROR REPORT.

    Sorry, that was a lot of logs, but I don't know exactly what you'd be interested in seeing. It's possible that all of the logs from host xcp-ng2 are from the last time host xcp-ng1 melted down. I'm still trying to determine exactly when that happened overnight. šŸ™‚

    Let me know if you need to see anything else! Thank you!

  • kswapd0: page allocation failure under high load

    7
    0 Votes
    7 Posts
    554 Views
    olivierlambertO

    Use it from the sources then šŸ˜‰

  • gost server and ghost vm's

    4
    0 Votes
    4 Posts
    197 Views
    F

    the only thing referencing xcp-ng-02 when i xe vm-list

    uuid ( RO) : 0002a023-44d2-4185-a949-a8583d070a76
    name-label ( RW): Control domain on host: xcp-ng-02
    power-state ( RO): running

  • GPU passthrough, Windows 11 guest, "Working properly" becomes "Code 43"

    29
    0 Votes
    29 Posts
    10k Views
    olivierlambertO

    That might change in the future šŸ™‚ We are working on better chipset emulation that should help on many aspects šŸ™‚

  • Looking for hosting companies that can host XCP-NG VMs

    6
    0 Votes
    6 Posts
    503 Views
    A

    @bikepope Thank you. Useful information to understand the market landscape.

  • Windows 10 VM freezes when connecting through RDP

    Solved
    5
    0 Votes
    5 Posts
    392 Views
    olivierlambertO

    Ah great news! Thanks a lot for the feedback: it's really important to come back to tell when it works, as you said, it helps a lot the whole community!

  • Nvidia Quadro P400 not working on Ubuntu server via GPU/PCIe passthrough

    105
    0 Votes
    105 Posts
    25k Views
    olivierlambertO

    Yaaay!!! Nice catch!