Custom Query (16363 matches)
Results (532 - 534 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #400 | invalid | After updating from 1.38 to 1.4, I can't resume my virtual machine anymore. | ||
| Description |
Hello, After updating from 1.38 to 1.4, I can't resume my virtual machine anymore. I get following error message : Failed to restore VM state from '/home/panini/.VirtualBox/Machines/Panini-Win/Snapshots/{9fc5025a-e8f9-46bf-8b73-7c07de52fd56}.sav' (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION).
VBox status code: -1821 (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION).
Host machine : Kubuntu Feisty. Guest machine : Windows XP Pro. Grasyop |
|||
| #401 | worksforme | Font Tahoma, Ubuntu 7.04 Kernel 2.6.20-16-generic on ASUS Pundit/64bit x2 Athlon | ||
| Description |
After installing msttcorefonts and manually copying an unaltered tahoma/tahoma-bold set from xp to /usr/share/fonts/truetype/msttcorefonts and running dkpg-reconfigure fontconfig, I wanted to use Tahoma as major general system font. Afterwards, the VirtualBox graphical interface fails to load. The interface seems like derived from Windows/ QT3 and it looks like it is using Tahoma internally and thus producing a conflict which leads to the error message that fails to load the interface: "Segmentation fault (Core dumped)" After deleting the tahoma-set from said folder, and running dpkg-reconfigure fontconfig, GDM seems to use the standard "Sans" as a substitute setting for Tahoma and all works fine. I havent checked with other settings though (e.g. Verdana as font for everything in gdm). Its not so nice, because tahoma is very good for interface lettering. |
|||
| #402 | fixed | Guest-Additions don't work under Host Xubuntu 7.04 AMD64 Guest Kubuntu 7.04 or 7.10 -> fixed in SVN/1.5.0 | ||
| Description |
I can install Kubuntu 7.04 or Kubuntu 7.10 on a virtual machine. The host system is Xubuntu 7.04 wit latest updates. Everything works fine until I install guest additions with: sh ./VBoxLinuxAdditions.run Everything seems to work fine until I reboot. KDE login appears. When I log in KDE goes blank, and the login screen apperas again. Dmesg says: mtrr: your processor doesn't support write combining Could this possibly be a hardware error since write combining is disabled in the host's bios? The guest shouldn't see anything of the host's hardware except the CPU, should he? Or is it a software incompatibility? |
|||

