Resize...

Discussion:

Resize...

Gregory Nowak

2014-05-20 01:50:21 UTC

Since the vdi is dynamically allocated, the size of the vdi won't
change until you start filling it. What should change is the size of
the hard disk as reported by the OS inside the guest. You will then
need to either expand existing partitions and the file systems inside
them, or create new partitions and file systems on the resized drives.

Greg

--
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-manager-iDweQDFWK/***@public.gmane.org

SH Development

2014-05-20 00:30:06 UTC

Permalink

I have a 20G dynamically allocated VDI file. I need to make it 80G.

OSX Mountain Lion, I run this:

sh-3.2# vboxmanage modifyhd --resize 80580 /Users/myusername/VirtualBox\ VMs/WIN7\ PRO/WIN7\ PRO.vdi

I get this:

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
sh-3.2#

Size of VDI doesn't change. Nothing appears to happen. What's wrong here?

Jeff

Mike Newell

2014-05-20 17:01:58 UTC

Permalink

The VDI is dynamically allocated so all you did was extend the virtual
size of the drive - the VDI won't get physically bigger until your guest
OS starts using the newly allocated space. You should be able to check
this by going into the guest OS that uses the drive and checking the
drive size there - it should reflect the new size.

Mike

I have a 20G dynamically allocated VDI file. I need to make it 80G.
sh-3.2# vboxmanage modifyhd --resize 80580 /Users/myusername/VirtualBox\ VMs/WIN7\ PRO/WIN7\ PRO.vdi
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
sh-3.2#
Size of VDI doesn't change. Nothing appears to happen. What's wrong here?
Jeff
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
VBox-users-community mailing list
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________

SH Development

2014-05-20 19:01:57 UTC

Permalink

Ahh...I see it now. And then do a partition extend and all is well!

Jeff

Post by Mike Newell
The VDI is dynamically allocated so all you did was extend the virtual
size of the drive - the VDI won't get physically bigger until your guest
OS starts using the newly allocated space. You should be able to check
this by going into the guest OS that uses the drive and checking the
drive size there - it should reflect the new size.
Mike

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
VBox-users-community mailing list
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________

Cliff Scott

2014-08-14 19:45:40 UTC

Permalink

I just installed Ubuntu 14.04 to a VM and find its booting as well as app loading times very slow. I’m running VBox 4.3.14 on a Mac OSx 10.9 host. Other VMs for XP and OS/2 are very responsive, but Ubuntu is a real dog. Opening the System Settings app takes probably 10 seconds. I’ve never used Linux before so don’t know where to start looking. I did all I could find in the VBox manual regarding the installation and the latest Ubuntu updates have been applied as well as the Guest Additions installed. BTW, I only assigned 1 CPU even though this is a dual core laptop. The only sign of anything unusual is early in the boot process I get the message “[9.430471] piix4_smbus 0000:00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr”, but it keeps booting and the message goes away. It gave the same message as it started installing also.

Ideas?

Thanks for any and all suggestions.

Cliff
------------------------------------------------------------------------------