Strange memory usage with Longhorn B3 in a guest

Discussion in 'Virtual PC' started by Bo Berglund, May 25, 2007.

  1. Bo Berglund

    Bo Berglund Guest

    I just installed Longhorn beta3 in a VPC2007 guest.
    The strange thing is that I would have believed that VirtualPC should
    consume the 512 Mb RAM I had given it but TaskManager just reports 8
    Mb RAM usage. How could this be?

    And the Longhorn guest runs really slow even with the VMAdditions
    installed, in fact my whole PC runs slow now when it is started.

    This is not the same experience as I had with Win2003 Enetrprise
    server as a guest it runs just fine...

    Any explanations?

    Host= XP-Pro SP2 with 1 Gb RAM


    Bo Berglund
    Bo Berglund, May 25, 2007
    1. Advertisements

  2. Bo Berglund

    Steve Jain Guest

    As far as memory used, that is correct behavior regardless of host.
    Task Manager will not report the VM's memory usage under the Virtual
    PC.exe file, it will only show as an increase in PF usage.

    Longhorn may be running slowly simply due to the fact it is still in

    ----------- ---- --- -- - - - -
    Steve Jain, Virtual Machine MVP
    Steve Jain, May 25, 2007
    1. Advertisements

  3. Bo Berglund

    Bo Berglund Guest

    Right, the PF usage is way up at the ceiling....
    I specifically did not download the checked build in order to get a
    bit of a speed increase. But probably they still have code in there
    that slows it down, I guess.

    On a side note:
    When downloading the iso file I couldn't get the MS download manager
    to actually do the download. Tried several times with the resume, but
    to no avail.
    Finally I found out why:
    The iso file to download is named:

    And I tried to download to my preferred location:

    By moving the download to:
    the download manager was able to start working.

    Should there not be a warning message that tells you that the combined
    path to the file is too big for download manager (140 chars)? I assume
    that this was the cause of course.
    And why did they invent this stupidly long file name in the first
    place at MSDN? 82 characters in the name alone!
    Go figure....

    Bo Berglund
    Bo Berglund, May 25, 2007
  4. Checkout:

    For details of why the memory doesn't show up - and how to check the ammount
    of memory that is being used.

    Benjamin Armstrong
    Windows Virtualization Program Manager

    This posting is provided "AS IS" with no warranties, and confers no rights.
    You assume all risk for your use.
    Ben Armstrong [MSFT], May 25, 2007
  5. The issue wouldn't be the checked build, but whether virtual machine
    additions include optimizations yet for WS2k8 beta. They probably don't.
    Colin Barnhorst, May 25, 2007
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.