Fedora Servers :: Unable A Virtualbox Guest To Start At Boot?
Mar 27, 2010
Can anyone help me with how to create an init.d script that will startup a vm machine in virtualbox at boot? I found this script:[URL]..But it is for ubuntu. I am running fedora 12 x386 and using it as an Amahi server. Very cool, but it would be extra cool if I had a virtual windows machine startup when I booted up this server. Then I could just rdp into it when I needed something in windows.
I'm running the host server on Ubuntu 10.04 LTS (64bit) . I'm using virtual box. I want to automatically for one of the guest vritualboxes to start on reboot. Following is already done without a success. Please help me in solving this.
1. I have created the following shell script #!/bin/bash /usr/bin/nohup /usr/bin/VBoxHeadless --startvm "VMNAME" 2> /dev/null &
2.From the current logged on user I did a crontab -e and did the following
crontab -e @reboot /bin/sh /home/myaccount/shellscript.sh note that I do not encrypt the home directory and sufficient permissions are there.
I just installed Fedora 12 VM using Virtualbox. The next thing I want to do is install the guest addons.So I mount the drive and go the the folder and I use the command:
Quote: su (my username) VBoxLinuxAdditions-x86.run After that I give my password. The message I get is that This program must be run with administrator privileges. Aborting What Have I done wrong? I used su and gave my password, but it still is refusing to install.I am sure I am missing something very simple.
I installed a Fedora 14 guest on a Fedora 14 host with Virtualbox, then i run these commands on the guest:yum install kernel-devel kernel-headersbut if i try to install the virtualbox-guest additions on the guest, is still complains about that it's unable to find the kernel source directory?Ha anyone succeded installing the guest additions on a guest Fedora 14?
I had a lot of trouble installing Guest Additions within the Fedora 13 Guest on a Linux host. I had to mount the vboxGuestadditions.iso from the Device --> CD/DVD Devices menu. Then I located the appropriate package for my system. In my case it was the AMD64 Linux version.I ran this as administrator in Terminal. I used the "bash" command followed by the package name. This was after CDing the the appropriate directory. The packaged installed, I then rebooted and it worked fine. (Something that would make this easier is to load a script into nautilus that would allow me to open a locatation as administartor at the open window. I'm sure there is something in Fedora to do this but I couldn't find it in a hurry so I used the command line way).
Recently I've been unable to load web pages, hosted on my Ubuntu Guest in Apache, from my OSX Host. In fact, I can no longer even ping the Guest OS from the Host. In the past, when I did ifconfig on the Guest, I got an IP of 10.0.1.n. Now I'm getting 10.0.2.15--the default NAT Address. The thing is, I didn't change any settings recently. What I did do is run software update for OSX, Ubuntu, and updated VirtBox.
why I can no longer access my Guest OS from my Host? I spent hours on this last night, to no avail. What would cause the Guest IP to change from 10.0.1.n to 10.0.2.15? As I say, I manually made no config changes.
What will be the easiest way to ssh connect a VM on VirtualBox, exporting its desktop to host, while it is already running ? I found; Howto Access via ssh a Virtualbox Guest machine.
OpenSUSE installed in a Virtualbox Virtual Machine and I want to set a shared folder.
1 - Set up a Virtual Machine and install OpenSUSE 11.2
2 - Create a shared folder on host (HostFolder)
3 - Setup the shared folder in Virtualbox Via the Virtual Machine details or via Devices > Shared Folders...
4 - Install dependencies for running the Virtualbox installer You need to install the right development kernelpackage for your machinetype (use 'zypper search -i kernel' to see what's installed) sudo zypper make gcc kernel-source kernel-hosttype/default-devel
5 - Run the Virtual Machine and go to Devices > Guest Additions This mounts an iso image in your OpenSUSE guest.
6 - Open a root terminal and run
cd /usr/src/linux make oldconfig && make prepare && make scripts && make dep cp ../linux-obj/$HOSTTYPE/default/Module.symvers . make prepare
* A commenter on previously mentioned thread says this step is unnecessary but it doesn't work without on my system. I suggest trying step 7 first and returning to step 6 if that fails. *
7 - Run ./VirtualboxLinux yourhosttype .run from the mounted iso image.
8 - Create shared folder in OpenSUSE (GuestFolder)
9 - Test with sudo mount -t vboxsf HostFolder /home/user/GuestFolder It works? Great! Let's set up the system so it automounts for your regular useraccount instead of root-only access.
10 - Add this line to /etc/fstab HostFolder /home/user/GuestFolder vboxsf defaults,uid=1000,gid=1000 0 0
11 - It works for me but if it still doesn't automount after a reboot; sudo mount -a
My laptop boot up time increased considerably (10 seconds) after allocating a virtual drive for virtualbox guest. The guest installation did not work so i removed it along with the virtual disk. Now everytime when i boot to ubuntu, after inputting my password in the login screen, it takes much longer to load the system. And during the loading time the disk activity indicator light blinks indicating the harddisk is actually busy loading the system.
I decided to search around for a possible answer and force reprofiling ureadahead does the trick Now boot time is back to what it used to be
I've installed fedora 15 on virtualbox as my guest OS.I've configured bridged networking and I've set my router to assign an IP to it.when it boots up,I have 2 devices shown via "ifconfig" which is "lo" and "p2p1" and none has the ip assigned to it.I'm unable to access the Internet. How can I configure it to do so?I've tried following this tutorial: [URL] but the file "ifcfg-ethX" doesn't exist...it only has ifcfg-lo..... I've installed fedora 15 spin edition which doesn't have a GUI for me to edit network settings...
I have VirtualBox v3.1.0 r55467 running on f12 2.6.31.6-162.fc12.i686. The guest is Windows XP SP3. I need to enable bridged mode for the virtual network interface on the guest. Everytime I enable bridge mode the following error occurs.
Quote:
Failed to start the virtual machine Windows XP. Failed to open/create the internal network 'HostInterfaceNetworking-wlan0' (VERR_SUPDRV_COMPONENT_NOT_FOUND). One of the kernel modules was not successfully loaded. Make sure that no kernel modules from an older version of VirtualBox exist. Then try to recompile and reload the kernel modules by executing '/etc/init.d/vboxdrv setup' as root (VERR_SUPDRV_COMPONENT_NOT_FOUND). When I run '/etc/init.d/vboxdrv setup' i get the following compilation error:
Quote:
Stopping VirtualBox kernel module [ OK ] Removing old VirtualBox netadp kernel module [ OK ] Removing old VirtualBox netflt kernel module [ OK ]
[code]....
dmesg gives me nothing. I have scoured the web .. and even asked on #vbox and #fedora cant get.
I have tried a few times already the following procedures: start a new installation (each time, I create a new VBox VM) with the Fedora 12 DVD iso attached to the DVD drive of the VM. I select the default setting, like US english, US keyboard, local time (GMT +8), standard installation ... etc). The installation process had been smooth to the screen the system asking for a reboot after installing something like 1100+ packages. Then I click the reboot button offered. The VM restarted but each and every time, it came up with the following error message:
Booting from local disk... FATAL: INT18: BOOT FAILURE
There was no other error message durint the installation process. It would be very much appreciated if some one can tell me what went wrong and how to solve it. I believe even I try again the same way, it will end up with same result. Is it a software or hardware problem? In case software problem, is it Fedora or VirtualBox?
i am planning on installing virtualbox on a fedora 9 machine and would like to know if it is possible to migrate another fedora 9 (totally seperate) machine to a virtualbox as a guest OS.
I have the nvidia 121.21 file for XP and Win2K. I have the driver running on this box on a dual boot win2k install. works fine. The same file on my guest win2k VirtualBox install says no driver available for my current hardware setup. My video card has the 8400 GS chip set. It is currently running 3D on This Fedora 12 install. Is the problem the VirtualBox will not allow the 3D driver to be installed. The installation had a comment about no 3D when it started. I also have not been able to get control of a USB port Device I need. There any way to have Virtual and 3D video drivers with a USB port?
i'm running VirtualBox v3.0.2 on F11x86_64. As my guest in virtualbox i will am using xp sp3. In virtualbox settings i need the use of my serial port (e.g. com1). I have `enable serial port` ticked, port number set to com1, port mode set to host device and port/file path set to /dev/ttyS0. I have done hours of searching and this is the best i have come up with so far. My question is this: How do i give permission for my guest os to use the serial port?
I can start my webservers sometimes, but not at everytime. After restarting the system, again I can start my web server as usual. Whether it is a problem of fedora9 or web servers?
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've built a customized 2.6.32 kernel over Ubuntu 10.04 server (physically) -note: it is the same version that comes with the livecd-. Then I added my stuff, cloned the disk, applied it to 3 different hardware boxes and it works perfectly. But when I put that image on a VMWare Workstation 7.1 or VirtualBox machine it doesn't load... I get a "kernel panic: not syncing vfs unable to mount root fs on unknown-block 0,0". So, I've created a new vm, I've installed ubuntu and it booted without a problem.
I ran my kernel patching as I did on the physical machine, but when I rebooted with the new kernel, I got the same error. So, the problem seems to be something in the customized kernel, but specifically going over virualized copies. By the way - In a previous version, specifically Debian 5 with kernel 2.6.18, I did the same stuff about a year ago and the machine loads perfectly in any virtualized environment. Then, the only thing left to think about my problem is that some grub parameter or kernel driver or something is messing up with booting. The customization of the kernel is only the patching for IMQ stuff.
I can't get Ubuntu v10.10 to start on VirtualBox running under Windows XP. The installation wen smoothly. However when I try to start the machine what I see is a mere black screen... The boot order is fine. However it seems strange that no data is read from the virtual hard drive (which is about 2.15 GB):
I opted to install my Linux Fedora distribution, in a SUN VM (Virtualbox). [URL] I have 2 questions:
My current max res available to select is 1024x768. Can I run at 1920x1200? My display indicated that it is 'Unknown'. I don't know if that is in on the deal, or not...
Second question: When installing VBOXADDITIONS_3.1.2_56127, I am getting the error: Building the VirtualBox Guest Additions kernel modules [FAILED]
If I am displaying the log correctly, it indicates: Makefile:23: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop Pictures are located here, in the EVGA Linux forum: [URL] I am new to both Linux, and Fedora.
My mission statement: To run Linux using the Fedora distribution, in a VM window under Windows 7 64bit Ultimate, with the ability for scripting using Bash, with the Perl programming language installed, and use Apache Tomcat to monitor both apps, and various VM installs, on numerous Servers via the internet.
I'm trying to install the Guest Additions for a VM running a guest Lucid Lynx Server. The problem I'm encountering is this: The vboxadd-install.log for vbox says it "couldn't find the sources of your current Linux kernel" and to "Specify KERN_DIR=<directory> and run Make again."
I'm completely stumped by a problem with httpd in Fedora 13. It fails to start on boot: I can see: Starting htpd: FAILED, in /var/log/boot.log, but I can't find anything else in messages, audit.log or anywhere else that gives me any clue why. The weird thing is that running: run_init service httpd start after boot _works_ and the server runs fine, but even when it's running OK, service httpd status reports httpd dead but subsys locked
I'm guessing that the problem somehow relates to selinux, but I can't find anything in the audit logs that gives me a clue. How to turn on more logging so that I can get closer to the problem. I finally discovered the cause. This system was originally configured to use network services directly, without NetworkManager. It had been upgraded a number of times since installation. It seems that over time, if you have turned off NetworkManager, the defaults have changed. Used to be that the network services was 'enabled' by default (hence started at run time). Now, the default is 'disabled'. Httpd couldn't start because there was no network to start on. Enabling network services at boot time fixed this. I guess I should have noticed this. But one might think that httpd failing to start because of the lack of a network might at least give a warning message in the logs about the reason.
I am trying to set up Vista on my Lucid within VirtualBox so I can run 3CX IP PBX. I have installed the virtualBox and set up a virtual space called "Vista", but when I start it (Power on) I get an error message - see screenshot enclosed. If I run the command
HTML Code:
'/etc/init.d/vboxdrv setup'
as instructed in terminal I get.
HTML Code:
root@server:/home/server# /etc/init.d/vboxdrv setup WARNING: All config files need .conf: /etc/modprobe.d/dahdi, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/dahdi.blacklist, it will be ignored in a future release.
I remember a friend of mine was able to get my computer to boot under CUI, and the command 'start x' started the GUI. with booting up my computer through CUI.
Running VirtualBox 3.2.6 under some host OS (should be irrelevant which one, right?), I created a machine, intending to install Fedora 13 on it. Got the Fedora 13 Live CD iso image, and an 8.6 GB virtual hard drive, completely blank. I set the machine to boot off the Live CD image. The Live CD boots nicely and I get to its desktop. I open "Install to Hard Drive"...and nothing happens. No error message, zip, nada. Inspection of the system shows a series of odd file systems, but I have no clue what they are for and whether they're usable or not.
The sticky [URL] mentions that the blank virtual hard disk should be partitioned and formatted beforehand...So I did, using the Live CD's Disk Utility (Applications: System Tools: Disk Utility). Although the sticky states the small /boot partition should be ext2 or ext3, the Live CD installer proposes to reformat it as ext4. Shouldn't we have formatted it as ext4 right away, then? Also, the installer set the /boot partition's size to 524 MB, not 200 MB as recommended by the sticky.
OBSERVATION: This was not easy because VirtualBox sets the display to 800x600 at most, and the Disk Utility spills beyond those confines WITHOUT PROVIDING SLIDERS. It was sheer luck that the required buttons (create partition, format partition) were barely reachable (at the bottom edge of the screen). This is a serious problem, because increasing the VirtualBox display size can only be done *after* installation (see for instance[URL] - since this guest addition requires rebooting the guest OS, it probably won't stick to the Live CD).
Once those two partitions are prepared and the virtual machine rebooted, "Install to Hard Drive" works as expected.
OBSERVATION: It is absolutely inexcusable that the Live CD installer (Anaconda?) does not propose to do this partitioning and formatting for the user. It is even more inexcusable that it should fail without giving any feedback whatsoever to the user.
Aside: VirtualBox's guest additions does not work correctly (for 3.2.6 anyway). The Devices: Install Guest Additions menu merely mounts a CD image VBOXADDITIONS_3.2.6_63112) without any feedback (expected feedback because the menu ends with an ellipsis). The CD, once opened, has an Open Autorun Prompt button...which fails to do anything. Manually running autorun.sh also fails. I had to manually invoke VBoxLinuxAdditions-x86.run from a terminal to get anywhere. Even then I was unable to go higher than 1024x768.