 Home |
Products |
Support |
Community |
News |
xen-users
[Xen-users] Why does domU Windows have to be re-registered after Xen 3.1
| To: | "Xen Users" <xen-users@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-users] Why does domU Windows have to be re-registered after Xen 3.1.0 dom0 upgrade |
| From: | Derek <xen@xxxxxxxxxxxxxxxx> |
| Date: | Tue, 11 Sep 2007 09:09:42 -0600 |
| Delivery-date: | Tue, 11 Sep 2007 08:10:18 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; bh=NeNskg5LOnkl4z799SHBEihKvkq5WIGbzRYxwrCBfoE=; b=sUI1C3Uw2piU8YCjcHvegaz203WosmK3lG1KqJxGm/lZchCpgDVjhau41MkwWIqI7GFTSqs7cFywPVHf5tAU87faxHy+qBNzG0kNwWdUTlF2iCJLtMIyd8nC2FjNmGQwibGLq+B4TZR0SAoLytIjZRQGUgNtcyA08UL37kaW8qA= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=eaZxYuhkNQvHyWL9jY5CiLqOyaia/LvpZgAYoDXAE/0o36bkIuTtPOLAzf4M2q6pMRHhmZU4X5MJqBjhZ+U0N2vVvQEk7C0HRI8T3t7Y2JeTYflnFkWQOB0OhDAGAPeA2beZlwzvsQvn0ZLNafRNhsj4xnbFrDq0mFRjwcEMS8k= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-users-request@lists.xensource.com?subject=help> |
| List-id: | Xen user discussion <xen-users.lists.xensource.com> |
| List-post: | <mailto:xen-users@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-users-bounces@xxxxxxxxxxxxxxxxxxx |
|
Hi all, Just wondering if anybody knows the answer to this mystery? I upgraded my Dom0 from Xen 3.0.4 + kernel 2.6.16.33-xen to Xen 3.1.0 + kernel 2.6.18-xen. After the upgrade, my domU (WInXP home edition) popped up a message saying that it needed to be re-registered with Microsoft, owing to significant changes in the hardware environment on which it is running. Something about windows genuine advantage (ie. they suspect it's a pirate copy?) Just wondering... Does anybody know what changes these might be? There's nothing obvious that I can tell, but something about my new Xen 3.1.0 environment is different enough to upset Microsoft. It's the same memory size, same peripherals etc. The only thing I can think of is PAE versus non-PAE. My new 3.1.0 installation is PAE, my old one was not (as far as I know anyway). Could that be it? Not critical that I get to the bottom of this, but I'm curious. Derek. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-users] redhat guest and changing cds, Takekazu Okamoto |
|---|---|
| Next by Date: | Re: [Xen-users] Why does domU Windows have to be re-registered after Xen 3.1.0 dom0 upgrade, Emre Erenoglu |
| Previous by Thread: | [Xen-users] redhat guest and changing cds, Mohammad Zohny |
| Next by Thread: | Re: [Xen-users] Why does domU Windows have to be re-registered after Xen 3.1.0 dom0 upgrade, Emre Erenoglu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
