@stormi I've placed the tarballs here https://student.oedu.se/~peder/xcp-ng/
I changed the static min to 512M, to match the Fedora case, but it still failed.
Olivier, I'm not using Xen Storage motion but I am using two old Lenovo L430 Thinkpads as "servers" so that could be part of the problem.
I'll install a new C7 guest and see if the problem persists.
@dan2462 Don't know what's causing the error but you can export the VHD by ssh:ing to your server or selecting "Local Command shell" on the console and running the following
xe vdi-list
xe vdi-export uuid=the-uuid-of-your-VM filename=filename.vhd format=vhd
Make sure the location you're saving to has enough space for the file.
If you have curl installed on your VirtualBox machine you can run
curl -u root:your-xcpng-root-password -X GET "server-name-or-IP/export_raw_vdi?vdi=your-vdi-uuid&format=vhd" -o filename.vhd
on it.
I don't know if it's the case here but one not-so-obvious thing in XO(A) is that you have to enable the slider to accept unverified certificates when you try to connect to the XCP-ng server.
The error here does suggest there's something else going on but make sure to check the above.
You should also install the XOA to make sure there's nothing wrong with your self-compiled XO.
Run this in a command shell on your XCP-ng server to install the appliance
bash -c "$(curl -s http://xoa.io/deploy)"
You can also run the vm-clone command on the XCP-ng server.
Something like
xe vm-clone new-name-label="clone name" vm="original name"
Stopping xo-server before compiling shouldn't be necessary unless someone tries to use XO while it's building.
That said, I would recommend building the source under /usr/src or ~/src or something and then moving the files ( mv * ) to something like /opt/xen-orchestra-DATE (or git revision)
Then use "stow" to create symlinks in /usr/local, like this
stow -d /opt/ -t /usr/local xen-orchestra-DATE
The stow command is in the CentOS repository or can be downloaded and compiled separately from any GNU mirror.
Make sure the /etc/xo-server/ config points to the relevant symlinks in /usr/local and restart xo-server
This way you can keep a number of different XO versions available in /opt and if there's a problem with any one of them you simply run
stow -D -d /opt -t /usr/local xen-orchestra-BADVERSION
to delete the symlinks to the bad version and
stow -d /opt -t /usr/local xen-orchestra-GOODVERSION
to create links to the old, good one and then restart xo-server
When it's time to update the XO build go to the, now seemingly empty, source folder and run
git reset HEAD --hard
to repopulate the working directory and then
git pull && yarn && yarn build
AFAIK XO can only create a new storage repository, it would be nice to being able to attach an existing one as well.
@tonyp90 I did file a feature suggestion, https://github.com/vatesfr/xen-orchestra/issues/4273 , but not a bug report.
I'm using the xsconsole on the xcp-ng server itself in the few cases where I need to re-attach an SR.
@ccsmith Is Firefox's System Preferences > Keyboard > Input Sources set to U.S. , or whatever language you're using?
I don't know if it's related but some guy in https://support.mozilla.org/de/questions/1217111?&mobile=0 had set it to Unicode Hex and had problems with Option-Shift-Arrow
Can you ping the server reliably? Because it kind of seems like it's a network problem.
Start a CMD prompt on your XCP-ng Center PC and run ping -n 30 192.168.66.17 to see if you get packet losses.
If you do then it's probably a bad NIC or cable or switch port.
I don't know if it's the case here but one not-so-obvious thing in XO(A) is that you have to enable the slider to accept unverified certificates when you try to connect to the XCP-ng server.
The error here does suggest there's something else going on but make sure to check the above.
You should also install the XOA to make sure there's nothing wrong with your self-compiled XO.
Run this in a command shell on your XCP-ng server to install the appliance
bash -c "$(curl -s http://xoa.io/deploy)"
You can also run the vm-clone command on the XCP-ng server.
Something like
xe vm-clone new-name-label="clone name" vm="original name"
@jmccoy555 said in CEPH FS Storage Driver:
device-config:server=10.10.1.141,10.10.1.142,10.10.1.143
Are you sure that's supposed to work?
Try using only one IP-address and see if the command works as intended.
@x-rayd
If you have 3 VMs that each have a 5TiB disk and you want to back up all of them you need at least 3x5=15TiB on the SR for the initial snapshots. Then you also need some extra GiBs or TiBs for the deltas.
The workaround is to set up the SR as EXT, instead of LVM.
Then it's using thin provisioning, meaning that the snapshot only uses as much space as you have data in each 5TiB disk.
So if your VMs are only using 1,3 and 4 TiB of actual disk space then you only need an SR that's 1+3+4=8 TiB + the extra space for the deltas.
@dan2462
Plug the USB stick into your XCP-ng server and run
dmesg | tail
# You should see "sdb: sdb1" or something similar at the bottom of the screen
mount /dev/sdb1 /mnt
cd /mnt
# Make sure you've mounted the correct device and partition :
df -h .
# You should see that it's the expected USB size
If that's the case run the xe commands to save on the USB.
When that's done you run
cd /root
sync
umount /mnt
Then it's safe to remove the USB
@dan2462
I don't think you can do a CLI export to ova.
You couldn't in 2015, at least
https://discussions.citrix.com/topic/361151-how-to-export-to-ovaovf-with-command-line/
If you absolutely need ova you have to try and figure out why there's a communication failure.
My guess would be something network related, like a firewall between the XCP-ng server and your XCP-ng Center PC.
Or you're not using the correct setting on the Network page.
Someone said "To solve it I simply had to choose an unused static IP on the same subnet as the Network Management Console where the server pool resides."
I don't know what ports the transfer uses and a quick google search didn't show anything either.
@dan2462 Don't know what's causing the error but you can export the VHD by ssh:ing to your server or selecting "Local Command shell" on the console and running the following
xe vdi-list
xe vdi-export uuid=the-uuid-of-your-VM filename=filename.vhd format=vhd
Make sure the location you're saving to has enough space for the file.
If you have curl installed on your VirtualBox machine you can run
curl -u root:your-xcpng-root-password -X GET "server-name-or-IP/export_raw_vdi?vdi=your-vdi-uuid&format=vhd" -o filename.vhd
on it.