locked
Windows 7 Pro as XEN DomU (guest) RRS feed

  • Question

  • I have a headless linux system running xen hypervisor with windows 7 as a domU guest.  

    It has its own windows key that was bought specifically for it, and no other machine has ever used this key, virtual or physical.

    Every so often, as it's likely to do, windows will stop responding to RDP and VNC and I'll have to restart the VM via the host system, .  Every time this happens, I have to go in via the phone system and re-activate windows; online activation won't work.

    I don't expect anyone to provide a way to circumvent MGA (there's lots of that elsewhere on the 'net), nor do I want to.  I'm trying to be legal here, but this is kind of frustrating to say the least, and I can't find any good answer on what is causing it.  Does anyone have any ideas on what might be causing it to think it's a new machine, and a possible way to stop it?  I've included the mgadiag output below, for reference:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-4DV32-BCTB9-DB6MG
    Windows Product Key Hash: NHqi2kpJuml5VnhhgnXukONx9E4=
    Windows Product ID: 00371-OEM-9045073-41869
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {F150DEA9-498D-4DBB-A0D7-0FD6BD0E3C1D}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.120830-0333
    TTS Error: 
    Validation Diagnostic: 
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{F150DEA9-498D-4DBB-A0D7-0FD6BD0E3C1D}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-DB6MG</PKey><PID>00371-OEM-9045073-41869</PID><PIDType>3</PIDType><SID>S-1-5-21-3432425163-3260625003-1036436250</SID><SYSTEM><Manufacturer>Xen</Manufacturer><Model>HVM domU</Model></SYSTEM><BIOS><Manufacturer>Xen</Manufacturer><Version>4.0.0</Version><SMBIOSVersion major="2" minor="4"/><Date>20100604000000.000000+000</Date></BIOS><HWID>780F0600018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.1.7601.17514

    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
    Activation ID: e120e868-3df2-464a-95a0-b52fa5ada4bf
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00180-450-741869-02-1033-7601.0000-3612011
    Installation ID: 016366871590682784486742925030049036605774900024240532
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: DB6MG
    License Status: Licensed
    Remaining Windows rearm count: 3
    Trusted time: 10/24/2012 7:25:44 PM

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0x00000000
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 9:19:2012 06:28
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: KAAAAAAAAgABAAEAAAAAAAAAAQABAAEAJJRO9Yw2Usi2gRzqho5QXg==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information: 
      ACPI Table Name OEMID Value OEMTableID Value
      APIC Xen HVM
      FACP Xen HVM

    Wednesday, October 24, 2012 8:04 PM

Answers

  • Thanks for the reply Noel;

    I had just re-activated it after it lost it, didn't think to do it while it was complaining.  

    It looks like it was the xen config being set to generate a new MAC address when the vm was 'destroyed' and 'created' again.  Gave it a persistent MAC and it seems to be behaving now with hard VM resets.  If this changes, I'll definitely let everyone know.

    Tuesday, October 30, 2012 6:14 PM

All replies

  • There's nothing amiss with your report - was the notification showing at the time you ran it? If not, please wait until th enotification shows again, and then run the tool and post the results.

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Thursday, October 25, 2012 7:12 AM
    Moderator
  • Thanks for the reply Noel;

    I had just re-activated it after it lost it, didn't think to do it while it was complaining.  

    It looks like it was the xen config being set to generate a new MAC address when the vm was 'destroyed' and 'created' again.  Gave it a persistent MAC and it seems to be behaving now with hard VM resets.  If this changes, I'll definitely let everyone know.

    Tuesday, October 30, 2012 6:14 PM
  • Changing the NIC does seem to be a major trigger for activation requests - thanks for the feedback!


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Tuesday, October 30, 2012 6:26 PM
    Moderator