When you boot in UEFI mode, press "e" to edit the boot command line, you have a line to change the memory for dom0.

I did the manual installation via the XVA. It worked for me.

@akurzawa said in Extrlemy slow backup speec = about few MB/s: @nikade said in Extrlemy slow backup speec = about few MB/s: Maybe you saw the same thing I did - I also had major issues with backups. Then in the summer of 2019 I upgraded our XOA (Yes, we have the paid version) and everything was going 3-4x times faster. Must have been some major improvement in the XOA code. So maybe some official info that if you have XO from source Your backup speeds will be as low as 3-4 MB/s? Or what? Sorry if I was unclear - XOA is built from the same sources so there is no difference in that aspect. All tho, there was a big performance issue regarding backups which was resolved. I am using XO from sources in my "private" infrastructure and I can assure you there are no "limits" on purpose.

How about doing your own matrix?

Feedback/tests is REALLY vital for the community We might have spotted this, or not. So we spared bundling another ISO/upgrade after the release Thanks again!

@dvdhngs install onto (mdadm/ZFS) RAID 10: no to use (mdadm/ZFS) RAID 10 as SR: yes, of course!

P.S.: I gave my latest "trick" another run: Did a full copy of the VM within xo to the other host. While that job ran, I started the delta backup that finished OK. After the copy was done I deleted the copy and saw - as last time - that the host was coalescing. After finishing the sr's advanced tab is empty again and stayed empty.

@danp said in XCP-ng 7.5.0 final is here: @dblogic said in XCP-ng 7.5.0 final is here: Just tried updating our pool and after updating the master had failed migration of VM (Ubuntu) and then was unable to get VM to start (Missing VDI error). Only solution was to roll master back to 7.4 and everything working again. I ran into a similar situation when I upgraded to 7.5 this week. Did you check to see if there was a non-existent ISO mounted in the CD rom for the VM in question? Thank you. That was my problem. I gave cd empty. Everything works.

Actually, looks like I had already written something about it in the Updates Howto: https://github.com/xcp-ng/xcp/wiki/Updates-Howto#a-special-word-about-xcp-ng-75-76-and-live-migrations

anyone can request a change in https://github.com/xcp-ng/xenadmin/issues

@stormi dd stands for disk dump and does exactly that: Copy a stream of data. Fio however can be configured for precise workloads and read/write mixes, parallel workloads etc. So the first thing will only give you streamline benchmarks, what almost nobody cares about. The second can simulate realworld (VM/database...) workloads, where (controller) Caches and non magnetic storage (Flash, Optane, MRAM...) makes the real difference. Also use big amount of data, since caches can impact small ones extremely. Don't get me wrong: We need them and they can make huge differences, but as long as your benchmarks fully fit into them, it gives your nonsense/fake results. Also (consumer) SSDs start throttling after some 10 to a very few 100 GB of data written. Their caches fill up and they 'overheat'. You can spend days on benchmarks and how to do what.

A slightly less hacky work around for USB v1 passthrough based on the issue I created: --- /opt/xensource/libexec/usb_scan.py 2019-11-04 10:03:02.000000000 +0000 +++ /tmp/usb_scan.py 2020-03-01 17:32:29.266317478 +0000 @@ -152,10 +152,11 @@ _CLASS = "bDeviceClass" _CONF_VALUE = "bConfigurationValue" _NUM_INTERFACES = "bNumInterfaces" + _USB_SPEED = "speed" _PRODUCT_DESC = [_DESC_VENDOR, _DESC_PRODUCT] _PRODUCT_DETAILS = [_VERSION, _ID_VENDOR, _ID_PRODUCT, _BCD_DEVICE, _SERIAL, - _CLASS, _CONF_VALUE, _NUM_INTERFACES] + _CLASS, _CONF_VALUE, _NUM_INTERFACES, _USB_SPEED] _PROPS = _PRODUCT_DESC + _PRODUCT_DETAILS _PROPS_NONABLE = _PRODUCT_DESC + [_SERIAL] @@ -590,7 +591,10 @@ pusb["path"] = device.get_node() # strip the leading space of "version" - pusb["version"] = device[UsbDevice._VERSION].strip() + if int(device[UsbDevice._USB_SPEED]) <= 12: + pusb["version"] = "1.00" + else: + pusb["version"] = device[UsbDevice._VERSION].strip() pusb["vendor-id"] = device[UsbDevice._ID_VENDOR] pusb["product-id"] = device[UsbDevice._ID_PRODUCT] pusb["vendor-desc"] = device[UsbDevice._DESC_VENDOR] in theory any deice which is "low" or "full" speed (i.e. USB1) will have it's version number changed to 1.00 which forces xenopsd to use a USB1 bus. It may have side effects if the driver in the guest relies on the version number so caveat emptor.

I tested on a fresh 2016 install. The install went well and the management agent was installed. I enabled VSS but the VSS snapshots don't seem to be working. To compare I installed the citrix client tools on a fresh 2016 install and VSS does work.

Thanks for your input! I think it might be the one then Also, if there is a big problem with it, we can always update the package!

Should I still just get a different NIC card?

Here's another willing script tester

Oh ok.. I know why... mount.ceph came in nautilus release. I have edited the post to install nautilus. Unlike RBD, CephFS gives browsable datastore + thin disks and is super easy to scale up/down in capacity with immediate reflection. I'd spend some time later to implement "Scan" and have a proper SR driver. Thanks for testing and feel free to raise if you come across further issues.