1 |
On 1/2/22 12:14 AM, John Covici wrote: |
2 |
> OK, I fixed it, the group name was wrong when I tried the last time, I |
3 |
> had libvirtd and its only libvirt and that seems to have fixed things. |
4 |
|
5 |
Thank you for the clarifying follow up. Here's hoping you same someone |
6 |
else time in the future. :-) |
7 |
|
8 |
On 1/2/22 9:58 AM, John Covici wrote: |
9 |
> OK, more progress and a few more questions. |
10 |
|
11 |
Yay progress! |
12 |
|
13 |
> In the virt-manager, I could not figure out how to add disk storage |
14 |
> to the vm. I have a partition I can use for the disk storage -- |
15 |
> is this different from the virtual machine image? |
16 |
|
17 |
It depends.™ |
18 |
|
19 |
KVM / libvirt / Qemu can use raw partitions, files on a mounted file |
20 |
system, logical volumes, ZFS vDevs, iSCSI, and other things for storage. |
21 |
Each one is configured slightly differently. So, which method do you |
22 |
want to use? |
23 |
|
24 |
I'd suggest that you /start/ with files on a mounted file system and |
25 |
then adjust as you need / want to. At least as long as you're getting |
26 |
your feet wet. |
27 |
|
28 |
From memory, you need to define a directory as a storage location to |
29 |
KVM / libvirt. -- I'm not currently using KVM so I'm working from a |
30 |
mixture of memory and what I can poke without spinning things up. |
31 |
|
32 |
1) Open VMM (virt-manager). |
33 |
2) Select the KVM host in the window. |
34 |
3) Edit -> Connection Details |
35 |
4) Go to the Storage tab. |
36 |
5) Click the plus below the left hand pane. |
37 |
6) Choose and enter a name for the storage pool. |
38 |
7) Choose "dir: Filesystem Directory" as the type. |
39 |
8) Choose a target path by typing or browsing to it. |
40 |
9) Click Finish. |
41 |
|
42 |
Now the storage pool you created should appear as an option when |
43 |
creating a VM. |
44 |
|
45 |
> Of even more importance, how do I bridge the vm onto my existing |
46 |
> network? |
47 |
|
48 |
This is also done through host properties on the Virtual Networks tab. |
49 |
|
50 |
I don't remember the specifics (and can't walk through it the same way |
51 |
for reasons). I usually did most of the management via the |
52 |
/etc/conf.d/net file as I do a lot of things with networking that few |
53 |
things can properly administer (802.3ad LACP, 802.1q VLAN, bridging, l2 |
54 |
filtering, l3 filtering, etc). |
55 |
|
56 |
What I remember doing was re-configuring the (primary) network interface |
57 |
so that it came up without an IP address and was added as a member to a |
58 |
newly created bridge. As part of that I moved the system's IP |
59 |
address(es) from the underlying Ethernet interface to the newly created |
60 |
Bridge interface. |
61 |
|
62 |
With the bridge created and manged outside of VMM (virt-manager) I was |
63 |
able to add new VMs / containers to the existing Bridge interface. Thus |
64 |
establishing a layer 2 connection from the VM(s) / LXC(s) to the main |
65 |
network. |
66 |
|
67 |
Note: This is somewhat of a simplification as there are VLANs and |
68 |
multiple physical interfaces with many logical interfaces on the machine |
69 |
that I'm replying to you from. However, I believe, the concepts hold as |
70 |
I've written them. |
71 |
|
72 |
> I have a nic for internal items named eno1 and another nic which |
73 |
> connects to the outside world, I would like to bridge to the internal |
74 |
> network, that would give the vm a dhcp address, etc. |
75 |
|
76 |
If you have a separate physical NIC, as I had suggested starting with, |
77 |
then you can avoid much of the bridge & IP re-configuration in the |
78 |
/etc/conf.d/net file and /mostly/ manage an independent bridge on the |
79 |
additional NIC from within VMM (virt-manager). |
80 |
|
81 |
The 2nd NIC means that you don't end up with a chicken & egg problem |
82 |
trying to administer a network interface across the network, which is |
83 |
how I do much of my work. Re-configuring things through the console |
84 |
also simplifies things in this regard. |
85 |
|
86 |
|
87 |
|
88 |
-- |
89 |
Grant. . . . |
90 |
unix || die |