1 |
On Fri, 31 Dec 2021 12:50:43 -0500, |
2 |
Grant Taylor wrote: |
3 |
> |
4 |
> On 12/31/21 8:12 AM, Rich Freeman wrote: |
5 |
> > ++ |
6 |
> |
7 |
> +++ to KVM / libvirt / VirtManager (GUI) |
8 |
> |
9 |
> > This is just a front-end to libvirt and kvm, so you're building |
10 |
> > entirely on solid technologies, and anything you set up with |
11 |
> > the GUI can be edited or run or otherwise managed from the |
12 |
> > command line, and vice-versa. |
13 |
> |
14 |
> Close, but not quite. |
15 |
> |
16 |
> Yes, anything that can be done in the GUI can be done at the CLI |
17 |
> / config files. |
18 |
> |
19 |
> Though I have had some more essoteric things that had to be done |
20 |
> at the CLI / config files that couldn't be done in the GUI. This |
21 |
> usually has to do with more advanced things like iSCSI, Fibre |
22 |
> Channel, ZFS pools / dataset per guest, etc. |
23 |
> |
24 |
> The vast majority of the things that someone starting with KVM |
25 |
> will want to do can be done with the Virtual Machine Manager GUI. |
26 |
> |
27 |
> > It ends up resembling something like VirtualBox or the old |
28 |
> > VMWare Workstation edition, but it is all FOSS and in-kernel so |
29 |
> > it just is more reliable/etc. |
30 |
> |
31 |
> Yep. There are only so many ways that you can present a concept; |
32 |
> inventory of VMs, VM console, VM management. They start to look |
33 |
> similar after a while. |
34 |
> |
35 |
> > That said, I only use VMs situationally and at this point just |
36 |
> > about everything I'm doing is in containers if it can be |
37 |
> > linux-based. Way lighter all-around, even if I'm running a full |
38 |
> > OS in the container. I personally prefer to run my containers |
39 |
> > with nspawn and virtual ethernet, so each container gets its |
40 |
> > own IP via DHCP. |
41 |
> |
42 |
> The Virtual Machine Manager GUI can also administer / manage some |
43 |
> aspects of containers. |
44 |
> |
45 |
> I would highly suggest giving Virtual Machine Manager GUI for |
46 |
> KVM+libvert+qemu a try. It is probably the quintessential Linux |
47 |
> virtualization method. |
48 |
> |
49 |
> > Oh, and for kvm if you want to run your guests on your main LAN |
50 |
> > you'll probably need to set up a bridge interface. |
51 |
> |
52 |
> Yes, bridging is very nice and is my preferred way for most VM |
53 |
> use cases. Though it might be a bit more than someone wants to |
54 |
> tackle while getting their feet wet with virtualization. |
55 |
> Especially if you're trying to share a single NIC for other |
56 |
> aspects of the hosting system. It can all be done, but there is |
57 |
> a lot of minutia (methods and configurations therein) that are |
58 |
> easy to get lost in. I'd probably recommend a second NIC, even |
59 |
> if it's an inexpensive USB NIC just for the virtualization. Doing |
60 |
> that will avoid complexities that don't need to be dealt with |
61 |
> /now/. -- Reduce the number of variables that you're working |
62 |
> with at one time. |
63 |
> |
64 |
> |
65 |
|
66 |
OK, I made some progress -- I emerged qemu/kvm packages including |
67 |
libvirtd and virt-manager came along. Now, when I start virt-manager, |
68 |
it complains the qqemu/kvm not connected. I am running virt-manager |
69 |
as my regular user. |
70 |
|
71 |
Is it correct that the command line version of this is virt-install ? |
72 |
|
73 |
|
74 |
-- |
75 |
Your life is like a penny. You're going to lose it. The question is: |
76 |
How do |
77 |
you spend it? |
78 |
|
79 |
John Covici wb2una |
80 |
covici@××××××××××.com |