Custom Query (16363 matches)
Results (1255 - 1257 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7105 | obsolete | Appliance import wizard fails with VBOX_E_FILE_ERROR | ||
| Description |
I did export an existing VM as appliance (ovf). The import wizard fails throwing VBOX_E_FILE_ERROR. Without checking the .mf checksum file import went fine. I opened the .mf file an verified the SHA1 hashes and they are correct. There must be a bug with the import wizard in calculating the SHA1 hash. CPU load rises very high when the wizard is trying to calculate and the calculation takes a lot of time. I'm using Win 7x64 with HashTab extension which calculates hashes quite fast with just a small footprint on CPU usage, so the whole hash code seems to be buggy. |
|||
| #15947 | duplicate | Mouse integration broken in Mint Debian guest with 4.7 kernel -> duplicate of #15913 | ||
| Description |
Test system Linux Mint Debian Edition (LMDE 2) 32-bit guest was upgraded to the the latest kernel - 4.7.2 which is now available through backports. Upon rebooting the guest, the VBox Client crashed. Mouse integration didn't work and the screen image was only 2/3rds of the full screen. Re-installed Guest Additions and re-booted. Screen size was now correct (namely fullscreen) but mouse integration still does not work. My LMDE 2 64-bit guest was also upgraded to use the latest kernel and that is fine. Therefore, it appears as if mouse integration is only broken for 32-bit guests debian based guests running the 4.7 kernel. I have attached both the latest VBox log of the guest and the kernel log of the guest itself. |
|||
| #15949 | wontfix | Change default time stamp of Vbox.log to absolute (not relative) | ||
| Description |
Each entry of the release log (VBox.log) appears to have a time stamp. The format of which is hh:mm:ss: but relative to the start of the virtual machine. So an entry starting 00:24:31.123456 is 24 minutes and 31 seconds from when the guest was started. However, most if not all logs from within the guest (examples being the linux kernel log or the windows event log) prefix their entries with the wall clock time. This makes attempting to synchronise entries in both logs, for troubleshooting purposes, quite difficult. I did find out myself that I could get actual (not relative) time stamps in the release log by using the VBoxManage command but some users that are new to the product may not feel confident in attempting such commands, or indeed know about the command at all. Perhaps consideration could be given to changing the release log time stamp to show the wall clock time by default ? |
|||

