Mark Syms
-
Posts
296 -
Joined
-
Last visited
-
Days Won
8
Content Type
Forums
Articles
Labs
Videos
TechZone
Citrix Community Articles
Events
Profiles
Posts posted by Mark Syms
-
-
Support for PV guests is removed because they are a security nightmare, in particular since the discovery and disclosure of SPECTRE, MELTDOWN and friends. Only HVM VMs are supported now.
-
Several things here.
- XenServer 7.6 is long out of support so you need to upgrade to Citrix Hypervisor 8.2 LTSR.
- To use https to connect to the hypervisor from XenDesktop the certificate on the hypervisor must be trusted by the server running XenDesktop. Out of the box this will not be the case the certificates on the hypervisor are self signed. See https://support.citrix.com/article/ctx128656?_ga=2.159144442.1132053.1629821742-1118127804.1580377989 for instructions on how to update the certificate. Citrix Hypervisor 8.2 has improved support for installing externally trusted certificates, see https://docs.citrix.com/en-us/citrix-hypervisor/whats-new/whats-new-since-7-1.html#security-improvements
-
It would be a question for VMware support and not Citrix anyway as it's nesting on VMware's hypervisor that is the important thing here.
-
This is not an XCP-ng issue, that's a core service of Citrix Hypervisor and yes, you can restart it like that, but why do you need to restart it?
-
Yes, the NBD server runs in read-only mode.
-
We don't support software raid in the Hypervisor Dom0 but that has nothing to do with software raid in the guest VM.
-
Raiding/striping disks inside the VM is the only option apart from GFS2 to get more than 2TB as a single device inside the VM. Citrix won't raise any red flags as what you do inside your VM is none of our business.
-
DVSC is deprecated and no longer supported, being fully removed in Citrix Hypervisor 8.2.
XenServer 6.5 is long out of support and has numerous unpatched and publicly disclosed security vulnerabilities (which have been fixed in newer and in support releases). You make a plan to migrate your deployment to something else as soon as you can.
-
There was an issue in the configuration of the network time daemon and it would cause the boot process to block until it timed out trying to connect to the network time server when none was configured. If you had a valid one configured it connected immediately and booted straight up.
-
Really do not expose your hypervisor to the internet even via a gateway.
-
CentOS 7 will run as an HVM guest. PVHVM is only used in special circumstances to wrap true PV virtual machines into an HVM shim. In most cases HVM is what you want.
-
At the risk of getting lynched by my product management, does Xen Orchestra satisfy your requirements? https://xen-orchestra.com/#!/xo-home
-
I think you meant the XS 7.1 Cumulative Update (CU being internally code numbered 7.1.2). You need to be licensed to access this release.
-
No, this has no impact on the hypervisor as whilst it uses packages from CentOS the majority are internally rebuilt by Citrix and we continue to support our product distribution including creation and distribution of security updates.
-
This is not possible.
-
All in support versions of XenServer/Citrix Hypervisor support SMB3 ISO Shares. The SMB SR has always required SMB3.
-
It definitely sounds like an issue with the OcenStore then. Creation of a new virtual disk on NFs should be practically instantaneous, taking 20 minutes is ridiculous and probably means there are lots of operations failing and being retried.
I'll ignore the fact that both XS 7.6 and CH 8.0 are long out of support as that isn't really relevant here.
-
Approved security approach is to not share the VM/Guest network with any other traffic. If you really much use the same NICs then you should put the storage traffic onto a separate VLAN.
-
the xs-container supp-pack no longer works with current Linux distributions and as a result support for this supplemental pack has been withdrawn.
-
1
-
-
I'm not sure which bit of you comments are accurate or not but the error messages
Quoteo [root@starbase3 ~]# multipath -ll
o Mar 25 19:39:22 | /etc/multipath.conf line 112, invalid keyword: getuid_callour
o Mar 25 19:39:22 | /etc/multipath.conf line 115, invalid keyword: prio_callout
o Mar 25 19:39:22 | /etc/multipath.conf line 116, invalid keyword: hardware_handlet
Show typos in the parameters getuid_callour instead of getuid_callout and hardware_handlet instead of hardware_handler are you sure the contents of the multipath.conf are actually correct?
-
When you disable CBT the empty snapshots will be reaped by the background garbage collection process (not instantly as the process can take some time). When you re-enable it will starty again from scratch.
-
There is no need to "break" the cluster to apply the update. Just run the update process from XenCenter and the hosts will update and reboot in sequence. As you are using GFS2 on 8.0 you should prioritise getting upgraded as there are a number of fixed issues in the GFS2 kernel driver.
-
Ignore any errors about cbtlog files. XenServer 7.6 had a bug where it would noisily complain about cbtlog even when CBT wasn't enabled.
-
That's the wrong log and not the one I mentioned in my comment above, looks like audit.log?
Citrix Hypervisor (formerly Xenserver) on Hyper-V
in Server Installation
Posted
Note, the support or lack of nested virtualisation here is irrelevant if your trying to run Citrix Hypervisor as the nestee, that just comes down to the outer hypervisor, be it VMware or Hyper-V. What is definitely not supported (or functional) is nesting another hypervisor inside Citrix Hypervisor.