The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    V1S: Hardware virtualization reported as unavailable after return from sleep, available before.

    Discussion in 'Asus' started by Starfox, Apr 8, 2008.

  1. Starfox

    Starfox Notebook Evangelist

    Reputations:
    81
    Messages:
    302
    Likes Received:
    0
    Trophy Points:
    30
    Hi,
    I have a V1S with a T7700 Duo, with intel VT extensions (the VX* instructions). Virtual PC detects and uses that, but when i sleep and return, VPC decides that HW virtualization is not supported on this computer. Any idea what might be wrong?
    (Hey, I'm a programmer, I checked the Intel System Programmers' manual, and VT should be exposed through CPUID instruction. How can CPUID result differ after return from sleep?!)
     
  2. AlexF

    AlexF Notebook Deity

    Reputations:
    142
    Messages:
    795
    Likes Received:
    0
    Trophy Points:
    30
    I would imagine it's probably left in an uninitialized state when it comes back from sleep (sort of like the processor serial number debacle back in the old PentiumIII days). Or maybe the level of sleep might have something to do with it.

    Either way, that looks like something like that would probably need a firmware fix.
     
  3. Starfox

    Starfox Notebook Evangelist

    Reputations:
    81
    Messages:
    302
    Likes Received:
    0
    Trophy Points:
    30
    Is someone else experiencing similar problems? The CPUID instruction shouldn't depend on firmware, though (and if it does that's bad, bad design!).
    It's also stateless, so sleep shouldn't affect it. I'm baffled by this bug, really. I hope the problem's with Virtual PC not properly exiting or saving/restoring VMX mode.
     
  4. mujtaba

    mujtaba ZzzZzz Super Moderator

    Reputations:
    4,242
    Messages:
    3,088
    Likes Received:
    510
    Trophy Points:
    181
    Before we start to track down the problem, I suggest you try CPU-Z or other CPU identification programs, so we would know whether the problem is from the CPUID instruction, or other subsystems [maybe the program is try to detect this through a function windows or some sort of API that has bugs ?]
     
  5. Keith_C

    Keith_C Notebook Consultant

    Reputations:
    2
    Messages:
    104
    Likes Received:
    0
    Trophy Points:
    30
    It's a known issue with Intel CPUs and virtualisation, and I believe isn't limited to just Asus machines. I personally drop the laptop into hibernate and back if I want to use VirtualPC.