Hi James :), On 3 slices, all W2003 built from the same base, the PV drivers install as expected. After the install though, if I include the XVD driver, none of my Windows settings appear to save over a reboot. This includes settings such as network (IP, etc..) and services (disabled, etc...). On XP I do not see this issue. Tried a few versions including 138. So, if I install and disable just the XVD driver (include network, scsi, shutdown monitor, etc...) everything is fine. If I include that driver during the initial install, I can no longer keep settings over a reboot. If I install everything but XVD, restart, change some settings, restart to show that the settings are kept, then install the XVD..... Nothing is saved after a reboot. Perhaps this is something that was discussed before and I have not found it, or it''s an obvious setup change I have been skipping? Any help/ideas appreciated. Thanks, JES _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Hi James :), > > On 3 slices, all W2003 built from the same base, the PV driversinstall> as expected. After the install though, if I include the XVD driver,none> of my Windows settings appear to save over a reboot. This includes > settings such as network (IP, etc..) and services (disabled, etc...). >What device backend are you using? (eg phy: file: tap:aio etc) James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 11/17/2009 12:14 AM, James Harper wrote:>> Hi James :), >> >> On 3 slices, all W2003 built from the same base, the PV drivers >> > install > >> as expected. After the install though, if I include the XVD driver, >> > none > >> of my Windows settings appear to save over a reboot. This includes >> settings such as network (IP, etc..) and services (disabled, etc...). >> >> > What device backend are you using? (eg phy: file: tap:aio etc) > > James >disk=[ ''phy:/dev/mapper/nt0026,hda,w'' ] Physical. Backend is an LVM slice. With the XP instance, I changed to xvda from hda once I had the drivers installed and noticed it appeared that would work :). I did not change away from phy: on the W2003 instances. JES _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 11/17/2009 07:41 AM, James MacLean wrote:> On 11/17/2009 12:14 AM, James Harper wrote: >>> Hi James :), >>> >>> On 3 slices, all W2003 built from the same base, the PV drivers >> install >>> as expected. After the install though, if I include the XVD driver, >> none >>> of my Windows settings appear to save over a reboot. This includes >>> settings such as network (IP, etc..) and services (disabled, etc...). >>> >> What device backend are you using? (eg phy: file: tap:aio etc) >> >> James > disk=[ ''phy:/dev/mapper/nt0026,hda,w'' ] > > Physical. Backend is an LVM slice. > > With the XP instance, I changed to xvda from hda once I had the > drivers installed and noticed it appeared that would work :). > > I did not change away from phy: on the W2003 instances. > > JESTried changing from hda to xvda. This resulted in continuous boot, install driver, reboot, install driver.... and sometimes blue screen on boot :(. So then changed phy:/ to tap:aio/ and first boot it installed the driver, but since then... it''s looking good. Not asking for the driver to be installed and settings are staying changed. So, why is phy:/ wrong, and isn''t phy:/ considered faster then aio:tap:/ ? Now I need to find some benchmark to run to show the affect of the new drivers :). JES _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James MacLean
2009-Nov-24 11:47 UTC
[Xen-users] Windows PV Drivers on W2003 Question - Service failing to start
Hi Folks, On all W2003 instances where James'' XVD driver is installed, on boot we are getting : "At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details." Yet, I am seeing no services failing to start. The only odd entry before this is : "The COM sub system is suppressing duplicate event log entries for a duration of 86400 seconds. The suppression timeout can be controlled by a REG_DWORD value named SuppressDuplicateDuration under the following registry key: HKLM\Software\Microsoft\Ole\EventLog" and after it is : "The IPSec Driver is starting in Bypass mode. No IPSec security is being applied while this computer starts up. IPSec policies, if they have been assigned, will be applied to this computer after the IPSec services start." I originally thought it was caused by Citrix starting up as it''s IMA service and other pieces sometimes do not all take off at the right time, but since the latest one was just a straight W2003 server I wanted to report it in case others have seen this, and perhaps, have a way to correct it :) ? Or perhaps I am not even looking for the right problem :(. Cheers, JES _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users