[qubes-users] anyone experiencing issues with whonix-ws ?
Hi, i'm experiencing a weird issue with whonix-ws template and anon-whonix appVM. The VM starts up properly, i can confirm by the logs reaching the login, and by the fact that i can attach to the console for interacting with it. The problem is that i cant run any application. By trying to run an application (like xterm) from the attached console, the VM says it cant connect to the X server. Generally this is obvious in many distributions when you run a command from the terminal that requires an X server to be available, but i tried to do the same thing with the personal domain, based on fedora and if i type xterm, the terminal pops up in the dom0 window manager with the appropriate window decoration for the specific domain. Is there anything i can try to solve the problem? Thanks in advance for your kind help. -- 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/5f58bec6-e4f6-4db6-8092-f05a916dc2a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: attaching to VM consoles for debugging purposes
Il giorno sabato 28 ottobre 2017 07:19:52 UTC+2, Foppe de Haan ha scritto: > you can try 'qvm-start-gui --all' first, to see if that helps; otherwise, > your best bet is 'sudo xl console -t pv VMNAME' Ok i can use xl to reach the console. here are my findings. if i attach to my "personal" domain using xl, log in as root and launch xterm from the console, i get the terminal window appearing on the desktop and everything works. On the other end, if i do the same with whonix and try to run a graphical application, i get a "cannot open display" error, which suggests me that it cant connect to the x server? or the qubes services are not properly running in the VM? -- 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/29a2d735-2560-47d0-be83-411a096e8205%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] attaching to VM consoles for debugging purposes
Hi, i've just installed qubes 4.0 rc2, and i'm having some issues with VMs, they start correctly, i see them running, but for some reasons certain VMs don't run the applications, not even a terminal emulator. since the VM is running i'd like to see what's the problem, so that i have something more useful to investigate or even ask about when coming here instead of just asking "help with this VM i cant start firefox" which i know can be really annoying. is there a way to attach to the console? i thought of virsh but it's not installed in dom0. anyway, the VM that is giving me issues is whonix-ws it starts up but i cant run any application from the menu, even qvm-run doesn't return anything and stays hung there. -- 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/fe2c1625-d303-4c38-9275-dfc1cadca774%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] whonix-gw and whonix-ws not running on qubes 4.0 rc1
Hi again, i'm sorry that i'm posting so many help requests all of a sudden. I was trying to get whonix to work on qubes 4, i've followed some tutorials and with some helps from the bug tracker on github i could get the template VMs installed and both the sys-whonix and anon-whonix domains. The problem is that they just don't start up, and i don't know how to debug the problem I've also tried setting the VMs in debug mode, but i cant get any output that i can look up for to understand what's going on. The only thing i can get is the boot up windows (with black border) when i do qvm-start -v sys-whonix but it disappears too fast for me to read the output. Appearently there is something wrong in there that causes the VM to die. can anyone help me out in understanding what's wrong? i ised the suggetions in this issue: https://github.com/QubesOS/qubes-issues/issues/2954 to set things up by configuring the repositories and keys needed to install the community templates. all other domains work fine. -- 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/42a5820d-9685-44dd-be87-80930ce7c66d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: qubes 4.0 RC1 networking problems
Il giorno domenica 22 ottobre 2017 16:29:14 UTC-4, yura...@gmail.com ha scritto: > On Sunday, October 22, 2017 at 5:27:17 PM UTC, Francesco Rmp wrote: > > Hello everyone, > > i've just installed qubes 4.0 RC1 on my ryzen system ( i couldn't get the > > 3.2 to install because of the kernel compatibility). > > > > The installation went smooth and i can boot fine in the system, but i'm > > having some networking issues. > > > > Making the long story short: i cant get any VM to go online. > > > > I'm no that familiar with the networking in qubes, but i tried to do some > > troubleshooting myself, and here is what i get. > > > > - The sys-net VM works fine, it gets the IP from DHCP, gateway, DNS and > > everything and this is the only VM that goes online. i can ping hosts and > > communicate with the network. I didn't do anything fency in this VM but > > using some terminal commads to check i could actually go online, and it > > works. > > > > This network fetches the IPs from my DHCP and is set to a 192.168.1.0/24 > > > > - the sys-firewall VM doesn't go online at all. I checked the VM > > configuration in qubes manager, and according to the configuration, it > > looks like it's using sys-net as its gateway, but still nothing. > > Curious that when i check in the terminal, it has a network interface with > > class 10.xxx (i dont' remember exactly) and an additional interface for > > each appVM that i spin up (this is fine). > > My question is.. how can this VM masquarade any traffic to the sys-net VM > > if the class of the network interface is completely different and the > > gateway is actually not set to the sys-net VM ip? > > > > - As a consequence of the fact that the sys-firewall VM doesn't go online, > > all the appVMs suffer the same problem. > > > > Can anyone help me out in troubleshooting this problem? > > Am i right to assume that this is not an hardware problem? considering that > > the physical network interface assigned to sys-net works fine? > > > > thanks in advance for your kind reply and support. > > > Typically the Firewall AppVM is not happy to go online if there are problems > with the sys-net AppVM. The issue is therefore likely in the sys-net AppVM, > and not the firewall AppVM. For example if you take a fully functioning Qubes > system, and you kill off the sys-net AppVM, while allowing the firewall AppVM > to stay online, and then start up sys-net again, will cause issues with the > Firewall AppVM. You'll have to shutdown the firewall AppVM and start it > again, to establish a proper tied connection with the sys-net. Something > similar is likely happening here, if there is something not properly working > in your sys-net. > > There are likely two reasons to the problems you face, that I can think of. > > - The first issue is the planned premature release of Qubes 4 (kind of alpha > release), does not always support PCI passthourgh too well, which might > explain why your network card can't be passed through properly. Indeed it > might work for a single VM, but if it can't communicate perfectly, it might > cause the Firewall AppVM to bug out (A possibility). This major Qubes 4-RC1 > issue has very recently been fixed, as early as last week. But since you > don't have networking, you can't fetch the patch that fixes it. You're in > luck though, Qubes 4-RC2 is planned to be released tomorrow, as you can see > here https://www.qubes-os.org/doc/releases/4.0/schedule/ > It shouldn't be delayed once more, a major issue holding it back, is exactly > the issue up above causing problems with PCI passthrough hardware in Qubes 4. > If this still does not work,then you can try turn your Passthrough AppVM's > into PV virtualization mode, instead of HVM mode, which Qubes 4 can do with a > single command. I believe it should be in terminal dom0: QVM-prefs "AppVM > name" -l > somewhere. I don't run Qubes 4 atm, so I can't check, but it should be easy > to do, from what I've heard. > > - The other issue, that I can think of, is Ryzen. The kernel that almost > fully supports Ryzen should be around version 9.12+. For example I've seen > Qubes with Ryzen that only partially allow USB passthrough, but not fully > passtrough, causing weird issues. Qubes does not run version 9.12 just yet > (as far as I know at least), but it should happen soon since 9.12 longterm > status is close now. This, as you probably already know, typically happens > when newer kernels are pushed out regularly, check ht
[qubes-users] Re: qubes 4.0 RC1 networking problems
Il giorno domenica 22 ottobre 2017 13:41:33 UTC-4, Foppe de Haan ha scritto: > On Sunday, October 22, 2017 at 7:27:17 PM UTC+2, Francesco Rmp wrote: > > Hello everyone, > > i've just installed qubes 4.0 RC1 on my ryzen system ( i couldn't get the > > 3.2 to install because of the kernel compatibility). > > > > The installation went smooth and i can boot fine in the system, but i'm > > having some networking issues. > > > > Making the long story short: i cant get any VM to go online. > > > > I'm no that familiar with the networking in qubes, but i tried to do some > > troubleshooting myself, and here is what i get. > > > > - The sys-net VM works fine, it gets the IP from DHCP, gateway, DNS and > > everything and this is the only VM that goes online. i can ping hosts and > > communicate with the network. I didn't do anything fency in this VM but > > using some terminal commads to check i could actually go online, and it > > works. > > > > This network fetches the IPs from my DHCP and is set to a 192.168.1.0/24 > > > > - the sys-firewall VM doesn't go online at all. I checked the VM > > configuration in qubes manager, and according to the configuration, it > > looks like it's using sys-net as its gateway, but still nothing. > > Curious that when i check in the terminal, it has a network interface with > > class 10.xxx (i dont' remember exactly) and an additional interface for > > each appVM that i spin up (this is fine). > > My question is.. how can this VM masquarade any traffic to the sys-net VM > > if the class of the network interface is completely different and the > > gateway is actually not set to the sys-net VM ip? > > > > - As a consequence of the fact that the sys-firewall VM doesn't go online, > > all the appVMs suffer the same problem. > > > > Can anyone help me out in troubleshooting this problem? > > Am i right to assume that this is not an hardware problem? considering that > > the physical network interface assigned to sys-net works fine? > > > > thanks in advance for your kind reply and support. > > try setting debian-8 as your sys-net template. By swapping the template for the net-vm now internet works, but the problem is only partially solved. For some odd reasons, which i couldn't giure out myself.. all of a sudden internet stops working again, and the only way to get it back to work is by disabling and reenabling the wired connection (using the network manager icon on the top right corner). This is really troublesome because i can't get qubes to update or install additional template VMs, as it always stops in the middle of the task and i have to start over. -- 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/eca0acda-c61e-47ba-9630-1862d610100a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] qubes 4.0 RC1 networking problems
Hello everyone, i've just installed qubes 4.0 RC1 on my ryzen system ( i couldn't get the 3.2 to install because of the kernel compatibility). The installation went smooth and i can boot fine in the system, but i'm having some networking issues. Making the long story short: i cant get any VM to go online. I'm no that familiar with the networking in qubes, but i tried to do some troubleshooting myself, and here is what i get. - The sys-net VM works fine, it gets the IP from DHCP, gateway, DNS and everything and this is the only VM that goes online. i can ping hosts and communicate with the network. I didn't do anything fency in this VM but using some terminal commads to check i could actually go online, and it works. This network fetches the IPs from my DHCP and is set to a 192.168.1.0/24 - the sys-firewall VM doesn't go online at all. I checked the VM configuration in qubes manager, and according to the configuration, it looks like it's using sys-net as its gateway, but still nothing. Curious that when i check in the terminal, it has a network interface with class 10.xxx (i dont' remember exactly) and an additional interface for each appVM that i spin up (this is fine). My question is.. how can this VM masquarade any traffic to the sys-net VM if the class of the network interface is completely different and the gateway is actually not set to the sys-net VM ip? - As a consequence of the fact that the sys-firewall VM doesn't go online, all the appVMs suffer the same problem. Can anyone help me out in troubleshooting this problem? Am i right to assume that this is not an hardware problem? considering that the physical network interface assigned to sys-net works fine? thanks in advance for your kind reply and support. -- 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/9f2b71c5-a5ef-42e9-b271-70d51ed43fca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: a cumulative post about some issues i'm having with my qubes installation (looking forward for help)
Il giorno martedì 25 aprile 2017 17:00:30 UTC+2, cooloutac ha scritto: > On Monday, April 24, 2017 at 7:41:46 PM UTC-4, Francesco Rmp wrote: > > Il giorno martedì 25 aprile 2017 00:32:51 UTC+2, cooloutac ha scritto: > > > On Monday, April 24, 2017 at 3:45:52 PM UTC-4, Chris Laprise wrote: > > > > On 04/24/2017 12:20 PM, cooloutac wrote: > > > > > linux always lags a few years behind hardware support. looking at > > > > > this https://bugzilla.redhat.com/show_bug.cgi?id=1411830 makes me > > > > > think 1060 not gonna work with nouveau on any kernel right now. > > > > > > > > > > another solution would be to try and install the proprietary nvidia > > > > > driver from rpm fusion in dom0 but prop drivers are considered > > > > > insecure. Not sure it will even work but maybe worth a shot. > > > > > > > > Somewhere in this thread belongs a diatribe against Nvidia being > > > > FOSS-hostile. But I'll let you all search Youtube for "Torvalds nvidia" > > > > to see -- graphically -- what I mean. ;) > > > > > > > > -- > > > > > > > > Chris Laprise, tas...@openmailbox.org > > > > https://twitter.com/ttaskett > > > > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 > > > > > > lmao just watched it. Personally I never had any problems with nvidia on > > > linux, with either open source or prop drivers. I've always prefered it > > > over ati. But then again I would never buy bleeding edge hardware to > > > run linux. > > > > Indeedbleeding edge VGAs are not really the best idea for a linux OS in > > general, but with other "mainstream" distributions, i don't have these > > problems, mainly because they are more frequently updated then qubes. > > > > I'm not blaming qubes for being conservative, don't misunderstand me, a > > system focusing primarly on security for the end user needs to be throughly > > tested and you can't simply pick up packages and import them into the repo > > without previously making sure that they don't breake the security model in > > any possible way.. also XEN is a b*** when it comes to hardware > > compatibility.. so.. yeah i just hope i'll find a way to solve my problem, > > as said, i'm not looking for high end 3d graphics in qubes at all, but at > > least an even non accelerated decent resolution.. I'd love to gain that :) > > you would have same issue on mainstream linux apparently man. Nouveau is > about the kernel version you are using. Apparently even 4.9 might still not > work correctly for you even on a baremetal fedora system with that card, as > seen by the amount of people complaining on fedora forum threads. Most > people buy cards like that for gpu intensive processing like graphics design > and gaming and use the nvidia proprietary drivers. There seems to be no > choice, I guess if you want to use open source drivers, your nvidia card > has to be at least over two years old to ensure compatibility. It'd be fine to install the nvidia proprietary drivers in dom0, but looking at the documentation on the qubes project site, the guidelines are a bit outdated and i cant seem to be able to follow the procedure, do you know any other more updated tutorial that would work on an updated qubes installation? what version of fedora is it based on, 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/88f12133-c612-4dee-a745-d4635af4e4c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: a cumulative post about some issues i'm having with my qubes installation (looking forward for help)
Il giorno martedì 25 aprile 2017 00:32:51 UTC+2, cooloutac ha scritto: > On Monday, April 24, 2017 at 3:45:52 PM UTC-4, Chris Laprise wrote: > > On 04/24/2017 12:20 PM, cooloutac wrote: > > > linux always lags a few years behind hardware support. looking at this > > > https://bugzilla.redhat.com/show_bug.cgi?id=1411830 makes me think 1060 > > > not gonna work with nouveau on any kernel right now. > > > > > > another solution would be to try and install the proprietary nvidia > > > driver from rpm fusion in dom0 but prop drivers are considered insecure. > > > Not sure it will even work but maybe worth a shot. > > > > Somewhere in this thread belongs a diatribe against Nvidia being > > FOSS-hostile. But I'll let you all search Youtube for "Torvalds nvidia" > > to see -- graphically -- what I mean. ;) > > > > -- > > > > Chris Laprise, tas...@openmailbox.org > > https://twitter.com/ttaskett > > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 > > lmao just watched it. Personally I never had any problems with nvidia on > linux, with either open source or prop drivers. I've always prefered it over > ati. But then again I would never buy bleeding edge hardware to run linux. Indeedbleeding edge VGAs are not really the best idea for a linux OS in general, but with other "mainstream" distributions, i don't have these problems, mainly because they are more frequently updated then qubes. I'm not blaming qubes for being conservative, don't misunderstand me, a system focusing primarly on security for the end user needs to be throughly tested and you can't simply pick up packages and import them into the repo without previously making sure that they don't breake the security model in any possible way.. also XEN is a b*** when it comes to hardware compatibility.. so.. yeah i just hope i'll find a way to solve my problem, as said, i'm not looking for high end 3d graphics in qubes at all, but at least an even non accelerated decent resolution.. I'd love to gain that :) -- 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/55164a11-5669-49c5-b40d-3a1894d89170%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: a cumulative post about some issues i'm having with my qubes installation (looking forward for help)
Il giorno lunedì 24 aprile 2017 21:45:52 UTC+2, Chris Laprise ha scritto: > On 04/24/2017 12:20 PM, cooloutac wrote: > > linux always lags a few years behind hardware support. looking at this > > https://bugzilla.redhat.com/show_bug.cgi?id=1411830 makes me think 1060 > > not gonna work with nouveau on any kernel right now. > > > > another solution would be to try and install the proprietary nvidia driver > > from rpm fusion in dom0 but prop drivers are considered insecure. Not sure > > it will even work but maybe worth a shot. > > Somewhere in this thread belongs a diatribe against Nvidia being > FOSS-hostile. But I'll let you all search Youtube for "Torvalds nvidia" > to see -- graphically -- what I mean. ;) > > -- > > Chris Laprise, tas...@openmailbox.org > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 let's say that, for now i'd be happy enaugh if i could increase the screen resolution to my native monitor one, but i don't know if i have to add something in the xorg configuration, since even trying to force the resolution from there doesn't seem to work. -- 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/e3fb91dc-42fe-49ae-a296-3324697aee8c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] a cumulative post about some issues i'm having with my qubes installation (looking forward for help)
Hello, since i didn't want to flood the group with a bunch of problems i'm having, i thought it was quite a good idea to collect them in a single post, I hope someone can help me out with either any of these. a short background: everything started when i've upgraded my VGA from an old GTX560 to a new GTX1060, this is when i discovered that qubes, because of nouveau not really at a bleeding edge version isn't compatible with the said video card, at a point that i can't see anything on screen. I've solved this by blacklisting the driver and eventually i managed to get the system to boot into X, but now i have the following problems: 1) the only supported resolution appears to be 1024x768@75hz, and this is kinda frustrating considering i have a full HD display, i'd like to get back to 1920x1080@120Hz, since this resolution is supported by my display. 2) collaterally, by trying to fix the video issue, i've discovered that the EFI partition (i have qubes running from an external USB3 HD) boots stright into the OS, and doesn't chainload to GRUB, I have absolutely no idea why, since this is something that the installer took care of on its own, but this is becoming very limiting, because every update in the qubes dom0, especially when related with a new kernel, requires quite a bit of extra work: - mounting the EFI system partition - fix the parameters manually in the CFG can anyone help me out in setting things up properly so that i have a proper grub configuration? 3) the last thing: for some odd reasons i'm stuck on kernel 4.4.14 because of performance reasons, despite not changing ANYTHING except from the kernel version, when running from 4.4.55, X is extremely slow and choppy, mouse lags, and to a point that the system is absolutely unusable. any idea on what this can be caused by? Since this is quite an active development community i'm fairly confident that across the users and/or devs, someone will be able to help me out with my issues, because I'm really enthusiast about this OS, and looking forward to use it more, despite the transition is quite complex as of now. Thanks in advance -- 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/39948b77-8fa3-42e1-b9f1-4f50c73506ab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] cannot boot into qubes: drive not detected as boot device (EFI)
Il giorno lunedì 14 novembre 2016 22:44:03 UTC+1, Marek Marczykowski-Górecki ha scritto: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Mon, Nov 14, 2016 at 08:42:41AM -0800, Francesco Rmp wrote: > > Hello everyone, > > thanks in advance for your support. > > > > I'm new tu qubes but not to linux un general and i'm having a bad issue > > with my qubes installation. > > > > I have a qubes 3.2 installation on an external USB drive (because $reasons) > > and it's not willing to boot, my system doesn't even detect it as a > > bootable device, for reasons i really don't know. > > > > The partition layout is as follows: > > > > 32MB unallocated space (i think for GPT alignment reasons > > 192MB FAT16 EFI System partition > > 512MB ext4 /boot partition > > my LUKS root partition > > other 60MB inallocated (again i think for alignment reasons but meh, anyway > > who cares) > > > > in the EFI FAT16 partition i have the following files > > > > EFI/qubes/ > >initramfs-4.4.14-1.pvops.qubes.x86_64.img > >vmlinuz-4.4.14-1.pvops.qubes.x86_64 > >xen-4.6.1.efi > >xen.cfg > >xen.efi > > > > while in the /boot partition i have all the usual grub related files and > > kernel images. > > > > i've tried booting into rescue mode from the installation media in an > > attempt to restore the grub bootloader, what i generally do in a > > traditional linux distro is chrooting into my installation and then > > manually restore grub, but in my / i can't find anything grub or grub2 > > related that i can use to reinstall the bootloader, so i'm a bit stuck. > > > > any advice on how to rescue my qubes installation so that i can boot into > > it again? > > Some EFI BIOSes handle external drives differently in looking for > what to boot... Try this: > 1. Copy EFI/qubes/ to EFI/BOOT/ > 2. Rename EFI/BOOT/xen.efi to EFI/BOOT/BOOTX64.efi > 3. Rename EFI/BOOT/xen.cfg to EFI/BOOT/BOOTX64.cfg > > - -- > 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? Hi Marek, thank you very much for your support, you were right, i've followed your instructions and i was able to boot back into my qubes :) now from time to time what happens is that, if i'm not booting from a completely shut down system (cold boot) i receive an error about buffer being too small and xen doesn't boot. but that's a minor issue, as long as it boots up in the end. again, thank you very much -- 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/67ae4fc1-8ab7-419a-81b6-a5bf6fae820d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] cannot boot into qubes: drive not detected as boot device (EFI)
Hello everyone, thanks in advance for your support. I'm new tu qubes but not to linux un general and i'm having a bad issue with my qubes installation. I have a qubes 3.2 installation on an external USB drive (because $reasons) and it's not willing to boot, my system doesn't even detect it as a bootable device, for reasons i really don't know. The partition layout is as follows: 32MB unallocated space (i think for GPT alignment reasons 192MB FAT16 EFI System partition 512MB ext4 /boot partition my LUKS root partition other 60MB inallocated (again i think for alignment reasons but meh, anyway who cares) in the EFI FAT16 partition i have the following files EFI/qubes/ initramfs-4.4.14-1.pvops.qubes.x86_64.img vmlinuz-4.4.14-1.pvops.qubes.x86_64 xen-4.6.1.efi xen.cfg xen.efi while in the /boot partition i have all the usual grub related files and kernel images. i've tried booting into rescue mode from the installation media in an attempt to restore the grub bootloader, what i generally do in a traditional linux distro is chrooting into my installation and then manually restore grub, but in my / i can't find anything grub or grub2 related that i can use to reinstall the bootloader, so i'm a bit stuck. any advice on how to rescue my qubes installation so that i can boot into it again? 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/7378aa02-3074-40db-9ab5-cc755c3207df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
