I guess to further clarify what I want to try to do is have sys net be
connected to the interface that is connected to my modem(to the ISP/world).
I would like another vm to control all(or some) other
physical interfaces on my machine (access points/etc..).
I would like a qubeVM from within
Its a fresh install of 4.0 and im using default sys vms.
Id rather not have all these vms as the overhead is pointless.
I also did not realize there was a switch, ill read up on nft.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
I am still having difficulty getting these vms to be reachable with each other.
Basically what I want to do is have a home security/automation vm, and a
freenas vm, communicate with the outside world and with the vm that controls my
access points/physical switches.
Currently I have the usual
I want to allow a debian qube to use a BSD qube as its network and to allow
traffic between them. The BSD sees the vif created for the debian when I do
this, but no traffic passes between them. In the firewall settings for debian
qube I get a warning that its not attached to a firewall vm so no
I tried nomsi and permissive mode but they did not work. I had thought that
intel nics would work better but perhaps I will switch to realtec nics once
some other issues are worked out.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
Entering sudo xl console sys-net returns "sys-net is an invalid domain
identifier (rc=-6)." this does not work for any other vm.
Status of qrexec agent returns:
Loaded: not found (reason: no such file or directory)
Active: inactive(dead)
Trying to start qrexec agent returns
Failed to restart
On mine this happened when I did not create a proxy vm with network manager.
My vpn had an option for a script file to initialize the .Ovpn file inside the
appvm. Doing this hid the ip but the dns stayed the same. I guess because the
dns settings are in one of the service vms.
--
You
So for what it's worth, I upgraded from 3.1 to 3.2 and was still able to boot
from efi. Doing a clean install with 3.2 would not boot at all(without moving
/boot or /boot/efi to a usb). So there must be something in the 3.2 installer
that is different from 3.1 preventing this from working.
So this could be on my end. But in 3.1 I have to install /boot and /boot/efi.
Otherwise it would not let me install. It does boot which is cool.
On 3.2 I can install /boot or /boot/efi, or both, and it won't boot(cant find
the drive).
Tomorrow I will try and update 3.1 kernel to 3.2 and see if
I am working on custom partition configs to boot qubes into an nvMe drive and
was wondering if, when using efi boot, I still need /boot. The help screen just
states that efi boot needs to be >200mb and /boot needs to be >=500 mb. I took
this as meaning it needs both but now I got to thinking
10 matches
Mail list logo