VirtualBox

Changeset 2054 in vbox for trunk


Ignore:
Timestamp:
Apr 12, 2007 4:24:22 PM (18 years ago)
Author:
vboxsync
Message:

Think I found the problem with the double shutdown mess. Removing the workaround.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/VBox/VMM/VM.cpp

    r1890 r2054  
    11971197
    11981198    /*
    1199      * The Windows guest additions might have performed a VMMDevPowerState_PowerOff()
    1200      * request which was not completed yet. Later, the Windows guest shuts down via
    1201      * ACPI and we find the VMSTATE_OFF. Just ignore the second power-off request.
    1202      */
    1203     /** @todo r=bird: We should find a proper solution to this problem. This is just a workaround.
    1204      * Guest code should really run after we've entered VMSTATE_OFF really... */
    1205     if (pVM->enmVMState == VMSTATE_OFF)
    1206         return VINF_EM_OFF;
    1207 
    1208     /*
    12091199     * Validate input.
    12101200     */
     
    12801270            SUPGLOBALINFOPAGE GipCopy = *g_pSUPGlobalInfoPage;
    12811271            for (unsigned i = 0; i < RT_ELEMENTS(GipCopy.aCPUs); i++)
    1282                 if (GipCopy.aCPUs[i].u64CpuHz != 0 && GipCopy.aCPUs[i].u64CpuHz < _1T)
     1272                if (GipCopy.aCPUs[i].u64CpuHz != 0 && GipCopy.aCPUs[i].u64CpuHz < _4G)
    12831273                    RTLogRelPrintf("%#d: u64CpuHz=%RU64Hz u32TransactionId=%#x u64TSC=%RX64 u64NanoTS=%RX64\n",
    12841274                                   i,
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette