I'm trying to set up Virtualbox to run as a service so that it auto starts the VM when the PC boots and shuts down the VM when the PC is shut down.
I've found a set of scripts that do this but set up of the scripts was written for Ubuntu so I'm stuck at one of the steps.
The set of scripts can be found HERE
The part of the install that I'm not sure about is the part in bold. I know what it's trying to do (basically start the script last during the boot process and stop the script first during shutdown) but don't know how to do it in oS.
VBoxTool currently consist only of a set of scripts. With this scripts, virtual machines of VirtualBox in a Linux headless server can be controlled. Start, stop, save, backup and show status of sessions in batch mode from the command line.
Usage and installation is tested only on Ubuntu. Please report if a specific function is not working in another environment, say OpenSUSE, Fedora, etc.
I created a F14 x86_64 guest OS in VirtualBox4 (hosted by F14 x86_64) and configured it to get its IP from my router but it won't do so on boot. The other guest OS's (Fedora 14 i386, 2x Oracle EL5) are able to get their IPs on boot.
I checked the setting in the network manager and they show that the interface is to be activated on boot but it doesn't. When I log in and run ifup eth0 as root it works.
Observed on two host systems both with openSUSE 11.3 32 bit using ext4: When a big files, in this case a 1.2 GB and a 1.7 GB is copied from DVD, usb harddrive or shared folder into a Windows 7 32 bit guest system, the copied file is corrupted. The md5sum has changed and until the guest system has been rebooted successive md5sum tests on the same file comes up with various results... After a reboot md5sum tests show consistent results, but a sum different from the original file.
I recently switched desktops. Kinternet connects fine with Gnome, but it doesn't start up with Gnome. I tried putting kinternet into the Gnome startup, but kinternet errors when it starts.
I got autostart working on 11.2/gnome, but I've switch to kde4.3.1. Duncan on the kde list suggested to manually save a session, but in the session manager there's not a clue how to manually save a session. In gnome I wrote a shell script to start kinternet, but the script has to start after smpppd. That script starts too soon in kde4.The reasoon kinternet doesn't start with the "restart on login" box, is a kde3 app. I have already tried kinternet --kicker, but apparetly kicker starts before smpppd. The script I wrote starts kinternet but with this error:
Error - KInternet Connection to local and remote server refused. Maybe smpppd is not running or you are not member of the group "dialout". Also check the server settings in the dialog "Various Settings". OK
The error to the calling shell looks like this:
Starting kinternet --kicker DCOPClient::attachInternal. Attach failed Could not open network socket DCOPClient::attachInternal. Attach failed Could not open network socket DCOPClient::attachInternal. Attach failed Could not open network socket buildsycoca running...
absolutely positive, but I think the following is a bug in/etc/xdg/openbox/autostart.sh
24# Make GTK apps look and behave how they were set up in the gnome config tools 25if test -x /usr/lib/gnome-settings-daemon >/dev/null; then 26 /usr/lib/gnome-settings-daemon &
I'm a KDE fan giving GNOME Shell a try, and I find I like it better with a dock. The one in GNOME Shell extensions is still primitive, so I installed Cairo and set it to start automatically, but then I found it starting in KDE too, where I prefer the Plasma Panel. So I disabled it for autostart and checked "Restore Programs" in the Startup Manager instead, but that didn't do the trick. Now I'm thinking that instead of an autostart entry for Cairo dock, I should have one for a script that says, "IF running GNOME, THEN launch Cairo, ELSE leave well enough alone." Can anyone here tell me how to do that? I've never written a script, but I figure the internet can help me with the basics; the piece I'll need is a way to check whether I'm in GNOME.
For one of the users on my system, knetworkmanager abruptly ceases to autostart once on a while. This happens once in roughly 10-15 days. When that happens, i have to go into .kde4/share/config/networkmanagementrc and manually toggle Autostart=true (from false). This trick works for another 2 weeks or so, before the value of "Autostart" automagically changes to 'false' and i have change it again.I dont mind doing it manually, but the user in question is my mom, and she does not have the know-how to do it herself when i'm not around.
I was trying to install VirtualBox through the YaST > Software Management but it is not working, someone in the forum told me that I have to download the OSE version and do it manual way. Finally I am able to start up VB but not able to use the network connection. Thus I am trying to do this:
/etc/init.d/vboxdrv setup. I get this error:
[code]...
When I type dmesg, it shows me a bunch of info which I don't know what should look for. When I type modprobe vboxnetflt, I get the error: FATAL: Error inserting vboxnetflt (/lib/modules/2.6.37.1-1.2-default/updates/vboxnetflt.ko): Invalid module format. what should I do in order to get my VB to be able to connect to the internet?
I'm having a problem since my last upgrade from 11.2 to 11.3 (Gnome).
Before the upgrade NetworkManager would run just fine at start up, now I have to explicitly run the command from a console using the root user to start it.
(My problem is the same as this one, only in gnome instead of kde)
my error when trying to run a VB (Virtualbox). Error as copied from error box. install the virtualbox-ose-modules package for your kernel and execute 'modprobe vboxdrv' as root. VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).
[code]...
I get this when trying to launch a VB after making one with wizzard.
I have been going through forums and following "how to's" and walkthroughs on how to use VirtualBox to run my Win 7 VM. I have a pre-created VHD that I am importing to my OpenSuse 11.4 machine. One vhd was created in Hyper-V and has hardware and cpu cross compatibility turned on. Everything works perfect when booting it up on my Hyper-V server. When I move it over to my OpenSuse VirtualBox the VM will not boot. It gets to the "Starting Windows" screen and then throws an error screen that the VM encountered errors while booting. It then runs the Window's startup recovery tool and even tried to do a system restore. Nothing works and it never progresses beyond that point. Figuring there was something with the vhd file. I used Acronis Advanced Backup and Recovery to create a non hardware dependent backup that was automatically converted to a vhd. I know the process works as that is how I have converted the bulk of the servers at work into VM's. However, when I move the vhd file to the OpenSuse VirtualBox... it does the same thing.
So I am trying to figure out what might be going on here. Is VirtualBox not able to virtualize Win 7? If not then what VM software should I use? VMWare, Xen, ???
A long time I used the Virtualization:VirtualBox-Repository (which is still suggested in the yast-repository-module) to get the latest version, but the version 3.1.6 is still missing here.I found that this repository will be dropped and instead Virtualization:VirtualBox_backports should be used.But the packages there have two problems:No localization is available, you can just use english.The kernel-modules are just available for Kernel 2.6.31.5 (there is no update-repo for updated kernels)
I tried upgrading today from VirtualBox 3.1 to 3.2 (VirtualBox-3.2-3.2.0_61806_openSUSE111-1.x86_64.rpm) on my openSUSE 11.2 system and it's not cooperating. The installation itself went fine, but as soon as I try to start a guest, the VirtualBox process ramps up to 100% and stays there until I poweroff the guest. The guest itself is VERY slow. These guests worked fine on 3.1.
For example, if I start an openSUSE guest and stop the Grub counter, therefore leaving the screen at the Grub bootloader, the VirtualBox process remains at 100% forever, without any activity on the guest.I also have a Windows guest and it has the same problem.
I can obviously try downgrading again to 3.1, but I was hoping that someone else has run into this issue and knows what to do about it.
I'm trying to update VirtualBox but I'm getting a few problems:
1. When I go into YAST, it doesn't show any other versions available (just 3.0.x)
2. When I download the rpm from the website, I keep getting some insanely long error that says something about NOKEY perhaps? (It's a long error that gets cut off by the screen height)
I currently have vbox 2.0.6 OSE and its been running awesome except I get errors with directx when running 3D apps cause of the video card driver that comes with vbox(at least so far thats I narrowed it down to). So, Im trying to update to 3.2.2 but cant seem to find an easy way to do it. I downloaded the RPM for OpenSUSE 11.1 from Sun's website and when installing it I got errors about files conflicting with the previous version. So I ran a "zypper rm vbox" to remove the current one and then ran the RPM again and it seemed to finish the installation fine, I just cant find it to run it.I currently have the 2.0.6 version installed again just so I can use it... but now am back to trying to get 3.2 installed before looking in another direction.
So after a series of uninstalling and reinstalling VirtualBox to get the updated version, I was able to get it installed and working but it seemed to be crashing my computer as everytime i walked away for 10 minutes and came back, it would be at the login screen. It never did it while I was on it though so I never saw any errors. Now after a couple days of that... Whenever I start it I get an error:
Failed to create VirtualBox COM object The application will now terminate. Could not load the settings file '/home/user/.VirtualBox/VirtualBox.xml'
Earlier i installed Virtualbox from Package Repository. Now VB Repository doesn't work anymore. I only get en error-msg if i try to ad VB in Package Repository. I've been always adviced to install from repos than downloading. What happens with Virtualbox?
So, on OpenSuse 11.3 I installed VirtualBox, and I would like to put other account to be able to start virtual os-es, but... I would like to have them 2-3 and that other users see them when they start VirtualBox and that they can start them, but not to add new one..
I've been having problem after problem trying to install virtualbox 4.0.2, on 32 bit opensuse 11.3. I've been able to jump over a few hurdles by installing the kernel source. But now I get this error when starting virtualbox from the command line:
Code: WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (2.6.34-12-default) or it failed to
i have virtualbox installed from the oracle virtualbox repositorie and had trouble with running virtual machines. It was a permission error: VERR_SUPLIB_OWNER_NOT_ROOT
Turns out after some searching that the permission had changed on /usr to owner:chris and group:vboxusers. Directories inside /usr still belonged to the user root and the group root.
I don't know how much of a security issue this is, but i wanted it to let you all know just in case it is. I changed /usr again to root:root and all is well again.
I have previously been using VirtualBox on an Ubuntu installation, but have now switched to openSUSE 11.4. I have a .vdi file that I want to continue using and would like to know if it is possible to import this to the (preferred?) hypervisor which appears in the openSUSE System menu, which I assume is XEN.
I am using opensuse 11.1.I have installed virtualbox in my machine.The problem is that when i am running it doesn't open.Do you know why it doesn't work?
Host is x64 openSUSE 11.2 guest is winxp pro VirtualBox ver 3.0.12
The install and setup of VirtualBox is good and working.
I'm having a perplexing issue with usb devices. I have three usb devices connected to my system - apc battery, sd carder, and a Logitech joystick. All devices work on the host. I can connect the apc and the card reader to the guest and they work perfectly. But not the Logitech joystick. I get this error, same as I've seen in some other threads:
Failed to attach the USB device Logitech Force 3D Pro [0600] to the virtual machine winxp1. Failed to create a proxy device for the USB device. (Error: VERR_READ_ERROR)
under "details" is this:
Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}
I installed VirtualBox, and I want to install Vista on it. I just have the copy of vista that came with my computer. I made the back up disks for it, and tried to use them to install it in the virtual box, but it said it was unable to install in that machine.
After that I looked in my windows partition and found the product ID for the vista copy. My question is: Can I download a copy of Vista and then use the product ID of my copy to make the installation in the VirtualBox? Are there any technical or legal reasons not to do this?
VirtualBox is successfully installed on my openSUSE 11.2 and the guest OS is Win XP. I am looking for a way to acomplish two things from the guest OS:-use USB -use internet connection
On the first one, I've run into a howto for openSUSE 11.2 that says usb access for guest OSes in VBox is supported only in the binary (non-free) version. Since I am running the free one, does that mean I am out of luck on usb matter?
On the second one, I am puzzled as well. WinXP image is already installed and I tried to configure its networking via the "settings" section in VBox which gives me several options out of which none is for setting up IP's. How do I get internet connection that openSUSE host already has to share it with the guest OS within VBox?
I have a few VMs set up with virtualbox but am finding that I'm now running out of space in some of the VMs. I really don't fancy creating new VMs and reinstalling and configuring them so is there an easy way to increase the size of the virtual disks?
I've install virtualbox and got it working.In KDE, the normal Alt-F2 -> virtualbox will start virtualbox. However, when I login to openbox or fluxbox, I am unable to get virtualbox started.Curious, re-login into KDE and virtualbox can be started as normal.However, in konsole, when I try to locate virtualbox, I am unable to locate it.Any idea how to locate and start virtualbox in fluxbox, openbox?