Re: [qubes-users] Re: Why is there no qubes manager in V4.0?
On Wednesday, 1 November 2017 12:23:22 UTC+8, Desobediente wrote: > Just felt like I have to say that I would love to stop everything I'm doing > in > my life to write a proper Qubes Manager for 4. > > But I don't see that happening. It sounds trivial at first, but it requires a > lot of testing and it will have bugs as the current one does. I agree. It wouldn't take long to put something together that does the basic stuff, but to make it as feature complete as the Qubes Manager in 3.2 let alone implement all the cool features we all want would take more time than one might think. -- 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/d67165f8-cb7f-44e6-84dd-c5daff025632%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3.2 HVMs not working - screen stays black ??
Tails 3.2 working for me in a standalone HVM. It's very weird to have Tails as an AppVM with network routed through Whonix inside Qubes, though. Feels like I'm trying to find the ultimate question for 42 or something. -- iuri.neocities.org -- 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/CAF0bz4QS1GOKYGtX6Rpxb-H4DfLEA9EtrRggKK0SooEdbiVg6A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Why is there no qubes manager in V4.0?
Just felt like I have to say that I would love to stop everything I'm doing in my life to write a proper Qubes Manager for 4. But I don't see that happening. It sounds trivial at first, but it requires a lot of testing and it will have bugs as the current one does. On the other hand, the more people demanding, the more likely someone would at least start something. -- iuri.neocities.org -- 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/CAF0bz4QVuj0ZWBy-4vX4w0CbByrsd%3Dk8KKvi5ybUppa0ikttAQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Why is there no qubes manager in V4.0?
On Wednesday, 1 November 2017 11:32:58 UTC+8, Fun Zork wrote: > And not just that. If I'm being honest, it is also because it makes me feel > more like I am running a cool, unique, complicated OS. The qubes manager is > kind of Qubes' signature look. It's > > I agree that the UI for it is kind of meh in 3.2, but that's mostly a > graphical > issue IMO. Personally, I'd rather see 4.0 have a qubes manager > that is > functionally the same as in 3.2, but with a more modern look. Darker, new > icons. I agree with you, but at the same time it is very clear that the team are very resource-constrained. I'm sure they would love to implement a better replacement but there is only so much they can do in a day, and there are plenty of other issues that I'd rather see them work on. I have considered working on such a tool myself, but it's a lot of work and I have other projects I need to work on as well. -- 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/df99834b-e47e-4e32-99c8-23b6cd592359%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Why is there no qubes manager in V4.0?
Remember when Microsoft got rid of the start menu for a lot of reasons that sounded really compelling and revolutionary in PowerPoints presentations and articles, but just annoyed users? Same sort of deal I think. I like seeing the status of all my VMs, not just when I go and seek that information out, but all the time. It just gives me more insight into what my computer is up to. It makes me feel more confident that it isn't doing anything it isn't supposed to be doing. It reminds me to be conscious of which qube I am in when I'm performing different tasks. I like having a sense that I am more aware of what my computer is up to, like I notice that sys-net's CPU bumped up a bit and maybe that alerts me to an issue, or I notice that my personal VM is taking longer to shut down than it used to, and maybe there is an issue there. And not just that. If I'm being honest, it is also because it makes me feel more like I am running a cool, unique, complicated OS. The qubes manager is kind of Qubes' signature look. It's I agree that the UI for it is kind of meh in 3.2, but that's mostly a graphical issue IMO. Personally, I'd rather see 4.0 have a qubes manager that is functionally the same as in 3.2, but with a more modern look. Darker, new icons. -- 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/ef1f6a51-c8e6-4d87-8842-ccb2df522a3b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3.2 HVMs not working - screen stays black ??
Apart from the obligatory "that's not how you should use Tails", I can say that if I recall correctly, Tails used to have some sort of blocking or a warning when you attempt to run it in a virtual environment. I have fedora 24 on qubes 3.2, I will attempt to reproduce this here. -- iuri.neocities.org -- 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/CAF0bz4RpJ0SqS0Ox4z%2B4OnkzRe1HPqeRsZTbh_koZMqXmyf72Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 3.2 HVMs not working - screen stays black ??
Hi, I have some issues with Qubes Hardware VMs. I can't get them to work, even though everything else works fine. I tried the following ISOs / linux distributions: - Fedora 26 LXDE - Tails 3.2 Each time the HVM window opens but then the screen stays black and the boot starts to hang. I haven't been able to login to any HVM yet. Do you have any idea how I can solve this issue ? Any help is highly appreciated ;) PS: I did everything exactly the same way as stated in the docs: 1. $ create-qvm tails --hvm --label red 2. $ start-qvm tails --cdrom=personal:/home/marek/Desktop/Tails.iso Hardware: - Gigabyte GA-Z97X-UD5H - OnBoard Graphics - Intel i7-4770K - 32GB RAM -- 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/1f83e673-a957-4c45-a441-ea828ac82ea5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Unable to Attach ISO to Windows HVM
I created a Windows 10 HVM on Qubes (I know Windows 10 isn’t supported, but I know some people succeeded with it, so I’m trying it), and when I attached the ISO to the HVM, I get an error message: “libvirt.libvirtError: internal error: libxenlight failed to create new domain ‘windows-10’”. I don’t believe that there is anything wrong with the ISO, because it was a download directly from Microsoft; and I don’t believe that I messed up the command, because it worked previously. It booted up a picture of the Windows logo and then suddenly crashed. One of the solutions I found online was to use “systemctl start xendriverdomain”, but I don’t seem to have this service and I don’t know how to install it. -- 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/40d0e01d-4d14-4e10-a2f0-85a4e64fc66f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
AW: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start
Hello, Honestly what is bothering me a bit, is that there seem to be lots of problems with Qubes 4-rc2, which is ok, as it is a testing release - bit I'd like to see more feedback from the Qubes Dev's, so that we can find out what is the Root cause. Isn't this how a test release should work? We (normal) users are testing, so that developers can get a qualified feedback what needs to be fixed. Or am I missing something and there is some action on the developer mailing list? [799] -- 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/cN0eVl_x2fCMyjKkbEij_kCRXH6Ba5tuKBWwe93gCxehDdXW17GSVDgmVxqhGk6z1bEVnNCEvjBgW8d3P_4k8Uy9IO0QF1WR1RoCkbBTdbQ%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start
Em terça-feira, 31 de outubro de 2017 11:10:22 UTC-2, Roy Bernat escreveu: > On Tuesday, 31 October 2017 14:56:46 UTC+2, Roy Bernat wrote: > > On Tuesday, 31 October 2017 14:52:10 UTC+2, Roy Bernat wrote: > > > On Wednesday, 25 October 2017 20:26:51 UTC+3, [799] wrote: > > > > Hello, > > > > > > > > As at least one other Qubes user has the same problem, that VMs won't > > > > start, I'll add this as special topic. > > > > > > > > I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't > > > > boot the VMs. > > > > This includes sys-net, sys-firewall, but also others. > > > > > > > > I tried to check the logs but I don't get any valuable information. > > > > See screenshot. > > > > > > > > I started the following command in dom0: > > > > > > > > watch -n 1 xl list > > > > > > > > When I try to launch a VM I can see that the VMs appears in the xl list > > > > output, but the State is -- and the Time(s) is 0.0. > > > > After ~30sec the start is aborted with error message: Cannot execute > > > > qrexec-daemon. > > > > > > > > Questions: > > > > 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230? > > > > 2) is someone additionaly running Coreboot? > > > > 3) I am running the Qubes Installation with the default settings, any > > > > options to tweak on the Grub command line > > > > > > > > [799] > > > > > > > > > > > > > > > > > > > > > > > > Gesendet von ProtonMail mobile > > > > > > not worked for me . > > > > > > until now i dont know what cause this issue ? > > > > > > this is a huge bug the cause us not to work . for me 3.2 dont work so i > > > have only one option . By the way rc01 worked ok > > > > It seems that asomething with the sys-net causing the sys-firewall not > > working > > Someone of the developer know this issue ? and maybe he will have a > workaround until fix . > R I am not a developer. Sorry if I get wrong you problem. Are you sure it is not a iommu problem? Did you tested (qubes-hcl-report on dom0 terminal)? Mine has no iommu and is working with PV until next oct-10, when arrives my 990fx chipset motherboard to my old AM3 cpu. See https://groups.google.com/forum/#!searchin/qubes-users/iommu/qubes-users/QZIWyQVFYp4/vfeC58rhAgAJ -- 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/0044c7d0-a7dd-4d9b-82cf-4e0c3f12a6ae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Ledger Nano S works for me with Qubes OS R3.2 and R4 - now documented
Experimented with this. Documented it. Feel free to test and contribute to the instructions. https://www.whonix.org/wiki/Ledger_Hardware_Wallet -- 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/e852ff07-1456-547f-11da-210a93e11203%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Rc2 hangs on install -- Dell Inspiron i5759-8835SLV
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, Oct 30, 2017 at 04:29:55PM -0700, billol...@gmail.com wrote: > Don't know what this means, but I downloaded the new 4.0 RC2, put it on a > flash drive, and tried to install it on my new Dell laptop. It froze early > on, with the messages: > > > Firmware Bug: TSC_DEADLINE disabled due to errate. Please update microcode > to version 0xb2 (or later) This is about CPU bug, fixable with newer microcode. In most cases it is applied by BIOS early during system startup. In short: update your BIOS. > 2.035271 Could not get size 0x8000e > > Anyway, just a data point. > > I tried the "troubleshooting" option. It froze again, but I didn't write > down the step. I believe it was after discovering/creating /dev/sdd > > Good luck! I'll try again once the final version comes out. I'll monitor > this if someone has an idea of how to get beyond this, but it's just an early > hang for me. > > billo > - -- 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- Version: GnuPG v2 iQEcBAEBCAAGBQJZ9wxuAAoJENuP0xzK19csB3AH/0kSEWjZDt+zbe4It7bkHI4F QKIkUBc/XAThel8d+VQiH67XFxYw6g7f1CquRCQ1EGIj+dl9L2pwauWFEOeDs6q1 YgZAN6CSZMQ3aBqiblHiOtuIn+9+7BsAxTydhAkD+Bf6qHyKpcf0JJuafRK3bMNn IVByv5VOKiUV0KHOrM5wlXBkZe0JDSnJGHfISA1HOeoBBh4yOegX1pj6VVw3aLv7 xx4hMQFaUbFY6r8eqoj0k9sGuGC7RqhGx4hwL+9ZzqX2/L9jLzs09Z6Ulln+Txb5 I9wvmpRz97mFjbm0diGk0tVOusEvEZmiAXGgIf0tgXh0njNQ8ewdFDZE3S7XZQU= =IaqP -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/20171031213040.GB4535%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Recover broken bootloader
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, Oct 30, 2017 at 08:23:39PM -0700, loke...@gmail.com wrote: > My laptop has started to fail to boot my 4.0rc2 installation. This started > after doing a qubes-dom0-update, but I'm pretty sure that I had rebooted the > machine successfully at least once since then. > > The computer has now gone into a bootloop, and fails to display the GRUB > screen. I can only assume that the bootloader is crashing. However, nothing > is displayed on the screen. > > Is there a recommended procedure to reinstall GRUB when booting from the > installation media? Standard things should work: 1. Boot from installation media (rescue mode) 2. Agree to mount the system 3. Chroot into /mnt/sysimage (chroot /mnt/sysimage) 4. If /dev is empty, mount it with: mount -t devtmpfs none /dev 5. Execute: grub2-install /dev/sda (or other disk, depending on your configuration) Then, exit from chroot and reboot the system. - -- 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- Version: GnuPG v2 iQEcBAEBCAAGBQJZ9wv1AAoJENuP0xzK19csWWAH/j190OmGcCr9LcFy5kpm0pZH vvfIGrSm8MsydbhnRv5tCuuhCmBpLD71siC5fxcI63E/bon1VDIZFd7Glc0I6Z9B +Uvwi1pMtc+i38ixfa9UUDmhenjQ5zZRAxNQwvCDVsNxFZBiAdWvk1FdtSqKsEU9 SGKDxO81HgsL84JD0JzzCn4iCFBzcwTEJrnJHmrb+7KteevynFNMAGRIcoXXCNhH cmuTB6QoRC5b5Kvx5NizKjUMfPehmfdik0FQVy1Mi3O9BwIgweNnUDEQ7mbjH6JR seKuH2VYa/7DjgAv05nmjv8DjalDlhbimc5CkKlLwtac8NmFQUdeiM88no2lpaE= =5yqg -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/20171031212839.GA4535%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0rc2 install on corebooted Lenovo G505s (AMD)
I also experienced problems with item 2. The progress meter would simply stop and the system would appear to be locked up. I was installing RC2 to a USB stick. Amazingly, the system was actually making progress despite what the meter was reporting. By coincidence, my attention was diverted and I had to walk away from the system. When I returned, it was ready for the next installation step. -- 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/71e45a21-b3bc-467d-9cec-351592582c4e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start
I had this problem as well. However, the problem vanished when I adjusted the qrexec_timeout setting to 120 via qvm-prefs for the desired VMs. This kind of makes sense, since I'm doing my RC2 testing from a usb stick (color me cautious). -- 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/227ac3ab-6c00-40ae-a2e0-e82f2e5bc35f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start
On Wednesday, October 25, 2017 at 11:26:51 AM UTC-6, [799] wrote: > Hello, > > As at least one other Qubes user has the same problem, that VMs won't start, > I'll add this as special topic. > > I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot > the VMs. > This includes sys-net, sys-firewall, but also others. > > I tried to check the logs but I don't get any valuable information. > See screenshot. > > I started the following command in dom0: > > watch -n 1 xl list > > When I try to launch a VM I can see that the VMs appears in the xl list > output, but the State is -- and the Time(s) is 0.0. > After ~30sec the start is aborted with error message: Cannot execute > qrexec-daemon. > > Questions: > 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230? > 2) is someone additionaly running Coreboot? > 3) I am running the Qubes Installation with the default settings, any options > to tweak on the Grub command line > > [799] > > > For what it's worth, I'm having the same issues on a stock-BIOS X220. Sometimes a random reboot will give me both sys-net and sys-firewall, but the other two never come up, it's very problematic and very finnicky. If you do find a solution/workaround, please let me know. -- 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/2f4e5352-f832-4508-936a-88e292c9d048%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start
Not working Found that with debug it’s starting but then the appvm not... -- 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/6ecb46ca-9cf7-4c4d-802a-2d0ec36573e0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start
On Tuesday, October 31, 2017 at 1:56:46 PM UTC+1, Roy Bernat wrote: > On Tuesday, 31 October 2017 14:52:10 UTC+2, Roy Bernat wrote: > > On Wednesday, 25 October 2017 20:26:51 UTC+3, [799] wrote: > > > Hello, > > > > > > As at least one other Qubes user has the same problem, that VMs won't > > > start, I'll add this as special topic. > > > > > > I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't > > > boot the VMs. > > > This includes sys-net, sys-firewall, but also others. > > > > > > I tried to check the logs but I don't get any valuable information. > > > See screenshot. > > > > > > I started the following command in dom0: > > > > > > watch -n 1 xl list > > > > > > When I try to launch a VM I can see that the VMs appears in the xl list > > > output, but the State is -- and the Time(s) is 0.0. > > > After ~30sec the start is aborted with error message: Cannot execute > > > qrexec-daemon. > > > > > > Questions: > > > 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230? > > > 2) is someone additionaly running Coreboot? > > > 3) I am running the Qubes Installation with the default settings, any > > > options to tweak on the Grub command line > > > > > > [799] > > > > > > > > > > > > > > > > > > Gesendet von ProtonMail mobile > > > > not worked for me . > > > > until now i dont know what cause this issue ? > > > > this is a huge bug the cause us not to work . for me 3.2 dont work so i > > have only one option . By the way rc01 worked ok > > It seems that asomething with the sys-net causing the sys-firewall not > working try changing the sys-net template to debian? -- 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/83a385b5-bd13-4ea7-8054-736e5887da22%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: AW: Re: AW: [qubes-users] Reinstalled Qubes 3.2 -> /grub2/i386-pc/normal.mod not found
On Mon, October 30, 2017 20:57, '[799]' via qubes-users wrote: > Hello, > >> Try repeating the Qubes install but when you >> get to the custom partitioning step, make sure >> to specify the appropriate partitions for boot >> and /. You will probably want to re-enable the >> boot flag on your hda1 partition as well > > Thank you for the feedback, I have meanwhile installed a fresh > installation of Fedora 26 and could boot up fine, I reinstalled Qubes 3.2 > afterwards and got the same result. > > Can't boot, tried to setup the partitions manually and made sure that the > Boot partition is installed correctly. > I also set the Boot flag to the first partition. > It doesn't matter ... Can't boot. > Totally annoyed that I tried Qubes 4 which can't boot any VMs and that I > can't go back to Qubes 3.2 without deleting all partitions including my > windows setup. > > I think I'll try to reboot into windows when Fedora is installed, make a > backup of my windows partition and then reinstall Qubes from scratch. > Have invested so much time already in this Qubes upgrade/downgrade topic > that I am done for the year. Remembered later I encountered this issue on a fresh 3.2 install, maybe you are hitting it too. This does not apply if you are doing UEFI boot, only GRUB. Found a fix in https://groups.google.com/forum/?_escaped_fragment_=msg/qubes-users/TS1zfKZ7q8w/JQFkVF4xBgAJ#!msg/qubes-users/TS1zfKZ7q8w/JQFkVF4xBgAJ: "after a Clean Install of Qubes R3.2, it fails to boot - stuck at "Booting from hard drive:" SeaBIOS message with blinking "_" character, cant reach GRUB Boot Menu because MBR (or GRUB) is corrupted out-of-the-box. Luckily it can be fixed: boot from your Qubes R3.2 installation media, go to "Troubleshooting -> Rescue a Qubes system", after booting to anaconda installer please choose "1) Continue" (and enter your Qubes partition password if you chose to encrypt it during install), then enter "chroot /mnt/sysimage" - and, finally, "grub2-install /dev/sdX" (where X is a letter for your hard drive with Qubes, in my case it was sda: "grub2-install /dev/sda")" -- 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/21b3833dba668065096445d46d5961f6%40elude.in. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start
On Tuesday, 31 October 2017 14:56:46 UTC+2, Roy Bernat wrote: > On Tuesday, 31 October 2017 14:52:10 UTC+2, Roy Bernat wrote: > > On Wednesday, 25 October 2017 20:26:51 UTC+3, [799] wrote: > > > Hello, > > > > > > As at least one other Qubes user has the same problem, that VMs won't > > > start, I'll add this as special topic. > > > > > > I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't > > > boot the VMs. > > > This includes sys-net, sys-firewall, but also others. > > > > > > I tried to check the logs but I don't get any valuable information. > > > See screenshot. > > > > > > I started the following command in dom0: > > > > > > watch -n 1 xl list > > > > > > When I try to launch a VM I can see that the VMs appears in the xl list > > > output, but the State is -- and the Time(s) is 0.0. > > > After ~30sec the start is aborted with error message: Cannot execute > > > qrexec-daemon. > > > > > > Questions: > > > 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230? > > > 2) is someone additionaly running Coreboot? > > > 3) I am running the Qubes Installation with the default settings, any > > > options to tweak on the Grub command line > > > > > > [799] > > > > > > > > > > > > > > > > > > Gesendet von ProtonMail mobile > > > > not worked for me . > > > > until now i dont know what cause this issue ? > > > > this is a huge bug the cause us not to work . for me 3.2 dont work so i > > have only one option . By the way rc01 worked ok > > It seems that asomething with the sys-net causing the sys-firewall not > working Someone of the developer know this issue ? and maybe he will have a workaround until fix . R -- 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/5acb43ad-f051-4060-a27a-4e942c6c3913%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start
On Tuesday, 31 October 2017 14:52:10 UTC+2, Roy Bernat wrote: > On Wednesday, 25 October 2017 20:26:51 UTC+3, [799] wrote: > > Hello, > > > > As at least one other Qubes user has the same problem, that VMs won't > > start, I'll add this as special topic. > > > > I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot > > the VMs. > > This includes sys-net, sys-firewall, but also others. > > > > I tried to check the logs but I don't get any valuable information. > > See screenshot. > > > > I started the following command in dom0: > > > > watch -n 1 xl list > > > > When I try to launch a VM I can see that the VMs appears in the xl list > > output, but the State is -- and the Time(s) is 0.0. > > After ~30sec the start is aborted with error message: Cannot execute > > qrexec-daemon. > > > > Questions: > > 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230? > > 2) is someone additionaly running Coreboot? > > 3) I am running the Qubes Installation with the default settings, any > > options to tweak on the Grub command line > > > > [799] > > > > > > > > > > > > Gesendet von ProtonMail mobile > > not worked for me . > > until now i dont know what cause this issue ? > > this is a huge bug the cause us not to work . for me 3.2 dont work so i have > only one option . By the way rc01 worked ok It seems that asomething with the sys-net causing the sys-firewall not working -- 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/fe760441-9082-42d9-bdbf-3843f875b495%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start
On Wednesday, 25 October 2017 20:26:51 UTC+3, [799] wrote: > Hello, > > As at least one other Qubes user has the same problem, that VMs won't start, > I'll add this as special topic. > > I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot > the VMs. > This includes sys-net, sys-firewall, but also others. > > I tried to check the logs but I don't get any valuable information. > See screenshot. > > I started the following command in dom0: > > watch -n 1 xl list > > When I try to launch a VM I can see that the VMs appears in the xl list > output, but the State is -- and the Time(s) is 0.0. > After ~30sec the start is aborted with error message: Cannot execute > qrexec-daemon. > > Questions: > 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230? > 2) is someone additionaly running Coreboot? > 3) I am running the Qubes Installation with the default settings, any options > to tweak on the Grub command line > > [799] > > > > > > Gesendet von ProtonMail mobile not worked for me . until now i dont know what cause this issue ? this is a huge bug the cause us not to work . for me 3.2 dont work so i have only one option . By the way rc01 worked ok -- 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/4db91507-6b35-4f04-b378-f4adf0e50495%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start
On 10/31/17 05:21, RSS wrote: I see I am not alone here. Having the information on which laptops Qubes 4 "should" run or even more where it is running (Dev Users?) would help. The HCL https://www.qubes-os.org/hcl/ does not help me, as it has no information if 4.x is ok for the X230. It looks to me like a bigger problem, not necessarily device specific: https://github.com/QubesOS/qubes-issues/issues/3221 Remember this is not a public release, this is RC2. Release CANDIDATE 2. That means it is a version meant for TESTING, not necessarily ready for anything more. TEST_FAILED As mentioned before I am running Coreboot, should I go back to stock ROM? In fact I have an x230 without Coreboot, and I too cannot reliably even get sys-net to run, let alone sys-firewall, which I do not think I have seen running once. FYI the internal ethernet controller seems to give RC2 sys-net big problems. I had to remove it from my sys-net Devices list, so there is only wifi. So my sys-net will usually start, but not the other VMs following it. Personally I am going to close the lid and wait for the next release. (Unless anyone would like to collect some debug information from me.) -- 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/5655a465-7622-9a2b-11a1-e19704e144be%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] qubes 4.0 whonix updates, which netvm? none or sys-whonix?
the default netvm of the whonix-ws and gw templates is "none", but when you try to update them a pop up tells you to set it to sys-whonix. which is it? if it is sys-whonix, why not make that the default? does this work with qubes network filtering of templatevms? has that changed in 4.x? -- 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/e9569175-52b9-4e65-b778-47117aa1f904%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: best mini pc for qubes os
Just installed 4.0rc2 on an intel NUC7i5BNH. It comes with a special back plate for mounting. qubes installed with no issues. sound only works out of the headphone jack, but not the hdmi port. ethernet and wifi both work. youtube is good fullscreen at 1080p. no ps2 ports and only one usb controller, so no usbvm. dont use this if malicious usb devices are in your threat model. This is brand new hardware, so it may have trouble with qubes 3.2. if your going to also run windows on this, i suggest putting qubes on the external one. that way, when you boot windows, it wont have a chance to mess with your qubes drive. or even better, swapping the drives so you dont risk accidentally booting windows with your qubes disk still in. If your photoshop and illustrator files are not too demanding, you can run windows in qubes and save yourself that effort. ive never tried it, only seen a coworker do it. -- 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/9021a036-b0b3-46a7-a3c1-9f87316faf02%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start
I see I am not alone here. > Having the information on which laptops Qubes 4 "should" run or even > more where it is running (Dev Users?) would help. The HCL > https://www.qubes-os.org/hcl/ does not help me, as it has no > information if 4.x is ok for the X230. It looks to me like a bigger problem, not necessarily device specific: https://github.com/QubesOS/qubes-issues/issues/3221 Remember this is not a public release, this is RC2. Release CANDIDATE 2. That means it is a version meant for TESTING, not necessarily ready for anything more. TEST_FAILED > As mentioned before I am running Coreboot, should I go back to stock > ROM? In fact I have an x230 without Coreboot, and I too cannot reliably even get sys-net to run, let alone sys-firewall, which I do not think I have seen running once. Personally I am going to close the lid and wait for the next release. (Unless anyone would like to collect some debug information from me.) -- 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/20171031172103.7d8826c0%40x220i. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 3.2(4) and Nvidia mobile 9xx m bad idea? Have anyone success with installation video drivers?
Hi, i'am trying this guide, but there is no success. Xen does not support mobile laptop nvidia videocards? https://github.com/QubesOS/qubes-issues/issues/2526 https://groups.google.com/forum/#!topic/qubes-users/v26zXkiNElg/discussion https://www.qubes-os.org/doc/install-nvidia-driver/ -- 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/78c31b69-a3dc-48ac-87d8-12294b190b02%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Properly setup a qube dns cache server
I'm already in the process of implementing this feauture (method A) in R4.0.
> dom0 doesn't store any DNS settings. Each VM forwards packets to the
> next upstream VM and the DNS decision is made at your netvm resolv.conf.
> Dynamic firewalls (iptables in 3.2, netfilter or so in 4.0) managed by
> the dom0 qvm-firewall in your proxsy & firewall VMs ensure only allowed
> traffic is going through. DNS uses dnat rules. Dom0 uses your firewall
> VM to pull updates.
I'm aware of the Qubes networking mechanisms.
What I'm trying to achieve is the following:
1) New fields in 'Qubes Global Settings' menu, under 'System defaults' (Dom0)
that let the user choose the default primary and secondary DNS (now
'10.139.1.1' and '10.139.1.2').
How this will be implemented?
Dom0 will inform the first NetVM backends ('sys-firewall', 'sys-net' or a
VpnVM) of the change though a rpc service and this will trigger
`qubes-dnat-to-ns` which will procede to update the (NAT) iptables.
-> All the DNS requests destinated to '10.139.1.1' and '10.139.1.2' DNAT to
the new DNS backend specified by the user <-
This method doesn't require any changes to the Templates or the AppVMs, but
only to install a rpc service and a custom `qubes-dnat-to-ns` script in the VMs
that provide network (ProxyVMs and NetVMs).
2) New fields in 'VM Settings' menu (Dom0) that let the user choose the primary
and secondary DNS for each VM, if the machine has network.
How this will be implemented?
Dom0 will inform the NetVM backend to which the VM is attached and the (NAT)
iptables will be modified to DNAT all the DNS requests from a the specific VM
vif interface (-i vifX.0) to the new addresses provided.
Again, no changes are required to the Templates or the AppVMs, but only to the
VMs that provide network (ProxyVMs and NetVMs).
*
ISSUES:
1) I solved the first issue and I discovered how to retrieve vif names from xen
database,
2) I still don't know how to make all VMs that provide network launch a script
when a new vif interface came up.
As I said before, I've found the this file
'/etc/udev/rules.d/99-qubes-network.rules' that I believed was the solution,
but it seem not to work at all,
3) My code still rely on files, because the Qubes API and Qubesadmin API has
confused me a lot.
I need to add:
- the attributes 'default_primary_dns' and 'default_secondary_dns' to
'qubesadmin.app.QubesBase' and
- the properties 'primary_dns' and 'secondary_dns' to the base Class that
represent a VM object.
I don't know if I have to modify 'Qubes' or 'Qubesadmin' and if this is enough
for the `qubesd` calls or if it's not possible to add new properties at all.
I really need help from the developers, expecially for the point n.3.
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/7a66a147-8348-4eeb-98f7-bb4b2438a7e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
