Article: Just How Do Exclusions In App-V Packages Work?

Aaron Parker, at the terrific Stealthpuppy blog, has written a great article about exclusions in App-V packages. If you utilize this technology in your environment, I would recommend you keep this handy for future reference. Read his article here:
http://blog.stealthpuppy.com/virtualisation/just-how-do-exclusions-in-app-v-packages-work/

Thanks,
Alain

Article: An overview of virtual appliances for Citrix XenServer

An overview of virtual appliances for Citrix XenServer

Alexander Johnsen put together a list of virtual appliance that are avaialble for Citrix XenServer.  Check it out at: http://www.ervik.as/index.php/citrix-mainmenu/xendesktop/3231-an-overview-of-virtual-appliances-for-citrix-xenserver

Thanks,
Alain

XenServer: Fish and dead hosts stink after three days

Fish story

Prolog:
We had a XenServer go down and it required a rebuild.  The problem was that we could not use the same name until the old server was removed from XenCenter.  Using XE Host-Forget UUID=<Host UUID> did not work because the pool master thought a VM was still running on the missing server.  However, using some other, more drastic commands, we managed to remove the host UUID from the pool master so we could not use the typical XE commands to shut down the VM and remove the host.

Get to work:

Here are the steps I used to remove the host (these commands were culled from different sources, so hopefully putting them in once place will be a benefit)For the purposes of this example the dead server will be known as FISHHEAD and the pool master IP will be 192.168.1.1.

I first had to get the UUID of FISHHEAD which was no longer in the host list, so I ran this command from a server with XenCenter installed:

xe –s 192.168.1.1 – u root –pw <MYROOTPW> pool-sync-database

This generated the following error:

You attempted an operation which involves a host which could not be contacted.
host: 5491fe8d-70ae-4a82-aae1-ab2719f1469e (FISHHEAD)

Now with the UUID of FISHHEAD I ran this from the pool-master’s console.

xe vm-list resident-on=5491fe8d-70ae-4a82-aae1-ab2719f1469e

Which listed FISHHEADGUEST (UUID=1d75984e-1b9c-0ea0-0a22-8db2175ca70f) which was preventing the removal of FISHHEAD.

I used this command to power off FISHHEADGUEST :

xe vm-reset-powersate uuid=1d75984e-1b9c-0ea0-0a22-8db2175ca70f force=true

Finally, I could use host-forget to remove FISHHEAD.

xe host-forget UUID=5491fe8d-70ae-4a82-aae1-ab2719f1469e

Thanks,
Alain