Re: [opensuse] Virtual box running out of disk space
On 09/16/2011 06:38 AM, Fr David Ousley wrote:
In the Virtual Box Settings > Storage, it shows the correct file, with the correct size 20 gigs. In Windows, Computer > Hard disk properties shows the old size, 10 gigs.
I also noted that VBoxManage has an expand utility, which I had tried earlier, before posting. I tried that on the old file and successfully expanded it to 15 gigs. But in widows it still shows 10. So it seems to be a windows issue, and I don't see an obvious way around it. It seems like it must be something obvious, which I dodn't see.
It went very smooth on this end...
It was very smooth here too, until the last step .../
Thanks for your efforts!
Hmmm... Obviously something isn't right. Let's start with a .vdi file review on your system. Under ~/.VirtualBox, the .vdi location has changed not too long ago. Originally, I had my .vdi files under ~/.VirtualBox/VDI: 13:10 providence:~/.VirtualBox> l total 64 drwxr-xr-x 5 david david 4096 Sep 16 11:58 . drwx------ 76 david david 4096 Sep 16 13:09 .. drwxr-xr-x 2 david david 4096 Feb 10 2011 HardDisks drwxr-xr-x 4 david david 4096 Feb 10 2011 Machines drwxr-xr-x 2 david david 4096 Feb 8 2008 VDI 13:10 providence:~/.VirtualBox> l VDI/ total 15358136 -rw------- 1 david david 16106189312 Jul 15 10:45 Windows XP Pro.vdi The new location for the .vdi files is under ~/.VirtualBox/HardDisks/<vmname> So my new XP guest disk went under: 13:10 providence:~/.VirtualBox> l Machines/Windows\ XP\ Pro/ total 20877512 -rw------- 1 david david 21378478080 Sep 16 13:09 xp25gdyn.vdi Is there anyway possible you are still actually booting your old .vdi due to the changed path to the new .vdi file?? Also, have you completely removed the old .vdi file name from the VirtualBox app disk controller? Just a couple of thoughts and checks to confirm the basic setup is fine. I don't see how it could be an XP issue. It seems like it must be a VirtualBox config issue... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 16 Sep 2011 14:16:32 -0400, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
On 09/16/2011 06:38 AM, Fr David Ousley wrote:
In the Virtual Box Settings > Storage, it shows the correct file, with the correct size 20 gigs. In Windows, Computer > Hard disk properties shows the old size, 10 gigs.
I also noted that VBoxManage has an expand utility, which I had tried earlier, before posting. I tried that on the old file and successfully expanded it to 15 gigs. But in widows it still shows 10. So it seems to be a windows issue, and I don't see an obvious way around it. It seems like it must be something obvious, which I didn't see.
It went very smooth on this end...
It was very smooth here too, until the last step .../
Thanks for your efforts!
Hmmm...
Obviously something isn't right. Let's start with a .vdi file review on your system. Under ~/.VirtualBox, the .vdi location has changed not too long ago. Originally, I had my .vdi files under ~/.VirtualBox/VDI:
Mine are set up in the second way: the .vdi files under each machine's directory. The Virtual Box set up does not complain, however, about using a hard disk from another directory.
Is there anyway possible you are still actually booting your old .vdi due to the changed path to the new .vdi file??
I think we can eliminate this possibility. (a) the Virtual Box manager storage for the machine (shown before booting) lists the correct .vdi (in my case xp2.vdi rather than windowsxp.vdi). (b) I moved windowsxp.vdi completely out of the Virtual Box tree (too paranoid to delete it entirely). (c) windowsxp.vdi has been expanded to 15 gigs using VBoxManage modifyhd --expand, so there should still be room if that were the one being used. And Windows when booted shows a 10 gig hd, completely full. The detailed instructions to which you referred me mentioned using Disk Management in Windows 7 to recognize the added space, though it says nothing about XP, and I can find no equivalent. This led me to suspect windows rather than Virtual Box, as the latter seems to be correctly configured. The only thing left to try that I can think of is creating a new, fixed size disk. But we do seem close on this one, should you have another idea. Thanks. dao -- Fr David Ousley davidousley@verizon.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 16/09/11 20:08, Fr David Ousley wrote:
On Fri, 16 Sep 2011 14:16:32 -0400, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
On 09/16/2011 06:38 AM, Fr David Ousley wrote:
In the Virtual Box Settings > Storage, it shows the correct file, with the correct size 20 gigs. In Windows, Computer > Hard disk properties shows the old size, 10 gigs.
I also noted that VBoxManage has an expand utility, which I had tried earlier, before posting. I tried that on the old file and successfully expanded it to 15 gigs. But in widows it still shows 10. So it seems to be a windows issue, and I don't see an obvious way around it. It seems like it must be something obvious, which I didn't see.
It went very smooth on this end...
It was very smooth here too, until the last step .../
Thanks for your efforts!
Hmmm...
Obviously something isn't right. Let's start with a .vdi file review on your system. Under ~/.VirtualBox, the .vdi location has changed not too long ago. Originally, I had my .vdi files under ~/.VirtualBox/VDI:
Mine are set up in the second way: the .vdi files under each machine's directory. The Virtual Box set up does not complain, however, about using a hard disk from another directory.
Is there anyway possible you are still actually booting your old .vdi due to the changed path to the new .vdi file??
I think we can eliminate this possibility. (a) the Virtual Box manager storage for the machine (shown before booting) lists the correct .vdi (in my case xp2.vdi rather than windowsxp.vdi). (b) I moved windowsxp.vdi completely out of the Virtual Box tree (too paranoid to delete it entirely). (c) windowsxp.vdi has been expanded to 15 gigs using VBoxManage modifyhd --expand, so there should still be room if that were the one being used.
And Windows when booted shows a 10 gig hd, completely full.
Could be you need to expand the partition to fill the new larger HD.
The detailed instructions to which you referred me mentioned using Disk Management in Windows 7 to recognize the added space, though it says nothing about XP, and I can find no equivalent. This led me to suspect windows rather than Virtual Box, as the latter seems to be correctly configured.
Disk Management is in the Administrative Tools part of Windows XP if I remember correctly. Right click on the start menu, and somewhere in the settings you can enable the "Administrative Tools" menu.
The only thing left to try that I can think of is creating a new, fixed size disk. But we do seem close on this one, should you have another idea.
Thanks.
dao
Regards, Tejas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 16 Sep 2011 15:21:08 -0400, Tejas Guruswamy <tejas.guruswamy@opensuse.org> wrote:
On 16/09/11 20:08, Fr David Ousley wrote:
On Fri, 16 Sep 2011 14:16:32 -0400, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
On 09/16/2011 06:38 AM, Fr David Ousley wrote:
In the Virtual Box Settings > Storage, it shows the correct file, with the correct size 20 gigs. In Windows, Computer > Hard disk properties shows the old size, 10 gigs.
I also noted that VBoxManage has an expand utility, which I had tried earlier, before posting. I tried that on the old file and successfully expanded it to 15 gigs. But in widows it still shows 10. So it seems to be a windows issue, and I don't see an obvious way around it. It seems like it must be something obvious, which I didn't see.
It went very smooth on this end...
It was very smooth here too, until the last step .../
Thanks for your efforts!
Hmmm...
Obviously something isn't right. Let's start with a .vdi file review on your system. Under ~/.VirtualBox, the .vdi location has changed not too long ago. Originally, I had my .vdi files under ~/.VirtualBox/VDI:
Mine are set up in the second way: the .vdi files under each machine's directory. The Virtual Box set up does not complain, however, about using a hard disk from another directory.
Is there anyway possible you are still actually booting your old .vdi due to the changed path to the new .vdi file??
I think we can eliminate this possibility. (a) the Virtual Box manager storage for the machine (shown before booting) lists the correct .vdi (in my case xp2.vdi rather than windowsxp.vdi). (b) I moved windowsxp.vdi completely out of the Virtual Box tree (too paranoid to delete it entirely). (c) windowsxp.vdi has been expanded to 15 gigs using VBoxManage modifyhd --expand, so there should still be room if that were the one being used.
And Windows when booted shows a 10 gig hd, completely full.
Could be you need to expand the partition to fill the new larger HD.
The detailed instructions to which you referred me mentioned using Disk Management in Windows 7 to recognize the added space, though it says nothing about XP, and I can find no equivalent. This led me to suspect windows rather than Virtual Box, as the latter seems to be correctly configured.
Disk Management is in the Administrative Tools part of Windows XP if I remember correctly. Right click on the start menu, and somewhere in the settings you can enable the "Administrative Tools" menu.
The only thing left to try that I can think of is creating a new, fixed size disk. But we do seem close on this one, should you have another idea.
Thanks.
dao
Regards, Tejas
I found Disk Management, but it only shows "Unallocated Space" wihtout (so far as I can tell) giving me any way of using it. -- Fr David Ousley davidousley@verizon.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Sep 16, 2011 at 2:08 PM, Fr David Ousley <davidousley@verizon.net> wrote:
On Fri, 16 Sep 2011 14:16:32 -0400, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
On 09/16/2011 06:38 AM, Fr David Ousley wrote:
In the Virtual Box Settings > Storage, it shows the correct file, with the correct size 20 gigs. In Windows, Computer > Hard disk properties shows the old size, 10 gigs.
I also noted that VBoxManage has an expand utility, which I had tried earlier, before posting. I tried that on the old file and successfully expanded it to 15 gigs. But in widows it still shows 10. So it seems to be a windows issue, and I don't see an obvious way around it. It seems like it must be something obvious, which I didn't see.
It went very smooth on this end...
It was very smooth here too, until the last step .../
Thanks for your efforts!
Hmmm...
Obviously something isn't right. Let's start with a .vdi file review on your system. Under ~/.VirtualBox, the .vdi location has changed not too long ago. Originally, I had my .vdi files under ~/.VirtualBox/VDI:
Mine are set up in the second way: the .vdi files under each machine's directory. The Virtual Box set up does not complain, however, about using a hard disk from another directory.
Is there anyway possible you are still actually booting your old .vdi due to the changed path to the new .vdi file??
I think we can eliminate this possibility. (a) the Virtual Box manager storage for the machine (shown before booting) lists the correct .vdi (in my case xp2.vdi rather than windowsxp.vdi). (b) I moved windowsxp.vdi completely out of the Virtual Box tree (too paranoid to delete it entirely). (c) windowsxp.vdi has been expanded to 15 gigs using VBoxManage modifyhd --expand, so there should still be room if that were the one being used.
And Windows when booted shows a 10 gig hd, completely full.
The detailed instructions to which you referred me mentioned using Disk Management in Windows 7 to recognize the added space, though it says nothing about XP, and I can find no equivalent. This led me to suspect windows rather than Virtual Box, as the latter seems to be correctly configured.
The only thing left to try that I can think of is creating a new, fixed size disk. But we do seem close on this one, should you have another idea.
I seem to recall that this issue is a shortcoming in Windows. After using VBoxManage to re-size a .vdi image, it's necessary to make Windows aware of the re-sized disk. This can be done using a tool called Easus Partition Manager. A free version is available here: http://www.partition-tool.com -- JAY VOLLMER I write technical manuals, therefore, I am a manual laborer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 16 Sep 2011 15:24:53 -0400, Jay Vollmer <jaycvollmer@gmail.com> wrote:
I seem to recall that this issue is a shortcoming in Windows. After using VBoxManage to re-size a .vdi image, it's necessary to make Windows aware of the re-sized disk. This can be done using a tool called Easus Partition Manager. A free version is available here: http://www.partition-tool.com
Thanks -- this appears to be what I need. The problem is that there is no space on the (windows virtual) hard drive in which to install it. And there is not enough space in uninstall a program to free up space. Catch-22. Any windows experts who know how to get around this? -- Fr David Ousley davidousley@verizon.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Fr David Ousley <davidousley@verizon.net> [09-16-11 16:17]:
On Fri, 16 Sep 2011 15:24:53 -0400, Jay Vollmer <jaycvollmer@gmail.com> wrote:
I seem to recall that this issue is a shortcoming in Windows. After using VBoxManage to re-size a .vdi image, it's necessary to make Windows aware of the re-sized disk. This can be done using a tool called Easus Partition Manager. A free version is available here: http://www.partition-tool.com
Thanks -- this appears to be what I need. The problem is that there is no space on the (windows virtual) hard drive in which to install it. And there is not enough space in uninstall a program to free up space. Catch-22. Any windows experts who know how to get around this?
I did the same thing to a linux partition. Download the boot iso for parted from sourceforge and set it as the active cd in your subject-VBox, then boot from it. It will access the virtual-disk and resize/expand the partition, something you cannot do when the partition is *mounted*. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
David C. Rankin -
Fr David Ousley -
Jay Vollmer -
Patrick Shanahan -
Tejas Guruswamy