1. Home
  2. XCP-ng

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.
Log in to post
Load new posts
  • J

    Pool master and slaves cannot communicate with each other but can reach everything else

    7
    0 Votes
    7 Posts
    2k Views
    J
    Just updating for anyone that has the same issue, we ended up just rebooting the master and like @JamuelStarkey said everything just automatically fell in place. Did have to exit maintenance mode on the master and replug the PBD but everything else went back to normal immediately. Still frustrating to experience and would really love to know what caused this. If there's any logs I can pull to figure this out do let me know @olivierlambert
  • J

    This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • X

    XCP-ng Center 20.04.01 - console no "remote desktop RDP" on Windows 11 VM

    Solved
    15
    0 Votes
    15 Posts
    4k Views
    olivierlambertO
    Perfect!
  • kasn_codeK

    Multiple PCI-E passthrough problem

    3
    0 Votes
    3 Posts
    580 Views
    kasn_codeK
    So I managed to get the VM to see both drives. In dmesg I can see something like this [ 1.160149] ahci 0000:00:08.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x20 impl SATA mode [ 1.161043] ahci 0000:00:08.0: flags: 64bit ncq sntf ilck led clo only pmp fbs pio slum part [ 1.187888] ahci 0000:00:09.0: SSS flag set, parallel bus scan disabled [ 2.186211] ahci 0000:00:09.0: controller reset failed (0xffffffff) [ 2.187307] ahci: probe of 0000:00:09.0 failed with error -5 So I removed the pci and did a rescan with root@mars-test-uefi:~# echo "1" > /sys/bus/pci/devices/0000\:00\:09.0/remove root@mars-test-uefi:~# echo "1" > /sys/bus/pci/rescan Now when I checked dmesg it shows up properly [ 795.538214] ahci 0000:00:09.0: AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x4 impl SATA mode [ 795.538219] ahci 0000:00:09.0: flags: 64bit ncq sntf ilck led clo only pmp fbs pio slum part fdisk -l also shows up both drives now too root@mars-test-uefi:~# fdisk -l Disk /dev/sda: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: ST8000DM004-2U91 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sdb: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: WDC WD80EFZZ-68B Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes It seems like on boot it tries to find the device but it fails to, but on a remove/rescan it seems like its fine? The question now becomes, how do I make this work ON boot.
  • B

    This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • N

    Upgrade from 8.1 to 8.2

    Solved
    12
    1
    0 Votes
    12 Posts
    1k Views
    olivierlambertO
    Thanks a lot for your feedback!
  • B

    Ubuntu desktop issue

    1
    0 Votes
    1 Posts
    259 Views
    No one has replied
  • D

    Host dbsync failed and XAPI restart everytime after patches installation

    4
    0 Votes
    4 Posts
    446 Views
    olivierlambertO
    Really, you should because it would have prevent you this situation in the first place, but also some other future questions or problem you might have That's one of the few capital rules in XCP-ng world. Your master must ALWAYS be more recent than the slaves (or at the same level obviously), otherwise slaves won't be able to connect. I think you really need some assistance on best practices and such, please contact us so we can assist more generally. If this basic requirement is not understand, you might have other/deeper issues.
  • S

    Error: Connection refused (calling connect ) (XCP-ng toolstack hang on boot)

    8
    0 Votes
    8 Posts
    4k Views
    olivierlambertO
    Any of the host: if they are in the same pool, that's logical. Only the master is needed to be reach. XAPI will probably be in "Starting state" as long as all SR aren't plugged. If you have the SR on a VM on another host than the master, reboot the master only, you should be able to connect sooner Alternatively, check https://docs.xcp-ng.org/troubleshooting/
  • richiebyteR

    One VM forcibly restarts

    5
    0 Votes
    5 Posts
    906 Views
    richiebyteR
    On this one VM yeah, all other VM's have been fine with the Citrix tools. I am not sure if the tools change anything on the VM level once installed, as the problem did continue after attaching a fresh blank virtual disk to the problem VM.
  • S

    Ubuntu VM struck at boot

    2
    1
    0 Votes
    2 Posts
    536 Views
    planedropP
    How long have you waited for it? Like is it truly stuck or maybe just really slow to boot?