@stacksofplates said in I can't even:
@scottalanmiller said in I can't even:
@gjacobse said in I can't even:
I just can't....
When Amazon was interviewing me, the police had to be called on their drunked staff out at the bar. So I'm not entirely surprised.
Yup definitely wasn’t impressed with my 6 interviews I had to do with them......
6 interviews? Seems like a waste of time and resources for all parties.
Looks nice.
Idea: Add a tag for all of these called "Linux Distro Previews" or something along those lines. This way, someone browsing for different distros can find them all in one spot which makes it easier to find them all to check out.
@dustinb3403 said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@dashrender said in What Are You Doing Right Now:
@tim_g said in What Are You Doing Right Now:
I've about had it with Hyper-V.
Now what?
Yes details please.
They always just stop working out of nowhere when you are "using" it. I'm so sick of it.
If you set up some VMs on Hyper-V, and never touch anything again, it'll go forever.
But as soon as you spend time importing/exporting, replication, VM settings, etc for a while, the hypervisor just completely loses it's stability for no real reason... causing you to need to restart the HV management service. And then eventually, you'll get crap like this below that requires a reboot:
Failed to register the service principal name 'Microsoft Virtual System Migration Service'. Failed to register the service principal name 'Hyper-V Replica'. Failed to register the service principal name 'Microsoft Virtual Console Service'.I verified in AD they are registered, so I don't know wtf it's talking about. Though, I'm sure a reboot will make it all well again.
"They" as in Hyper-V "just stops working" as in shits the bed for no goddamn reason.
Good to know.
Yeah, exactly.
I'm using Hyper-V Manager on a Win10 VM on my laptop, doing a ton of VM work... nothing relating to the hypervisor... you know, just doing thing in the way it's designed...
Oh, how about it just decides to stop working? Sure why not! How about again? Sure! Oh what's that... now your on another Hyper-V hypervisor, how about that stops working too!
I tried to follow Scott's guide here, but for Fedora 26 it didn't quite work and I had to do things differently.
Here's the steps I logged as I went along. I believe following them exactly will get you from a fresh install to a working https gitlab.
New-VHD -Path "E:\Hyper-V\Virtual Hard Disks\gitlabServer.vhdx" -SizeBytes 500GB -Dynamic -BlockSizeBytes 1MB
dnf install hyperv-daemons hypervvssd hyperv-tools
systemctl stop NetworkManager.service
systemctl disable NetworkManager.service
systemctl enable network.service
reboot now
dnf install policycoreutils-python-utils
dnf install cockpit
dnf upgrade
dnf install -y curl openssh-server openssh-clients cronie
firewall-cmd --permanent --add-service=http
firewall-cmd --permanent --add-service=https
firewall-cmd --reload
semanage permissive -a httpd_t
dnf install -y pygpgme yum-utils
wget https://packages.gitlab.com/gitlab/gitlab-ce/packages/el/7/gitlab-ce-9.4.5-ce.0.el7.x86_64.rpm/download
mv download gitlab-ce-9.4.5-ce.0.el7.x86_64.rpm
dnf install -y gitlab-ce-9.4.5-ce.0.el7.x86_64.rpm
gitlab-ctl reconfigure
gitlab_rails['smtp_enable'] = true
gitlab_rails['smtp_address'] = "smtpServer.domain.local"
gitlab_rails['smtp_port'] = 25
gitlab_rails['smtp_authentication'] = false
gitlab_rails['smtp_enable_starttls_auto'] = true
gitlab_rails['gitlab_email_from'] = '[email protected]'
gitlab_rails['gitlab_email_reply_to'] = '[email protected]'
gitlab-ctl reconfigure
gitlab-rails console
Notify.test_email('[email protected]', 'GitLab Test Email', 'This is a test.').deliver_now
openssl pkcs12 -in domain_wildcard_cert.pfx -out domainwild-encrypted.key
openssl pkcs12 -in domain_wildcard_cert.pfx -clcerts -nokeys -out domainwild-certificate.crt
openssl rsa -in domainwild-encrypted.key -out domainwild-decrypted.key
openssl pkcs12 -in domain_wildcard_cert.pfx -out domain-ca.crt -nodes -nokeys -cacerts
cat domainwild-certificate.crt domain-ca.crt > full_cert.crt
mkdir -p /etc/gitlab/ssl
chmod 0700 /etc/gitlab/ssl
cp /mnt/domainwild-decrypted.key /etc/gitlab/ssl/gitlabServer.domain.local.key
cp /mnt/full_cert.crt /etc/gitlab/ssl/gitlabServer.domain.local.crt
external_url "https://gitlabServer.domain.local"
nginx['redirect_http_to_https'] = true
sudo gitlab-ctl reconfigure
@coliver said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@popester said in What Are You Doing Right Now:
Looking at my cobbled together lab machine with the intent of learning KVM. I feel like a dog that chased a car and caught it.......... WTF do I do now??
Install VyOS for internal host routing, a blog of some sort (WordPress or Drupal), NextCloud, a DNS server (I like Pi-Hole), and tie it all up with a FreePBX install (even if you don't get any SIP/VOIP service for it, still good to know). That's where my home lab is at this point at least.
But build it all with Dev Ops tools like salt or ansible.
Yeah, once you get into Salt or Ansible, it really feels like there's no better way to do things.
Also, it may be a way for you to set it up how your software license requires it to be on the guest.
If you don't want your entire set-up peer-reviewed, why include it? Simply ask your question and leave out the irrelevant stuff.
He included all of that stuff on purpose, for the specific purpose of having it reviewed... you can tell.
When you bring up a Fedora 26 VM on Hyper-V, all you need to do is run this:
dnf install hyperv-daemons hypervvssd hyperv-tools
What .iso are you using?
Also, if creating a Linux VM on Hyper-V, you'll need to create the .vhdx like this:
New-VHD -Path "E:\Hyper-V\Virtual Hard Disks\linuxvm.vhdx" -SizeBytes 150GB -Dynamic -BlockSizeBytes 1MB
The important part is the -BlockSizeBytes. Make the -SizeBytes what you want.
When you create the VM in HyperV Manager, it asks you where you want to create the .vhdx disk for the VM... choose the C drive of the host. Then after the VM is created, you can create another disk for the VM on the RAID10 in the VM settings.
As for what you are doing, your tech team is almost 100% wrong and they don't understand virtualization. You need to send them here.
@wirestyle22 said in What Are You Doing Right Now:
@tim_g Congratulations man. I hear that is a lot of work
Thanks, yea it took years and a lot of money and paperwork. We used a lawyer for the first part of the app, but did it ourselves the rest of the way. I'm good with paperwork sometimes.
Hyper-V Replica is for replicating Virtual Machines.
DFS-R is for replicating files that are NOT virtual machines or databases.
Never replicate Virtual Machine disks (.vhd,.vhdx, etc) or databases via DFS-R.
@dbeato said in What Are You Doing Right Now:
For all us of posting, take a look at this:
https://twitter.com/kevinmitnick/status/943648556165898240
This is why you don't used closed source crap.
Creating a Linux VM on Hyper-V is easy. Creating a nested VM inside your Linux VM running on Hyper-V... well, it's not going to work out of the box.
Here's how to do it: https://www.timothygruber.com/hyper-v-2/run-a-nested-vm-on-kvm-qemu-vm-in-hyper-v/
Why would you want to? In my case, there was a developer who needed to compile code on a special Linux VM, and immediately needs to test it inside a throw-away VM running in there.
Doing this on his own or another physical PC or other means was not an option.
Learning about SaltStack pillars, how to encrypt them, and how to reference them in state files for passwords and keys for example.
@kuyaz said in 2 RAID 1 or 1 RAID 10 for VM Server Host:
@jaredbusch ok noted with thanks. I got the idea now.
I usually cut a small partition out of the big RAID10 (or in your case the RAID1). Like 50 GB for the hypervisor, and use the rest for DATA (virtual disks).
Omg he's at it again!!!
Actually making an effort to steer people the wrong way.
https://community.spiceworks.com/topic/2100629-fuzzy-hyper-v-practices?page=1#entry-7459694
I've found that the very best way to manage your KVM virtual machines is to SSH into the KVM hypervisor and use the virsh command. Nothing beats that.
If you need a GUI, I've found Virt-Manager to be the next best.
If you would like a whole management interface GUI that is similar to Microsoft's System Center Virtual Machine Manager, then you should look into oVirt. I'm currently doing some things with oVirt and I really like it.
As other's mentioned, the Kimchi-Project is an excellent way to manage your KVM server and VMs via HTML5 web interface. I've got a guide on my blog on how to set it up here: https://www.timothygruber.com/linux/fedora-26-kvm-html5-remote-access-with-web-console-via-kimchi-part-1/
There is also cockpit-machines, a part of Cockpit, a web interface, but that only allows you to reboot/shutdown/on/off your virtual machines, and also allows you to view your VMs through your browser.
@fuznutz04 said in What Are You Doing Right Now:
@thwr said in What Are You Doing Right Now:
@fuznutz04 said in What Are You Doing Right Now:
Getting ready to swap over from old ISP to new ISP & do a firmware update on an ER-L Then back to tickets.
Good luck with the swap. The upgrade should just work(TM)
And done! no issues.
Here are my notes on doing the conversion:
openssl pkcs12 -in wildcard_cert.pfx -out wild-encrypted.key
openssl pkcs12 -in wildcard_cert.pfx -clcerts -nokeys -out wild-certificate.crt
openssl rsa -in wild-encrypted.key -out wild-decrypted.key
openssl pkcs12 -in wildcard_cert.pfx -out domain-ca.crt -nodes -nokeys -cacerts
cat wild-certificate.crt domain-ca.crt > full_cert.crt
=== Certificate convert PFX to PEM ===
(converts .pfx certificate file to .PEM with non encrypted private key)
openssl pkcs12 -in key.pfx -out key.pem -nodes