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

Re: [Xen-users] p2v wlh windows?

  • To: chris <tknchris@xxxxxxxxx>
  • From: Todd Deshane <deshantm@xxxxxxxxx>
  • Date: Thu, 23 Sep 2010 22:00:03 -0400
  • Cc: Xen-Users List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 23 Sep 2010 19:01:49 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; b=FAs9OL5jGzQgSUYy05pl/OepbsiO/o7suJAGc2Bsp/B910ikLc4J0xCQs8SErSeC9T +Zj+gHLjT/sB2PWi1khWHrEYsBUMaJd4dzOm4dVWwoHRA6636sIDWmOX/8EVrNSqg9Ae A6o/JMAmieqcZuFUYjL1edXymqMjq9vh5txK4=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi Chris,

On Thu, Sep 23, 2010 at 9:53 PM, chris <tknchris@xxxxxxxxx> wrote:
> I've been using Xen quite a bit the last 3 years and everything has
> been going very well. I usually create my vm's from scratch but
> occasionally for certain special situations I will p2v. I have run
> into a brick wall with p2v of wlh editions of windows (vista,server
> 2008, etc). Since these editions of windows have imaged based
> installs, they do not have the in place upgrade "repair" function that
> is in many earlier versions of windows. Has anyone been successful
> p2v'ing these versions of windows? I've tried various things from the
> recovery console, rebuild bcd, fix boot record, etc. I fully
> understand that the windows hal is what causes the bluescreen and
> causes it not to boot, and I've read some people being able to replace
> the hal dll's but it seems like there has got to be a better way?
> Any input would be appreciated.

Adding the IDE settings to the registry can help:

These links should help.


Todd Deshane

Xen-users mailing list



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