Subcategories

  • All Xen related stuff

    605 Topics
    6k Posts
    TeddyAstieT
    @EddieA Can you try differents combinations of passedthrough hardware in this VM ? e.g try with each device one by one at a time; at least in the VM
  • The integrated web UI to manage XCP-ng

    26 Topics
    348 Posts
    olivierlambertO
    It's not meant to be used like that. If you are behind a NAT, the right approach is to have your XOA behind the NAT and inside the same network than the hosts. That's because hosts will always use and return their internal IPs to connect to some resources (stats, consoles etc.). XOA deals with that easily as being the "main control point" for all hosts behind your NAT (or a XO proxy if you prefer).
  • Section dedicated to migrations from VMWare, HyperV, Proxmox etc. to XCP-ng

    115 Topics
    1k Posts
    A
    @florent said in vmware vm migration: @acebmxer yes after the first migration, XO knwo that the migration is incomplete and that you may want to finish it later. But if you start this VM direvtly , it will write some data, thus it won't be in sync anymore with the Vmware snapshot. Then XO won't be able to resume You can start a copy of the VM ( XO will handle it for you ) and delete the copy when you're done My advice is to migrate this VM to the right SR and then do the resume. But keep in mind that the V2V tool is intended to target only one SR, so migrate all they disk to the same SR, and select the right one when resuming the V2V. You can change the network after My previous migration was successful with no issues. Previously test vm was fresh install so no vmtools installed. But I did shut the vm down myself prior to starting the migration. VM boots no issues no prompts. This time I decided to follow the steps listed in the documentation as i have been following the changes and updates for the v2v migration. Following the steps as mention XO presented me with that prompt which was not mention in the documentation. As i was typing the post to gather my information it was then i noticed i did not select the proper destination SR and the appropriate nic/vlan for networking. So I noted that in the post. With the assumption i could correct that on the final migration. With that said the I guess the documentation should state - Start vm to test if boots, etc.. When prompted choose "Start a copy". When done shutdown vm and remove.
  • Hardware related section

    153 Topics
    1k Posts
    A
    @whyberg Nope... that feature is part of the CPU. But is that the actual problem? Maybe... As that machine is too old to do any real work, it's a fine toy. There are better faster cheap test machines available.
  • The place to discuss new additions into XCP-ng

    246 Topics
    3k Posts
    yannY
    @Tristis-Oris yes it is likely you're using a newer kernel, we likely need to rebuild the agent using a newer version of the netlink crate.
  • Endless Xapi#getResource /rrd_updates in tasks list

    85
    0 Votes
    85 Posts
    47k Views
    1
    Spoke too soon. Still getting them... Just much slower and father apart.. about 5-10 a day
  • 8.3beta2 dom0 kernel panic, possibly triggered by over-mtu packet?

    3
    0 Votes
    3 Posts
    481 Views
    W
    @bleader No, the opnsense box itself doesn't have wireguard (or anything else VPN-ish) running on it. It's mostly just a NAT with the normal variety of DHCP, DNS, ... services running on it.
  • After installing updates: 0 bytes free, Control domain memory = 0B

    92
    7
    0 Votes
    92 Posts
    49k Views
    nikadeN
    @Dataslak said in After installing updates: 0 bytes free, Control domain memory = 0B: @nikade @olivierlambert @stormi @Danp @yann Just wanted to say to you all: Thank you for your contributions and kind helpful assistance which has helped me through this crisis. I would have been in deep trouble without you. I respect your expertise, and appreciate deeply that you are working so hard to help us dumb users. I have learned a lot, and hope one day to become skilled enough to at least help other new users on this forum. Best wishes Aslak Happy everything worked out, this is what this community is all about. I've gotten a lot of help and given some too, it's all about helping out with the things that you can. With time you'll be able to help out more and more and more
  • 8.3 beta, crashed Windows11 VM when trying to snapshot with memory

    18
    0 Votes
    18 Posts
    2k Views
    stormiS
    Using dynamic memory is known to be prone to causing occasional issues. Thanks for the feedback. Oh, by the way, regarding vTPM and snapshots, we finally established that it's fully supported by XenServer 8 and that the documentation was just out of date.
  • cluster slave no connection to pool

    1
    0 Votes
    1 Posts
    306 Views
    No one has replied
  • Guest tools in nested XCP-ng

    Solved
    2
    0 Votes
    2 Posts
    293 Views
    olivierlambertO
    Hi, It's not possible.
  • XCP/Vates support hours

    support xcp-ng xostor
    2
    0 Votes
    2 Posts
    426 Views
    olivierlambertO
    Hi, No.
  • Hosts fencing after latest 8.2.1 update

    4
    0 Votes
    4 Posts
    703 Views
    J
    Right, so yeah I did just that - disabled HA and have been keeping an eye on the logs as well as general performance in the env. Glad to know my actions align with your recommendations at least There are a couple of hosts that get a lot of these sorts of messages in the kern.log: Apr 25 08:15:33 oryx kernel: [276757.645457] vif vif-21-3 vif21.3: Guest Rx ready Apr 25 08:15:54 oryx kernel: [276778.735509] vif vif-22-3 vif22.3: Guest Rx stalled Apr 25 08:15:54 oryx kernel: [276778.735522] vif vif-21-3 vif21.3: Guest Rx stalled Apr 25 08:16:04 oryx kernel: [276788.780828] vif vif-21-3 vif21.3: Guest Rx ready Apr 25 08:16:04 oryx kernel: [276788.780836] vif vif-22-3 vif22.3: Guest Rx ready Am I wrong to attribute this to issues within specific VMs (i.e. not a hv performance issue)? I know one of the VMs that causes these is a very old centos 5 testing VM one of my devs use and the messages stop when it's powered down. Is there any way to easily associate those vifs with the actual VMs they are attached to? My google-foo failed me for that. Other than that, I noticed my nic firmware is a bit old on the X710-da2's I use so I'm going through and upgrading those with no noticeable changes. I'm fairly hesitant to re-enable HA without tracking down the root cause.
  • Stuck in maintenance mode after joining pool.

    2
    8
    0 Votes
    2 Posts
    955 Views
    DanpD
    @DwightHat said in Stuck in maintenance mode after joining pool.: When I try to look at the host in Xen Orchestra it just says "An error has occurred". Check to browser's Dev Tools console when this happens. It will likely contain some additional details. You likely need to check the logs to find out why you are encountering this issue. Many times the "stuck in maintenance mode" issue is related to an unmountable storage repository. https://docs.xcp-ng.org/troubleshooting/log-files/
  • Whatchdog support for Linux and Windows guests

    4
    0 Votes
    4 Posts
    855 Views
    olivierlambertO
    This post specifically: https://xcp-ng.org/forum/post/57441 The person had issues to speak in English but wanted to tell this configuration worked. You can use the xen_wdt backend to rely on a Xen operation to force restart the VM. I have no idea how it works on Windows.
  • 0 Votes
    12 Posts
    2k Views
    A
    @lawrencesystems I think this is quite common when you need to test certain scenarios with multiple hypervisors (backup, migrations, etc.). You only need a couple of HVs with a few tiny running VMs. We have done this setup with nested esxi many times for testing purposes. And since e.g. Ubuntu and Windows work this way, the problem is probably specific to Debian (and maybe others?).
  • PXE Boot a VM and use HTTP for kernel/initrd download

    4
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    Question for @gduperrey or @stormi
  • USB pass-through device with wrong product and vendor identifiers on 8.2

    Unsolved
    3
    0 Votes
    3 Posts
    521 Views
    I
    @infodavid Finally, I follow an existing topic and configure nut-server on the hypervisor to access the ups via usb. I know that Olivier is not fully aligned with the fact that the host is modified but IMO it is an acceptable change on my XCP-NG host.
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    25 Views
    No one has replied
  • VMs are abruptly getting shutdown

    14
    0 Votes
    14 Posts
    2k Views
    J
    @lritinfra Something to consider also the HPE Intelligent Provisioning is the main way, outside of HPE iLO, HPE SUM or HPE SPP to update the server's hardware firmware. If you aren't using individual RPMs or SCEXE files for the task. With HPE Intelligent Provisioning and HPE SPP being able to update, both firmware and BIOS. As not all of the updates for firmware will be in a compatible format, for use with HPE iLO. I'm not sure if it has changed but an Administrator Password set on the BIOS (at minimum), also locks out (disables) access to the Erase option on the HPE Intelligent Provisioning. At least it does on my only HPE Server running an up to date BIOS, HPE iLO and HPE Intelligent Provisioning. Thus disabled HPE Intelligent Provisioning doesn't help with being up to date enough to fix vulnerabilities and bugs at hardware or firmware level.
  • 1 Votes
    6 Posts
    2k Views
    R
    @rjt Note to self about creating and managing appliances at xe cli. xe help --all | egrep -i '(appliance)' # find xe appliance related commands. appliance-assert-can-be-recovered, appliance-create, appliance-destroy, appliance-list, appliance-param-clear, appliance-param-get, appliance-param-list, appliance-param-set, appliance-recover, appliance-shutdown, appliance-start,
  • XCP-ng on a laptop - turning off the monitor

    5
    0 Votes
    5 Posts
    1k Views
    D
    @abudef I ran into the same thing on a dell latitude 5411, but I eventually found a workaround. In the BIOS under System Configuration there was an option called Unobtrusive Mode, and when enabled, a specific key combination will turn off the display and speakers, independent of the OS. The same key combination will then turn them back on when needed. While an automatic feature would be preferable, the manual option meets my needs since it would be rare to need to use the laptop screen. The one downside for me is that if power is lost long enough that the battery drains, the screen will need manual intervention after power is restored - the BIOS will turn the machine back on when it receives power, but won't put the screen back in its previous state. I put a sticker on the laptop with the key combination so I will remember it when needed.
  • XAPI servic failed

    8
    0 Votes
    8 Posts
    1k Views
    DanpD
    @sushant-diwakar I think you misunderstood @olivierlambert as he was referring to the support ticket that you opened with Vates, which is still open and awaiting a response from you. I restored the forum thread that you deleted because it contains information that is pertinent to this discussion. I'm leaving this topic separate for now, but IMO there really was no valid reason to start this new thread instead of continuing the prior one.
  • Pool Master unreachable

    8
    0 Votes
    8 Posts
    2k Views
    S
    @sushant-diwakar
  • Issues with PCIE Passthrough

    20
    0 Votes
    20 Posts
    4k Views
    J
    @ImThatFluffy said in Issues with PCIE Passthrough: @john-c Yea im not sure, it was either an issue with the way I had Debian setup or compatibility things booted up Ubuntu 22.04LTS with the HWE kernel and it worked perfectly. Well if you are using Ubuntu Linux 22.04.1 LTS or one of the later point releases then it would be using a Linux Kernel version 6.1 or later, when its a HWE kernel. So any bugs from earlier versions of the kernel would have been fixed, also the Intel ARC graphics hardware would have been released during one of the point releases. On the Debian Linux front a distribution version earlier than version 12.0 would have been unlikely to have complete properly functioning support, due to that release being the first one with the Linux kernel version of 6.1 or later.