>I was testing my Wndows Server 2008 Enterprise system with Virtual Server
>2005, and I created a new virtual machine giving it a set amount of RAM (I
>forget how much it was, but it was at least 512Mb) and a Virtual Drive that I
>created (not a pre-existing one). I ended up removing the virtual machine,
>and deleting the VHD file, but when I tried adding another new virtual
>machine with a new virtual drive, it told me I didn't have enough free disk
>space.
>
>Here's the thing, I installed the Virtual Server on my D: drive, and I was
>trying to use my D: drive for all of the data files (virtual drives, etc.),
>but it is telling me that I don't have enough space on my C: drive, and the
>amount of space that the C: drive is being required to have is related to the
>amount of RAM I am setting for Virtual Machine.
>
>I am thinking that there is a file hanging around for the RAM from the 1st
>virtual machine that I created. So, anyone know where I should look to see
>if the RAM file is still hanging around, or have another direction to point
>me to?

> C:\documents and settings\All Users\Documents\Shared Virtual
> Machines\<Virtual Machine name>
>
> is where it should be if it's in the default place.
>
> --
> Bob Comer
>
>
>
> On Mon, 30 Mar 2009 01:16:01 -0700, rolaaus
> <(email address - cut out)> wrote:
>
> >I was testing my Wndows Server 2008 Enterprise system with Virtual Server
> >2005, and I created a new virtual machine giving it a set amount of RAM (I
> >forget how much it was, but it was at least 512Mb) and a Virtual Drive that I
> >created (not a pre-existing one). I ended up removing the virtual machine,
> >and deleting the VHD file, but when I tried adding another new virtual
> >machine with a new virtual drive, it told me I didn't have enough free disk
> >space.
> >
> >Here's the thing, I installed the Virtual Server on my D: drive, and I was
> >trying to use my D: drive for all of the data files (virtual drives, etc.),
> >but it is telling me that I don't have enough space on my C: drive, and the
> >amount of space that the C: drive is being required to have is related to the
> >amount of RAM I am setting for Virtual Machine.
> >
> >I am thinking that there is a file hanging around for the RAM from the 1st
> >virtual machine that I created. So, anyone know where I should look to see
> >if the RAM file is still hanging around, or have another direction to point
> >me to?
>

>It's actually a different location for Windows 2008 Server Enterprise
>
>C:\Users\Public\Documents
>
>But I still didn't see any large files.
>
>I must be SOL - unless someone else has another dirctory to look into (I did
>do a search for "virtual" but only came up with some folders in the WWWRoot
>and there wasn't any large files there either), or if there is any other
>possible problem.
>
>I am only running a 20 GB C: drive, so that is an issue that I know is a
>problem, but I'm only running a test on 2008 server, and plan on getting a
>larger drive sometime in the near future, but can't do it right now.

> >I am only running a 20 GB C: drive, so that is an issue that I know is a
> >problem, but I'm only running a test on 2008 server, and plan on getting a
> >larger drive sometime in the near future, but can't do it right now.
>
> Unless you named your VMs with "virtual" that probably won't help.
>
> The large files will have a .VHD extension on them. These are the
> virtual hard drive.
>
> --
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/
>

>
>> >I am only running a 20 GB C: drive, so that is an issue that I know is a
>> >problem, but I'm only running a test on 2008 server, and plan on getting a
>> >larger drive sometime in the near future, but can't do it right now.
>>
>> Unless you named your VMs with "virtual" that probably won't help.
>>
>> The large files will have a .VHD extension on them. These are the
>> virtual hard drive.
>>
>> --
>> Cheers,
>> Steve Jain, Virtual Machine MVP
>> http://vpc.essjae.com/
>>
>I'm not sure I understand? I know that when I try to create the virtual
>machine it says that I only have only X amount of space available (which is
>what I have on the C: drive) and I need Y ...
>
>I don't remember the specific amounts, because after not doing anything with
>it for a couple of days, and possibly doing some Windows updates on this
>machine (host) I came back to the Virtual admin page and the guest VM is
>sitting there (which I thought it wasn't allowing me to even create, so I'm
>thinking it's the old one that I had previously created - I don't know), so I
>try to activate it and it's missing the Virtual HDD (which is right, because
>I thought I would need to nix this whole project until I could upgrade my
>physical HDD), so I re-created a new VHD and now it's going just fine.
>
>Anyways, I'm curious why you say "it won't help", when it was showing me
>that my C: drive was low on space? That was the only "solution" that I was
>proposing, eventhough I was mentioning having checked my C: drive for other
>folders with the word "virtual" in them, and all I saw were the folders for
>the Admin pages? I didn't say I was going to do anything with them. Maybe
>there was a misunderstanding of what I wrote and what was thought that I
>meant? I know I"m confused :-)
>
>Thanx for the responses, everyone, I sure am glad there are these
>communities that people are willing to help others, that's how I started out
>with learning to program/code, and now I'm helping others too, when I'm able
>and know what problem they are facing.
>

