From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dor Laor Subject: Re: Weird Windows license issue Date: Mon, 06 Jul 2009 18:43:26 +0300 Message-ID: <4A521B9E.8070100@redhat.com> References: <1480789170.1281246574715523.JavaMail.root@mail.ampx.net> <4A4DA90C.4090909@redhat.com> Reply-To: dlaor@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Michael Jinks Return-path: Received: from mx2.redhat.com ([66.187.237.31]:34589 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751754AbZGFPnA (ORCPT ); Mon, 6 Jul 2009 11:43:00 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 07/06/2009 06:33 PM, Michael Jinks wrote: > Sorry for the slow response, mail sorting issue. No, this is a > license our team purchased for doing large numbers of public lab > installations. > > I've used it successfully with the same ISO image I'm trying now. > Only difference (that I know of) is that my previous installations > were on VMware and Xen. > > We're supposed to have a new license code on the way, will see if that > makes a difference. Hooray for welded-shut software! > Do you try to use -smp > 1? Currently we present each vcpu as a separate socket. Some windows OS have their vcpu disappear. Maybe it hurts installation more. There is work in progress to optionally represent them as cores. Also, it worth juggling with some -cpu options. > > > On Fri, Jul 3, 2009 at 1:45 AM, Yaniv Kaul wrote: >> On 7/3/2009 2:02 AM, Michael Jinks wrote: >>> On Thu, Jul 2, 2009 at 5:45 PM, Sterling Windmill >>> wrote: >>> >>>> What do you mean by "rejected"? Is the installer not taking your key (I >>>> doubt this would be caused by anything KVM specific), >>>> >>> Right, that. I don't have the screen in front of me so I might be >>> getting the exact word wrong, but it immediately throws back something >>> to the effect that the key is invalid. >>> >>> Since the license key entry stage happens before Windows tries to >>> bring up networking, I don't think that license exhaustion is a likely >>> explanation. >>> >>> Maybe KVM isn't either (yes, it does strike me as unlikely), but like >>> I said in my first post I'm having a hard time finding other >>> explanations. >>> >>> But anyhow. If license issues like this one aren't known to occur on >>> KVM, there must be something else going on, so I'll try again and look >>> elsewhere for the cause of the problem. Thanks for the info. >>> >> Any chance you are using OEM licenses? >>> Cheers, >>> -j >>> -- >>> To unsubscribe from this list: send the line "unsubscribe kvm" in >>> the body of a message to majordomo@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> >> > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html