[qubes-users] Re: sys-net unresponsive after wake from sleep
On Wednesday, February 7, 2018 at 4:02:38 PM UTC-8, Yuraeitha wrote: > On Wednesday, February 7, 2018 at 8:58:13 PM UTC+1, Dave C wrote: > > I've upgraded a laptop from 3.2 to 4.0rc4. I didn't have the problem > > described here in 3.2... > > > > When I sleep the laptop (by closing lid), I find that every time I wake it, > > sys-net is unresponsive. > > > > I cannot bring up a terminal in sys-net. Terminals already open are > > unresponsive to input. > > > > Calling `qvm-shutdown sys-net` does nothing. `qvm-kill sys-net` does kill > > it. > > > > I can restart sys-net and call `qvm-prefs -s sys-firewall netvm sys-net`, > > in order to be connected to internet again. > > > > How can I troubleshoot sys-net, given the description above? Which logs > > should I be looking at? > > > > I have tried putting iwlmvm and iwlwifi in > > /rw/config/suspend-module-blacklist, but that has not changed the behavior. > > I'm just not sure what else to try. Thanks! > > There is another Qubes users discussion going on atm about how to get around > this bug, over here > https://groups.google.com/forum/#!topic/qubes-users/1vijiBx0ftU > > For the record, I have this new bug too, and it seems quite a few others also > have it, so it may perhaps just be a question of little time before its > fixed. I don't have much time atm to look my self, nor do I have much > experience. But here is what I'd suggest. > > My guess is that you can use "sudo journalctl" in sys-net after restarting > from a crash. You can also do a "man journalctl" or "journalctl --help" to > find out how to list the system/kernel state history, or further google it > for how to use journalctl. The --boot attribute will give you everything > since last boot till you type that command, though its also possible look at > the second last boot, or any other saved time-stamps as well. > > Also if you use something like "-n 100" to journalctl, then it should only > list the last 100 lines, instead of thousands upon thousands of lines, which > can take a while to move through with a slow scrolling down by holding the > enter key down... tick clock, goes the clock. Better limit that huge log, and > you're only interested in the last few lines before it freezes anyhow :-) > > For example, if you use journalctl on the second last boot, and put it to > something like last 100 lines, then my guess is it could quite likely give > you some useful information as to what happened. > > I don't think this is a bug outside the sys-net, but is a bug involved inside > the sys-net VM. Whatever happens, it should probably show up in the > journalctl before it freezes. But I'm not an expert though. Thanks for all the advice, and for the pointer to other thread. For the record, the problem does not happen for me with every sleep/wake. Although for a while earlier today I thought it was. The last several wakes have not had the problem. When it happens again, I'll take your advice here. Cheers, -Dave -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b1bbf66e-fe4d-401d-a0a2-9fb59041d42e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] 4.0-rc4 install on Lenovo G505S - no network
On Thu, February 8, 2018 1:58 am, dbr287 wrote: > This worked fine. Applied 2 patches, and rebuild coreboot, flashed, and > re-ran R4.0rc4 install, works like a charm. Thanks again for the prompt > response. Great! They are pretty unique laptops. PS Don't suppose you (or anyone else reading and interested) are any good at C++? Would be nice to get that Coreboot patch re-activated and working properly. I can usually hack my way around code but that AGESA code base is beyond my skill-set. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/518a0c838a52d3aed8bf8a2152d02e08.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: performance hit with 4.0rc4
they're all pvh. they were hvm when restoring from qubes-backup, but that restore partially failed. On Wed, Feb 7, 2018 at 9:23 PM Chris Laprise wrote: > On 02/07/2018 09:55 PM, pixel fairy wrote: > > On Wednesday, February 7, 2018 at 6:54:32 PM UTC-8, pixel fairy wrote: > >> reinstalled over 4.0rc3 and vms take much longer to start now. it > usually takes a few seconds before getting the notification that an app vm > is starting. > >> > >> firefox performs fine, including youtube in full screen (1080p) > >> > >> chrome is a bit jumpy in most use, but plays video fine as long as it > not full screen > >> > >> blender is noticeably slower, but still usable for small scenes. > > > > If theres any strait forward way to debug this id love to. > > > > What does 'qvm-prefs' show for the virt_mode? It is the hvm mode that > starts most slowly and taxes the system. Most of the VMs (except sys-net > and sys-usb) should be using pvh mode. > > If the VMs are taking a very long time to start you can try enabling > debug mode from either 'qvm-prefs' or VM Settings dialog. > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 > -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CACr%3DtZdtkuDVkjWQCL%2BE2TSfgnBci%3DKBZpjAVOeGKprLsXySoA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: performance hit with 4.0rc4
On 02/07/2018 09:55 PM, pixel fairy wrote: On Wednesday, February 7, 2018 at 6:54:32 PM UTC-8, pixel fairy wrote: reinstalled over 4.0rc3 and vms take much longer to start now. it usually takes a few seconds before getting the notification that an app vm is starting. firefox performs fine, including youtube in full screen (1080p) chrome is a bit jumpy in most use, but plays video fine as long as it not full screen blender is noticeably slower, but still usable for small scenes. If theres any strait forward way to debug this id love to. What does 'qvm-prefs' show for the virt_mode? It is the hvm mode that starts most slowly and taxes the system. Most of the VMs (except sys-net and sys-usb) should be using pvh mode. If the VMs are taking a very long time to start you can try enabling debug mode from either 'qvm-prefs' or VM Settings dialog. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7d726375-a83c-dd04-80e2-274d1dfa393a%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: performance hit with 4.0rc4
On Wednesday, February 7, 2018 at 6:54:32 PM UTC-8, pixel fairy wrote: > reinstalled over 4.0rc3 and vms take much longer to start now. it usually > takes a few seconds before getting the notification that an app vm is > starting. > > firefox performs fine, including youtube in full screen (1080p) > > chrome is a bit jumpy in most use, but plays video fine as long as it not > full screen > > blender is noticeably slower, but still usable for small scenes. If theres any strait forward way to debug this id love to. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c1757531-2f67-4c9e-bc10-f687cd03d4ac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] performance hit with 4.0rc4
reinstalled over 4.0rc3 and vms take much longer to start now. it usually takes a few seconds before getting the notification that an app vm is starting. firefox performs fine, including youtube in full screen (1080p) chrome is a bit jumpy in most use, but plays video fine as long as it not full screen blender is noticeably slower, but still usable for small scenes. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5e4aee63-30bb-4329-a45d-5a7ab232a67c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] after update no VM 'starts' apps anymore.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-02-07 05:20, 'Tom Zander' via qubes-users wrote: > On Wednesday, 7 February 2018 08:17:11 CET Andrew David Wong > wrote: >> Are you using the `-a` option? >> >> qvm-run -a >> >> This starts the VM if it's powered off, then runs the command in >> it. Working fine for me on 3.2. > > As I wrote, qvm-start works fine, the VM is active and working. > > You just can t actually “run” anything on it. The reasons seems to > be that there is some magic thing that starts when you log into > xfce4, and only xfce4. See the screenshot attached elsewhere in > this thread of qubes manager dying on startup due to the same > issue. > > Tested on Rc4. > I was mainly replying to awokd's last sentence in the quoted portion you left out: On 2018-01-29 19:51, 'awokd' via qubes-users wrote: > On Tue, January 30, 2018 12:05 am, 'Tom Zander' via qubes-users > wrote: >> Is this a known issue? >> >> >> I can start a VM using qvm-start, but when I use qvm-run nothing >> happens, it hangs forever. Even commands that don't need a X >> server. For any qube of the various OSs I run. > > qvm-run works on both powered on and off VMs on my 4.0 on testing > repo. qvm-run works on powered on (only) VMs on my 3.2 stable. > Based on the fact that awokd wrote this in reply to you, and your description (in the quoted portion) leaves open the possibility that the same issue was affecting you, I included you as a "To:" recipient. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlp7uuQACgkQ203TvDlQ MDAg5BAAw76und38XfkYaE/qp/PrGrMFn73rp5vI73/iOUkT6vi5O0NGBd9hkAky IrG4Gaqe/fGj1rbX+Dp4J5hcJ+8HTggm8ftcv7/NgjmJ2ClkMKU/oitQinGn45Fo 6mh+X12qm3EjqtNGddg8xdBhKAuI9L428wv4MIjSgTXghkIhXWXRjFae0tHMl8Tl SkQpGYtsaRAq3NZlJDol7NmRoCctNiCIvOah3VpFxFPgEHFbJ4OUG7BSDz9WwEbW kakXDZAd1PTvY2BU8+c2rvKmUg9QoriNBEBJziliHtqXg4YPs+dwMIZBZwXAQ6F0 e3KsTr3yD79/iFdIKHAxEY6LfJrp6MgHHULJoGxHjDVc10/cMGVBTNaW+1v5bFbq cq9fihipZgaTblWGVjlfahBOYzRPZRvzhO5SljR4B4kRpUSEEkA4f8FKCkHL/wYZ 5WowJ27bORtP+tRV4IBgHB52TEzvhLZ4+ECY3RsGZC5ReSj6oqCH6X5bSqkqbacA z63o+ebaGUsNIMOgXiaOKInidv0VZ+V7vnrIdIX729g9L2gu3yEDsC9dcRgMO/sk EA6wD/vWdfJX6cbH0QxJY9wQOoIWR0zRdZ4CVoJ9MojvuY/izN98JskeSYMkPe+x zVlH24AGNh0Am5AWOClUS8LV88SpaP0rdXLOCmPC336o7pQqVrY= =wUuc -END PGP SIGNATURE- -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/56cb4586-0127-4a9f-35e5-eb92f6359786%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] 4.0-rc4 install on Lenovo G505S - no network
On Wednesday, February 7, 2018 at 3:12:34 AM UTC-5, awokd wrote: > On Wed, February 7, 2018 3:28 am, dbr287 wrote: > > I've installed rc4 on G505S with Coreboot (legacy bios). Installation > > went ok (found iommu and interrupt remapping just fine). > > > > On 1st (gui) boot, I've tried all the combinations selecting 1) create > > ServiceVMs, AppVMs, 2) only ServiceVMs, 3) only configure templates,... > > but none works. It always hangs at Configuring 1st template (usually > > debian-9). > > You probably need to manually add this patch > https://review.coreboot.org/#/c/coreboot/+/22843/ to your coreboot image. > Also, disable XHCI (two options right next to each other in menuconfig.) > > If it continues to hang on sys-net creation, try pulling the wireless card > before installing Qubes. It will still create a sys-net qube containing > the onboard ethernet, but then you can add the wireless card back and > troubleshoot on a full system. Thanks! This worked fine. Applied 2 patches, and rebuild coreboot, flashed, and re-ran R4.0rc4 install, works like a charm. Thanks again for the prompt response. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c64bcb95-2c51-4829-aa85-b334ec204887%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: sys-net unresponsive after wake from sleep
On Wednesday, February 7, 2018 at 8:58:13 PM UTC+1, Dave C wrote: > I've upgraded a laptop from 3.2 to 4.0rc4. I didn't have the problem > described here in 3.2... > > When I sleep the laptop (by closing lid), I find that every time I wake it, > sys-net is unresponsive. > > I cannot bring up a terminal in sys-net. Terminals already open are > unresponsive to input. > > Calling `qvm-shutdown sys-net` does nothing. `qvm-kill sys-net` does kill it. > > I can restart sys-net and call `qvm-prefs -s sys-firewall netvm sys-net`, in > order to be connected to internet again. > > How can I troubleshoot sys-net, given the description above? Which logs > should I be looking at? > > I have tried putting iwlmvm and iwlwifi in > /rw/config/suspend-module-blacklist, but that has not changed the behavior. > I'm just not sure what else to try. Thanks! There is another Qubes users discussion going on atm about how to get around this bug, over here https://groups.google.com/forum/#!topic/qubes-users/1vijiBx0ftU For the record, I have this new bug too, and it seems quite a few others also have it, so it may perhaps just be a question of little time before its fixed. I don't have much time atm to look my self, nor do I have much experience. But here is what I'd suggest. My guess is that you can use "sudo journalctl" in sys-net after restarting from a crash. You can also do a "man journalctl" or "journalctl --help" to find out how to list the system/kernel state history, or further google it for how to use journalctl. The --boot attribute will give you everything since last boot till you type that command, though its also possible look at the second last boot, or any other saved time-stamps as well. Also if you use something like "-n 100" to journalctl, then it should only list the last 100 lines, instead of thousands upon thousands of lines, which can take a while to move through with a slow scrolling down by holding the enter key down... tick clock, goes the clock. Better limit that huge log, and you're only interested in the last few lines before it freezes anyhow :-) For example, if you use journalctl on the second last boot, and put it to something like last 100 lines, then my guess is it could quite likely give you some useful information as to what happened. I don't think this is a bug outside the sys-net, but is a bug involved inside the sys-net VM. Whatever happens, it should probably show up in the journalctl before it freezes. But I'm not an expert though. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bf7309f5-0a14-4ba2-89a7-744b1f2fc0ba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Old Kernel versions in all VM
Hi, I noticed that all Templates and all App-VM are using a old Kernelversion. (4.9.56-21.pvops.qubes.x86_64) That are Fedora 26 and Debian stretch Templates. With the update routine you can observe the installation of new and the removal of old Kernel versions. The last one witch was installed was 4.14 something but you cannot choose it with the Qubes Manager. And with uname -a you will get the results above. Independent from the distribution. Is this intended? All the best -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/672b23d7-c510-4af1-be0d-224298d3d523%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] sys-net unresponsive after wake from sleep
I've upgraded a laptop from 3.2 to 4.0rc4. I didn't have the problem described here in 3.2... When I sleep the laptop (by closing lid), I find that every time I wake it, sys-net is unresponsive. I cannot bring up a terminal in sys-net. Terminals already open are unresponsive to input. Calling `qvm-shutdown sys-net` does nothing. `qvm-kill sys-net` does kill it. I can restart sys-net and call `qvm-prefs -s sys-firewall netvm sys-net`, in order to be connected to internet again. How can I troubleshoot sys-net, given the description above? Which logs should I be looking at? I have tried putting iwlmvm and iwlwifi in /rw/config/suspend-module-blacklist, but that has not changed the behavior. I'm just not sure what else to try. Thanks! -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/00dd019d-8692-4df9-b032-b3286f0cb85b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Is debian 9 recommended now for 3.2?
On Wed, Feb 07, 2018 at 09:08:54AM -0800, cooloutac wrote: > Is debian 8 still supported, or should I be upgrading to debian 9 now for > Qubes 3.2? > > Thanks. > > Rich. > Debian-8 is "oldstable" - it will get security patches etc til about June 2018, and then LTS. Unless you have some pressing need to retain Jessie, I'd suggest you migrate to Stretch. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20180207172535.lg4x34ycx7usajir%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Installing Qubes on ASUS X53E-RH51 does nothing
I made my 32 GB flash drive into a bootable drive using Rufus (just to see if it will run on the laptop), but when I select anything other than the command line or to modify the selection, it starts to run and then goes back to the main menu. Tried it on another device, and it would run properly (although it failed the test). Is there a way to run the test through the command line? -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d30fbbb4-275e-477e-ac4a-b3ff7a78b95b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Linux & Qubes enthusiast in Zug area of Switzerland for part time employment (student/apprentice?)
You would receive more takers if you stated the wage you were paying. Considering you did not mention this I imagine it isn't exactly high. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e7dfb7b1-be17-9afd-fbb2-b694d6650f37%40gmx.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Is debian 9 recommended now for 3.2?
Is debian 8 still supported, or should I be upgrading to debian 9 now for Qubes 3.2? Thanks. Rich. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0ed2a69a-8458-45ae-925a-f320538aa4d9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HVM freeze during OS installation
Hello, I have attempted to install OSs in an HVM using several different ISOs, and all have frozen during the start up in the same place. I have tried to install Kali Linux, Fedora 27, Fedora 26, Fedora 26 using the NetInstaller. All have frozen on the following line: x86: Booting SMP configuration: I am running Qubes OS 3.2, on Dell Inspirion 13 with Intel Core i5 7th Gen. I have tried playing with the boot options of the installers, including trying to run it in text only mode (inst.text) yet with the affect. I am unsure what logs to send, so I'll send as needed/requested. Thanks in advance for any help, NaBaCo. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/p5f5nu%24tak%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Salt management questions
Gentlepeople, For a while I have been managing a qubes setup using a dedicated management VM and ansible via https://github.com/Rudd-O/ansible-qubes. As auditing that code is beyond me and as salt is integral to qubes, I was wondering whether that layout is currently possible using the salt management stack, in other words: can the management stack (currently) be used with a vm as the master to the entire system including dom0? Sincerely, Joh -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1518013657.2002.46.camel%40graumannschaft.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] reboot sys-net
On 02/07/18 10:22, haaber wrote: I remember some issues with reattaching in the past, but recently, the qvm-shutdown --wait --force sys-net && qvm-start sys-net seems to be working. This sounded even more interesting than the script. But: It does not work in my Q4rc4 install. last experience of this type was with sys-whonix and anon-whonix. The latter running, the former did not power off (even with --force); after some wait I kill it, but it won't reboot: on boot it spills out "network device with MAC ... already exists" before dying. I had to power off anon-whonix, then restart sys-whonix. Same thing happen with the sys-net - sys-firewall - sys-whonix - anon-whonix chain. I need to power off all of them to get sys-net to rebbot, which is, frankly, annoying. So finally a script is a good idea, even if Ilpo's did not work out of the box in my install (may be a Q3.2 - Q4 issue). FWIW on R4.0rc4 I don't need to poweroff/boot any VM depending on sys-net: 'qvm-kill sys-net' (or clean shutdown) followed by 'qvm-start sys-net' works perfectly well, ie. network connectivity is automatically restored in sys-firewall and other dependent VMs. Note that I ran 'qvm-prefs sys-firewall netvm sys-net' (once after a complete reboot) after reading Awokd's reply, where he pointed to the doc explaining how to reconnect sys-firewall after a sys-net crash [1]. So maybe that step is required to get "automatic" re-connection. [1] https://www.qubes-os.org/doc/firewall/ -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2685ee5f-5863-fcce-104d-f60eac9a8f9e%40maa.bz. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Linux & Qubes enthusiast in Zug area of Switzerland for part time employment (student/apprentice?)
Dear Qubes Community, I appreciate the positive feedback received on the previous posts, but unfortunately I am reaching out again this way, as the candidates we had identified for sudden personal reasons will not be able to do it. This is a part time "jack of all trades" IT position, which requires good knowledge of Linux, and knowledge / ability to acquire knowledge of Qubes to an extent being able to set up a few machines in a small office environment with a handful of users. There will also be other tasks, such as setting up alarm system / video monitoring, networking infrastructure, server, secure communications etc. etc. We do not expect Superman, but rather someone who has a good basic knowledge of Linux / networking, and who has interest in IT and is motivated to learn what is necessary and get things done. In addition, if you are flexible, self-starter and work independently, then your enthusiasm and motivation is more important than your formal background. If you like working in a relaxed athmosphere and have a good sense of humor, then we will definetely like to add you to our team! We expect the first few weeks this can be between 50 - 100% workload, which in large parts will be up to you and your other commitments, but we would like to start soonest possible, after which we expect 10 - 25% workload, with the option of most of it being evening/weekend work, maybe in part from your home. NOTE: It is a requirement that you at times are able to come to our offices in Sihlbrug/Baar in Switzerland (just off the highway ... busstop 200 meters away). Whilst we appreciate the interest shown from abroad, it is just not feasable for the tasks at hand. Given the nature of work, and that we cannot offer a full time position, we would expect a student or an apprentice, who would like to have some additional challenges and earn some extra money. However, it could also be someone who's in between jobs. If you are interested, or know of someone who could be interested, please send me a short description of your background and your motivation and general situation as well as contact details, and we will revert asap. I will be looking forward to hearing from you on the following e-mail address: mba (at) corpconsult (dot) info or as a reply to this post. Best regards Mogens Berg Andersen MBA Consulting GmbH -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/58eea990-7115-4cdd-ab14-fd8e1e4bc3ac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] after update no VM 'starts' apps anymore.
On Wednesday, 7 February 2018 08:17:11 CET Andrew David Wong wrote: > Are you using the `-a` option? > > qvm-run -a > > This starts the VM if it's powered off, then runs the command in it. > Working fine for me on 3.2. As I wrote, qvm-start works fine, the VM is active and working. You just can t actually “run” anything on it. The reasons seems to be that there is some magic thing that starts when you log into xfce4, and only xfce4. See the screenshot attached elsewhere in this thread of qubes manager dying on startup due to the same issue. Tested on Rc4. -- Tom Zander Blog: https://zander.github.io Vlog: https://vimeo.com/channels/tomscryptochannel -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5810037.nmPg43q2Ws%40strawberry. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Install on Dell XPS 13 (9350)
On Wed, February 7, 2018 9:03 am, Davit Barbakadze wrote: > Sorry, but what's PV mode? > > > On Sunday, February 4, 2018 at 7:49:19 AM UTC+4, xxx@gmail.com wrote: > >> Yes I stil have the permissive mode on 3a:00.0 PV is ParaVirtual mode. It's OK for testing, but in R4.0 you want to use PVH mode for everything except for qubes with an attached PCI device need HVM mode. PS I have a document update in progress explaining how to assign devices in permissive mode in R4.0. It's a different procedure than R3.2. See https://github.com/awokd/qubes-doc/blob/patch-15/configuration/assigning-devices.md/#pci-passthrough-issues for the working copy. The approved version of it should end up here eventually: https://www.qubes-os.org/doc/assigning-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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2653b7265a6ec0c38dd463a0055c3432.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] size difference between 4.9 and 4.14 kernels
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, Feb 06, 2018 at 11:04:41AM +, Holger Levsen wrote: > hi, > > on 3.2 I ran "sudo qubes-dom0-update" this morning, followed by "sudo > qubes-dom0-update --enablerepo=qubes-dom0-current-testing --action=upgrade > kernel-qubes-vm" > which then prompted me with this: > > Installing: > kernel x86_64 1000:4.14.13-3.pvops.qubes > qubes-dom0-cached46 M > kernel-qubes-vm x86_64 1000:4.14.13-3.pvops.qubes > qubes-dom0-cached62 M > Removing: > kernel x86_64 1000:4.9.35-20.pvops.qubes > @qubes-dom0-cached 179 M > kernel-qubes-vm x86_64 1000:4.9.35-20.pvops.qubes > @qubes-dom0-cached 206 M > > Is that really expected and correct that the new kernels are that much > smaller? I think this is just about estimation of used disk space - one package is already installed and rpm know how much disk space is really used, the other one have only some estimation in rpm metadata. RPM package sizes are very similar: 41M (4.9) vs 46M (4.14). - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlp6zn0ACgkQ24/THMrX 1yxppgf/eRkovw1Hjo/1buWrYDcLtakItPwUbJboYpxyU4bbMbpc6Kt4BGo3L7O1 1oC4JuNCb+SjobVR4mWBLgc0fZKvyqr77abFUWI4ejHAN+uxx0/SfqWJeiXBGc6F JAE73FEzxMDbF4TohPqfSu+Ej1sLHZ3L6BQwOUEJ997hWGekqBS1nwoqVPzR8UDh /Pd821jGTWLptGVwjuOj2CVr5hXhP+O/J5xoBjI5hq42swhE19hrFK2LzLZknwq6 u8Js9xODIxQjDHwxl3wsYSpATiF+pycV0W4/xXVZR2niEozxpdBtjqUs5iLjpPPq kijZOJQbpUa21g+wGzYwcoOBzGc/QA== =4a2H -END PGP SIGNATURE- -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20180207100133.GD12544%40mail-itl. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: template debian-9 no network (Q4r4) ?
Le mercredi 7 février 2018 10:24:40 UTC+2, ThierryIT a écrit : > Le mardi 6 février 2018 17:42:33 UTC+2, Connor Page a écrit : > > you probably ticked update over Tor option when installing. > > templates do not connect to network directly, they use an updates proxy. > > I' not sure it can be changed in GUI, but you can find the appropriate rpc > > policy in /etc/qubes-rpc > > alternatively you can temporarily set template vm's network provider, but > > that is considered less secure. > > Hi, > No I didn't ticked anything when I have installed this Template. > I don't know why is it running sys-whonix ... When checking the config of > this template, there is no sys-whonix is the config ... > As I said, even if using the same proxyVM and netVM than working VMs, I still > do not have access to internet ... > I will check the rpc policy. > Thx sys-whonix still run when I start the template ... Still don't know why. After having changer the default netVM for this template to sys-whonix and done a Whinixcheck I was able to update my template Why ? No clue. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/07685a26-96f6-45ae-899f-de837ea22b4a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Install on Dell XPS 13 (9350)
Sorry, but what's PV mode? On Sunday, February 4, 2018 at 7:49:19 AM UTC+4, xxx@gmail.com wrote: > Yes I stil have the permissive mode on 3a:00.0 > > No luck in HVM mode with the current-testing repo. > qubes-core-dom0 4.0.21 > vm kernel 4.14.13-3 > > > > > > Thanks for writing -- are you using permissive mode in combination with > > PV mode for sys-net? > > > > I've been relying on a usb wifi adapter, but will give this another > > shot. Previously, a developer kindly addressed this via issue #3476 > > > > https://github.com/QubesOS/qubes-issues/issues/3476 > > > > To correct this, try: > > > > sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing > > > > I'll test this and reply here once I have _rc4 running on this machine. > > > > -m0ssy -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d4d86005-3b7e-46aa-811a-15bb8e22cd8b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] GPU Passthrough Status - (Purely a meta-discussion, no specifics)
On Sunday, 17 December 2017 12:16:04 UTC, Tom Zander wrote: > On Saturday, 16 December 2017 03:25:46 CET Yuraeitha wrote: > > Initially, this is all the reasons I can think of for wanting V-GPU. > ... > > - Extending a single Qubes machine around the house or company, using > > multiple of screens, keyboards/mouses or other thinkable means. > > This sounds inherently unsafe. > Not sure what your usecase is, but there has to be a better way than > allowing a multitude of foreign, not-directly-connected hardware from > accessing various very security sensitive channels. > > ... > > - Cryptocoin miners who wish to utilize a single machine > > for all round purposes. > > To build a proper crypto-mining rig based on GPUs, you would not run an OS > on the machine. It literally drains money out of your system to use it on > the same hardware as you main desktop. > If you install 8 GPUs on a mainboard, you have to realize that the mainboard > ends up costing a fraction of the total. > Reusing it for non-mining purposes (while mining) just doesn't make any > sense. Both from an economics as well as a security point of view. I think it makes sense it you are on a budget. But you do not need GPU path-through, you only need CUDA interface, so I believe it is already feasible today. Use the integrated GPU for Dom0 and all your work VMs. Have a MiningVM with all the other GPU attached to it. However ,you probably want a kvm switch to distance yourself from your new radiator and noise generator. > > -- > Tom Zander > Blog: https://zander.github.io > Vlog: https://vimeo.com/channels/tomscryptochannel -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/13948b3c-f21f-45ae-ae87-20593c6d424e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: template debian-9 no network (Q4r4) ?
Le mardi 6 février 2018 17:42:33 UTC+2, Connor Page a écrit : > you probably ticked update over Tor option when installing. > templates do not connect to network directly, they use an updates proxy. > I' not sure it can be changed in GUI, but you can find the appropriate rpc > policy in /etc/qubes-rpc > alternatively you can temporarily set template vm's network provider, but > that is considered less secure. Hi, No I didn't ticked anything when I have installed this Template. I don't know why is it running sys-whonix ... When checking the config of this template, there is no sys-whonix is the config ... As I said, even if using the same proxyVM and netVM than working VMs, I still do not have access to internet ... I will check the rpc policy. Thx -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/41904485-427e-4f76-b62c-63b49781aad5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] reboot sys-net
> I remember some issues with reattaching in the past, but recently, the > qvm-shutdown --wait --force sys-net && qvm-start sys-net seems to be working. This sounded even more interesting than the script. But: It does not work in my Q4rc4 install. last experience of this type was with sys-whonix and anon-whonix. The latter running, the former did not power off (even with --force); after some wait I kill it, but it won't reboot: on boot it spills out "network device with MAC ... already exists" before dying. I had to power off anon-whonix, then restart sys-whonix. Same thing happen with the sys-net - sys-firewall - sys-whonix - anon-whonix chain. I need to power off all of them to get sys-net to rebbot, which is, frankly, annoying. So finally a script is a good idea, even if Ilpo's did not work out of the box in my install (may be a Q3.2 - Q4 issue). Best, Bernhard -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/688e1318-b7e4-f7e0-0b8a-b73b67a5c6b4%40web.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] 4.0-rc4 install on Lenovo G505S - no network
On Wed, February 7, 2018 3:28 am, dbr287 wrote: > I've installed rc4 on G505S with Coreboot (legacy bios). Installation > went ok (found iommu and interrupt remapping just fine). > > On 1st (gui) boot, I've tried all the combinations selecting 1) create > ServiceVMs, AppVMs, 2) only ServiceVMs, 3) only configure templates,... > but none works. It always hangs at Configuring 1st template (usually > debian-9). You probably need to manually add this patch https://review.coreboot.org/#/c/coreboot/+/22843/ to your coreboot image. Also, disable XHCI (two options right next to each other in menuconfig.) If it continues to hang on sys-net creation, try pulling the wireless card before installing Qubes. It will still create a sys-net qube containing the onboard ethernet, but then you can add the wireless card back and troubleshoot on a full system. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a62c46c15e0e7fe007c564c5edbfdf40.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
