Search Results

Search found 1619 results on 65 pages for 'virtualbox'.

Page 2/65 | < Previous Page | 1 2 3 4 5 6 7 8 9 10 11 12  | Next Page >

  • How do I solve VirtualBox error 0x80004005?

    - by maria
    Hi I was trying to run Windows XP under Virtual Box (host system Ubuntu 10.04) and I've got an error message saying: Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. This is terminal output: maria@maria-laptop:~$ sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules * done. * Uninstalling old VirtualBox DKMS kernel modules * done. * Trying to register the VirtualBox kernel modules using DKMS * Failed, trying without DKMS * Recompiling VirtualBox kernel modules * done. * Starting VirtualBox kernel modules * done. After that I can run XP on Virtual Box, but when I try to log into user's account, I have the message that I have to register XP (I haven't done it yet, as each time I was cliking on pop-up window suggesting registration, nothing was happening). I click that I want to register it now and appears the message about error 0x80004005, which prevents Windows to check the license for that computer (the message is in Polish, so I don't post it here...). I forgot to install DKMS first, but I've done it after. What should I do to run virtual machine? It was using it already, the problem occured only today. Thanks for any suggestion

    Read the article

  • VirtualBox error 0x80004005

    - by maria
    Hi I was trying to run Windows XP under Virtual Box (host system Ubuntu 10.04) and I've got an error message saying: Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. This is terminal output: maria@maria-laptop:~$ sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules * done. * Uninstalling old VirtualBox DKMS kernel modules * done. * Trying to register the VirtualBox kernel modules using DKMS * Failed, trying without DKMS * Recompiling VirtualBox kernel modules * done. * Starting VirtualBox kernel modules * done. After that I can run XP on Virtual Box, but when I try to log into user's account, I have the message that I have to register XP (I haven't done it yet, as each time I was cliking on pop-up window suggesting registration, nothing was happening). I click that I want to register it now and appears the message about error 0x80004005, which prevents Windows to check the license for that computer (the message is in Polish, so I don't post it here...). I forgot to install DKMS first, but I've done it after. What should I do to run virtual machine? It was using it already, the problem occured only today. Thanks for any suggestion

    Read the article

  • VirtualBox: Why are some USB devices disabled?

    - by torbengb
    Overview: My Host OS is Ubuntu 10.10 and guest OS is WinXP on the VirtualBox version downloaded from Oracle including "VirtualBox 4.0 Oracle VM VirtualBox Extension Pack" so that USB passthrough works. This works in general (I was able to back up my iPhone to iTunes in the guest OS), but some devices aren't available even though they're ptrovided in the VirtualBox settings. Specifics: In the VirtualBox settings for the guest OS, there's the part where you can select which of your USB devices should be visible to the guest OS. I've selected several devices including the iPhone. So far so good. Then an iOS upgrade came along; my iPhone is now in DFU mode (or recovery mode?) and represents itself not as "iPhone" but as "iPhone (DFU mode)". I have now also added this device to the list of USB devices that the guest OS should see -- but it doesn't see this device. Questions: Am I right in expecting that the guest OS ought to see the DFU device when I add it in the VirtualBox settings? What steps do I need to take so that the guest OS will really see the DFU device?

    Read the article

  • virtualbox installing iso Error "could not find a valid v7 on sda"

    - by MountainX
    I decided to try this suggestion to install Android x86 on Virtual Box. I'm following those steps and I'm at #4. I used the android-x86-4.0-RC1-amd_brazos.iso (because I have a ThinkPad that this might be compatible with and it seemed as good as any of the other choices...) I'm getting an endless series of errors: .[numbers] VFS: could not find a valid v7 on sda. .[numbers] VFS: could not find a valid v7 on sda. repeating... For storage, I made a VDI image sized at 4.0 GB (dynamically allocated) attached on SATA Port 0. Background and more details: I'm running Kubuntu 12.04. I installed VirtualBox 4.1.12 after adding deb http://download.virtualbox.org/virtualbox/debian precise contrib to my sources. EDIT: Now I'm wondering if I installed the right package. I verified that I'm running 4.1.12. But I installed it with apt-get install virtualbox instead of the recommended apt-get install virtualbox-4.1. I checked just now and see this: apt-cache search virtualbox virtualbox - x86 virtualization solution - base binaries virtualbox-4.1 - Oracle VM VirtualBox But when I run VirtualBox, I get the Oracle VM VirtualBox Manager version 4.1.12, so I think I'm OK. I did see one minor issue (possibly related to this question) when installing VB, but in my case I don't think it is actually an error at all: * No suitable module for running kernel found [fail] invoke-rc.d: initscript virtualbox, action "restart" failed. VirtualBox installed and seems to be running fine. I just can't get the ISO image to install. The error is as shown above.

    Read the article

  • virtualbox snapshot size

    - by intuited
    I've started using Windows 7 under VirtualBox on an Ubuntu 10.10 host. I took about 6 snapshots over the course of setting up the VM from the Windows restore image that came with the computer. My installations were more or less limited to windows updates, antivirus, and the VB Guest Additions. I uninstalled much more than I installed. The VM was running for about 24 hours total. The snapshots increased in size at a worrisome rate, even when the machine was idle: the snapshot .vdi file for the period between 11:22 PM and 9:02 AM is 6 gigs in size; during that time very little happened. The other .vdi files are between 0.5 and 3 GB, most between 1 and 2 GB. The corresponding .sav files are between 0.5 and 1 GB. The Internet connection where I was doing this is limited to 30KB/s download, which, constantly saturated, works out to less than 3 GB per 24 hour period. Is this normal? Is there something that can be done to make snapshots more practical? update On starting up the VM again, I've noticed that mscorsvw is using significant processing time. Apparently this process [precompiles .NET assemblies]. This may have been going on during the period when I was taking snapshots, which might explain some of the snapshot size increase. I would be somewhat surprised to learn that this could be responsible for over 10 GB of additional disk usage, or that it would run for roughly 24 hours. Is this possible?

    Read the article

  • Loss of iPod nano connection via VirtualBox and iTunes

    - by user69245
    I use VirtualBox 4.12 with Ubuntu 12.04, and up until a couple of days ago I was able to sync my iPod nano, my iPod Classic and my iPad via Windows XP and iTunes. A few days ago, when I connected the iPod nano, iTunes told me it was in recovery and I'd have to Restore it. I did this, but when it started up again I was told it was still in recovery. I went through this loop a few times, and then I got it to work again, and synched successfully. Since then, I have been unable to sync my iPod nano, although both iPod Classic and iPad work fine. I have successfully synched the iPod on a laptop with Windows XP since then, but each time I connect it through VirtualBox I get the same error message. I have tried disabling the iPod service in (the VirtualBox version of) Windows, and find that the iPod isn't being mounted as a disc drive, which is what happens in Ubuntu, and on my Windows XP laptop. I've tried changing USB leads, and I've also booted Windows XP on my Ubuntu machine, and here iTunes recognises the iPod nano. As far as I know, I made no changes to the configuration of VirtualBox between the time it was synching satisfactorily and the time it failed. I don't think iTunes is at fault here, as the same version of iTunes syncs with the iPod nano on two different computers running Windows XP - I think it may be the way XP running in VirtualBox handles the mounting of the iPod. Any suggestions?

    Read the article

  • Creating and using VM Groups in VirtualBox

    - by Fat Bloke
    With VirtualBox 4.2 we introduced the Groups feature which allows you to organize and manage your guest virtual machines collectively, rather than individually. Groups are quite a powerful concept and there are a few nice features you may not have discovered yet, so here's a bit more information about groups, and how they can be used.... Creating a group Groups are just ad hoc collections of virtual machines and there are several ways of creating a group: In the VirtualBox Manager GUI: Drag one VM onto another to create a group of those 2 VMs. You can then drag and drop more VMs into that group; Select multiple VMs (using Ctrl or Shift and click) then  select the menu: Machine...Group; or   press Cmd+U (Mac), or Ctrl+U(Windows); or right-click the multiple selection and choose Group, like this: From the command line: Group membership is an attribute of the vm so you can modify the vm to belong in a group. For example, to put the vm "Ubuntu" into the group "TestGroup" run this command: VBoxManage modifyvm "Ubuntu" --groups "/TestGroup" Deleting a Group Groups can be deleted by removing a group attribute from all the VMs that constitute that group. To do this via the command-line the syntax is: VBoxManage modifyvm "Ubuntu" --groups "" In the VirtualBox Manager, this is more easily done by right-clicking on a group header and selecting "Ungroup", like this: Multiple Groups Now that we understand that Groups are just attributes of VMs, it can be seen that VMs can exist in multiple groups, for example, doing this: VBoxManage modifyvm "Ubuntu" --groups "/TestGroup","/ProjectX","/ProjectY" Results in: Or via the VirtualBox Manager, you can drag VMs while pressing the Alt key (Mac) or Ctrl (other platforms). Nested Groups Just like you can drag VMs around in the VirtualBox Manager, you can also drag whole groups around. And dropping a group within a group creates a nested group. Via the command-line, nested groups are specified using a path-like syntax, like this: VBoxManage modifyvm "Ubuntu" --groups "/TestGroup/Linux" ...which creates a sub-group and puts the VM in it. Navigating Groups In the VirtualBox Manager, Groups can be collapsed and expanded by clicking on the carat to the left in the Group Header. But you can also Enter and Leave groups too, either by using the right-arrow/left-arrow keys, or by clicking on the carat on the right hand side of the Group Header, like this: . ..leading to a view of just the Group contents. You can Leave or return to the parent in the same way. Don't worry if you are imprecise with your clicking, you can use a double click on the entire right half of the Group Header to Enter a group, and the left half to Leave a group. Double-clicking on the left half when you're at the top will roll-up or collapse the group.   Group Operations The real power of Groups is not simply in arranging them prettily in the Manager. Rather it is about performing collective operations on them, once you have grouped them appropriately. For example, let's say that you are working on a project (Project X) where you have a solution stack of: Database VM, Middleware/App VM, and  a couple of client VMs which you use to test your app. With VM Groups you can start the whole stack with one operation. Select the Group Header, and choose Start: The full list of operations that may be performed on Groups are: Start Starts from any state (boot or resume) Start VMs in headless mode (hold Shift while starting) Pause Reset Close Save state Send Shutdown signal Poweroff Discard saved state Show in filesystem Sort Conclusion Hopefully we've shown that the introduction of VM Groups not only makes Oracle VM VirtualBox pretty, but pretty powerful too.  - FB 

    Read the article

  • Problem with the installation of VirtualBox

    - by Antonis Grigoriadis
    I am trying to install virtualbox and make it work but it doesn't seem I can. In the image you can seem the output. If I run VBoxManage --version I get: WARNING: The character device /dev/vboxdrv does not exist. Please install the virtualbox-dkms package and the appropriate headers, most likely linux-headers-generic. You will not be able to start VMs until this problem is fixed. 4.3.10_Ubuntur93012 But virtualbox-dkms is already installed and at the latest version. So I tried to reinstall it and i got this: Any help will be appreciated. EDIT: The output after reconfigure (@M.Tarun suggestion): EDIT 2: Also installed the sources as @Hmayag instructed, purged virtualbox and installed it again but I got the same problem.

    Read the article

  • How to get Cinnamon working in Virtualbox?

    - by kavoura
    I installed Ubuntu 11.10 (32-bit) in VirtualBox 4.1.8. I wanted to install Cinnamon, so I did and I have the option to choose it from the login screen, as well as GNOME options. If I choose Ubuntu I get Unity, which works fine. GNOME also works. But when I choose Cinnamon, the screen goes black and nothing responds and I have to reset the virtual machine. I have already installed Ubuntu 11.10 (64-bit) onto the PC in a separate partition (currently running 10.10 but trying out 11.10) and in that Cinnamon works perfectly. In VirtualBox I have 3D settings enabled and gave the virtual machine 128 MB graphics RAM, and 1024 MB system RAM. What settings should I change or what should I do to get Cinnamon working in Ubuntu in VirtualBox? I have also tried doing it in LinuxMint 12, but I get the same problem, just a black screen when selecting Cinnamon. So are Cinnamon and VirtualBox incompatible?

    Read the article

  • Adjust resolution in xfce4 virtualbox guest guest

    - by David
    I have Virtualbox 4.1.2_ubuntur3859 installed on an Ubuntu 11.10 host, running a guest ubuntu server 10.04 with xfce4 and xorg installed with no-install-recommends. I have installed guest additions, but the maximum resolution in the display settings is 800x600. I have read related questions: How to change resolution of the VirtualBox (Ubuntu guest and host)? Higher screen resolution in VirtualBox? upgrading VirtualBox 3.2.10 breaks my guest Ubuntu screen resolution Ubuntu as guest OS (with Vista host) stuck at 800x600 resolution but none contain the solution to my issue. Am I missing any particular packages that would allow me to change resolution? I would like to keep the machine as small as possible.

    Read the article

  • How to clone a VirtualBox Disk

    - by [email protected]
     How to clone a VirtualBox DiskCopying the image of Virtual Disk (.vdi file) is a convenient way to duplicate the disk, in cases you want to avoid re-installing an operating system from scratch. However, simply copying the .vdi file into another location will make a verbatim copy of the virtual disk, including the UUID of the disk. If you try to add the copy in the Virtual Media Manager, you will get an error like this:In this case, you have to do is to clone the vdi disk: cd C:\Program Files\Sun\VirtualBox\C:\Program Files\Sun\VirtualBox>vboxmanage clonevdi G:\VMWARES\Database\11GR2onOEL5forVbox\11GR2_OEL5_32GB.vdi G:\VMWARES\Database\11GR2onOEL5forVbox\OEL5_32GB.vdi$ VBoxManage clonevdi Master.vdi Clone.vdiIn case you receive a error like this. It means that the disk is already a copy of other VirtualBox Disk.In that case you chould change the UUID before to clone the Disk.Follow the steps given here in order to do that.

    Read the article

  • Playing Age of Empires II multiplayer in VirtualBox Over wi fi network

    - by Gaurav_Java
    I installed Age of Empires II (Expansion) in VirtualBox (hosting Windows XP). It works great in single player mode. Unfortunately, I tried playing multiplayer via WI-FI which I created on my Ubuntu machine and can't seem to join games. But when I connected to my WI-FI router other able to connect to my system and we can play multiplayer mode This is what I've done so far to try to resolve the issue: I noticed that the IP address of my virtual machine was 10.0.x.x, While the local IP on Ubuntu is 192.168.x.x, which I figured was a Problem. So I changed from NAT networking to bridged networking in VirtualBox . I turned off the Windows firewall in the virtual machine and don't have any ports blocked by Ubuntu, so no software firewall should be at fault. However I'm still unable to play multiplayer games, and suspect that some kind of networking issue lies at the heart of the problem. I'm not sure what else I would need to change, however. So essentially I was wondering if anyone else here has managed to play AOE2, or any similar game, inside VirtualBox from Ubuntu, and if so what you needed to do to make it possible. Or if anyone has suggestions on where else to look to figure out the problem, I'd appreciate that as well. Unfortunately AOE2 itself doesn't provide any debugging information to troubleshoot the inability to connect to network games. Here MY IP result both for Ubuntu and Virtualbox XP I want to play game on multiplayer mode in virtualbox on my system(Own Created on Ubuntu ) wi-fi on which other can connect and play hope someone will answer this

    Read the article

  • Upgrade to Ubuntu 13.10 in a VirtualBox: Gnome desktop not working

    - by Xavier
    I had Ubuntu 13.04 running in a VirtualBox (the host is WinXP). I've upgraded it to 13.10 but I've some issues: Gnome desktop is not working correctly (I can log in but the main menu bar remains empty - I can only log out with CTRL-ALT-BACKSPACE) I cannot build and install the VirtualBox Guest Addons: When trying to build it, it says: me@virtuntu:/etc/init.d$ sudo ./vboxadd setup Removing existing VirtualBox DKMS kernel modules ...done. Removing existing VirtualBox non-DKMS kernel modules ...done. Building the VirtualBox Guest Additions kernel modules The headers for the current running kernel were not found. If the following module compilation fails then this could be the reason. Building the main Guest Additions module ...done. Building the shared folder support module ...fail! (Look at /var/log/vboxadd-install.log to find out what went wrong) Doing non-kernel setup of the Guest Additions ...done. In the log file, I see the following error: /tmp/vbox.0/dirops.c:292:5: error: unknown field ‘readdir’ specified in initializer .readdir = sf_dir_read, ^ /tmp/vbox.0/dirops.c:292:5: warning: initialization from incompatible pointer type [enabled by default] /tmp/vbox.0/dirops.c:292:5: warning: (near initialization for ‘sf_dir_fops.flush’) [enabled by default] make[2]: *** [/tmp/vbox.0/dirops.o] Erreur 1 make[1]: *** [_module_/tmp/vbox.0] Erreur 2 make: *** [vboxsf] Erreur 2 Creating user for the Guest Additions. Anyone had a similar experience? Any clue to help me? Thanks a lot!

    Read the article

  • How do I get VirtualBox to work?

    - by Karasu
    I can't seem to make VirtualBox to work, I've installed it and reinstalled by 3 ways: Terminal, Ubuntu Software Center and VirtualBox's official web site installation and I keep getting the same kernel error. I found a "solution" to this problem by typing in terminal: sudo apt-get install virtualbox-dkms But it tells my that "virtualbox-dkms is already the newest version". Then I typed in terminal what the error tells me: sudo /etc/init.d/vboxdrv setup but then I tells me that DKMS is actually NOT installed (which is a contradiction). If anyone has encountered the same problem and actually solved it please tell me and explain me step by step 'cause I'm new to Linux.

    Read the article

  • Problem installing virtualbox on ubuntu 9.04

    - by debanjan
    I'm using ubuntu 9.04. From last few days I'm trying to install a virtualbox,but i can't. I went to this link for virtualbox. https://www.virtualbox.org/wiki/Download_Old_Builds_3_0 Found the virtualbox for my version. After downloading it in xp i restarted my pc and opened ubuntu. While installing by package installer there is a problem. But the status giving a massage everytime I'm trying to install.it saying "Error: Dependency is not satisfiable: libcurl3 (=7.16.2-1)". Here is an icon named "install package" but its hidden. I don't know what's the problem.I'm new to ubuntu,pls try to help me.

    Read the article

  • VirtualBox: Error -610 in supR3HardenedMainInitRuntime

    - by JamerTheProgrammer
    virtualbox VirtualBox: Error -610 in supR3HardenedMainInitRuntime! VirtualBox: dlopen("/usr/lib/virtualbox/VBoxRT.so",) failed: /usr/lib/x86_64-linux-gnu/libk5crypto.so.3: symbol krb5int_buf_len, version krb5support_0_MIT not defined in file libkrb5support.so.0 with link time reference VirtualBox: Tip! It may help to reinstall VirtualBox. I cant launch Virtualbox at all. It was working perfectly fine yesterday but I tried using it today and it is now not working. Tried: sudo apt-get install virtualbox* and I have also tried installing the .debs on the virtualbox website but nothing helps. Im using the latest crunchbang.

    Read the article

  • What's New in Oracle VM VirtualBox 4.2?

    - by Fat Bloke
    A year is a long time in the IT industry. Since the last VirtualBox feature release, which was a little over a year ago, we've seen: new releases of cool new operating systems, such as Windows 8, ChromeOS, and Mountain Lion; we've seen a myriad of new Linux releases from big Enterprise class distributions like Oracle 6.3, to accessible desktop distros like Ubuntu 12.04 and Fedora 17; and we've also seen the spec of a typical PC or laptop double in power. All of these events have influenced our new VirtualBox version which we're releasing today. Here's how... Powerful hosts  One of the trends we've seen is that as the average host platform becomes more powerful, our users are consistently running more and more vm's. Some of our users have large libraries of vm's of various vintages, whilst others have groups of vm's that are run together as an assembly of the various tiers in a multi-tiered software solution, for example, a database tier, middleware tier, and front-ends.  So we're pleased to unveil a more powerful VirtualBox Manager to address the needs of these users: VM Groups Groups allow you to organize your VM library in a sensible way, e.g.  by platform type, by project, by version, by whatever. To create groups you can drag one VM onto another or select one or more VM's and choose Machine...Group from the menu bar. You can expand and collapse groups to save screen real estate, and you can Enter and Leave a group (think iPad navigation here) by using the right and left arrow keys when groups are selected. But groups are more than passive folders, because you can now also perform operations on groups, rather than all the individual VMs. So if you have a multi-tiered solution you can start the whole stack up with just one click. Autostart Many VirtualBox users run dedicated services in their VMs, for example, running a Wiki. With these types of VM workloads, you really want the VM start up when the host machine boots up. So with 4.2 we've introduced a cross-platform Auto-start mechanism to allow you to treat VMs as host services. Headless VM Launching With VM's such as web servers, wikis, and other types of server-class workloads, the Console of the VM is pretty much redundant. For some time now VirtualBox has offered a separate launch mechanism for these VM's, namely the command-line interface commands VBoxHeadless or VBoxManage startvm ... --type headless commands. But with 4.2 we also allow you launch headless VMs from the Manager. Simply hold down Shift when launching the VM from the Manager.  It's that easy. But how do you stop a headless VM? Well, with 4.2 we allow you to Close the VM from the Manager. (BTW best to use the ACPI Shutdown method which allows the guest VM to close down gracefully.) Easy VM Creation For our expert users, the  New VM Wizard was a little tiresome, so now there's a faster 2-click VM creation mode. Just Hide the description when creating a new VM. Powerful VMs  As the hosts have become more powerful, so are the guests that are running inside them. Here are some of the 4.2 features to accommodate them: Virtual Network Interface Cards  With 4.2, it's now possible to create VMs with up to 36 NICs, when using the ICH9 chipset emulation. But with great power comes great responsibility (didn't Obi-Wan say something similar?), and so we have also introduced bandwidth limiting to prevent a rogue VM stealing the whole pipe. VLAN tagging Some of our users leverage VLANs extensively so we've enhanced the E1000 NICs to support this.  Processor Performance If you are running a CPU which supports Nested Paging (aka EPT in the Intel world) such as most of the Core i5 and i7 CPUs, or are running an AMD Bulldozer or later, you should see some performance improvements from our work with these processors. And while we're talking Processors, we've added support for some of the more modern VIA CPUs too. Powerful Automation Because VirtualBox runs atop a fully blown operating system, it makes sense to leverage the capabilities of the host to run scripts that can drive the guest VMs. Guest Automation was introduced in a prior release but with 4.2 we've revamped the APIs to allow a richer and more powerful set of operations to be executed by the guest. Check out the IGuest APIs in the VirtualBox Programming Guide and Reference (SDK). Powerful Platforms  All the hardcore engineering that has gone into 4.2 has been done for a purpose and that is to deliver a fast and powerful engine that can run almost any x86 OS because of the integrity of the virtualization. So we're pleased to add support for these platforms: Mac OS X "Mountain Lion"  Windows 8 Windows Server 2012 Ubuntu 12.04 (“Precise Pangolin”) Fedora 17 Oracle Linux 6.3  Here's the proof: We don't have time to go into the myriad of smaller improvements such as support for burning audio CDs from a guest, bi-directional clipboard control,  drag-and-drop of files into Linux guests, etc. so we'll leave that as an exercise for the user as soon as you've downloaded from the Oracle or community site and taken a peek at the User Guide. So all in all, a pretty solid release, one that we hope you'll enjoy discovering. - FB 

    Read the article

  • Cannot get Virtualbox to install properly on Ubuntu 12.04

    - by lopac1029
    I cannot get Virtualbox to install properly on my 12.04. I first went with a manual install for the .deb from the old builds section of the Virtualbox page. That .deb opened up the Software Center and installed. Then I got the error coming up of VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot. which I can only assume was due to my Ubuntu version being 32-bit (System Details - Overview - OC type: 32-bit, right?) So I followed these instructions to remove the .deb manually, restarted my laptop, and then FOUND the actual Virtualbox install in the Software Center and installed from that (assuming it would give me the correct version I need for my system) So after all that (and then some), I'm still getting the same error when I connect to my new job's project in Virtualbox. Can anyone point me in the right direction of what to do here? This is the first time I've ever worked with Virtualbox, and no one at this company is using Ubuntu, so I'm on my own here. EDIT: Here is the direct info from running the 2 suggested commands Inspiron-1750-brick:~ $lscpu Architecture: i686 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 23 Stepping: 10 CPU MHz: 2100.000 BogoMIPS: 4189.45 L1d cache: 32K L1i cache: 32K L2 cache: 2048K Inspiron-1750-brick:~ $cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU T6500 @ 2.10GHz stepping : 10 microcode : 0xa07 cpu MHz : 1200.000 cache size : 2048 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dtherm bogomips : 4189.80 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU T6500 @ 2.10GHz stepping : 10 microcode : 0xa07 cpu MHz : 1200.000 cache size : 2048 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dtherm bogomips : 4189.45 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:

    Read the article

  • VirtualBox 3.2 Release

    - by [email protected]
    The latest version of VirtualBox is out - version 3.2.  It is the first release as Oracle VirtualBox and there are a lot of new features.  Many of these I see directly impacting the Oracle VDI solution in upcoming releases (just my guess, of course), and I am updating my notebook as I write this. Er... OK - Done!There are enough features that they warrant you taking a look at this two-page VirtualBox Community Bulletin.pdf.  No point in me restating them.If you and your organization haven't tried VirtualBox, or you haven't looked at it in a while, you owe it to yourself to give this a run.  This is small, simple, powerful, software that allows you to do way more than most people would ever need in hosting a Virtual machine on you local machine.  I routinely will do a demo on a two-year-old Macbook running OS X locally, plus a Solaris 10 VM running the Sun Ray server, and a Windows XP VM and hang a couple Sun Rays off of it - and the performance is stellar.You can subscribe to the mailing lists and get access to the Beta releases as they come out as well, if you are into 'bleeding edge'.40,000 downloads a day is the current rate (before this new release), but it will jump for sure now.  Might as well join in!  

    Read the article

  • VirtualBox : increase hard disk size of the virtual machine

    - by wim
    I have run out of space on my WinXP virtual machine, which I only gave 10 GB space for when I created it. Is there an easy way to increase it to, say, 20 GB? I can't see any obvious option in VirtualBox settings. edit: the suggestion below gives this error wim@wim-ubuntu:/media/data/winxp_vm$ VBoxManage modifyhd wim.vdi --resize 20000 VBoxManage: error: Cannot register the hard disk '/media/data/winxp_vm/wim.vdi' {46284957-2c09-4e70-8a49-bfbe0f7f681d} because a hard disk '/home/wim/VirtualBox VMs/winxp_vm/wim.vdi' with UUID {46284957-2c09-4e70-8a49-bfbe0f7f681d} already exists VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component VirtualBox, interface IVirtualBox, callee nsISupports Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, AccessMode_ReadWrite, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 210 of file VBoxManageDisk.cpp edit2: removing the .vdi from VirtualBox before calling VBoxManage command, then adding it back in, was successful. But now I can't boot the virtual machine, I get this worrying screen: By the way, it says FATAL: Could not read from the boot medium! System halted. edit3: The vdi must be reattached to the VM after VBoxManage command. Further, the partition will need to be resized from WITHIN windows, because you will have this empty space: I was able to resize the partition easily using a bit of freeware called EASEUS Partition Master 9.1.0 Home Edition.

    Read the article

  • Using VirtualBox to test drive Windows Blue

    - by Fat Bloke
    Oracle VM VirtualBox is great for trying out the latest and greatest technologies and platforms. So when Microsoft recently announced the Developer Preview for Windows Server 2012 R2 and Windows 8.1,  it was with eager anticipation that FatBloke ran to the TechNet Evaluation Center to download the isos. Once downloaded,  a new VM in VirtualBox Manager was created that used Windows 2012 (64-bit) OS type and all the defaults were selected. And on starting the VM, and pointing to the iso file to install from, the excitement rose as we saw a cool new splashscreen image: But suddenly our hopes are dashed.... It would seem that this platform requires an instruction (CMPXCHG16B) that VirtualBox doesn't offer "out-of-the-box".  Fear not, for the VirtualBox team knew that this day would finally arrive and have prepared an "in case of emergency" switch as follows: Power off the vm; At the command line type:  VBoxManage setextradata [vmname] VBoxInternal/CPUM/CMPXCHG16B 1 Start the VM and install Windows Server 2012 R2 This will be enabled by default in a future release, but geeks can't wait, hence this blog. Enjoy! -FB 

    Read the article

  • Run virtualbox in other X session

    - by Valicek1
    I'm running ubuntu on my laptop (host). Inside ubuntu, there is running one instance of virtualbox. (where is installed MS Windows). My idea is to run virtualbox in separate X session (something like multiuser). If it is not clear, i'll try to explain... When I want to visit tty1, I'll press CTRL+ALT+F1. To return to my Unity desktop, I'm gona use CTRL+ALT+F7... And here comes what I need. After pressing CTRL+ALT+F8 show fullscreen virtualbox windows system, just to switch as ttys.. I am using Ubuntu 14.10. I have wasted hours by using google to find some solution, but my biggest prolem is I cannot name the problem.

    Read the article

  • Ubuntu and VirtualBox

    - by Sinan
    I have the following configuration, A host running Windows 7; A guest running Ubuntu 14.04 LTS (VirtualBox); I am connecting a Cisco router directly to my PC running Windows 7 and testing the router for netflow packets in the virtualBox I am having a difficulty capturing the traffic of the netflow from the Cisco device in my virtualBox using port 2222. I tried to use the many different networking modes provided by virutalBox (i.e. NAT, Bridged Adapter, Host only adapter) but I am not successful in capturing the netflow traffic. Could you please advise me on the configuration setup that need to be done on the virtual box to allow capturing the traffic coming from the router. I successfully capture the netflow traffic on my PC (windows 7). Thank you

    Read the article

  • No sound in 12.04 on VirtualBox

    - by john crisp
    No sound when installed in VirtualBox. When I boot from the live CD in Windows, sound works fine on my speakers. When in boot the live CD in VirtualBox it does not see my speakers. In sound properties only digital output built in S/PDIF and headphones! I've done the pavcontrol - alsamixer - all settings are OK. I've tried both 32/64 versions of Ubuntu. Running current version VirtualBox. System: Windows 7 64 - i5. What am I overlooking?

    Read the article

  • How do I install VirtualBox 4.1?

    - by William
    How to install virtualbox-4.1.4 in ubuntu 11.04 fluently? when apt-get install libqt* unmet dependency. there is a long list of unmet dependency. Where start first and any command to install virtualbox fluently? You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: virtualbox-4.1 : Depends: libcurl3 (>= 7.16.2-1) but it is not going to be installed Depends: libqt4-network (>= 4:4.5.3) but it is not going to be installed Depends: libqt4-opengl (>= 4:4.7.0~rc1) but it is not going to be installed Depends: libqtcore4 (>= 4:4.7.0~beta1) but it is not going to be installed Depends: libqtgui4 (>= 4:4.7.0~beta1) but it is not going to be installed Recommends: libsdl-ttf2.0-0 but it is not going to be installed Recommends: dkms but it is not going to be installed Recommends: libhal1 (>= 0.5) but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

    Read the article

< Previous Page | 1 2 3 4 5 6 7 8 9 10 11 12  | Next Page >