1. Xen Pv Drivers

I use Citrix XenServer 5.5 and on a Windows Server 2008 R2 Guest there is installed Xentools 5.5, for a year all works well. After a restart we get a BSOD with Stop Code 7B, it is a problem with the Citrix pv-driver I think, but how can I delete this driver without GUI, safe mode also bring up a BSOD.So I install a second Windows Server on same VM and can access the filesystem of the Guest.

Xen Pv Drivers

Just tried XCP 0.5 rc Win PV drivers on Xen 4.0 x64 2.6.31 PVOPS kernel. Installation of XCP PV drivers in domU Windows 2008 x64 drivers went ok, no warning about driver signing. Unfortunately after reboot domU is stuck showing progressbar on black screen. Booting into safe mode works ok.

In the Windows/System32/driver I delete xenvbd.sys and scsifilt.sys in the registry I delete everything I found with xenvbd or scsifilt, but the BSOD is still here.The Windows Startuprepair and sfc /scannow dosent help.Update:All known Snapshots are with the same Issue. If you install the Xen PV driver on a guest and you get the BSOD with stop 7B it is possible that the driver is corrupt or some files are missing. First you should find out the version of the driver: go to filesystem and get properties of - for example - xenvbd.sys then go to your XenTools Installdisk and search for the following Files: xenutil.sysxenvtchn.sysxenvbd.sysscsifilt.sysAfter copy this files to WindowsSystem32Drivers you can start your Guest in safe mode. Now you can install a newer version of the Xentools from safemode (you find a install file on Xentools that works also in safemode) and you will get some errors. Don't reboot your server. Deinstall this Programm now and a cleanup will starts, all corrupt or missing files and registry Entries will delete and cleanup your installation.Now reboot and it works! I'm glad the problem is resolved, and I'm upvoting the question.

The problem was after I realize that the driver installation was wrong I try to deinstall the driver but it would be better to revert to another snapshot on that the driver was not installed. So next time when I install a new driver and this produce failuers than I revert. The deinstallation routine from the driver has some failures and this wrong registry entries and sys Files affect the problem. In this case the reason is long time ago and so I need the above solution to solve the problem.–May 19 '13 at 21:13.