5 Commits

Author SHA1 Message Date
Christophe Fergeau
79e078b297 build: Rename vm to gvforwarder
This aligns the naming with 'gvproxy' and hopefully makes it a bit more
descriptive

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
2023-04-25 15:00:34 +02:00
Christophe Fergeau
db02c55d04 systemd: Add dependency on the tap device
This ensures that the network device the systemd unit needs exists.

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
2023-04-21 15:43:27 +02:00
Christophe Fergeau
d820a9aaa9 systemd: Use unit file template for device name
This will allow to always install gv-user-network.service system-wide.
After configuring a tap network device, gv-user-network.service
can be enabled/started with:
 # systemctl enable --now gv-user-network@vsock0

(if the device is named `vsock0`)

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
2023-04-21 15:43:27 +02:00
Christophe Fergeau
f4baa98dfa systemd: Improve user-network.service naming/description
When this is installed in /etc/systemd/system/, the very generic unit
name/description can be a problem.

Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
2023-04-21 15:43:27 +02:00
Brent Baude
7d1dd1cee4 hvsock related systemd and nm config files
the network manager file configures a vsock0 network interface with the
specific mac-address that gvproxy needs.  this must be run before the vm
command is run.

the systemd file is for running the vm command after network manager
creates the network interface.  the url must be modified with the vm ID
when using hvsock and Microsoft HyperV virtualization.  Once the vm
command has been run, we issue a postexec to ask NM to bring the "link"
up.  this may not be entirely necessary but wfm.

Signed-off-by: Brent Baude <bbaude@redhat.com>
2023-04-21 15:30:04 +02:00