1. Home
  2. XCP-ng

Subcategories

  • All Xen related stuff

    576 Topics
    6k Posts
    K
    @olivierlambert thank you! I did a little digging, but I could be looking at the wrong place, according to: https://github.com/xcp-ng/qemu-dp/blob/master/qemu-options.hx there is an option vga: none DEF("vga", HAS_ARG, QEMU_OPTION_vga, "-vga [std|cirrus|vmware|qxl|xenfb|tcx|cg3|virtio|none]\n" " select video card type\n", QEMU_ARCH_ALL) SRST -vga type ... none Disable VGA card. I tried setting this manually via "xe vm-param-set platform:vga=none " and I still get Cirrus PCI device created in the VM Is there something else that needs to be done to have no virtual VGA in the VM at all?

  • The integrated web UI to manage XCP-ng

    20 Topics
    280 Posts
    G
    @acebmxer I did install the certs, and everything went fine with that. But I never went back to try and install any uefi VMs through XO-Lite. Something I may or may not get back to, should really wipe the system and start fresh again to see how things have advanced. Things may be changing, and my lab may not have a physical place in my world. Which troubles me because I'll need to model things if this path turns into reality. Lots of unknowns right now.

  • Section dedicated to migrations from VMWare, HyperV, Proxmox etc. to XCP-ng

    98 Topics
    1k Posts
    olivierlambertO
    Don't blame yourself, XO UI isn't great. It will be a lot more natural in XO 6 VM creation

  • Hardware related section

    120 Topics
    1k Posts
    W
    @olivierlambert I Hello! I apologize for the long silence. Major medical and system hardware problems came up and had to be dealt with. I now have what I consider to be a very stable v8.3 install. I can report that the base i40 driver does not work with Intel x710 v9.54 firmware. In pfSense's console, both interfaces are report as active but there is no traffic flow, no response to a ping request, and the GUI is unavailable. I installed the alternate drive with both interfaces reported as active but again there is no traffic on the WAN interface. The LAN interface is ping-able and the GUI available. At this point I feel my option is to build the driver from source. As I am not a developer I asked (don't laugh) ChatGPT for a recipe. The installed kernel is 4.19.0+1 and ChatGPT claims 4.19.19-8.0.38.2.xcpng8.3 is the development kernel and is installed. Your input would be greatly appreciated. Best regard

  • The place to discuss new additions into XCP-ng

    241 Topics
    3k Posts
    lalitmaL
    Yes, you can install Windows Server 2022 Essentials as a VM on XCP-ng, but the issue is likely due to using a DELL ROK DVD. ROK media checks for DELL hardware during setup and won’t work properly in a virtual environment like XCP-ng. Instead, download the standard Microsoft ISO for Server 2022 Essentials and install that. If your DELL key doesn’t work or you need a new one, you can get a genuine key from Noxkeys.com for around $20 worked perfectly for me. Activation was smooth after that.
