How to create a static IP address when connecting to ethernet

User Support
,
21

Change Virtualization mode from PVH to HVM and press Apply, then try again.

22

It seems I cannot get it to work. I passed the ethernet controller (Broadwell) to the right in HVM mode.
sys-firewall has NetVM sys-net.
zyra-net has NetVM sys-firewall.
work has NetVM zyra-net.

When tried to fire up work VM it shows

Qube Status: zyra-net
Qube zyra-net has failed to start: Requested operation is not valid: PCI device 00000:00:19.0 is in use by driver xenlight, domain sys-net

also for work

Qube Status: work
Qube zyra-net has failed to start: Requested operation is not valid: PCI device 00000:00:19.0 is in use by driver xenlight, domain sys-net

I will do some more research on this.

23

You need to remove the ethernet PCI device in sys-net, the messages tells you that it can’t be used by zyra-net as it’s already in use in sys-net

2 Likes
24

Finally it Works !!!
Thank you so much @apparatus and @solene .

Objective
Two different networks Wireless and Ethernet.
Wireless is supposed to connect with personal qube.
Ethernet with work qube.

Phase 1
Create a separate AppVM called zyra-net;

  • during creation select “Provides network access to other qubes” (Advanced tab)

Phase 2
Do not create clash with sys-net VM

  • Remove ethernet controller from sys-net VM to prevent error above. (Thanks Solene)

Phase 3
Change settings to provide internet access to AppVM

  • only service is network-manager (Services tab)
  • with HVM mode in Virtualization section (Advanced tab) — Thanks apparatus
  • Uncheck Include in memory balancing (Advanced tab)
  • ethernet controller selected (Devices tab)
  • Advanced Network Configuration selected as Application (Application tab)
  • Configure static IP and DNS from Advanced Network Configuration in zyra-net

Phase 4

  • sys-firewall has NetVM sys-net.
  • zyra-net has NetVM sys-firewall.
  • work has NetVM zyra-net.

Fire up firefox from work qube and check ip on both work and personal VMs to see the difference. It works :slight_smile:

Things to consider - Downsides

  • Ethernet connection is not stable at the moment. It goes up and down frequently. Maybe is on my side.
  • Network settings on zyra-net AppVM are not persistent after restart. You have to reconfigure each time after restart.
  • It appears as work VM uses Wireless connection as fallback option. That happens after restart and probably because Network settings at zyra-net are not persistent.

P.S I am tagging this as solution since both @apparatus and @solene helped me. No other way to tag two solutions simultaneously.

1 Like
25

How did you configure your network settings? If it was using Network Manager and zyra-net is not configured as disposable VM then your network settings should persist.

It’s because you’ve set sys-firewall as zyra-net NetVM. Set zyra-net NetVM to (none).

1 Like
26

I changed it by going to zyra-net VM → Advanced Network Configuration. Then I input my static IP address and DNS. I am using Network Manager.

Setting up zyra-net NetVM as (none) solved the problem of persistence. Once I typed in static IP and DNS, the next restart settings were saved. And no fallback to wireless.

Is it possible to select ethernet controller in sys-net VM (Devices tab) now that zyra-net is set to (none).

27

No, the ethernet controller is still used by zyra-net.
NetVM is used for networking between qubes inside Qubes OS. When you set it to (none) it means that this qube don’t have/need a gateway for a connection to some upstream qube, this qube is the endpoint that should route traffic from qubes connected to this qube to the external network using network interface from device attached to it.

28

Thanks. Your help is greatly appreciated.

Why do I need to uncheck Include in memory balancing (Advanced tab) on zyra-net VM?

29

Dynamic memory balancing can result in some devices not working.