From: George Dunlap <george.dunlap@eu.citrix.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: "Tim (Xen.org)" <tim@xen.org>, Eddie Dong <eddie.dong@intel.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Bug: Windows 2003 fails to install on xen-unstable tip
Date: Tue, 16 Apr 2013 16:32:45 +0100 [thread overview]
Message-ID: <516D6F1D.7020007@eu.citrix.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A10C92830@SHSMSX101.ccr.corp.intel.com>
On 16/04/13 16:24, Ren, Yongjie wrote:
>> -----Original Message-----
>> From: xen-devel-bounces@lists.xen.org
>> [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of George Dunlap
>> Sent: Tuesday, April 16, 2013 10:22 PM
>> To: xen-devel@lists.xen.org
>> Cc: Dong, Eddie; Tim Deegan; Suravee Suthikulpanit
>> Subject: [Xen-devel] Bug: Windows 2003 fails to install on xen-unstable tip
>>
>> The other day I just happened to try to install Windows 2003 on
>> xen-unstable tip. After booting the CD and copying the files, the
>> whole thing stops at "Setup is starting Windows".
>>
> 64bit or 32bit Windows 2003?
> We already covered 64bit Windows 2003 guest booting on Intel hardware in
> our auto testing system.
> (Of course, no installation is covered in our auto testing.)
> That booting case passed with changeset 26783 in xen-unstable tree.
> BTW, we use pure upstream QEMU.
This is 32-bit -- it's Windows 2003 Enterprise Edition SP2, 32-bit. I
just tried the 64-bit install and it does the same thing.
Win7 32-bit seems to work as well.
-George
next prev parent reply other threads:[~2013-04-16 15:32 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 14:22 Bug: Windows 2003 fails to install on xen-unstable tip George Dunlap
2013-04-16 14:34 ` Jan Beulich
2013-04-16 14:35 ` George Dunlap
2013-04-17 8:27 ` Jan Beulich
2013-04-17 18:13 ` George Dunlap
2013-04-18 8:13 ` Jan Beulich
2013-04-18 9:03 ` George Dunlap
2013-04-19 10:05 ` Jan Beulich
2013-04-19 10:44 ` Roger Pau Monné
2013-04-19 12:47 ` Jan Beulich
2013-04-19 13:28 ` Roger Pau Monné
2013-04-19 14:33 ` Jan Beulich
2013-04-19 14:41 ` Roger Pau Monné
2013-04-19 13:51 ` George Dunlap
2013-04-22 11:05 ` Jan Beulich
2013-04-22 15:32 ` George Dunlap
2013-04-23 10:25 ` Jan Beulich
2013-04-23 10:38 ` George Dunlap
2013-04-23 11:33 ` Jan Beulich
2013-04-23 11:52 ` George Dunlap
2013-04-23 11:57 ` George Dunlap
2013-04-23 12:45 ` Jan Beulich
2013-04-23 12:25 ` Jan Beulich
2013-04-23 13:00 ` Jan Beulich
2013-04-23 14:21 ` George Dunlap
2013-04-23 14:43 ` jacek burghardt
2013-04-23 14:47 ` George Dunlap
2013-04-23 14:55 ` Jan Beulich
2013-04-23 14:57 ` George Dunlap
2013-04-23 15:02 ` Jan Beulich
2013-04-23 15:46 ` George Dunlap
2013-04-23 16:04 ` Jan Beulich
2013-04-23 16:12 ` George Dunlap
2013-04-23 16:30 ` Tim Deegan
2013-04-24 16:09 ` Jan Beulich
2013-04-25 16:02 ` Jan Beulich
2013-04-25 16:34 ` Tim Deegan
2013-04-25 16:40 ` George Dunlap
2013-04-26 6:43 ` Jan Beulich
2013-04-26 16:10 ` Jan Beulich
2013-04-26 16:56 ` Ian Campbell
2013-04-29 6:53 ` Jan Beulich
2013-04-29 8:20 ` Ian Campbell
2013-04-29 8:37 ` Jan Beulich
2013-04-29 8:40 ` Paul Durrant
2013-04-29 8:47 ` Jan Beulich
2013-04-29 9:15 ` Paul Durrant
2013-04-29 9:53 ` Paul Durrant
2013-04-29 10:43 ` Jan Beulich
2013-05-01 14:49 ` Paul Durrant
2013-05-02 6:32 ` Jan Beulich
2013-05-02 8:23 ` Paul Durrant
2013-04-29 8:37 ` Paul Durrant
2013-04-29 10:29 ` Tim Deegan
2013-04-29 11:07 ` Ian Campbell
2013-04-29 11:27 ` Jan Beulich
2013-04-29 11:40 ` Ian Campbell
2013-04-29 11:35 ` Tim Deegan
2013-04-29 11:42 ` Jan Beulich
2013-04-29 11:44 ` Ian Campbell
2013-04-29 11:49 ` Tim Deegan
2013-04-29 11:57 ` Ian Campbell
2013-04-29 12:01 ` Jan Beulich
2013-04-29 8:35 ` Paul Durrant
2013-04-23 10:55 ` Tim Deegan
2013-04-16 15:24 ` Ren, Yongjie
2013-04-16 15:32 ` George Dunlap [this message]
2013-04-16 15:37 ` Tim Deegan
2013-04-16 15:56 ` George Dunlap
2013-04-18 2:21 ` Ren, Yongjie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=516D6F1D.7020007@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=eddie.dong@intel.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=yongjie.ren@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.