Custom Query (16363 matches)
Results (148 - 150 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2119 | fixed | when i create a fixed size virtual disk, the VB dissapear | ||
| Description |
Hi! I try create a new virtual machine, a Windows 98. (My real SO is Windows XP). I try create a new virtual disk in FAT32 and NTFS, 3 GB size, FIXED SIZE, when i push next for create disk, my VBox application dissapear, no msg error o anything. I can create in dinamyc size of 3 GB, and i can create a 2 GB fixed size (2 gb is default) and no problem. When i try create a new virtual machine, never find the exists disk in the select list, always i need create a new disk ¡¡And i can't find any log of virtualbox (i search in all hardisk virtual* al vb*, no logs!! |
|||
| #10847 | invalid | when dkms is installed, installing either host or guest additions for kernel >= 3.5.0 removes /usr/src/kernels/*/System.map file for corresponding kernel-devel package | ||
| Description |
The summary line should be pretty self-explanatory. I noticed the problem due to the fact that the missing System.map file prevents the deltarpm from the old to new kernel-devel package from being used, so the full package must be downloaded. Comparing rpm -V output with dkms installed vs. not installed, the only difference is one line indicating the missing System.map file when dkms is installed. There is a huge amount of output like .......T. /usr/src/kernels/3.5.2-1.fc17.x86_64/Kconfig .......T. /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/Kconfig .......T. /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/Kconfig .......T. /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/Kconfig.debug .......T. /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/Makefile .......T. /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/boot/Makefile .......T. /usr/src/kernels/3.5.2-1.fc17.x86_64/arch/alpha/kernel/Makefile etc. where only the mtime differs. This output exists even after a reinstall of kernel-devel, so appears to have nothing to do with VirtualBox. I don't know if that's normal. In any case, it obviously makes it hard to notice things like missing files. |
|||
| #4601 | fixed | when creating multiple vboxnetX configuration is always replaced with the first one | ||
| Description |
when creating more than one host-only network (vboxnet1, vboxnet2, etc.) the configuration (ip address, netmask, etc.) is always replaced with the configuration of the first interface (vboxnet0). you can reconfigure them by hand (ifconfig/ip addr) or using vbox ui but when starting the guest vm they get misconfigured again. from the guest vm using any of the internal interfaces (no matter if they are connected to vboxnet1 or vboxnet2) you can always ping vboxnet0 ip address. vbox 2.2.4 only supports one host-only network so deploying a not so complex network scenario is currently not possible in virtualbox. |
|||

