Custom Query (16363 matches)
Results (97 - 99 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3709 | fixed | failed to create a new session error | ||
| Description |
as i have no help on the forum for my problem http://forums.virtualbox.org/viewtopic.php?f=7&t=16316 my last solution is to ditch virtualbox until it works for me. i fill this bug report for the dev to know it does not work for everybody. may be it is the same bug than Ticket #3568 ? i upgraded to virtualbox 2.2.0 PUEL and when i run now virtualbox, after it tells me to migrate my configuration files, it begins to throw me errors about 'failed to create a new session'. if i click on details i see a NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) error code. it displays that error for each of my VM. if i click ok for each of my VM, i can get the virtualbox GUI running. but i get the same error again if i try to run one of my VM or if i try to create a new virtual drive. this errors even happen with a new user with a clean ~/.VirtualBox and no VM when i try to create a new virtual drive. i am running 2.6.29 kernel and a self made virtualbox package which allowed to run vbox 2.1.4 sucessfully and without errors. it seems to happen since i upgraded to kernel 2.6.29 (but other packages have been upgraded too) running archlinux current(rolling release) as of today 2009-04-12 i checked the perm on /tmp wich are drwxrwxrwt 12 root root 72K avril 12 08:32 /tmp/ |
|||
| #3734 | fixed | mouse integration with vbox addition 2.2 does not work (in windows xp guest ?) | ||
| Description |
i had in one of my VM vbox addition 2.1.4 running. so, as i run vbox 2.2.0, i uninstalled those addition and installed the vbox addition 2.2.0. and then mouse integration stopped to work. i tried several times to uninstall and reinstall the 2.2 addition and it changes nothing disable mouse integration is greyed out in Machine menu. and i had to click to use my mouse in the VM i finally reinstalled the vbox addition 2.1.4 and mouse integration worked again. i use archlinux (32 bits) host with windows xp pro 32 bits guest |
|||
| #9884 | duplicate | attempting to run a 64 bits guest reboot the linux host (AMD) | ||
| Description |
I am running Archlinux 32 bits, up to date as of 2011-11-10. with a 3.1 kernel on an inspiron 531 with an AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ AuthenticAMD For the record, I am able to run Ubuntu 11.10 64 bits on this box natively The issue/bug: When I attempt to run any (either windows 7 64 bits or ubuntu 11.10 64 bits, and I think I could enlarge the list to whatever you like) with virtualbox 4.1.6, it blacken the screen and reboot the box/pc! I was expecting this to be fixed other time but I see no improvement. This is not a new bug. It happens since at least vbox 4, kernel 2.6.39 I think it has to do with the linux kernel but I can't be sure. Scenario: Attempting to install Windows 7 64 bits by booting the iso/dvd With PAE/NX enabled with IO-APIC activated, it freezes after displaying "Starting Windows" With PAE/NX enabled without IO-APIC activated, it rebooted right after "Starting Windows" is displayed after the "Windows is loading files" screen If I enable PAE/NX with IO-APIC, it reboots as soon as "Starting Windows" is displayed One get a similar experience attemting to install ubuntu 11.10 64 bits from vbox (not sure about the config of the VM) Also booting ubuntu 11.10 64 bits from a real partition with vbox in archlinux 32 bits, gives a reboot as soon as the boot process begins (after grub screen) Also booting Windows 7 Home Premium 64 bits from a real partition with vbox in archlinux 32 bits) gives also a reboot I have gave up trying to use anything 64 bits with vbox because of that reboot. I got no problem running Ubuntu 11.10 64 bits (from a real partition) from Windows 7 Home Premium 32 bits with virtualbox. |
|||

