KVM - Virt-Manager on a Separate VM
-
@scottalanmiller said in KVM - Virt-Manager on a Separate VM:
@travisdh1 said in KVM - Virt-Manager on a Separate VM:
@scottalanmiller said in KVM - Virt-Manager on a Separate VM:
Who spends $5 on a wrench?
Anyone who goes to a brick and mortar store.
See.... you'd just use a brick for a fraction of the price.
Just steal a loose brick!
-
I've got an old CRT monitor sitting in the corner that could probably do the trick
-
@jaredbusch said in KVM - Virt-Manager on a Separate VM:
I use my user in the libvirt group so I do not have to bother with the root user.
gpasswd -a jbusch libvirt
Then this works.
Holy fuck it took way to long to get to this point.
So here is the stupid approach. ssh-keygen -t rsa generating. . . . . . . . . The key fingerprint is . . . ssh-copy-id -i /home/user/.ssh/d_rsa.pub user@kvm-server-ip
Login with user@kvm-server-ip password
Test the login
Disconnect from the remote server and run this next bit on your management system.
gpasswd -a username libvirt
and then run it on you kvm server assuming you're not using the "root" user.Done, and it works.
@JaredBusch thanks for cutting through the bullshit and helping out here.
-
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
Disconnect from the remote server and run this next bit on your management system.
gpasswd -a username libvirt
Run that on both systems. Assuming you are using your username and not root in the Virt-Manager connection.
-
@jaredbusch said in KVM - Virt-Manager on a Separate VM:
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
Disconnect from the remote server and run this next bit on your management system.
gpasswd -a username libvirt
Run that on both systems. Assuming you are using your username and not root in the Virt-Manager connection.
Yeah, I did that before, Updating my previous comment.
-
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
@jaredbusch said in KVM - Virt-Manager on a Separate VM:
I use my user in the libvirt group so I do not have to bother with the root user.
gpasswd -a jbusch libvirt
Then this works.
Holy fuck it took way to long to get to this point.
So here is the stupid approach. ssh-keygen -t rsa generating. . . . . . . . . The key fingerprint is . . . ssh-copy-id -i /home/user/.ssh/d_rsa.pub user@kvm-server-ip
Login with user@kvm-server-ip password
Test the login
Disconnect from the remote server and run this next bit on your management system.
gpasswd -a username libvirt
Done, and it works.
@JaredBusch thanks for cutting through the bullshit and helping out here.
Wyd you talking about. JARED mentioned that step like 3 posts down from your OP, and it was mentioned several other times as well.
-
@tim_g said in KVM - Virt-Manager on a Separate VM:
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
@jaredbusch said in KVM - Virt-Manager on a Separate VM:
I use my user in the libvirt group so I do not have to bother with the root user.
gpasswd -a jbusch libvirt
Then this works.
Holy fuck it took way to long to get to this point.
So here is the stupid approach. ssh-keygen -t rsa generating. . . . . . . . . The key fingerprint is . . . ssh-copy-id -i /home/user/.ssh/d_rsa.pub user@kvm-server-ip
Login with user@kvm-server-ip password
Test the login
Disconnect from the remote server and run this next bit on your management system.
gpasswd -a username libvirt
Done, and it works.
@JaredBusch thanks for cutting through the bullshit and helping out here.
Wyd you talking about. JARED mentioned that step like 3 posts down from your OP, and it was mentioned several other times as well.
Huh?
Nothing was as simple as what I just did, Jared was getting to the point at the top of the topic, but there were additional steps I was missing (failed to do entirely). So I dumped all of the rsa keys, and started fresh.
-
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
@tim_g said in KVM - Virt-Manager on a Separate VM:
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
@jaredbusch said in KVM - Virt-Manager on a Separate VM:
I use my user in the libvirt group so I do not have to bother with the root user.
gpasswd -a jbusch libvirt
Then this works.
Holy fuck it took way to long to get to this point.
So here is the stupid approach. ssh-keygen -t rsa generating. . . . . . . . . The key fingerprint is . . . ssh-copy-id -i /home/user/.ssh/d_rsa.pub user@kvm-server-ip
Login with user@kvm-server-ip password
Test the login
Disconnect from the remote server and run this next bit on your management system.
gpasswd -a username libvirt
Done, and it works.
@JaredBusch thanks for cutting through the bullshit and helping out here.
Wyd you talking about. JARED mentioned that step like 3 posts down from your OP, and it was mentioned several other times as well.
Huh?
Nothing was as simple as what I just did, Jared was getting to the point at the top of the topic, but there were additional steps I was missing (failed to do entirely). So I dumped all of the rsa keys, and started fresh.
The whole thing is taht simple.
- generate your ssh keys
- copy the ssh keys
- add to libvirt group (mentioned in beginning of thread and every other KVM related thread)
Done. You can break that up into as many sub steps as you want, but that's what you do.
-
@tim_g said in KVM - Virt-Manager on a Separate VM:
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
@tim_g said in KVM - Virt-Manager on a Separate VM:
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
@jaredbusch said in KVM - Virt-Manager on a Separate VM:
I use my user in the libvirt group so I do not have to bother with the root user.
gpasswd -a jbusch libvirt
Then this works.
Holy fuck it took way to long to get to this point.
So here is the stupid approach. ssh-keygen -t rsa generating. . . . . . . . . The key fingerprint is . . . ssh-copy-id -i /home/user/.ssh/d_rsa.pub user@kvm-server-ip
Login with user@kvm-server-ip password
Test the login
Disconnect from the remote server and run this next bit on your management system.
gpasswd -a username libvirt
Done, and it works.
@JaredBusch thanks for cutting through the bullshit and helping out here.
Wyd you talking about. JARED mentioned that step like 3 posts down from your OP, and it was mentioned several other times as well.
Huh?
Nothing was as simple as what I just did, Jared was getting to the point at the top of the topic, but there were additional steps I was missing (failed to do entirely). So I dumped all of the rsa keys, and started fresh.
The whole thing is taht simple.
- generate your ssh keys
- copy the ssh keys
- add to libvirt group (mentioned in beginning of thread and every other KVM related thread)
Done. You can break that up into as many sub steps as you want, but that's what you do.
nevermind. . .
-
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
@tim_g said in KVM - Virt-Manager on a Separate VM:
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
@tim_g said in KVM - Virt-Manager on a Separate VM:
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
@jaredbusch said in KVM - Virt-Manager on a Separate VM:
I use my user in the libvirt group so I do not have to bother with the root user.
gpasswd -a jbusch libvirt
Then this works.
Holy fuck it took way to long to get to this point.
So here is the stupid approach. ssh-keygen -t rsa generating. . . . . . . . . The key fingerprint is . . . ssh-copy-id -i /home/user/.ssh/d_rsa.pub user@kvm-server-ip
Login with user@kvm-server-ip password
Test the login
Disconnect from the remote server and run this next bit on your management system.
gpasswd -a username libvirt
Done, and it works.
@JaredBusch thanks for cutting through the bullshit and helping out here.
Wyd you talking about. JARED mentioned that step like 3 posts down from your OP, and it was mentioned several other times as well.
Huh?
Nothing was as simple as what I just did, Jared was getting to the point at the top of the topic, but there were additional steps I was missing (failed to do entirely). So I dumped all of the rsa keys, and started fresh.
The whole thing is taht simple.
- generate your ssh keys
- copy the ssh keys
- add to libvirt group (mentioned in beginning of thread and every other KVM related thread)
Done. You can break that up into as many sub steps as you want, but that's what you do.
nevermind. . .
That's the entire point i tried to make in my 5-steps before it getting ripped apart for me wanting to use 4096 instead of 2048, and not using ssh-copy-id.
-
@tim_g said in KVM - Virt-Manager on a Separate VM:
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
@tim_g said in KVM - Virt-Manager on a Separate VM:
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
@tim_g said in KVM - Virt-Manager on a Separate VM:
@dustinb3403 said in KVM - Virt-Manager on a Separate VM:
@jaredbusch said in KVM - Virt-Manager on a Separate VM:
I use my user in the libvirt group so I do not have to bother with the root user.
gpasswd -a jbusch libvirt
Then this works.
Holy fuck it took way to long to get to this point.
So here is the stupid approach. ssh-keygen -t rsa generating. . . . . . . . . The key fingerprint is . . . ssh-copy-id -i /home/user/.ssh/d_rsa.pub user@kvm-server-ip
Login with user@kvm-server-ip password
Test the login
Disconnect from the remote server and run this next bit on your management system.
gpasswd -a username libvirt
Done, and it works.
@JaredBusch thanks for cutting through the bullshit and helping out here.
Wyd you talking about. JARED mentioned that step like 3 posts down from your OP, and it was mentioned several other times as well.
Huh?
Nothing was as simple as what I just did, Jared was getting to the point at the top of the topic, but there were additional steps I was missing (failed to do entirely). So I dumped all of the rsa keys, and started fresh.
The whole thing is taht simple.
- generate your ssh keys
- copy the ssh keys
- add to libvirt group (mentioned in beginning of thread and every other KVM related thread)
Done. You can break that up into as many sub steps as you want, but that's what you do.
nevermind. . .
That's the entire point i tried to make in my 5-steps before it getting ripped apart for me wanting to use 4096 instead of 2048, and not using ssh-copy-id.
Because you were a twit about it.