Hey thanks for working on XCP-ng Center -- I find it a really useful tool.

Is this a README that describes how your project differs from XenCenter.

FWIW -- I had a similar problem with VMs going randomly down -- it wasn't windows but various BSD and Linux VM's. Sometimes they would run a few days, other times they would lock up every other day. Logs didn't help because when the VM locked, logs were not written. I even had the xcp-ng installation lock a few times, although it was usually on of the VMs. I started searching for faulty hardware and eventually SMART tested all the drives and mem86 the RAM. Turns out I had some bad RAM modules which I later RMA'd. With new RAM (after after thoroughly testing it), I haven't had any lock ups. I'm not sure this will help you at all.

@olivierlambert

Well damn -- you're right.

Well VM now up and running. Just have to figure out how networking works in this new copied VM. Thanks for help.

Not that you actually needed this reply, but confirmed patch works after upgrade this morning.

Thanks for update and the patch.

@nikade Hey thanks for for the link. I ended up just using a LetsEncrypt cert rather than self signed. I think had to add a DNS host override on my router to associate the Local LAN address of the xo server with the domain name of the server contained in the certificate -- Like 10.0.1.50 ---> xo.example.com. Thanks for pointing me in the right direction on this one.

@tjkreidl

So here is the dilemma I'm running into, the host I added with the incorrect network ports and such. It was reachable via the internet until I upgraded some pool patches, now its extremely unreachable. I can boot the installation, however I can't reach the slave to eject the host.

I tried emergency resetting network, however that didn't work either.

lshw -C network reveals a lot of unclaimed ethernet controllers which are the Intel 225-V version. I looked up various internet resources to see what "unclaimed" meant, and these sources suggest there isn't an appropriate driver -- which is weird since prior to the pool patches applied this installation was up and running (but misconfigured).

Sooo -- I either have two options at this point, and I don't really care. I'd like to eject this pool member -- destroy it -- however it seems I can't since it's unreachable, or I need to reinstall the I225V network driver.

Any suggestions?

@olivierlambert

Well damn -- you're right.

Well VM now up and running. Just have to figure out how networking works in this new copied VM. Thanks for help.

@olivierlambert

Here is my Home view screen -- the VM I'm trying to copy is called "Arch Time Machine". It's up and running on the original hypervisor. There are no running or halted VMs on the second hypervisor

@olivierlambert

Sorry both are 1TB -- I'll correct my prior post to reflect

Here is how I copied the VM --

I choose the SR (zfs disk on hypervisor #2) and chose zstd for compression.

@olivierlambert said in Question regarding copying of VMs within storage pool:

The VM should be visible on the second host, likely in a "halted" state.

Not exactly what I'm seeing here -- in fact I don't see any evidence of any halted VM -- probably because I did something incorrectly.

On the second hypervisor I running a 1Gb nvme drive which was partitioned during the installation process with partitions of /var/log, /boot, /efi, /, and SWP.

I have a second 1Gb SATA drive which I added as a zfs storage pool accessible as /mnt/tank.

Within the zfs pool I can see the copied VM (aedbfce5-7365-4d16-b39c-0b3c93a210f6.vhd).

Do I need to create a VM on the second host using this particular .vhd file?

So I've recently been blessed by building a second xcp-hypervisor. I'm trying to copy/recreate a VM on the second hypervisor which is located on the initial hypervisor.

I've added both the initial and second hypervisor to a pool. From within Xen Orchestra I selected the hypervisor I wanted to copy and selected the copy option and chose the destination to be the local zfs storage located on the second hypervisor. I waited about 30 min for VM to be copied.

Now what do I do? The copy operation completed -- how do I create the VM the second host using this copied image? Confused what to do at this point.

@lawrencesystems

Possibly I'm thinking about this all wrong, but I usually keep all my management interfaces on a different VLAN other than native. Perhaps the wrong approach.

Re: Change management network interface?

So I'm referencing the thread above.

I'm playing around with a new xcp-ng installation -- been awhile since I've done this -- amazing how much I forget after you get a system up and running.

Anyway I'm trying to set the management interface up using VLAN 40. I have no idea how to do this as it defaults to VLAN1. It's frankly very very awkward as it's not possible to specify a VLAN within the xcp-ng configuration screen.

I believe I was able to change the vlan management by connecting the new instance to my currently running XO server -- add a new tagged network associating it with the current XO host, and then the option suddenly appeared within the drop down list within the managment console terminal. (Hopefully that makes sense).

There is probably a way to do this via the command line, however the referenced command: xe host-management-reconfigure pif-uuid=<PIF_UUID> doesn't exactly have anything to do with VLANs that I can find. In fact the Citrix Documentation isn't very elusive about this either. I guess I'm looking to do this all at the command line, XO, or at the management console without having to jump back and forth between methods which makes the process clumsy.

Not that you actually needed this reply, but confirmed patch works after upgrade this morning.

Thanks for update and the patch.

@olivierlambert

I'm ok with RTFM.