Re: [qubes-users] Installation freezes at storaged.x86_x64
Check the integrity of the QubesOS installation ISO, it could be corrupted. If it's OK try writing it again to your USB disk. Original Message On Dec 3, 2018, 12:24 PM, OV_Ly wrote: > Hello everyone. > > I am trying to install Qubes, but everytime it stops on "storaged.x84_x64 > (748/1018)" I can move mouse, but thats all. > > I am booting in Legacy from USB disk. Installing to another usb disk (i want > to test Qubes before i overwrite my entirely system.) > > I have HP Pavilion Power 17 ab301-nc. > 8 GB ram DDR4 > i5 7.gen > nVidia GTX 1050 > > Previously i've got problems with nVivida drivers (Tails, Kali), so i've > tried Nvidia troubleshooting, but i am not shure if it's the problem. > > Can u help 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/1ee50756-76f3-405a-9b16-709a80a5b3b0%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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/8s-jkmg2hEbJHihlajccvODV3aTsYiXnZWhaYM2bAuiWPLZSfwEi9UOxMV5eC-QyMnNJe5AsBfYsKtwrmkZkXg%3D%3D%40fidelramos.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: [qubes-devel] QSB #46: APT update mechanism vulnerability
‐‐‐ Original Message ‐‐‐ On Wednesday, January 23, 2019 9:52 PM, Chris Laprise wrote: > On 01/23/2019 12:05 PM, Marek Marczykowski-Górecki wrote: > > > Patching > > > > = > > > > If you are a Qubes user, you should remove all APT-based (including > > Debian and Whonix) TemplateVMs and StandaloneVMs, then install fresh > > ones. You can do this by performing the following steps on each such > > TemplateVM: > > A shortened update procedure for debian-9: > > 1. If your "debian-9" template is customized or contains data, you may > wish to back it up with qvm-clone first... > > [dom0]$ qvm-clone debian-9 d9-backup > > 2. Run the upgrade command... > > [dom0]$ sudo qubes-dom0-update qubes-template-debian-9 \ > --enablerepo=qubes*testing --action=upgrade > > This will display package info as it begins downloading. The package > version-date should begin with "4.0.1-20190123" or later. > > 3. Shutdown all VMs so the upgrade can take effect... > > [dom0]$ qvm-shutdown --all --wait --timeout=30 > > This method also works with whonix-gw-14 and whonix-ws-14 templates. Also in case people don't know there is an easy procedure to store the list of installed packages from the old debian 9 template and reinstall the same packages in the fresh template: https://unix.stackexchange.com/questions/176134/installing-packages-by-importing-the-list-with-dpkg-set-selections/177187#177187 I reproduce the steps here for convenience: debian-9-old$ dpkg --get-selections > /tmp/dpkg_selections.txt debian-9-old$ qvm-copy-to-vm debian-9 /tmp/dpkg_selections.txt debian-9$ avail=`mktemp` debian-9$ apt-cache dumpavail > "$avail" debian-9$ dpkg --merge-avail "$avail" debian-9$ rm -f "$avail" debian-9$ sudo dpkg --set-selections < ~/QubesIncoming/debian-9-old/dpkg-selections.txt debian-9$ sudo apt-get dselect-upgrade That should do the trick. Of course check dpkg-selections.txt, it's a simple text file. Note that with this procedure the information of which packages have been installed manually and which automatically as a dependency is not kept. If you want to transfer this information use this procedure: debian-9-old$ apt-mark showmanual > pkgs_manual.lst debian-9-old$ apt-mark showauto > pkgs_auto.lst debian-9-old$ qvm-copy-to-vm debian-9 pkgs_auto.lst pkgs_manual.lst debian-9$ sudo apt-mark manual $(cat QubesIncoming/debian-9-old/pkgs_manual.lst) debian-9$ sudo apt-mark auto $(cat QubesIncoming/debian-9-old/pkgs_auto.lst) https://askubuntu.com/questions/101931/restoring-all-data-and-dependencies-from-dpkg-set-selections/108760#108760 Hope that's useful. Fidel Ramos PGP 7F07 1B7C 479F EDD1 https://www.fidelramos.net -- 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/DM9_q5vgod4jYvlICr67Wg1SpGKDv2BNytlGZBHx2Tmd6J6w9DmZ2s__jTMhGtfAHvjigwMnaFYKLLhkEQHliA%3D%3D%40fidelramos.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: How can I set up wireless connection in Qubes 4.0
On 2/20/19 6:39 PM, wlmini...@gmail.com wrote: > On Wednesday, February 20, 2019 at 10:36:28 AM UTC-8, wlmi...@gmail.com wrote: >> Hi. >> I am trying to get wireless connection setup using Alfa AWUS036H but I don't >> know how to do it. >> Do I have to install in sys-net vm? Where can I start? > > It is detected in dom0. > When I run lsusb in dom0 console. > It shows > Realtek Semiconductor Corp. RTL8187 Wireless Adapter. > But light in alfa adapter doesn't blink. The device should have been assigned automatically to sys-net, could you check if that's the case? Run "qvm-pci list sys-net" in dom0. -- Fidel Ramos PGP 7F07 1B7C 479F EDD1 -- 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/Ajan6bKicUILfZu_6MJMS0xfAJZNZCM9I53FzzS5iYPqVQGL2macbbVy5kpw3NyEncqjgaViPVUE54Ptdi31e6uKaZuodKK-uM4ri2KgXho%3D%40fidelramos.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: How can I set up wireless connection in Qubes 4.0
On 2/20/19 7:05 PM, wlmini...@gmail.com wrote: > On Wednesday, February 20, 2019 at 10:54:03 AM UTC-8, Fidel Ramos wrote: >> On 2/20/19 6:39 PM, wlmini...@gmail.com wrote: >>> On Wednesday, February 20, 2019 at 10:36:28 AM UTC-8, wlmi...@gmail.com >>> wrote: >>>> Hi. >>>> I am trying to get wireless connection setup using Alfa AWUS036H but I >>>> don't know how to do it. >>>> Do I have to install in sys-net vm? Where can I start? >>> >>> It is detected in dom0. >>> When I run lsusb in dom0 console. >>> It shows >>> Realtek Semiconductor Corp. RTL8187 Wireless Adapter. >>> But light in alfa adapter doesn't blink. >> >> The device should have been assigned automatically to sys-net, could you >> check if that's the case? Run "qvm-pci list sys-net" in dom0. >> >> -- >> Fidel Ramos >> PGP 7F07 1B7C 479F EDD1 > > Thanks I checked. > But it only shows Ethernet Controller. Try using qvm-pci list to find the Qubes device id for the wireless adapter and then qvm-pci attach to assign it to sys-net. -- Fidel Ramos PGP 7F07 1B7C 479F EDD1 -- 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/qDfWom0_lIerzi7F0C1DlZoHV-Ray3TfjaKswfvNBpvTvcySqehtOkcb940jP2k_apqL3GUOannYQh2H4ldLrlp1S9PVOMz4mN1q_XCP7N8%3D%40fidelramos.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: system doesn't boot after update
‐‐‐ Original Message ‐‐‐ On Monday, October 29, 2018 4:39 AM, wrote: > Me too, I did qvm-dom0-update yesterday and when it tried to re-boot it got > in a boot loop, and I'll re-type the messages here: > > > > Xen 4.8.4 (c/s) EFI loader > Using configuration file 'xen.cfg' > vmlinux-4.14.74-1.pvops.qubes.x86_64: 0x495ae000-0x49b8db20 > initramfs-4.14.74-1.pvops.qubes.x86_64.img: > 0x49002000-0x495ae000 > 0x:0x01:0x00.0x0: ROM: 0x19400 bytes at 0x5302e018 > 0x:0x00:0x02.0x0: ROM: 0x1 bytes at 0x5300c018 > > -- > > [ 0.179397] ACPI Error: [\SB.PCIO.XHC_.?HUB.HS11] Namespace lookup failure > AE-NOT_FOUND (20170720/dswload-210) > [ 0.179406] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog > (20170720/psobject-252) > [ 0.179500] ACPI Exception: AE_NOT_FOUND, (SSDT:ProjSalt) while loading table > (20170728/tbxfload-220) > [ 0.188039] ACPI Error: 1 table load failures, 11 successful > (20170728/tbxflad-246) > [ 0.508657] Initramfs unpacking failed: read error > [ 2.762742] Kernel panic 0 not syncing: UFS: Unable to mount root fs on > unknown-block(0.0) > [ 2.762769] CPU: Z PID: 1 Comm: swapper/0 Not tainted > 4.1474-1.pvops.qubes.x86_64 #1 > [ 2.762790] Hardware name: LENOVO , BIOS N1TET41W (1.15) 10/20/2017 > [ 2.762813] Call Trace: > [ 2.762826] dump_stack+0x5c/0x85 > [ 2.762839] panic+0xc4/0x252 > [ 2.762851] mount_block_root+0x35b/0x52c > [ 2.762865] ? do_early_param+0x16e/0x16e > [ 2.762879] prepare_namespace+0x278/0x245 > [ 2.762892] ? do_early_param+0x16e/0x16e > [ 2.762905] kernel_init_freeable+0x2c8/0x324 > [ 2.762920] ? rest_init+0xb0/0xb0 > [ 2.762932] kernel_init+0xa/0x101 > [ 2.762945] ret_from_fork+0x35/0x40 > [ 2.762964] Kernel Offset: disabled > > - > > I anyone could help me get my qubes running again I'd be much obliged. I found this post in an Archlinux forum that has the same error: https://bbs.archlinux.org/viewtopic.php?id=131785 The problem was that the /boot partition ran out of space. Try checking the available space in your boot partition and if it's zero or low remove some of the old kernels, then recreate the initramfs images. -- 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/XnPXXKP784ZOmR94pzVaziHlnikXFg7iwnYVWboNx-g0qa77Bev2Z3Btf9DXnz57DY_HFAgjklpe9t2V6XJ15g%3D%3D%40fidelramos.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Problem when creating a new standalone VM based on a template via the command line.
dom0 qubesd[2612]: unhandled exception while calling > src=b'dom0' meth=b'admin.vm.Create.StandaloneVM' dest=b'dom0' arg=b'bionic' > len(untrusted_payload)=26 <-- NOTICE THE UNTRUSTED MARKING HERE IS THAT THE > PROBLEM ? > Oct 29 10:27:46 dom0 qubesd[2612]: Traceback (most recent call last): > Oct 29 10:27:46 dom0 qubesd[2612]: File > "/usr/lib/python3.5/site-packages/qubes/api/init.py", line 262, in respond > Oct 29 10:27:46 dom0 qubesd[2612]: untrusted_payload=untrusted_payload) > Oct 29 10:27:46 dom0 qubesd[2612]: File > "/usr/lib64/python3.5/asyncio/futures.py", line 381, in iter > Oct 29 10:27:46 dom0 qubesd[2612]: yield self # This tells Task to wait for > completion. > Oct 29 10:27:46 dom0 qubesd[2612]: File > "/usr/lib64/python3.5/asyncio/tasks.py", line 310, in _wakeup > Oct 29 10:27:46 dom0 qubesd[2612]: future.result() > Oct 29 10:27:46 dom0 qubesd[2612]: File > "/usr/lib64/python3.5/asyncio/futures.py", line 294, in result > Oct 29 10:27:46 dom0 qubesd[2612]: raise self._exception > Oct 29 10:27:46 dom0 qubesd[2612]: File > "/usr/lib64/python3.5/asyncio/tasks.py", line 240, in _step > Oct 29 10:27:46 dom0 qubesd[2612]: result = coro.send(None) > Oct 29 10:27:46 dom0 qubesd[2612]: File > "/usr/lib64/python3.5/asyncio/coroutines.py", line 213, in coro > Oct 29 10:27:46 dom0 qubesd[2612]: res = yield from res > Oct 29 10:27:46 dom0 qubesd[2612]: File > "/usr/lib/python3.5/site-packages/qubes/api/admin.py", line 998, in _vm_create > Oct 29 10:27:46 dom0 qubesd[2612]: assert not self.arg > Oct 29 10:27:46 dom0 qubesd[2612]: AssertionError This is the code line that is raising an error: https://github.com/QubesOS/qubes-core-admin/blob/master/qubes/api/admin.py#L998 I think it's because of the argument "bionic". I'm still familiarizing myself with Qubes' CLI tools, but I think you might need to use "qvm-create --hvm-template". Reading https://www.qubes-os.org/doc/windows-tools/ it looks like "--hvm" and "--template" are to be used to create an AppVM based off a Standalone HVM. If this doesn't work you could edit /usr/lib/python3.5/site-packages/qubes/api/admin.py and add a "print self.arg" right before the assert, that way you should see what is the argument that is not expected by the code. Fidel Ramos PGP 7F07 1B7C 479F EDD1 - https://keybase.io/fidel -- 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/8kf67cfb97OGkbL-sMyBwX4Z5ALhcJPCWHd_55sLVsOtwc904mV7a88MB1xfZk5iPBEr0-0FTyVxqGhbuyynJA%3D%3D%40fidelramos.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Installation Problem
‐‐‐ Original Message ‐‐‐ On Monday, October 29, 2018 6:20 PM, Andy Powell wrote: > Hello Qubes group! > > I’m trying to install Qubes but it fails after “Test this media & install > Qubes R4.0” at “Loading initrd.img” > > I’m on a 2012 MacBook Pro, running Parallels (which I guess may be the issue, > as 100% of your documentation refers to VirtualBox...do you support other > hypervisors?) > > I’ve followed everything as best I can and am stuck in an infinite loop. No > issues running other major OS VMs (Ubuntu, Mint, Fedora, various Win, etc) > > Please help! Thank you! > > —Andy Running QubesOS inside a virtual machine is not supported, and as you found out it won't work in most configurations. If you want to try out Qubes in your machine you could install it into a USB drive or USB HDD (i.e. put the installer into a USB drive, boot the installer, then install into a *different* USB drive). It will be slower, but you can see if it works with your hardware. -- 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/7OYwu-82Jm_sf1Br-sHUg4tMLjtBjyghaP7jvVhfEjZYa_9dRIBAswahD7_dSnOv7qzPc2_dHrhzL8Nz-VfM6g%3D%3D%40fidelramos.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Two VPN questions and one Qube Manager question.
‐‐‐ Original Message ‐‐‐ On Thursday, November 1, 2018 1:59 AM, Chris Laprise wrote: > On 10/31/2018 03:06 PM, entiosis via qubes-users wrote: > > > 1. I’ve successfully managed to set up a “ProxyVM” (or “AppVM” as it is > > called in Qubes 4.0) to run as VPN gateway with Private Internet Access > > (PIA)/Openvpn by following the guide in qubes documentation; > > https://www.qubes-os.org/doc/vpn/ and > > https://www.youtube.com/watch?v=K1_zqT7_N7k > > PIA provides 33 gateways around the world to choose from, what I wonder > > is; how can I (easily) change and choose the various gateways of the > > sys-vpn (ProxyVM) as I normally can when directly using PIA? I may need to > > make my IP appear to come from one specific country, or have the desire to > > change from which country I’ve been connected to after a while. Also, can > > the ProxyVM be set to make gateway connections at random? > > > > It would not be too hard to write a shell script that shows all the ovpn > files in the /rw/config/vpn dir and lets you pick one. Then simply link > ('ln -s') the chosen ovpn file to "openvpn-client.ovpn". Finally, tell > openvpn to (re)start. It also wouldn't be too hard to do this manually > if you don't change locations very frequently. I'm starting work on a systray icon for Qubes-vpn-support that will make changing the VPN configuration a breeze. Please check out this Github issue: https://github.com/tasket/Qubes-vpn-support/issues/17 Fidel Ramos PGP 7F07 1B7C 479F EDD1 - https://keybase.io/fidel -- 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/30ZLgFE4GpIkJNVF1XqT6Wg-Rii_D-duRz4dqYrtz3bV4ERpSGqBO0Wfs2PaaObZi2J0unN5A85bKfCtKrKDtw%3D%3D%40fidelramos.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Fedora-29-minimal :: Feedback / Using it as sys-Template
‐‐‐ Original Message ‐‐‐ On Monday, November 12, 2018 6:51 PM, 799 wrote: > did someone succeeded installing and using sys-vms (sys-usb|net|firewall) > based on the new fedora-29-minimal template from the testing repositories > (sudo qubes-dom0-update --enablerepo=qubes-templates-itl-testing > fedora-29-minimal) with working network connectivity? When Fedora 29 was released I cloned my fedora-28-minima-net VM, that I use for sys-net, firewall and VPN VMs, and upgraded. Only sys-net is working with Fedora 29, for some reason neither the firewalls nor VPN VMs work. I haven't tried recently, nor have I tried with Qubes' fedora-29-minimal, I'm keeping fedora-28-minimal around for now. -- 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/l79mhzAUaYnoSoh_T9BRhczZ0TmXjCd7Jki-slkem0OK84kV2lrdHVJ1MLvvDbg85tQ0kd79YE-wolktKMByLQ%3D%3D%40fidelramos.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Whonix GW & WS upgrade failed (Help)
‐‐‐ Original Message ‐‐‐ On Tuesday, November 27, 2018 11:08 AM, wrote: > I press upgrade at Whonix GW & WS and get this message, see Screnshoot, what > should I do? thank you in advance ;) > > https://ibb.co/XbCsJWQ Did you try any of the things proposed by the error message? -- 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/msj4aOQCaqp8XM4kbNBclLEZx2yHXWoaJUQtHqcGDzacKVI7ZLWUTjkyCaxM1JqcbiBjrmotTBZ8LbKHxmODpw%3D%3D%40fidelramos.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Whonix GW & WS upgrade failed (Help)
‐‐‐ Original Message ‐‐‐ On Wednesday, November 28, 2018 12:39 PM, wrote: > so here is my file: /etc/qubes-rpc/policy/qubes.UpdatesProxy > > see screenshot number 1 > > 1. https://ibb.co/87qBcvc > > here is the message what I should do with him, see screnshoot number 2 > > 2. https://ibb.co/82TGjJF > > Here is my question, I need a more specific answer: What do I have to > change in my file now? do I have to delete everything on the 1 Screnshoot and > write in there from the 2 Screnshoot? and if so I just have to write the red > marked purely or continue to mark the green too? If you want you can also > send me a finished pattern with screenshot or text, thanks in advance;) Maybe the problem lies in the use of $tag:whonix-updatevm, try replacing it with the exact name of the whonix template VMs, e.g.: whonix-gw-14 $default allow,target=sys-whonix whonix-ws-14 $default allow,target=sys-whonix -- 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/xoiT0iWWFYotbqHa4iR97ecYF8CDzSb_bZjzo5c-6a_ircPR9vmWbyiEjG28uU9WYQdbJZXSJdCk-fHoHY5bnw%3D%3D%40fidelramos.net. For more options, visit https://groups.google.com/d/optout.