Re: [qubes-users] Need Help: Ruined my installation via PCI pass through

2020-12-08 Thread unman
On Tue, Dec 08, 2020 at 10:22:17PM +, 'awokd' via qubes-users wrote: > 
Ulrich Windl:
> > Hi!
> > 
> > Trying to get my WLAN adapter into sys-net, I made a fatal mistake: The USB 
> > host added also has the boot device (and mouse) connected. Now as soon as 
> > sys-net starts (maybe even earlier) the PV for qubes becomes inaccessible.
> > 
> > Mounting the device in another Linux system, I tried to prevent the start 
> > of sys-net by renaming the systemd link for multi-user target, but that did 
> > not help.  The kernel panics shortly after boot.
> > Before I had tried to find (and edit) the settings that cause the problem, 
> > but could not find them.
> > 
> > My idea was to prevent start of sys-net, then use the qubes manager to undo 
> > my bad setting.
> > Unfortunately I don't get that far.
> 
> Try
> https://github.com/QubesOS/qubes-issues/issues/2270#issuecomment-242900312
> first. If that doesn't work, make a copy of /var/lib/qubes/qubes.xml, and
> edit it by hand to remove autostarting sys-net (and all other autostarts
> that depend on it such as sys-firewall), and/or remove the WLAN binding to
> sys-net. It's XML so a somewhat fragile file; pay attention to the <>/ etc.
> 

I wouldn't change too much in that file, just the absolute minimum.
To edit the xml file and remove the devices assigned to sys-net, look
for lines like  in the
sys-net section - delete those lines.
MAKE SURE you have a copy of that file somewhere safe before editing.

Then restart - sys-net should start but wont be stealing the usb
devices.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20201209032523.GA21959%40thirdeyesecurity.org.


Re: [qubes-users] Need Help: Ruined my installation via PCI pass through

2020-12-08 Thread 'awokd' via qubes-users

Ulrich Windl:

Hi!

Trying to get my WLAN adapter into sys-net, I made a fatal mistake: The USB 
host added also has the boot device (and mouse) connected. Now as soon as 
sys-net starts (maybe even earlier) the PV for qubes becomes inaccessible.

Mounting the device in another Linux system, I tried to prevent the start of 
sys-net by renaming the systemd link for multi-user target, but that did not 
help.  The kernel panics shortly after boot.
Before I had tried to find (and edit) the settings that cause the problem, but 
could not find them.

My idea was to prevent start of sys-net, then use the qubes manager to undo my 
bad setting.
Unfortunately I don't get that far.


Try 
https://github.com/QubesOS/qubes-issues/issues/2270#issuecomment-242900312 
first. If that doesn't work, make a copy of /var/lib/qubes/qubes.xml, 
and edit it by hand to remove autostarting sys-net (and all other 
autostarts that depend on it such as sys-firewall), and/or remove the 
WLAN binding to sys-net. It's XML so a somewhat fragile file; pay 
attention to the <>/ etc.


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5d96d76a-01c2-889d-bd83-9674318f32c7%40danwin1210.me.


[qubes-users] Need Help: Ruined my installation via PCI pass through

2020-12-08 Thread Ulrich Windl
Hi!

Trying to get my WLAN adapter into sys-net, I made a fatal mistake: The USB 
host added also has the boot device (and mouse) connected. Now as soon as 
sys-net starts (maybe even earlier) the PV for qubes becomes inaccessible.

Mounting the device in another Linux system, I tried to prevent the start of 
sys-net by renaming the systemd link for multi-user target, but that did not 
help.  The kernel panics shortly after boot.
Before I had tried to find (and edit) the settings that cause the problem, but 
could not find them.

My idea was to prevent start of sys-net, then use the qubes manager to undo my 
bad setting.
Unfortunately I don't get that far.

Any help appreciated!

Regards,
Ulrich

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5FCFFA3F02A10003D674%40gwsmtp.uni-regensburg.de.


Re: [qubes-users] Re: Someone should port this RDP Windows windower thing for Qubes

2020-12-08 Thread evado...@gmail.com
:-( thanks for your research anyway

> Chances we get seamless windows apps anytime soon are slim.
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7181a3e2-642b-41c8-ae89-fbd7c4caaa60n%40googlegroups.com.