VMs run on their particular host servers. Citrix XenServer : CPU, memory, and network usage the number of running VMs on the host server and load average.Hyper-V : host health-critical values deposited pages network traffic CPU usage of guests, hypervisor, and in total.VMware : current reading and health status (via Web-based Enterprise Management (WBEM)), a general status as shown in vSphere (via Simple Object Access Protocol (SOAP)), and disk space of a VMware data store (via SOAP).The following monitoring data of your host servers can prevent issues in virtualized environments: You should closely monitor your VM host servers to be alerted if the hardware status changes in any significant way.īesides the standard hardware sensors, PRTG provides specific sensors for various virtualization host servers. If you have issues with your virtual machines (VM), the origin might be a host hardware failure. We recommend that you explicitly monitor the host hardware of your virtualization solution. In addition, you can identify potential bottlenecks that might affect your virtualized infrastructure. You can also get information about the network traffic and bandwidth usage of your routers and switches.Īlerts can tell you if there is an issue with a hardware component or if hardware resources are running out. With this monitoring technology, you can gather monitoring data such as CPU load, memory, and disk space. I found these links to be helpful: CTX122001 and Thread: Issue with reclaiming disk space in xenserver 6.0.įor the record, I'm running XenServer 5.6 SP2.Usually, you monitor most of the hardware components in your network with SNMP sensors. Subsequent rescans of my SR coalesced VDIs without problems. A few orphaned VDIs showed up which I promptly removed. I re-scanned the storage repository and it finally worked. This gave me a few warnings like 'open failed: Read-only file system' but in the end it did the trick. So I had to work it out using lvremove like this: After I ran vdi-forget I wasn't able to run vdi-destroy anymore.

I tried that, but that didn't fix anything. Now many people recommended running vdi-forget to get rid of this VDI. Vhd=VHD- scan-error=-22 error-message='invalid footer' Which, amongst others, gave me this line: usr/sbin/vhd-util scan -f -m 'VHD-*' -l VG_XenStorage-p ***** VHD scan error: vhd=VHD- scan-error=-22 error-message='invalid footer' In my case I had a VDI with an invalid footer. First of all check the file /var/log/SMlog on the pool master server and then trigger a rescan of the bad SR. This was nasty, because this meant it wasn't possible to backup virtual disks.Īfter reading comments on the XenServer forums for many hours I found a working solution. In the aftermath I had a corrupted storage repository, that manifested like this:Įrror parameters:, The VDI is not available Last week I encountered a weird issue with seemingly corrupted VDIs, which turned out to be fine after a server reboot. I've been happily running XenServer for a few years now.

Windows server vdi with xenserver host