Custom Query (16363 matches)
Results (2200 - 2202 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3955 | fixed | FreeBSD 7.0 networking tip | ||
| Description |
Please include this in the FAQ: FreeBSD 7.0 as guest OS: In addition to using the PCnet-PCI II driver, edit /etc/rc.conf to include: ifconfig_le0="DHCP" and run /etc/netstart I'm going to upgrade to 7.2 and see if this still works. |
|||
| #3959 | fixed | You can't delete an immutable hard disk because of child disks | ||
| Description |
I need to create a strictly controlled build environment. I want to use a batch file and vboxmanage.exe to create and configure a VM. I also want to be able to completely remove the VM via vboxmanage.exe when I am done. Everything is possible with the exception of removing the hard disk that was added. The vdi hard disk that I want to use is configured to be immutable. This seems to be the cause of the problem. When you create a VM using an immutable hard disk a differencing vdi child disk is automatically created. Then when it comes time to remove the VM everything can be removed except for the original immutable hard disk. This is because you get an error that the hard disk has child hard disks. The batch file doesn't know the name of these child hard disks. The "closemedium" option should have an option to remove (and optionally delete) all child hard disks. Error being experienced: ERROR: Hard disk '<NULL>' has 28833136 child hard disks Details: code E_FAIL (0x80004005), component HardDisk, interface IHardDisk, call ee IUnknown Context: "Close()" at line 1486 of file VBoxManageDisk.cpp |
|||
| #3960 | fixed | enhancement: optionally allow disk snapshots to be co-located with parent disk | ||
| Description |
I prefer housing my virtual disks on the physical disks which have the most room (not within my user profile). When I create a snapshot of the virtual machine, the snapshot always resides in
The feature request is to create the snapshot disk in the same directory as the parent disk, and in the optimal outcome, incrementally name the snapshot disk based on the basename of the parent disk. For example, I can appreciate that not everyone would like this behavior, so a checkbox in the preferences (or even at snapshot time) may be appropriate. Thank you for your consideration. |
|||

