Custom Query (16363 matches)
Results (1678 - 1680 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #6512 | fixed | Can't set file times or permissions from within Solaris guest on files in shared folder => fixed in SVN | ||
| Description |
Linux host, running ext3/ext4 (same behaviour for both), Solaris 10u8 guest,
mounted shared folder. If I use ' tar: can't set time on <file>: Operation not applicable tar: warning - file permissions have changed for <file> (are 0100600, should be 0755)
and using ' gtar: <file>: Cannot utime: Operation not applicable gtar: <file>: Cannot change mode to rwxr-xr-x: Operation not applicable Running truss I see the same error for both: <pid>: futimesat(-3041965, "<file>", 0x08047A40) Err#89 ENOSYS
...
<pid>: chmod("<file>", 0755) Err#89 ENOSYS
The tar/gtar completes, but with a non-zero exit code. And of course
just running ' This makes all sorts of scripts and operations fail, rendering the shared folder pretty much unusable for anything except simple copying. |
|||
| #6905 | obsolete | Can't spawn some VMs with a SATA HDD controller when the VDI file is on a btrfs partition => fixed in SVN | ||
| Description |
VirtualBox can't spawn some VMs if both these conditions are true:
VBox shows a window saying "Spawning..." and later another box appears saying "Spawning (20%)... 2/2". Neither box ever disappears (their processes must be killed). An example error in the log is: 00:00:00.733 AioMgr0-N: Request 0x000000018b0df0 failed with rc=VERR_INVALID_PARAMETER, migrating endpoint /vbox/maverick32-2.vdi to failsafe manager. Note however that some VDI files do load successfully from the btrfs partition using the SATA controller. Workaround are:
Version info: VirtualBox: 3.2.2-62298~Ubuntu~lucid Host: Ubuntu 10.04, kernel 2.6.34-generic or 2.6.35-rc1-generic |
|||
| #15040 | worksforme | Can't specify DHCP pool range for NAT Networks | ||
| Description |
Nat Networks have a DHCP server if you specify 'Supports DHCP', but it doesn't seem to be possible - certainly not in the GUI - to specify the DHCP pool range in a NAT Network. (It is possible in a host-only network.) There should be a way to specify the DHCP address pool limits. (Of course, within the CIDR.) Consider the case (which I have), where a NAT Network has a mix of client OSs that do DHCP, and servers that have static addresses (for port forwarding). The clients and servers have private conversations (think manageability.) The normal solution is to reserve an address range for static IP assignments, and allocate the rest of the subnet to DHCP. Otherwise, there can be address conflicts when the DHCP server inadvertently issues a static IP address to a dynamic client. This can happen even if the DHCP server pings before assigning, as the server might be down at the time the client requests an address. Because of this issue, I'm classifying this as a defect rather than an enhancement request. A typical allocation might be: 10.0.100.0/24 CIDR 10.0.100.1 Gateway 10.0.100.2-99 Static hosts 10.0.100.100-254 DHCP << It should be possible to specify this. 10.0.100.255 Broadcast Thanks. |
|||

