@bikemuch I registered an XOA-account to keep a few machines with XOA maintained. It's free, not much to loose.
Many of us are looking forward for a 9.0 release, including a modern 5.x or even 6.x kernel, including all the developments and improvements, that have been made.
Also things like 16TB+ disks on block storage (incl. thin provisioning) etc.
If your company is running a bigger environment: You can put priorities on features as a paying customer. 
@bikemuch While you're technically not wrong about the impression, especially Linux distros usually work with flawlessly with the former version template.
I also saw that there's a user-test running with updated templates including Debian 13 etc.
It should be GA in about 2 weeks.
IIRC I just "tried again".
It failed 2 times, then I looked up the logs from other console, removed the file (which shouldn't be of any importance for our instance) and retried without reboot.
I copied the whole installer-log to the usb stick before finshing the install. 
(Could actually be a good hint or even a menu-option for those, where the install fails and won't leave it on the harddrive - e.g. evaluating hardware)
[ 128.517356] ata1.00: exception Emask 0x0 SAct 0x800000 SErr 0x0 action 0x0
[ 128.517357] ata1.00: irq_stat 0x40000008
[ 128.517359] ata1.00: failed command: READ FPDMA QUEUED
[ 128.517362] ata1.00: cmd 60/80:b8:10:6c:d4/00:00:02:00:00/40 tag 23 ncq dma 65536 in
res 41/40:10:80:6c:d4/00:00:02:00:00/00 Emask 0x409 (media error) <F>
[ 128.517363] ata1.00: status: { DRDY ERR }
[ 128.517364] ata1.00: error: { UNC }
[ 128.518008] ata1.00: configured for UDMA/133
[ 128.518018] sd 0:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 128.518020] sd 0:0:0:0: [sda] tag#23 Sense Key : Medium Error [current]
[ 128.518021] sd 0:0:0:0: [sda] tag#23 Add. Sense: Unrecovered read error - auto reallocate failed
[ 128.518024] sd 0:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 02 d4 6c 10 00 00 80 00
[ 128.518025] print_req_error: I/O error, dev sda, sector 47475840
[ 128.518039] ata1: EH complete
[ 128.581286] ata1.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x0
[ 128.581287] ata1.00: irq_stat 0x40000008
[ 128.581288] ata1.00: failed command: READ FPDMA QUEUED
[ 128.581291] ata1.00: cmd 60/08:c8:80:6c:d4/00:00:02:00:00/40 tag 25 ncq dma 4096 in
res 41/40:08:80:6c:d4/00:00:02:00:00/00 Emask 0x409 (media error) <F>
[ 128.581292] ata1.00: status: { DRDY ERR }
[ 128.581293] ata1.00: error: { UNC }
[ 128.582111] ata1.00: configured for UDMA/133
[ 128.582117] sd 0:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 128.582118] sd 0:0:0:0: [sda] tag#25 Sense Key : Medium Error [current]
[ 128.582119] sd 0:0:0:0: [sda] tag#25 Add. Sense: Unrecovered read error - auto reallocate failed
[ 128.582121] sd 0:0:0:0: [sda] tag#25 CDB: Read(10) 28 00 02 d4 6c 80 00 00 08 00
[ 128.582122] print_req_error: I/O error, dev sda, sector 47475840
[ 128.582133] ata1: EH complete
[ 128.629307] ata1.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x0
[ 128.629309] ata1.00: irq_stat 0x40000008
[ 128.629310] ata1.00: failed command: READ FPDMA QUEUED
[ 128.629313] ata1.00: cmd 60/08:48:80:6c:d4/00:00:02:00:00/40 tag 9 ncq dma 4096 in
res 41/40:08:80:6c:d4/00:00:02:00:00/00 Emask 0x409 (media error) <F>
[ 128.629314] ata1.00: status: { DRDY ERR }
[ 128.629315] ata1.00: error: { UNC }
[ 128.630068] ata1.00: configured for UDMA/133
[ 128.630074] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 128.630076] sd 0:0:0:0: [sda] tag#9 Sense Key : Medium Error [current]
[ 128.630077] sd 0:0:0:0: [sda] tag#9 Add. Sense: Unrecovered read error - auto reallocate failed
[ 128.630078] sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 02 d4 6c 80 00 00 08 00
[ 128.630079] print_req_error: I/O error, dev sda, sector 47475840
[ 128.630092] ata1: EH complete
Indeed it looks like the SSD should be replaced.
8.3 is running stable on this (and all other hosts, I upgraded) so far.
It's a system at a UAS, running various student projects for several years now, coming from XenServer originally. I voluntarily maintain it. Thx for the hint!
@dinhngtu I can't say on XCP-ng side, but it's likely linked to:
August patch (and following), as Microsoft changed something to the NVMe stack.
Google gives a lot about it. It seems that it most likely doesn't kill NVMes but can cause trouble.
We have a few PCs becoming more unstable (BSODs) or even very slow after that upgrae.
I often wondered what's the general purpose of that option.
As I only have 1 - 2 socket servers, I always choose 1 socket with x cores (mostly 2 - 8, not exeeding 1 real CPU).
Also for historic reasons: Sockets have been limited, but not cores.
Does it generally make any difference on Xen side/backend?
VM OS might handle it different due to NUMA optimizations.
After upgrading my first server successfully, I upgraded another one recently (different environments, no pool), but it failed.
I remembered from the forum to check installer logs, so I copied the whole directory (in case it contains useful info) and switched to another console (ALT+F3?) to see where it failed.
I don't know if it's documented somewhere, but following that console is pretty informative, rather then just seeing a progress bar.
Older windows types didn't hide what the installer is doing. It's a bit sad XCP-ng "hides" that.
tl;dr: The problem seemed to be:
STANDARD ERROR:
cp: error reading '/tmp/primary-jqbXmQ/usr/lib64/python2.7/lib-dynload/_codecs_hk.so': Input/output error
cp: failed to extend '/tmp/backup-TbutMQ/usr/lib64/python2.7/lib-dynload/_codecs_hk.so': Input/output error
As it was during backup phase, nothing was broken and I could just retry... to end up with the same problem.
As it looks like some hongkong locales, I just removed the file and tried again: with success.
Backup ran through, install/upgrade went fine. Box is running since.
I didn't back the file up, but with "ls" it looked fine like everything else. Also nobody ever touched that file. I can't say why, but wanted to drop it here, for archival purposes. Maybe someone else stumbles over a close or similar problem.
As the logs and other terminal give quite some information about current actions, debugging was somehow fun and it was interesting to dig a bit into what the installer is actually doing. Big pro over Microsoft... which often is a big pain to debug.
If you want the whole installlog-dir: I still have it, but will delete the next days, if not.
Greetings
@nikade I found out the HPE MSA2060 has a full flash bundle option, wich is suprisingly cheap, so our SAN has 3.84 TB SAS SSDs - they'll be good within a few hours, but our backup server has a RAID6 with 10 TB HDDs.
@nikade It's also RAS. The risk of a 2nd failing disc during rebuild is a lot higher than usual.
Our B2D2T server needs about 24 hours for that.
@olivierlambert said in First SMAPIv3 driver is available in preview:
Hi,
8.3 release is eating a lot of resources, so that's the opposite: when it's out, this will leave more time to move forward on SMAPIv3
Lots of work means lots of changes, means: I'm exciting about it. Also sounds more like a 9.0, if that much work is going into it.
@hsnyder AFAIK every - even not so - modern RAID controller can do 'verification read', 'disk scrubbing' or however they call it. It won't fix bitrot with single parity, but it can fix a single and detect dual bit failures.
That's why the only option for our SAN is: RAID6 respectively any DP algorythm.
@Paolo If it's only for that: Any HW-RAID with DP should do the job. (in case you don't fully go for SW-RAID)
@bufanda mostly RAM is "required" if you go for things like online-deduplication, as that needs to be handled within the RAM.
I configured our servers to 12 GB memory for dom0 anyways, as it helps with the overall performance. 3 GB can be pretty tight if you have a bunch of VMs running.
IIRC generally rather 8 are recommended nowadays. (unless you have a rather small environment)
@olivierlambert I know the problem of a shared FS, the quesion I had was rather: does qcow2 or vhdx have benefits above each other. What are pros/cons with the choice of one.
Does it matter at all?
@still_at_work the question is technically wrong. It's less depending on SMAPI, moreso on the "drivers" that it'll be able to use.
Someone needs to implement something for thin provisioned shared storage that could handle it.
e.g. via GFS2 or something else.
You could make your own "adapter"/"driver" (I forgot how they called it) for it, like they did with ZFS.
@john-c as well as FC. Basically all shared storages that are production ready.
What are the up/downsides of qcow2 vs. VHDX?
@ThierryC01 said in XCP-ng Windows PV Drivers 8.2.2:
Why is there no video drivers for Windows, I have a Windows 10 Pro VM and the video lags a bit compared to my Linux Desktop VMs despite having 8GO RAM and 16MO (?16 max???) video memory.
Because it's rudimentary GFX and has no acceleration at all. It's not made for what you might expect.
Also something to keep in mind: It's not only about NUMA (which is different since 2nd Epyc gen, as they have all memory channels on an IO-Die and only split the caches now), it's also about memory bandwith!
So it adds more complexity and depends on the needs of your workload.
If it benefits from high memory bandwith, a 2nd socket doubles it (technically)!
I've set up a test-environment and indeed it worked. Commvault was (is?) checking for specific version/agent string when connecting to XS/CHV/XCP-ng and in older versions refused to connect to XCP-ng.
I successfully installed the agent on a proxy-vm (it uses a proxy to ro-mount the VM-VHDs and backup the content), connected the pool, delivered the VM-inventory and also ran a successful backup:
In other words: If you're using Commvault (11.28+) you're not any longer locked on Citrix.
@reinvtv said in NFS nconnect support:
As far as I understand it, this will give us multiple tcp streams over an LACP link, truely aggregating traffic on multiple interfaces. (Until now, you needed to use iSCSI multipathing for this, which isnt able to thin provision.).
You're neigher right nor wrong: LACP is more complex than just bundling NICs and in many cases it will NOT give you any benefit.
Why? Simple: For that you need to have NFS using multiple ports but stay with same MAC and IP, which means that your LACP balancing algo needs to be set (and support) L4.
Many just go L2 or L3 (means they decide on MAC or IP-Address).
As a quick search didn't answer me: If it even doesn't go that 'passive range' multiple port way: In typical environments it won't help you at all with LACP.
One might correct my post.
Also interesting: https://vastdata.com/blog/meet-your-need-for-speed-with-nfs/
@florent said in Backup solutions for XCP-ng:
@cg we are envisaging various way, from using iSCSI to access tape from the VM, to using an agent on the tape (but here we'll have to support physical hardware patching , updating ) . There is also a lot of work to ensure we write sequentially without concurrency and to make it work with the futur dedup and to keep a catalog of backups / tapes
I don't know every product, but yet I've never seen a Tapedrive/Library using iSCSI.
iSCSI is usually only used by storage systems, not by devices or libraries.
Common interfaces are either SAS or - especially in larger environments - Fiberchannel. So your way to go, probably, is to passthrough an HBA.