[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] windows vps can not start after a reboot


  • To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
  • From: Jingyun He <jingyun.ho@xxxxxxxxx>
  • Date: Tue, 22 Dec 2009 11:00:40 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 22 Dec 2009 02:01:20 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=wTiMyZeITUsPONBjBHz2AbYct/feTelUcDXRO7jr4UUZc4OHQydtjgNrG91VsdqV50 BsegvckJaH2qtnkRYRs4iITy0CU7fhThB0+3nsIkMc1hfqbtQh6TwhWR2zdlEjZmS4og tMfQGkvSOFp6d/gX5TQ5mWSt61oc43nGlITnY=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello,
I still have this issue for many VPSes, here are more information I
have right now.
When the windows vps can not boot up, it will report that some files
are missed, or corrupt.

Usually I boot up the vps with windows installation cd, and enter the
repair mode,
and execute the command chkdsk /r
Then after this the system will boot up again, but after a few
reboots, the issue will appear again, Do you have any idea about this?

ONE MORE THING is that we do not install the OS manually, we just use
ntfsclone to clone the drive C to a new VPS, and boot it up.


On Sun, Nov 22, 2009 at 1:11 PM, Jingyun He <jingyun.ho@xxxxxxxxx> wrote:
> Yes, its using phy,
> I guess the system automated applied a few updates, but I'm not sure,
> and I rebooted the vps manually after changing host name.
>
> On Sun, Nov 22, 2009 at 1:08 PM, James Harper
> <james.harper@xxxxxxxxxxxxxxxx> wrote:
>>> Hello,
>>> We have a windows vps running for a few days, today after we rebooted
>>> this vps, it never started, and I got this message from the vnc
>>> console.
>>>
>>> Windows could not start because the following file is missing or
>> corrupt:
>>> <Windows root>\system32\hal.dll
>>> Please re-install a copy of the above file.
>>>
>>> the OS is windows 2003 std 32bits with GPLPV 0.10.0.138,
>>> and hypervisor is xen 3.4.1, and we are using LVM paritions.
>>>
>>> Any one know why does this happen?
>>
>> What was the reason for the reboot? Was it applying updates?
>>
>> Did it reboot cleanly as far as you know?
>>
>> What backend are you using? In using tap:aio I have seen similar
>> problems, but on an LVM volume I assume you are using phy, can you
>> confirm?
>>
>> James
>>
>>
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.