Custom Query (16363 matches)
Results (1819 - 1821 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11261 | wontfix | Attempting to update | ||
| Description |
Attempting to update from 4.1.2.2 r80657 to 4.2-4.2.4 81684. Get the following errors: Test Transaction Errors: file /etc/rc.d/init.d/vboxballoonctrl-service from install of VirtualBox-4.2-4.2.4_81684_fedora17-1.x86_64 conflicts with file from package VirtualBox-4.1-4.1.22_80657_fedora17-1.x86_64 file /etc/rc.d/init.d/vboxdrv from install of VirtualBox-4.2-4.2.4_81684_fedora17-1.x86_64 conflicts with file from package VirtualBox-4.1-4.1.22_80657_fedora17-1.x86_64 file /usr/lib/virtualbox/VBoxBalloonCtrl from install of VirtualBox-4.2-4.2.4_81684_fedora17-1.x86_64 conflicts with file from package VirtualBox-4.1-4.1.22_80657_fedora17-1.x86_64 file /usr/lib/virtualbox/VBoxHeadless from install of VirtualBox-4.2-4.2.4_81684_fedora17-1.x86_64 conflicts with file from package VirtualBox-4.1-4.1.22_80657_fedora17-1.x86_64 file /usr/lib/virtualbox/VBoxManage from install of VirtualBox-4.2-4.2.4_81684_fedora17-1.x86_64 conflicts with file from package VirtualBox-4.1-4.1.22_80657_fedora17-1.x86_64 file /usr/lib/virtualbox/VBoxSDL from install of VirtualBox-4.2-4.2.4_81684_fedora17-1.x86_64 co... |
|||
| #6467 | fixed | Out of disk space error can lead to loss of virtualbox.xml | ||
| Description |
I ran out of space on the partition that I have VB writing hard disk images. It did a smart thing, and paused the virtual machine I was using. I tried to free up enough disk space, but wasn't succeeding. Something was eating space as I freed it. I decided I needed a new, bigger, better HD, so I closed virtual machine, which went smoothly. And closed vb, which appeared to go fine. Then I shut down the physical machine to install another drive. On restarting, I tried to open vb and got an error. My virtualbox.xml file was zero length. I surmise from this that there is an error in the code. It's not making a copy of the existing vb before trying to save a new one, or renaming it. And it's not checking that there is some space before deleting virtualbox.xml. This would be a better strategy in low-disk situations, and have stopped me from losing all my virtual machine setups. Classified as minor because it only ever has an impact if you run out of space. |
|||
| #17838 | invalid | Erro Atualização Windows 10 - Junho/2018 | ||
| Description |
Tenho 3 maquinas virtuais sendo duas windows xp e uma windows 7 64 bits prof, após a atualização do windows 10 de junho/2018, tenho o windows 10 prof, nenhuma das maquinas virtuais passou a funcionar gerando o erro "supR3HardenedWinReSpawn what: 5 VERR_INVALID_NAME (-104) - Invalid (malformed) file/path name" Ja desinstalei o virtual box, instalei a nova versão 5.2.12 e o erro persiste. Utilizo como antivirus o Windows Defender. |
|||

