-
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
-
-
No, you should delete base as well if you want to remove all snapshots, then the screen will go back to the empty one with the "There are currently no snapshots of this VM" message
-
Once you've deleted everything it should say "There are currently no snapshots of this VM"
-
You can highlight multiple snapshots in XenCenter and then delete them which will achieve the same thing.
- 1
-
that's the metadata volume and it's 4M not 4G and looks correct.
At a guess I say this is likely to be a drive that only support 4K native block sizes and as such not compatible with Citrix Hypervisor which requires the ability to write at 512byte block granularity.
-
XenServer 7.6 is out of support and at risk from publicly disclosed security vulnerabilities you should upgrade to a newer version or switch to a different hypervisor as soon as you can.
-
The drivers on the Citrix website are the only ones that Cisco have certified for use with Citrix Hypervisor. When they request new ones to be updated they will be updated on the Citrix website.
-
No, they don't, XenCenter handles all of that.
-
That script will, if I'm reading it correctly, delete the vhcache files for the parent VDIs as they will not be returned by your call to vbd-list.
-
@davidpages
Thanks for that update, glad you've resolved it. This is interesting though
tapdisk 2959 root 11w REG 8,5 16359 0 68343 /var/log/blktap/tapdisk.2959.log (deleted) tapdisk 3749 root 11w REG 8,5 9130 0 68335 /var/log/blktap/tapdisk.3749.log (deleted)
(and all the others similar).
That looks entirely unexpected and I'll go dig into the code to see if I can work out what's going on as that looks like a bug to me.
I assume that there wasn't any manual intervention at any point to clean up space which might have accidentally deleted files that were open in running processes?
-
Just look for exceptions in the log.
Or, run "tail -F /var/log/SMlog" while you take a snapshot and it will all be in that block (save the log to a file if you use an ssh client like putty) and then you can read just what happens in the time frame of interest.
-
@Mike Maggio you can email me the /var/log/SMlog file from the primary server in the pool and I'll take a quick look. Address is just my dot separated name @citrix.com
-
yes, may be better deploying new hardware with clean install and then migrating workloads as appropriate, but as it looks like that mostly PVS (and that looks like a very old version of PVS, and XenApp, unless I'm mistaken) then it's probably easier to deploy fresh there as well.
-
Pending means "running" and not complete. You can see it's in progress by the 0.419 (i.e. 41.9% complete)
-
You should also be aware that XenServer 7.6 is long out of support and is not receiving any updates, even security related fixes.
-
You won't want to hear this but the Dell R720 is no longer supported with Citrix Hypervisor since Intel dropped support for the CPU after one of the sets of SPECTRE/MELTDOWN bugs was unfixable on the CPU family used by that host (Intel IvyBridge).
-
Anything still running XenServer 6.2 is at high risk of security compromise. There are many unpatched and publicly known security issues, not least the entire SPECTRE and MELTDOWN CPU speculative execution exploits.
You should be making urgent plans to move to something else, whether that be Citrix Hypervisor 8.2 or a different solution entirely.
-
That looks like there are some unlinked but open files on the SR which are using a lot of the storage. They won't show up in "du -h" but they do contribute to the usage reported by "df". Unless you can find the process that has the files open the only solution is probably to reboot the host.
-
This is a confirmed bug in xsconsole where the DNS settings are not retained. A fix has been made but has not yet been released.
-
XenServer 7.0 is now out of support (and had been in priority security support mode for a couple of years prior to that).
-
Have you tried using XenCenter to change this or only xsconsole?
-
Also, XenServer 7.2 is long out of support now. This issue sounds like one that may have been fixed but you would have to upgrade to at least Citrix Hypervisor 8.2 in order to get a fix.
-
As Tobias says, to enable access to the RDP port on a VM you do not need to modify the firewall rules on the Hypervisor itself. The VMs are on a separate "guest" network and the only firewalls present are those implemented within the VM operating systems themselves guessing Windows here as you want RDP access).
-
@Mike Maggio yes, the workload balancer appliance installs as a VM onto your hypervisor pool and provides the capabilities that you're looking for.
-
Note that Citrix do not support installing any third party software into Dom0 or modifying the shipped firewall rules for any purpose.
Citrix Hypervisor snapshot refresher...
in Miscellaneous
Posted
Sorry, yes, you're quite correct Alan, there is no option to delete base or now so just deleting the three snapshots will leave it empty.