> On Tue, 31 Mar 2009 14:01:04 -0700, rolaaus
> <(email address - cut out)> wrote:
>
> >I'm not sure I understand? I know that when I try to create the virtual
> >machine it says that I only have only X amount of space available (which is
> >what I have on the C: drive) and I need Y ...
> >
> >I don't remember the specific amounts, because after not doing anything with
> >it for a couple of days, and possibly doing some Windows updates on this
> >machine (host) I came back to the Virtual admin page and the guest VM is
> >sitting there (which I thought it wasn't allowing me to even create, so I'm
> >thinking it's the old one that I had previously created - I don't know), so I
> >try to activate it and it's missing the Virtual HDD (which is right, because
> >I thought I would need to nix this whole project until I could upgrade my
> >physical HDD), so I re-created a new VHD and now it's going just fine.
> >
> >Anyways, I'm curious why you say "it won't help", when it was showing me
>
> You said you were searching the C: drive for "virtual" and this is
> what won't help since none of the files used by VS or VPC are named
> with "virtual" anywhere in the file name.
> What Steve meant was that a search with the pattern "*.VHD" would have
> been more appropriate to locate all VHD files and then you could have
> determined if there were some bogus files that you could remove top
> gain the space needed.
>
> >that my C: drive was low on space? That was the only "solution" that I was
> >proposing, eventhough I was mentioning having checked my C: drive for other
> >folders with the word "virtual" in them, and all I saw were the folders for
> >the Admin pages? I didn't say I was going to do anything with them. Maybe
> >there was a misunderstanding of what I wrote and what was thought that I
> >meant? I know I"m confused :-)
>
> I hope you have checked the "Recycle bin" for big contents as well?
> Emptying this could easily give you back a lot of disk space.
>
>
> >Thanx for the responses, everyone, I sure am glad there are these
> >communities that people are willing to help others, that's how I started out
> >with learning to program/code, and now I'm helping others too, when I'm able
> >and know what problem they are facing.
> >
> >"Steve Jain [MVP]" wrote:
> >
> >> >I am only running a 20 GB C: drive, so that is an issue that I know is a
> >> >problem, but I'm only running a test on 2008 server, and plan on getting a
> >> >larger drive sometime in the near future, but can't do it right now.
> >>
> >> Unless you named your VMs with "virtual" that probably won't help.
> >>
> >> The large files will have a .VHD extension on them. These are the
> >> virtual hard drive.
> >>
> >> --
> >> Cheers,
> >> Steve Jain, Virtual Machine MVP
> >> http://vpc.essjae.com/
> >>
>
> --
>
> Bo Berglund (Sweden)
>

>I'm not sure I understand? I know that when I try to create the virtual
>machine it says that I only have only X amount of space available (which is
>what I have on the C: drive) and I need Y ...
>
>I don't remember the specific amounts, because after not doing anything with
>it for a couple of days, and possibly doing some Windows updates on this
>machine (host) I came back to the Virtual admin page and the guest VM is
>sitting there (which I thought it wasn't allowing me to even create, so I'm
>thinking it's the old one that I had previously created - I don't know), so I
>try to activate it and it's missing the Virtual HDD (which is right, because
>I thought I would need to nix this whole project until I could upgrade my
>physical HDD), so I re-created a new VHD and now it's going just fine.
>
>Anyways, I'm curious why you say "it won't help", when it was showing me
>that my C: drive was low on space? That was the only "solution" that I was
>proposing, eventhough I was mentioning having checked my C: drive for other
>folders with the word "virtual" in them, and all I saw were the folders for
>the Admin pages? I didn't say I was going to do anything with them. Maybe
>there was a misunderstanding of what I wrote and what was thought that I
>meant? I know I"m confused :-)
>Thanx for the responses, everyone, I sure am glad there are these
>communities that people are willing to help others, that's how I started out
>with learning to program/code, and now I'm helping others too, when I'm able
>and know what problem they are facing.
>
>"Steve Jain [MVP]" wrote:
>
>> >I am only running a 20 GB C: drive, so that is an issue that I know is a
>> >problem, but I'm only running a test on 2008 server, and plan on getting a
>> >larger drive sometime in the near future, but can't do it right now.
>>
>> Unless you named your VMs with "virtual" that probably won't help.
>>
>> The large files will have a .VHD extension on them. These are the
>> virtual hard drive.
>>
>> --
>> Cheers,
>> Steve Jain, Virtual Machine MVP
>> http://vpc.essjae.com/
>>

>Oh, okay, now I get it. The reason I was searching for "virtual" is because
>of the folder names that I was given to look for. And the reason I didn't
>search for VHD is 2 fold - 1) I knew where those where and 2) as far as I
>understand, this is the file for the Hard Drive (virtual HDD), and I was
>looking for something else entirely, some file or something whereever the
>virtual RAM is stored, because the error message I was receiving was
>*definitely* pointing to something about that. I may be mistaken and VHD may
>have something to do with it, but I don't know.
>

> There's really no such thing as virtual RAM. A VM uses physical RAM
> and only when it is running. If the VM is shut off it will not be
> stored, it is released back to the host's OS.
> RAM for a VM will never use hard drive space in Virtual Server.
>
> --
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/

> Btw, not sure if you kept up with, or reviewed the entire thread, but I
> installed the Virtual Server in my D: drive, and made sure, during a
> customized installation,that all of the components were point to my D: drive,
> so I'm not sure about any of the internal nuts and bolts, but it was
> definitely trying to use my C: drive, and the numbers matched the RAM I was
> trying to assign the Vmachine (the Virtual Drive had already been created,
> and it was 75Gb, versus the RAM, which I was assigning either 512Mb or 1024,
> I forget which)