The continuing challenges of getting a workable server continue. The latest spins of VirtualBox seem to have solved the issues of DKMS auto compiles of the driver being aborted. The yum updates work as expected, provided one stops the running vms manually first.
However, trying to get systemd to start the vms is proving to be a PITA. I have extensively googled and found that there are no specific instructions for Fedora/Redhat/CentOS and VirtualBox setups for systemd. After many trials and errors I have this systemd service file:
filename - /etc/systemd/system/vboxstarter@.service
[Unit] Description=VBox Virtual Machine %i Service Requires=systemd-modules-load.service vboxballoonctrl-service.service After=systemd-modules-load.service vboxballoonctrl-service.service Conflicts=shutdown.target
[Service] User=<username> Group=vboxusers Restart=on-failure TimeoutSec=5min Environment="VBOX_USER_HOME=/home/rkampen/VirtualBox VMs/%i" ExecStart=/usr/bin/VBoxHeadless -s %i ExecStop=/usr/bin/VBoxManage controlvm %i savestate
[Install] WantedBy=multi-user.target
and on occasions the invocation systemctl start vboxvmstarter@Windoze10_2.service will work, although recently it is failing always with
$ systemctl status vboxvmstarter@Windoze10_2.service
● vboxvmstarter@Windoze10_2.service - VBox Virtual Machine Windoze10_2 Service Loaded: loaded (/etc/systemd/system/vboxvmstarter@.service; enabled; vendor preset: disabled) Active: deactivating (stop-sigterm) (Result: exit-code) since Tue 2016-05-17 03:25:02 EDT; 4s ago Process: 1987 ExecStop=/usr/bin/VBoxManage controlvm %i savestate (code=exited, status=1/FAILURE) Process: 1906 ExecStart=/usr/bin/VBoxHeadless -s %i (code=exited, status=1/FAILURE) Main PID: 1906 (code=exited, status=1/FAILURE) CGroup: /system.slice/system-vboxvmstarter.slice/vboxvmstarter@Windoze10_2.service └─1940 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
May 17 03:25:02 media.pcol.org systemd[1]: Started VBox Virtual Machine Windoze10_2 Service. May 17 03:25:02 media.pcol.org systemd[1]: Starting VBox Virtual Machine Windoze10_2 Service... May 17 03:25:02 media.pcol.org systemd[1]: vboxvmstarter@Windoze10_2.service: main process exited, code=exited, status=1/FAILURE May 17 03:25:02 media.pcol.org VBoxManage[1987]: VBoxManage: error: Could not find a registered machine named 'Windoze10_2' May 17 03:25:02 media.pcol.org VBoxManage[1987]: VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), com...pports May 17 03:25:02 media.pcol.org VBoxManage[1987]: VBoxManage: error: Context: "FindMachine(Bstr(a->argv[0]).raw(), machine.a...VM.cpp May 17 03:25:02 media.pcol.org systemd[1]: vboxvmstarter@Windoze10_2.service: control process exited, code=exited status=1 Hint: Some lines were ellipsized, use -l to show in full.
as <username> a vboxmanage list vms "Windoze10_2" {51c8f956-9aba-4d2a-942c-8f46889d5bc0}
shows the required vm. as root or using sudo it returns nothing. thus my only conclusion is that systemd actually runs this as root and ignores the User= line of the [Service] stanza.
No idea where to from here, so if there is anyone that has a working systemd autostart VirtualBox setup on a headless CentOS 7 server - please advise what you have done to get it working. Or any systemd gurus that can point me at the specific foo required to beat this deamon into submission. TIA Rob P.S. I deliberately set up the VirtualBox vms under a non privileged user account. I have tried setting up a symbolic link from /root to the ~/username/VirtualBox\ VMs folder and made root a member of the virtualboxusers group - no difference, as expected, but getting desperate.
On Tue, 17 May 2016, Rob Kampen wrote:
No idea where to from here, so if there is anyone that has a working systemd autostart VirtualBox setup on a headless CentOS 7 server - please advise what you have done to get it working.
I deliberately bailed on VirtualBox when we moved to C7, as KVM offered everything I needed with less hassle.
I take it you've considered switching?
jh
On 17/05/16 19:58, John Hodrien wrote:
On Tue, 17 May 2016, Rob Kampen wrote:
No idea where to from here, so if there is anyone that has a working systemd autostart VirtualBox setup on a headless CentOS 7 server - please advise what you have done to get it working.
I deliberately bailed on VirtualBox when we moved to C7, as KVM offered everything I needed with less hassle.
I take it you've considered switching?
Considered, very briefly. I have had great success and stability with running VirtualBox on both CentOS 5 & 6 for the few Windoze apps that my clients need to run and have up on a server 24x7. The set ups I am using have been running reliably for over 8 years and remote manged with zero issues - HUGE thanks to the CentOS team for an awesome OS system delivery Thus, I have simply installed the latest VirtualBox on CentOS 7 and gone from there. I was aware that systemd existed and deliberately waited until this year to upgrade the hardware and OS, thinking issues like this should have been sorted by now. Are there any good tutorial / howtos for KVM? Although at this point I am back on another continent and reluctant to shift to KVM when over 20 hours fly time away from the server.
jh _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On Tue, 17 May 2016, Rob Kampen wrote:
Considered, very briefly. I have had great success and stability with running VirtualBox on both CentOS 5 & 6 for the few Windoze apps that my clients need to run and have up on a server 24x7. The set ups I am using have been running reliably for over 8 years and remote manged with zero issues - HUGE thanks to the CentOS team for an awesome OS system delivery
Sure.
Thus, I have simply installed the latest VirtualBox on CentOS 7 and gone from there. I was aware that systemd existed and deliberately waited until this year to upgrade the hardware and OS, thinking issues like this should have been sorted by now.
You just get the win of running a setup Redhat test, rather than a setup they don't have any great interest in.
Are there any good tutorial / howtos for KVM? Although at this point I am back on another continent and reluctant to shift to KVM when over 20 hours fly time away from the server.
I'd probably start with:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/htm...
jh
On Tue, May 17, 2016 at 09:25:53AM +0100, John Hodrien wrote:
On Tue, 17 May 2016, Rob Kampen wrote:
Are there any good tutorial / howtos for KVM? Although at this point I am back on another continent and reluctant to shift to KVM when over 20 hours fly time away from the server.
I'd probably start with:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/htm...
An alternative might be this one. I've always found this person's KVM docs very easy to follow.
http://linux.dell.com/files/whitepapers/KVM_Virtualization_in_RHEL_7_Made_Ea...
On 17 May 2016 at 09:11, Rob Kampen rkampen@kampensonline.com wrote:
On 17/05/16 19:58, John Hodrien wrote:
On Tue, 17 May 2016, Rob Kampen wrote:
No idea where to from here, so if there is anyone that has a working
systemd autostart VirtualBox setup on a headless CentOS 7 server - please advise what you have done to get it working.
I deliberately bailed on VirtualBox when we moved to C7, as KVM offered everything I needed with less hassle.
I take it you've considered switching?
Considered, very briefly. I have had great success and stability with
running VirtualBox on both CentOS 5 & 6 for the few Windoze apps that my clients need to run and have up on a server 24x7. The set ups I am using have been running reliably for over 8 years and remote manged with zero issues - HUGE thanks to the CentOS team for an awesome OS system delivery Thus, I have simply installed the latest VirtualBox on CentOS 7 and gone from there. I was aware that systemd existed and deliberately waited until this year to upgrade the hardware and OS, thinking issues like this should have been sorted by now. Are there any good tutorial / howtos for KVM? Although at this point I am back on another continent and reluctant to shift to KVM when over 20 hours fly time away from the server.
Why would that be an issue? It's not Xen where you have to boot into a special kernel ... it's just the ordinary kernel. In fact I'd be surprised if you had to reboot at all, you should just have to install the virtualization group (along with virt-tools and virt-manager to make your life easier, dont' forget to install fonts if using virt-manager over X forward and wanting to avoid little boxes instead of characters) and be up and running.
On 17/05/16 22:38, James Hogarth wrote:
On 17 May 2016 at 09:11, Rob Kampen rkampen@kampensonline.com wrote:
On 17/05/16 19:58, John Hodrien wrote:
On Tue, 17 May 2016, Rob Kampen wrote:
No idea where to from here, so if there is anyone that has a working
systemd autostart VirtualBox setup on a headless CentOS 7 server - please advise what you have done to get it working.
I deliberately bailed on VirtualBox when we moved to C7, as KVM offered everything I needed with less hassle.
I take it you've considered switching?
Considered, very briefly. I have had great success and stability with
running VirtualBox on both CentOS 5 & 6 for the few Windoze apps that my clients need to run and have up on a server 24x7. The set ups I am using have been running reliably for over 8 years and remote manged with zero issues - HUGE thanks to the CentOS team for an awesome OS system delivery Thus, I have simply installed the latest VirtualBox on CentOS 7 and gone from there. I was aware that systemd existed and deliberately waited until this year to upgrade the hardware and OS, thinking issues like this should have been sorted by now. Are there any good tutorial / howtos for KVM? Although at this point I am back on another continent and reluctant to shift to KVM when over 20 hours fly time away from the server.
Why would that be an issue? It's not Xen where you have to boot into a special kernel ... it's just the ordinary kernel. In fact I'd be surprised if you had to reboot at all, you should just have to install the virtualization group (along with virt-tools and virt-manager to make your life easier, dont' forget to install fonts if using virt-manager over X forward and wanting to avoid little boxes instead of characters) and be up and running.
thanks James. I have started working through the document you indicated and will see how it goes. It may take a few days to sort out enough time. BTW, will I be able to use the Windows10 image file that VirtualBox uses? Is there a tool that changes the format of the vm image if its different? Or am I faced with a new Windoze install and installing the Windoze Apps all over again? That may be an issue as the Windoze application is quite complex and the last two times I have installed it, I had to use the app provider's help line to solve Windoze 10 issues as the default install has some things that need changing in order for their app to work.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 05/17/2016 05:49 AM, Rob Kampen wrote:
On 17/05/16 22:38, James Hogarth wrote:
On 17 May 2016 at 09:11, Rob Kampen rkampen@kampensonline.com wrote:
On 17/05/16 19:58, John Hodrien wrote:
On Tue, 17 May 2016, Rob Kampen wrote:
No idea where to from here, so if there is anyone that has a working
systemd autostart VirtualBox setup on a headless CentOS 7 server - please advise what you have done to get it working.
I deliberately bailed on VirtualBox when we moved to C7, as KVM offered everything I needed with less hassle.
I take it you've considered switching?
Considered, very briefly. I have had great success and stability with
running VirtualBox on both CentOS 5 & 6 for the few Windoze apps that my clients need to run and have up on a server 24x7. The set ups I am using have been running reliably for over 8 years and remote manged with zero issues - HUGE thanks to the CentOS team for an awesome OS system delivery Thus, I have simply installed the latest VirtualBox on CentOS 7 and gone from there. I was aware that systemd existed and deliberately waited until this year to upgrade the hardware and OS, thinking issues like this should have been sorted by now. Are there any good tutorial / howtos for KVM? Although at this point I am back on another continent and reluctant to shift to KVM when over 20 hours fly time away from the server.
Why would that be an issue? It's not Xen where you have to boot into a special kernel ... it's just the ordinary kernel. In fact I'd be surprised if you had to reboot at all, you should just have to install the virtualization group (along with virt-tools and virt-manager to make your life easier, dont' forget to install fonts if using virt-manager over X forward and wanting to avoid little boxes instead of characters) and be up and running.
thanks James. I have started working through the document you indicated and will see how it goes. It may take a few days to sort out enough time. BTW, will I be able to use the Windows10 image file that VirtualBox uses? Is there a tool that changes the format of the vm image if its different? Or am I faced with a new Windoze install and installing the Windoze Apps all over again? That may be an issue as the Windoze application is quite complex and the last two times I have installed it, I had to use the app provider's help line to solve Windoze 10 issues as the default install has some things that need changing in order for their app to work.
You can convert a Virtual Box VM into a KVM VM, it is a 2 step process. First is to convert ALL the drives to RAW format, then convert them to qcow2 image.
If you only have one drive for the VM, it is fairly easy. Here is one of many links from google:
https://kuther.net/content/convert-virtualbox-kvmqemu
Lots of other links available as well.
The qemu-img in centos 7 can do this in one step instead of 2 though ...
qemu-img convert -f vdi -O qcow2 vm.vdi vm.qcow2
(You would substitute your actual vdi file name for vm.vdi and name the output file whatever you want instead of vm.qcow2).
Once you have a qcow2 file, you just import it in virt-manager and it should work.
Hi all, I am using the google cloud compute engine and we have a client that does not want to share their ssh keys. So I have been attempting to set up a PEM file for ssh access. Both the local server I used for testing and the cloud vm are centos 6.
I created a user on the cloud box, ran "ssh-keygen -t rsa" and took the defaults. I then copied the id_rsa.pub file to the local centos box, renamed it then made my test user the owner of the file. I then attempted to connect to the user I created on the google cloud box with the PEM file as shown below, but got the following error.
[test1@pgpool1 ~]$ ssh -i /home/test1/my-key.txt upload@815.677.151.45 Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
Have any of you done this successfully before? Or know what the issue may be?
Thanks in advance
In article 573B48C8.1070000@consistentstate.com, Dustin Kempter dustink@consistentstate.com wrote:
Hi all, I am using the google cloud compute engine and we have a client that does not want to share their ssh keys. So I have been attempting to set up a PEM file for ssh access. Both the local server I used for testing and the cloud vm are centos 6.
I created a user on the cloud box, ran "ssh-keygen -t rsa" and took the defaults. I then copied the id_rsa.pub file to the local centos box, renamed it then made my test user the owner of the file. I then attempted to connect to the user I created on the google cloud box with the PEM file as shown below, but got the following error.
[test1@pgpool1 ~]$ ssh -i /home/test1/my-key.txt upload@815.677.151.45 Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
Have any of you done this successfully before? Or know what the issue may be?
Try adding -v to the ssh command, to get more information.
But also, on the server you are trying to log in to, the public key needs to be copied into ~/.ssh/authorized_keys - not left in its own file.
Also make sure that the ~/.ssh/directory is owned by the user and has permissions of 700.
Cheers Tony
On 5/17/16 10:47 AM, Tony Mountifield wrote:
In article 573B48C8.1070000@consistentstate.com, Dustin Kempter dustink@consistentstate.com wrote:
Hi all, I am using the google cloud compute engine and we have a client that does not want to share their ssh keys. So I have been attempting to set up a PEM file for ssh access. Both the local server I used for testing and the cloud vm are centos 6.
I created a user on the cloud box, ran "ssh-keygen -t rsa" and took the defaults. I then copied the id_rsa.pub file to the local centos box, renamed it then made my test user the owner of the file. I then attempted to connect to the user I created on the google cloud box with the PEM file as shown below, but got the following error.
[test1@pgpool1 ~]$ ssh -i /home/test1/my-key.txt upload@815.677.151.45 Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
Have any of you done this successfully before? Or know what the issue may be?
Try adding -v to the ssh command, to get more information.
But also, on the server you are trying to log in to, the public key needs to be copied into ~/.ssh/authorized_keys - not left in its own file.
Also make sure that the ~/.ssh/directory is owned by the user and has permissions of 700.
Cheers Tony
Thank you! I added the authorized keys on the server I am trying to connect to and now when I run the same command on the test server it is asking me for the passphrase, as I did not set one I just hit enter and then get the same permission denied error as before. Is there something I missed? permissions are correct for sure on the google cloud server that im trying to connect to. The key file on the test server is set to 0600
Thanks in advance!
On Tue, 17 May 2016 13:59:18 -0600 Dustin Kempter wrote:
Is there something I missed?
ssh -v serveryouwanttoconnectto
That will tell you what the problem is.
If you don't understand the output, post it here.
On 5/17/16 2:12 PM, Frank Cox wrote:
On Tue, 17 May 2016 13:59:18 -0600 Dustin Kempter wrote:
Is there something I missed?
ssh -v serveryouwanttoconnectto
That will tell you what the problem is.
If you don't understand the output, post it here.
Here is the command and output
[test1@pgpool1 ~]$ ssh -v -i /home/test1/my-key.txt upload@144.167.188.62 OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 104.197.158.61 [104.197.158.61] port 22. debug1: Connection established. debug1: identity file /home/test1/my-key.txt type 1 debug1: identity file /home/test1/my-key.txt-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5 none debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host '104.197.158.61' is known and matches the RSA host key. debug1: Found key in /home/test1/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug1: Next authentication method: gssapi-with-mic debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_501' not found
debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_501' not found
debug1: Unspecified GSS failure. Minor code may provide more information
debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_501' not found
debug1: Next authentication method: publickey debug1: Offering public key: /home/test1/my-key.txt debug1: Server accepts key: pkalg ssh-rsa blen 277 debug1: PEM_read_PrivateKey failed debug1: read PEM private key done: type <unknown> Enter passphrase for key '/home/test1/my-key.txt': debug1: No more authentication methods to try. Permission denied (publickey,gssapi-keyex,gssapi-with-mic). [test1@pgpool1 ~]$
On Tue, 17 May 2016 14:34:03 -0600 Dustin Kempter wrote:
Enter passphrase for key '/home/test1/my-key.txt':
Since your private key is encrypted, have you entered the passphrase for the private key when asked at this point in the login?
On 5/17/16 2:43 PM, Frank Cox wrote:
On Tue, 17 May 2016 14:34:03 -0600 Dustin Kempter wrote:
Enter passphrase for key '/home/test1/my-key.txt':
Since your private key is encrypted, have you entered the passphrase for the private key when asked at this point in the login?
Yes I did
On Tue, 2016-05-17 at 14:34 -0600, Dustin Kempter wrote:
Connecting to 104.197.158.61 [104.197.158.61] port 22.
(1) I would change the port from 22 to something more difficult to guess, perhaps 49026 (for example) and then block port 22 in the firewall.
(2) Allow to port 49026 (for example) traffic from your IP and block traffic from all other IPs.
Do not forget there are people out there desperate to get into your computer system, so make it more difficult for them.
On May 17, 2016, at 7:56 PM, Always Learning centos@u68.u22.net wrote:
(1) I would change the port from 22 to something more difficult to guess, perhaps 49026 (for example) and then block port 22 in the firewall.
If you’re going to change the port, change it to something <1024. You don’t want to have sshd running on a port that a non-root user can bind to.
-- Jonathan Billings billings@negate.org
On Tue, 2016-05-17 at 20:12 -0400, Jonathan Billings wrote:
On May 17, 2016, at 7:56 PM, Always Learning centos@u68.u22.net wrote:
(1) I would change the port from 22 to something more difficult to guess, perhaps 49026 (for example) and then block port 22 in the firewall.
If you’re going to change the port, change it to something <1024. You don’t want to have sshd running on a port that a non-root user can bind to.
But if, as I suggested, the enquirer restricts access to that port to his own IP, access attempts from other IPs will fail. Ports > 1024 can be accessed by authorised non-root users using the authorised originating IP whilst preventing access from all other IPs.
On Wed, May 18, 2016 at 03:25:11AM +0100, Always Learning wrote:
On Tue, 2016-05-17 at 20:12 -0400, Jonathan Billings wrote:
If you’re going to change the port, change it to something <1024. You don’t want to have sshd running on a port that a non-root user can bind to.
But if, as I suggested, the enquirer restricts access to that port to his own IP, access attempts from other IPs will fail. Ports > 1024 can be accessed by authorised non-root users using the authorised originating IP whilst preventing access from all other IPs.
That's not the point. If you bind to a port > 1024, then if your non root account is compromised (or some other non-root account), then it can start up a trojaned sshd on that port.
As others have said, might as well keep it on port 22, and just block connections from any network but what you trust. Make sure you keep your packages up to date and run SELinux enabled.
On 2016-05-17, Always Learning centos@u68.u22.net wrote:
(1) I would change the port from 22 to something more difficult to guess, perhaps 49026 (for example) and then block port 22 in the firewall.
(2) Allow to port 49026 (for example) traffic from your IP and block traffic from all other IPs.
Do not forget there are people out there desperate to get into your computer system, so make it more difficult for them.
If you've blocked access to the sshd port for all but whitelisted IPs, there's little point in moving sshd to a nonstandard port. If you want defense in depth, use the cloud firewall, the host firewall, and something like sshguard, and just leave sshd on port 22.
--keith
On Tue, May 17, 2016 at 08:58:16AM +0100, John Hodrien wrote:
On Tue, 17 May 2016, Rob Kampen wrote:
No idea where to from here, so if there is anyone that has a working systemd autostart VirtualBox setup on a headless CentOS 7 server - please advise what you have done to get it working.
I deliberately bailed on VirtualBox when we moved to C7, as KVM offered everything I needed with less hassle.
I take it you've considered switching?
jh
I don't understand the issue... I've installed Centos-7 on Virtualbox without hassle. it just runs.
what problem are you trying to solve?
In article 20160517130235.GA6498@fcshome.stoneham.ma.us, Fred Smith fredex@fcshome.stoneham.ma.us wrote:
On Tue, May 17, 2016 at 08:58:16AM +0100, John Hodrien wrote:
On Tue, 17 May 2016, Rob Kampen wrote:
No idea where to from here, so if there is anyone that has a working systemd autostart VirtualBox setup on a headless CentOS 7 server - please advise what you have done to get it working.
I deliberately bailed on VirtualBox when we moved to C7, as KVM offered everything I needed with less hassle.
I take it you've considered switching?
jh
I don't understand the issue... I've installed Centos-7 on Virtualbox without hassle. it just runs.
That sounds like you mean C7 as a guest. I've done that easily too.
what problem are you trying to solve?
It sounds like he is talking about C7 as a host. I haven't tried that.
Cheers Tony
On 05/17/2016 12:55 AM, Rob Kampen wrote:
May 17 03:25:02 media.pcol.org VBoxManage[1987]: VBoxManage: error: Could not find a registered machine named 'Windoze10_2'
http://karim-ouda.blogspot.com/2011/07/errors-solutions-19.html
This seems to be a common problem with VirtualBox, and doesn't appear to be systemd related.
(Like others, I'd encourage you to move toward KVM.)
On 17/05/16 17:55, Rob Kampen wrote:
No idea where to from here, so if there is anyone that has a working systemd autostart VirtualBox setup on a headless CentOS 7 server - please advise what you have done to get it working.
I'm running CentOS7 as my host and when I was using Virtualbox, I had my VM's autostarting for a while. I simply followed this answer [0] on "askubuntu.com" and it worked flawlessly. However, I've since migrated all my VM's to KVM once performance on KVM surpassed that of Virtualbox (most of my VM's are Linux servers).
My $0.02, ak.
[0] https://askubuntu.com/questions/404665/how-to-start-virtual-box-machines-aut...
On 28/05/16 12:43, Anthony K wrote:
On 17/05/16 17:55, Rob Kampen wrote:
No idea where to from here, so if there is anyone that has a working systemd autostart VirtualBox setup on a headless CentOS 7 server - please advise what you have done to get it working.
I'm running CentOS7 as my host and when I was using Virtualbox, I had my VM's autostarting for a while. I simply followed this answer [0] on "askubuntu.com" and it worked flawlessly. However, I've since migrated all my VM's to KVM once performance on KVM surpassed that of Virtualbox (most of my VM's are Linux servers).
thanks for the pointer which of the 9 answers did you use - there are four with [0] points. I did see this some time ago and got a variant working under CentOS 6. I was hoping to use the new-fangled systemd, partly as a learning exercise, but also to avoid having bespoke config files and methods of starting daemons proliferating which the methods described on askubuntu.com seem to be. rob
My $0.02, ak.
[0] https://askubuntu.com/questions/404665/how-to-start-virtual-box-machines-aut...
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 28/05/16 12:12, Rob Kampen wrote:
which of the 9 answers did you use - there are four with [0] points. I did see this some time ago and got a variant working under CentOS 6. I was hoping to use the new-fangled systemd, partly as a learning exercise, but also to avoid having bespoke config files and methods of starting daemons proliferating which the methods described on askubuntu.com seem to be. rob
Apologies - I should have stated that in my initial response.
It's the answer that starts of with - "You can use the VirtualBox Auto-start service." - it has an up-vote score of 20 (as of now).
That article cites the following link *[0]* as the original source:
*[0]* http://lifeofageekadmin.com/how-to-set-your-virtualbox-vm-to-automatically-s...
ak.
On 28/05/16 14:31, Anthony K wrote:
On 28/05/16 12:12, Rob Kampen wrote:
which of the 9 answers did you use - there are four with [0] points. I did see this some time ago and got a variant working under CentOS 6. I was hoping to use the new-fangled systemd, partly as a learning exercise, but also to avoid having bespoke config files and methods of starting daemons proliferating which the methods described on askubuntu.com seem to be. rob
Apologies - I should have stated that in my initial response.
It's the answer that starts of with - "You can use the VirtualBox Auto-start service." - it has an up-vote score of 20 (as of now).
That article cites the following link *[0]* as the original source:
*[0]* http://lifeofageekadmin.com/how-to-set-your-virtualbox-vm-to-automatically-s...
thanks, the other link helped but there are still errors in all the various instructions one error not noted was the /etc/defaults/virtualbox file it - cannot have spaces! it should be
# virtualbox defaults file VBOXAUTOSTART_DB=/etc/vbox VBOXAUTOSTART_CONFIG=/etc/vbox/autostart.cfg
My server has a very well exercised reboot as I have finally got it done Thanks for all the pointers, finally have something that seems to be reliable.
ak.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
-
Always Learning -
Anthony K -
Dustin Kempter -
Frank Cox -
Fred Smith -
Gordon Messmer -
James Hogarth -
John Hodrien -
Johnny Hughes -
Jonathan Billings -
Keith Keller -
Rob Kampen -
Scott Robbins -
tony＠softins.co.uk