Log in to post
Load new posts
  • A

    Windows Server not listening to radius port after vmware migration

    6
    0 Votes
    6 Posts
    91 Views
    nikadeN
    @acebmxer said in Windows Server not listening to radius port after vmware migration: After migrating our windows server that host our Duo Proxy manager having an issue. [info] Testing section 'radius_client' with configuration: [info] {'host': '192.168.20.16', 'pass_through_all': 'true', 'secret': '*****'} [error] Host 192.168.20.16 is not listening for RADIUS traffic on port 1812 [debug] Exception: [WinError 10054] An existing connection was forcibly closed by the remote host After the migration I did have to reset the IP address and I did install the Xen tools via windows update. Any suggestions? I am thinking I may have the same issue if i spin up the old vm as the vmware tools were removed which i think effected that nic as well.... On your VM that runs the Duo Auth Proxy service, check if the service is actually listening on the external IP or if its just listening on 127.0.0.1 If its just listening on 127.0.0.1 you can try to repair the Duo Auth Proxy service, take a snapshot before doing so. Also, if you're using encrypted passwords in your Duo Auth Proxy configuration you probably need to re-encrypt them, just a heads up, since I just had to do so after migrating one of ours. Edit: Do you have the "interface" option specified in your Duo Auth Proxy configuration?
  • A

    What to do about Realtek RTL8125 RTL8126 RTL8127 drivers

    5
    0 Votes
    5 Posts
    852 Views
    A
    @stormi Unless new Dom0 is Kernel 6.15 or newer (with updates), this will be an ongoing problem to support the newest hardware as they seem to keep updating the chips (you can't stop progress). The current r8125 driver in 8.2/8.3 supports the 8125 and some 8126 chips, but not 8127. Other than supporting the new hardware versions of the chips, I have not seen any real complaints posted about the current r8125 driver (may be there are some Vates tickets?) While the risk on the new driver is low, it is different (not just an update). I agree that it would be best to have r8125-module-alt for the new code and then r8126-module and r8127-module. Note, that the new r8126-module driver should not be installed without the r8125-module-alt as the existing r8125-module would conflict with the new r8126-module driver. The work is already done (compiled and running)... I'm just waiting for Realtek to fix some issues with the new code before it's worth fully testing the drivers (issues already acknowledged by Realtek).
  • J

    Best practices for small/edge/IoT deployments? (remote management, power)

    5
    0 Votes
    5 Posts
    127 Views
    H
    We have some sites with a single-host XCP-ng pool backed by a small UPS. We install nut directly in dom-0. I'm aware of the policy for adding anything to dom-0 but we believe this usecase fits in the recommendations (simple enough, no vast dependencies, marginal resources usage, no interference ...). With proper testing works pretty well. nut inside a dedicated RPi definitely makes sense for a site with multiple hosts backed by the same UPS.
  • C

    Unable to Access MGMT interface/ No NICS detected

    24
    4
    0 Votes
    24 Posts
    441 Views
    C
    @AtaxyaNetwork I'll check it out! Im currently on chrome. So ill see if they have something close to it. Thank you!
  • D

    Migration compression is not available on this pool

    9
    0 Votes
    9 Posts
    141 Views
    henri9813H
    Hello, We tried the compression feature. You "can see" a benefit only if you have a shared storage. ( and again, the migration between 2 nodes is already very fast, we don't see major difference, but maybe a VM will a lot of ram ( >32GB ) can see a difference. If you don't have a shared storage ( like XOSTOR, NFS, ISCSI ), then you will not see any difference because there is a limitation of 30MB/s-40MB/s ( see here: https://xcp-ng.org/forum/topic/9389/backup-migration-performance ) Best regards,
  • mdavicoM

    Debian 9 virtual machine does not start in xcp-ng 8.3

    5
    2
    0 Votes
    5 Posts
    85 Views
    olivierlambertO
    OK so potentially a vCPU topology issue
  • D

    [HELP] XCP-ng 4.17.5 dom0 kernel panic — page fault in TCP stack, crashdump attached

    25
    0 Votes
    25 Posts
    1k Views
    bleaderB
    I think whatever solution suits you will work. Personally, if I know there are issues with it, I would tend to disable it in the bios, to be sure nobody tries to use it later and waste their time, in a enterprise settings, that can be important. One thing to keep in mind if keeping it, is that if you want to add other hosts to the pool, they will need to have similar network topology, so if you endup having eth0 and eth1 with your current management network on eth1, any new host should be able to have its management on eth1 as well. You may work around it with interface renaming, but that tends to get messy over time. That being said, I'm unsure even removing the realtek nic from the bios will change the interface number now that eth1 exists already and is configured. If you don't plan to add hosts to the pool, and don't have a team with people that may act on these machines in the future without being aware of this setup history, leaving it connected and disabling the port on switch should not be an issue.
  • U

    Multi gpu peer to peer not available in vm

    4
    0 Votes
    4 Posts
    118 Views
    olivierlambertO
    Hmm I'm not sure it's even possible due to the nature of isolation provided by Xen Let me ask @Team-Hypervisor-Kernel
  • R

    Internal error: Not_found after Vinchin backup

    56
    0 Votes
    56 Posts
    2k Views
    olivierlambertO
    So you have to dig in the SMlog to check what's going on
  • B

    Migrating from XCP-ng Windows guest tools to Citrix

    20
    0 Votes
    20 Posts
    1k Views
    B
    I did it that way so as to get the old Citrix driver first, and then let it update and watch it reboot. That was my logic anyway. @dinhngtu said in Migrating from XCP-ng Windows guest tools to Citrix: @bberndt Okay, I managed to reproduce your situation. I think it's because the "driver via Windows Update" option was enabled after installing the XS drivers, which caused the drivers to lock onto the non-C000 device and prevent updates from coming in. Normally, XenClean should be able to fix the situation. But if you want to fix things manually, or if things still don't work (C000 is still not active), here's a procedure that should fix the problem: Take a snapshot/backup/etc. Keep a note of static IP addresses (if you have any; there's a chance those will be lost). You can also use our script here: https://github.com/xcp-ng/win-pv-drivers/blob/xcp-ng-9.1/XenDriverUtils/Copy-XenVifSettings.ps1 Reboot in safe mode and disable the non-C000 device. Reboot back to normal mode; it'll ask you to reboot a few more times. The C000 device should now be active and you should be able to get driver updates again. (Optional) You can now enable and manually update the non-C000 device (Browse my computer - Let me pick).
  • R

    Pool Master

    8
    0 Votes
    8 Posts
    178 Views
    R
    @olivierlambert Dang ok. I waited a few minute then clicked the Connect in XOA for that host and it connected. Not sure what to do really.
  • G

    v8.2.1 rolling pool update getting stuck

    4
    0 Votes
    4 Posts
    121 Views
    olivierlambertO
    Do you have any SR using a VM? (like an ISO SR in a NFS share inside a VM). This is freezing NFS and makes host taking half an hour to restart. Logs should tell you why the RPU failed if it failed
  • H

    Other 2 hosts reboot when 1 host in HA enabled pool is powered off

    10
    0 Votes
    10 Posts
    543 Views
    olivierlambertO
    It's impossible to answer right off the bat without knowing more in details what's going on. HA is a complex beast, and combined with HCI, requires a lot of knowledge to find what's causing your issue, between both xha and XOSTOR. In other words, it is very demanding to analyze all the logs and trying to make sense of it. However, I can give you some clues to make sense of it: The HA log is at /var/log/xha.log. When you shutdown a host, you should be able to watch (on each host) what the HA is deciding to do. My gut feeling: there's maybe a XOSTOR issue making the heartbeat SR being unavailable, and so all hosts will autofence Then you need to understand the XOSTOR logs for why the cluster wasn't doing what's expected. My best advice: remove HA first, and only then investigate on XOSTOR. Kill on node (not the master) and check if your VMs are still able to start/snapshot/write inside.
  • J

    PXE Boot from new VM not working

    2
    2
    0 Votes
    2 Posts
    108 Views
    bleaderB
    @JBlessing as it looks like it does start, it looks like the networking side is working, at least at first. Just for debugging purpose you could try to switch that VM to BIOS instead of UEFI if it is possible, maybe it is related to what the pxe is starting in the VM. You could also try switching the VM between realtek and e1000 NIC, at this stage, PV drivers are not there so it is using an emulated NIC, maybe the image your PXE starts doesn't like the one you're using and it gets stuck somehow. As you're already using it with vmware, I assume you know how to size your VM, but if you went for a tight RAM value for this VM, you could try to give it more RAM to see if that could be related, as everything has to fit in RAM at some point, we may be using more at startup than vmware… Hope one of this can help
  • R

    Can't get slave out of maintenance mode after yum updates

    3
    0 Votes
    3 Posts
    113 Views
    olivierlambertO
    About the xsconsole: sometimes it's not refreshing. You can try to get access to the console, then type "xsconsole" it will start it and you should see it works You must have the master up to date if you want your slave to connect again. I never tried to elect a new master in the middle of the upgrade, I would discourage it. Better shutdown some VMs on the master, upgrade it and you are automatically back on track.
  • R

    VM failed and won't start. Displaying "An emulator required to run this VM failed to start"

    35
    0 Votes
    35 Posts
    2k Views
    olivierlambertO
    Then try to find anything happening around that time on other hosts, equipment, storage and so on.
  • msupportM

    XCP-NG Kubernetes micro8k

    3
    7
    0 Votes
    3 Posts
    299 Views
    nathanael-hN
    Hello @msupport we published a step by step guide, read more in the announcement there https://xcp-ng.org/forum/post/94268
  • B

    NFS multipathing configuration

    xcp-ng nfs xenorchestra
    9
    3
    0 Votes
    9 Posts
    514 Views
    B
    Great, thank you!
  • F

    XCP-NG 8.2.1 slave node of cluster unresponsive. after hardware reboot (with software reboot the system hang for 20min) the node is unable to contact the master node...

    3
    0 Votes
    3 Posts
    139 Views
    F
    @Danp yes I ran "yum update" to be sure but "nothing to upgrade" on the pool-master. I try with storage (iscsi) NIC configured and without Storage NIC configured but the pool join freeze. Seems that persist some "SESSION" (may be referred to the slave host previously configured?) or some incoerence in the pool database... from /var/log/xensource of the slave host when try to join the pool: "session_check D:520c5b4e5b36 failed with exception Server_error(SESSION_INVALID, "
  • MK.ultraM

    Automating VM configurations after mass VMware imports

    9
    0 Votes
    9 Posts
    437 Views
    olivierlambertO
    Thanks, this is helpful We'll discuss that with the @Team-DevOps and try to get things implemented!