VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1981 - 1983 of 16363)

Ticket Resolution Summary Owner Reporter
#3556 fixed Cannot unlock guest VHD Dylan
Description

Host: XP Guest: 2003 Using VHD from Virtual PC.

The guest starts properly and waits at the login (unlock workstation) screen. Both the menu and host key fail to unlock the login screen on a Windows 2003 guest.

#3559 fixed vboxdrv & vboxnet services under debian based systems : incorrect S an K runlevel sequence numbers => Fixed in SVN Samuel Monsarrat
Description

The vboxdrv & vboxnet service scripts contain the following line:

# chkconfig: 35 30 60

Which suggests that the intent is to start these services at sequence 30 and stop them at 60.

First, it would seem more logical to follow basic formula K = 100 - S i.e. 30-70 or 40-60. Is there a special reason for not stopping the vbox services in the same sequence as they are started?

More importantly, under debian systems the chkconfig directive has no effect, chkconfig is a fedora/redhat directive. The start ans stop sequence numbers should be explicitly passed to update-rc.d command. This is no longer the case as with version 2.1.4 the start and stop sequence numbers are both 20 - the default for update-rc.d.

This causes serious problems on systems that run vbox guests as services as they must be stoped before any attempt to stop vboxdrv & vboxnet. On a Ubuntu 8.10 stopping vboxdrv & vboxnet with a guest running seems to result in a kernel crash, changing the sequence numbers to 20 80 solved the problem.

#3560 fixed Additional newsize parameter for VBoxManage clonehd Terry Ellison
Description

Another issue which comes up repeatedly on the forum: how to extend the size of a VDI, once created.

The new 2.1 clonehd algo now in essence does a create of the new hd and then a dd of the content of the old image to new. Adding an optional size parameter to the clonehd command, to allow the user to override the size of the output disk image would go a long way to simplifying this for basic users. This would involve perhaps a dozen extra lines to VBoxManage.cpp and a few to VBoxManageDisk.cpp.

With this change, the instructions to the users become a lot more straight forward:

Clone your virtual image to a larger VDI using the VBoxManage clonehd command specifying the new size, then use a third party partition resizing tool such as GParted (typically booting from a LiveCD) to resize your partitions. Note that you will need to have enough space on your underlying file system to contain both the old and new disk images.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy