Dear all,
I have debian sid i386 and kernel x86_64,now i installed Virtualbox according to virtualboxe's site and get it from virtualboxe's site.
I create a disk image and when started it i get the following log file:
VirtualBox (XP)COM Server 4.1.2 r73507 linux.x86 (Aug 15 2011 13:38:53) release log
00:00:00.017 main Log opened 2011-09-30T18:25:26.987270000Z
00:00:00.017 main OS Product: Linux
00:00:00.017 main OS Release: 3.0.0-1-amd64
00:00:00.017 main OS Version: #1 SMP Sat Aug 27 17:19:41 UTC 2011
00:00:00.017 main OS Service Pack: #1 SMP Sat Aug 27 17:19:41 UTC 2011
00:00:00.017 main Executable: /usr/lib/virtualbox/VBoxSVC
00:00:00.017 main Process ID: 3706
00:00:00.017 main Package type: LINUX_32BITS_DEBIAN_6_0
00:00:00.146 nspr-2 Loading settings file "/home/mohsen/.VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:00.175 nspr-2 Successfully initialised host USB using USBFS
00:00:00.310 nspr-2 VDInit finished
00:00:00.383 nspr-2 Loading settings file "/home/mohsen/VirtualBox VMs/bare debian/bare debian.vbox" with version "1.12-linux"
00:00:04.052 nspr-2 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false
00:00:04.556 Watcher ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine} aText={The virtual machine 'bare debian' has terminated unexpectedly during startup with exit code 1}, preserve=false
00:00:31.852 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={53f9cc0c-e0fd-40a5-a404-a7a5272082cd} aComponent={Medium} aText={Medium '/home/mohsen/VirtualBox VMs/bare debian/bare debian.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:32.062 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={c28be65f-1a8f-43b4-81f1-eb60cb516e66} aComponent={VirtualBox} aText={The object is not ready}, preserve=false
Oh, Shit
You, Said correctly:
My packages i386.but my kernel is amd64:
linux-image-3.0.0-1-amd64
When i use above kernel i had problem,
But i booted with i686-pea kernel and everything work good.
I had a new question:
My all of life is on linux-image-3.0.0-1-amd64, How can i run virtualbox without err on this kernel?
my virtualbox:
virtualbox-4.1_4.1.2-73507~Debian~squeeze_i386.deb
Last edited by m_pahlevanzadeh on 1. Oct 2011, 09:20, edited 1 time in total.
I can not help but have a similar problem with kubuntu 11.04, and I tried complete removal and reinstall, it had been working fine for at least a year or two but recently stopped. I do not use it often, mostly when I want to update my GPS so it could have been broken prior to the latest updates to my system. I looked but have not found a solution listed.
VirtualBox (XP)COM Server 4.1.2 r73507 linux.amd64 (Aug 15 2011 13:17:01) release log
00:00:00.000 main Log opened 2011-10-01T09:01:20.526223000Z
00:00:00.000 main OS Product: Linux
00:00:00.000 main OS Release: 2.6.38-8-generic
00:00:00.000 main OS Version: #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011
00:00:00.000 main OS Service Pack: #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011
00:00:00.000 main Executable: /usr/lib/virtualbox/VBoxSVC
00:00:00.000 main Process ID: 22318
00:00:00.000 main Package type: LINUX_64BITS_UBUNTU_11_04
00:00:00.108 nspr-2 Loading settings file "/home/joe/.VirtualBox/VirtualBox.xml" with version "1.7-linux"
00:00:00.178 nspr-2 Successfully initialised host USB using sysfs
00:00:00.531 nspr-2 VDInit finished
00:00:00.541 nspr-2 Loading settings file "/home/joe/.VirtualBox/Machines/xp/xp.xml" with version "1.7-linux"
00:00:00.545 nspr-2 Loading settings file "/home/joe/.VirtualBox/Machines/tomtom2/tomtom2.xml" with version "1.10-linux"
00:00:04.647 nspr-3 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false
00:00:05.259 nspr-2 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false
00:01:05.399 nspr-3 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false
00:01:05.964 nspr-4 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false
00:01:56.368 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={c28be65f-1a8f-43b4-81f1-eb60cb516e66} aComponent={VirtualBox} aText={The object is not ready}, preserve=false
uname -a = Linux ubuntu 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
I got mine working but it was a lot of trial and error. I think this is what fixed it:
sudo chown root:root -R /usr
which made sure everything in /usr belonged to root
However, after running that command VirtualBox would not even start because of a root uid error and it said I must
reinstall VirtualBox BUT using the chown command also messed up sudo so I had reboot and use the recovery console to fix sudo
using
chmod 4755 /usr/bin/sudo
and rebooted
I then used Synaptic to completely remove VituraBox, and reinstalled it again and this time it came up with an error about the usb. It informed me I must install the extension pack so I left that window open and used Firefox to download the extension pack and the default option in Firefox was to let VirtualBox VM take care of the installation it so that is what I chose. So far everything looks OK...
It was a lot of work and I may have created new problems but hopefully they will not be so bad.
I have exactly problem with x86_64 kernel, i installed a i686 kernel beside x86_64 kernel and boot the i686 kernel and my virtualbox worked correctly.So my linuxbox doesn't has problem.You made me wonderful that work with x86_64 kernel,of course, my packages are i386.