Subcategories

• Compute

  All Xen related stuff
  605 Topics

  6k Posts

  T

  @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
• XO Lite

  The integrated web UI to manage XCP-ng
  26 Topics

  348 Posts

  O

  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).
• Migrate to XCP-ng

  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

  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.
• Development

  The place to discuss new additions into XCP-ng
  246 Topics

  3k Posts

  Y

  @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.