I have created a new windows 10 HVM using qvm-create-windows-qube. The installation of QWT intially failed telling me to enable testsigning. I did that. Canceled te qvm-create-windows-qube run and installed the tools manually.
So far most tings seem to be working. I’m running with
gui = “” and gui-emulated=1
Coyping files from other qubes also works.
The only problem I have currently is with networking. I can ping the gateway set in te network preferneces but ping anting else like 8.8.8.8 results in a “Destination net unreachable” from the gateway. All other (debian-based) qubes have no issues with networking.
This looks like DNS is not working for the Windows qube or that it is not routed to the external network. There are several locations where a wrong configuration might rest:
The properties of the qube might point to the wrong IP addresses. So check, via qvm-prefs or the Qube Manager, if the gateway of the Windows qube has the IP address of sys-net, sys-firewall or sys-whonix. The DNS entry for that qube should be 10.139.1.1and 10.139.1.2. It might be better to change the second of these values to that of your router.
In the VM, have a look at the properties of its network interface, which will probably be something like Ethernet1. They should match those set in Qubes for the VM.
Thank you for your help. Here is the subset of qvm-prefs:
$ qvm-prefs reporting-vm | grep -P '(gateway|dns|net)'
dns D 10.139.1.1 10.139.1.2
gateway D
gateway6 D
netvm - sys-net1
provides_network D False
visible_gateway D 10.137.0.29
visible_gateway6 D
visible_netmask D 255.255.255.255
The netvm name deserves some explation: I restored it from a backp so it is not named sys-net (yet). I went with sys-net instead of sys-firewall in this case because I wanted to exlcude sys-firewall as a problem-source.
From what it looks like I cannot ping the DNS server, but that is also the case in my other VMs which have working DNS so its probably not the issue here.
C:\Users\user>ping 10.139.1.1
Pinging 10.139.1.1 with 32 bytes of data:
Reply from 10.137.0.29: Destination net unreachable.
Reply from 10.137.0.29: Destination net unreachable.
Reply from 10.137.0.29: Destination net unreachable.
Reply from 10.137.0.29: Destination net unreachable.
Ping statistics for 10.139.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\Users\user>
C:\Users\user>ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 10.137.0.29: Destination net unreachable.
Reply from 10.137.0.29: Destination net unreachable.
Reply from 10.137.0.29: Destination net unreachable.
That failing ping for 8.8.8.8 doesn’t seem normal though.
@GWeck I read something about QWT availability in Qubes 4.2 vs 4.3. What is the Version of QWT that I should use on QWT 4.3?
It’s the same version 4.2.2 for both R4.2.4 and R4.3.0.
In your qvm-prefs listing, the ip parameter is not shown. Please check if it is set to 10.137.0.33, which is expected from the VM.
If you have QWT installed in the VM, you have set the Ethernet 2 interface properties to obtain its address and DNS from DHCP. This works in my W10 VM, but I am not sure if it will work without QWT.
Ah yes. I was a bit too restrictive with the properties I filtered.
qvm-prefs reporting-vm | grep -P '(gateway|dns|net|ip|mac)'
dns D 10.139.1.1 10.139.1.2
gateway D
gateway6 D
ip D 10.137.0.33
ip6 D
mac D 00:16:3e:5e:6c:00
netvm - vpn-office
provides_network D False
visible_gateway D 10.137.0.25
visible_gateway6 D
visible_ip D 10.137.0.33
visible_ip6 D
visible_netmask D 255.255.255.255
As you can see I have switched around the net-vm in the hope it would change something (it didn’t). However, the IP address is as suggested.
I’ll try to redo the setup completely manually (without the aborted qvm-create-windows-vm) and see how that goes.
Thanks for the adivce. Now that you mention it, the 255.255.255.255 struck me as odd, but I compared it to my older Windows Qube (with working networking) and found it to be set there as well.
What to you mean by “setting it”. In the qvm-prefs and/or manually in Windows?