@marvine said in XCP-ng 8.3 betas and RCs feedback 
:
giving error code 43
This error is a driver issue on Windows side.
It says that the card is "virtualised" Nvidia is very strong in blocking this, if it's not allowed.
If you google for it there should be plenty of workarounds.
I see that there is a "known" limitation of the system.
See the following post.
https://xcp-ng.org/forum/topic/9389/backup-migration-performance/5
But also my question is, how can it drop down to 2MiB/s over the network. Even when I should have the possibility (according to iperf3) to pass through nearly 1GiB/s.
I once got 250MiB/s in the Logs of my Backups. I was on a 8.3 Beta but can't for the life of me see, where the speed as evaporated into.
Hi all,
i have my Host connected to my NAS via 10G Networking (over a different subnet).
dd if=/dev/zero of=/run/xo-server/mounts/{UUID}/test1.img bs=2G count=1 oflag=dsync
739 MB/s
Host: 6vCPU each with around 25%
NAS: 4CPU total of around 5% usage
The total speed is the same.
I also tested the Store backup as multiple data blocks instead of a whole VHD file. (creates 500-1000 files per backed up GB but allows faster merge) function for the nfs remote. No change.
nfsvers=4.1,async,noac,proto=tcp
Regarding that with bigger files and dd I have no issues. I did not expected an issue here. But i even changed on both sides the MTU. No change.
I disabled this everywhere.
I'm currently scratching my head for where the bottle neck comes from.
If I Backup with the same Instance a Remote Host (1G Down/50M UP) Network Link to a DC with 2G/2G Sync, I'm only getting like 4MiB/s in XO.
Anyone can point me in a direction or maybe help me with this Performance degradation in Xen Orchestra?
p.s. i'm not sure to post this in the backup or the Network Category, but regarding that the network works fine. I'll post it in backup
@olivierlambert
I'm known to "break" the systems to check if it's working correctly.
If you need any more information on how i "broke" it, let me know.
Greetings everyone,
i just looked at the new XO-Lite in the latest 8.3 Release.
The Access XOA Button managed to get the information, that my XOA is running. So that's awesome.
But
My XO is installed in a Docker Container and does not run on port 80 or 443, because i have it run behind Traefik.
It manages to find the Docker Internal Network IP.
I wouldn't expect it to work automagically with my special setup, but is there a plan to make a little config file where i could put my own IP/URL for this button, so that even on my other Hosts and Pools i could use one XO Appliance and have that quick link? 
@Andrew said in XCP-ng 8.3 betas and RCs feedback :
@stormi The CentOS Base yum repo need to be changed to the baseurl vault as the mirrorlist no longer works...
Oh yeah, i wanted to give that info to.
Is there any plan/information on a distro upgrade / distro rebase?
There is from plesk a centos2alma 8 script on the internet, if there is some ressource needed.
Hi there,
i was wondering for the install Image via ipxe, will there be something? I have it, that currently it only works with Legacy Bios and not the UEFI one.
Greetings,
i have 8.3 running on my MS-01, it's working fine.
I upgraded my network setup with a pfsense VM and some VLAN's (still work in progress).
But, when i open my pfsense VM i'm getting this regular message:
xenstore: could not write path attr/eth1.2/ip
the 1.2 is my VLAN2 on this interface. Is this a known issue/bug? If you need some logs, then ping me
If someone is already rocking and testing 8.3, what would be the best way to update?
A. Fresh Install 8.3 with the ISO
A.1 Afterwards importing configuration backup?
B. Update 8.3 beta with 8.3 ISO Upgrade path?
All i have from a screenshot, and from what i saw was ok, down i'll put the log i screenshoted to a colleague in the datacenter
[ OK ] Stopped TLS tunnel for xapi.
[ OK ] Stopped Generate TLS certificates for x
Stopping Generate TLS certificates for
[ OK ] Stopped Xapi storage script plugin serv
[ OK ] Stopped target System Time Synchronized
[ OK ] Stopped Wait for chrony to synchronize
Stopping Wait for chrony to synchronize
Stopping NTP client/server...
[ OK ] Stopped NTP client/server.
[ OK ] Stopped Tapback daemon for blktap3.
Stopping The Xen xenstore...
[ OK ] Stopped The Xen xenstore.
[ !! ] Forcibly rebooting: job timed out
What i just remember, is that my monitoring for my mailserver, running on a vm with alma and mailcow-dockerized, did not trigger until the Forced rebooting. Maybe in the "reboot" process the shutdown of the VM's hindered the process? I hadn't had that problem before. Just when i try to do the normal reboot process in XOA. This VM has the options Auto power on", "Protect from accidental deletion", "Protect from accidental shutdown" set to true. (Just verified the settings)
[ OK ] Stopped The Xen xenstore.
[ !! ] Forcibly rebooting: job timed out
That's all what i got from the console, if there is a log somewhere with more information, i'll be happy to provide it to you!
@stormi
I used "yum update" with the 8.3 repo in the yum.repos.d file activated.
After that i always do a sanity reboot.
So. I will post tomorrow some screenshots. But the install went 100% on first try. But the reboot process got timed out and it killed the job. After reboot everything works fine at the moment.
Can it be that after update and reboot and the bar goes to the left it needs a lot of time to reboot?
On tty 2 it hangs after “stopped the zen xenstore”
@usuari said in New Rust Xen guest tools:
Now we are considering to put the guest-tools in our repository (mirror) in order to get the templates automatically updated, but we couldn't find the right form to do it.
Currently we have a working and operational mirror, but when we put this:
deb [trusted=yes] https://gitlab.com/api/v4/projects/xen-project%252Fxen-guest-agent/packages/generic/deb-amd64/ release/Fails because couldn't find indexes:
Processing indexes: [PPPPPPPPPPPPPPPPapt-mirror: can't open index gitlab.com/api/v4/projects/xen-project%252Fxen-guest-agent/packages/generic/deb-amd64///release//Packages in process_index at /usr/bin/apt-mirror line 800. P]
Please see current issue on the gitlab repository.
https://gitlab.com/xen-project/xen-guest-agent/-/issues/18