This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: [Xen-users] boot a existing windows in hvm domain

To: "Keir Fraser" <keir@xxxxxxxxxxxxx>, "Mats Petersson" <mats@xxxxxxxxxxxxxxxxx>, AL.LINUX@xxxxxxxxxxx
Subject: Re: [Xen-devel] Re: [Xen-users] boot a existing windows in hvm domain
From: "Brady Chen" <chenchp@xxxxxxxxx>
Date: Thu, 9 Aug 2007 11:05:15 +0800
Cc: tygrawy@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, Z24 <z24@xxxxxxx>
Delivery-date: Wed, 08 Aug 2007 20:02:45 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=I23T58H3LO9j49SAa0mpUZ1sE7I2zuZgxNfSTgAPDFPQ+pZZezR246fGRv8W1DC2Gn0AjZjdzyOneVZhf/vzDEMmAlAJEsobCxYRGjugvKfH1W2y2XVPhq8/WMboKRzJ1VTZmemoy77tC1zp/MUktfxKfK015jJ72Rr4rAYhOfo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oKkTBlLQ+OJOSY2WqhRHQw5kEzbhdnm9enWLeUXMRt6BdP+kMahAPh/LPFOj1gb9q7Hle87ZzsOYNfXPYYeDk35Znl2xja/CO63qyw9mAW9JpnMI8YJMRjm6QW3VYSlxLacelJzWn76PcJ1E9p6u3lTyhGbWT9u5KcjIvk5+bP4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2DFE580.C410%keir@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <46ba0137.18e7300a.328b.ffffab4c@xxxxxxxxxxxxx> <C2DFE580.C410%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Keir, Mats, Archie, and all others
Thank you guys all.

I just read this

seems Randy Thelen tried to fix this issue one year ago, unfortunately
that patch doesn't work for me.

Finally I think we have the conclusion that I have to give it up on my
T60 Laptop now.
But I'd like to try in this way:
install windows in xen hvm guest, and then try to boot it in native
environment. Hope it works.

BTW, Keir, Mats, Any plan/schedule to support a full functional real
mode simulator? Or do you know anyone are working on this? thanks

On 8/9/07, Keir Fraser <keir@xxxxxxxxxxxxx> wrote:
> On 8/8/07 18:45, "Mats Petersson" <mats@xxxxxxxxxxxxxxxxx> wrote:
> > At 17:19 08/08/2007, Keir Fraser wrote:
> >> No, it's a processor mode halfway between real mode and protected mode 
> >> which
> >> all x86 processors support, but which vmxassist is really rather bad at
> >> handling. If this is a big-real-mode copy loop then that might explain why
> >> the loop is executing so bizarrely, and may mean you are out of luck until
> >> we retire vmxassist.
> >
> > And the fact that EDI is 0xC33FE when it tries to write to the memory
> > at address of EDI indicates that it's Big-Real-Mode.
> Yes, that's a giveaway.
> So I think the 'fix' here is to not try booting your native Windows
> partition on Xen. It's not likely to work too well anyway, as it'll look
> like all your hardware has changed, causing activation problems and also big
> driver changes whenever you switch between running on Xen and running
> natively.
> You're better off having a dedicated Xen Windows installation, perhaps on an
> LVM partition.
> The problems that others have been seeing are quite likely not the same root
> cause as yours. Most times there's an early boot problem it will end up with
> a trap and backtrace in vmxassist, when running on Intel CPUs.
>  -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>