Hi there
I also have this issue. Neither in XCP-NG-Center nor in XO I am able to use Shift + PgUp to scroll upwards. (Just nothing happens)
I tested it with Ubuntu 18, 20 and also with Rocky 9.1 VMs.
Is there a way to activate it?
Many thanks,
Cheers
Hi there
I also have this issue. Neither in XCP-NG-Center nor in XO I am able to use Shift + PgUp to scroll upwards. (Just nothing happens)
I tested it with Ubuntu 18, 20 and also with Rocky 9.1 VMs.
Is there a way to activate it?
Many thanks,
Cheers
Hi There
I have the same issue on BSD (in fact opnsense). If I do the same testing with a linux vm (ubuntu 18) beside, I get >1Gbs. But with the more or less same settings on opnsense (Freebsd 13.1) it will stay <1Gbs. (Set 9000 MTU manually on both vms)
Is this a known issue with bsd, or is it worth investigating further?
Cheers.
Hi There,
Just to mention, my personal hopes are for the future, that whatever kernel will be used, RPM packages will still be supported to install.
Usecase:
I am using Dell / Quest DR-Appliances for Backups. They've implemented RapidCIFS and RapidNFS in order to do kind of CBT enhancement on these protocols. So when backing up - only delta is copied.
However, as usual, they provide this driver officially only for Windows and RHEL. Therefore I could install the RPM on the XCP-Hosts, and benefit from this. It's running amazingliy smooth.
I would assume that there might be more of such use cases, and keeping support for RHEL packages could be wise in oder to keep a foot into the "enterprise door".
Thanks, for your work!
Regards,
RaHu
@olivierlambert hi there, looks like I found my mistake... I made IP-Ranges instead of prefixes in Netbox in order to prepare the sync. 
therefore, IPs which don't fit in any prefix will be dropped in netbox.
So actually, for quick and dirty, the well known 3 internal ranges are fine to cover all internal ips: 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16
is there any sync of the host itself to netbox (hostname, interfaces, ips, macs => netbox.device) ?
Thanks for your guidance!
@olivierlambert
hmm do be honest, I am using the docker-image from ezka77/xen-orchestra-ce:latest
I guess, even if I pull the latest version, it won't be really the same as if installed manually...
thanks for the tip with the console output - somtimes you miss the easy things... I just checked the output in my container... I probably have to do some cleanup first.. XO is heavily complaining about xo:storage WARN Xapi#_getUnhealthyVdiChainLength
The About-Screen looks different - maybe this indicates to you, what I have "under my feet"?
thanks,
As requested by Olivier, I put this in here instead of github:
Hi there,
I am on XO from the sources.
XCP-NG 8.2.1 Servers
min. 1 Ubuntu 20.04 VM with Agent 7.20 installed
Version: xo-server:5.91.0 / xo-web 5.95.0
Netbox-Version: 3.2.2
I just set up a new Netbox Instance (plain install on a ubu-vm, no docker this time).
The "token pairing" all went fine, and the sync does not seem to produce any errors, as far as I can see in XO->Settings-Logs (So far so good! ;D )
However, looking into Netbox shows me the cluster and VMs with uuid's. VMs have also their resources and NICs with MACs, but the IP address(es) is missing! Under IPAM -> IP Addresses, I don't have a single IP listed.
Sadly I don't have a clue, where to find the log, showing wha's going on during the sync. I am thinking about a missing dependency-object on Netbox side, or about a slight API-change on either side, which now causes the IP part to break. But as said, as I don't find any further details about what happened in the background, these are only theories.
It would be nice if someone could guide me to find the logs (cli), so I could dig for more information and provide this here.
Many thanks in advance!