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 at 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 deliverySure.> 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/html/Virtualization_Deployment_and_Administration_Guide/ jh
On 17 May 2016 at 09:11, Rob Kampen <rkampen at 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 at 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 at centos.org > https://lists.centos.org/mailman/listinfo/centos
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/html/Virtualization_Deployment_and_Administration_Guide/ >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_Easy.pdf -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6
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 at pgpool1 ~]$ ssh -i /home/test1/my-key.txt upload at 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 at consistentstate.com>, Dustin Kempter <dustink at 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 at pgpool1 ~]$ ssh -i /home/test1/my-key.txt upload at 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 -- Tony Mountifield Work: tony at softins.co.uk - http://www.softins.co.uk Play: tony at mountifield.org - http://tony.mountifield.org