If it helps same problem here, after using the Thinkpad Troubleshooting
docs link, went through the whole thing, then there is *No xen.cfg to
change to BOOT only a efi.cfg (which I saw in another post in the
usergroup someone also saw) ; I changed the efi.cfg references to BOOT
and was able
A alternative thought that doesnt require any knowledge on my part would be to
install qubes twice. Once on each device. Then format the 2nd device from
inside
the 1st qubes install. Keeping the LVM and LUKS while maintaining separation.
Then I should be able to mount the device without any
>From my understanding, LVM thin partitioning allows qubes to use 'pools' to
actively change... sizes or something for VMs.
I wasnt sure how to remove the drive before installation. Without having the
PC open while it was running and remove the hard drive after partitioning and
before
I saw some other similar posts, but they didn't have resolutions or were for
different systems.
Any suggests/help would be appreciated! -Thanks!
Issue:
After a successful installation of Q4 rc5 from USB the machine booted, and is
displayed the following 4 lines:
Xen 4.0.3 (c/s ) EFI loader
I just tried to remove some of them.
Well, actually they were a % of a whole backup system qube and I did not finish
the restore.
$ qvm-remove --force-root qubeVM
# Traceback:
File /bin/qvm-remove, line 5 in
sys.exit (main())
/usr/lib/python3.5/site-packages/qubesadmin/qvm_remove.py, line 47
I was confused by the same thing -
https://github.com/QubesOS/qubes-issues/issues/3527
--
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
On Sat, Mar 24, 2018 at 05:35:01PM -0400, Micah Lee wrote:
> ‐‐‐ Original Message ‐‐‐
>
> On March 24, 2018 2:28 PM, Micah Lee wrote:
>
> > When I installed Qubes 4.0 I chose to install all of my updates over Tor.
> > Since then, I've opened Qubes Global Settings
> Hi, hopes I'm not bothering you and thanks for your tips I finally got Qubes
> running on my MBP. However, I can't get the wifi card working using methods
> you discussed above, after running "sudo xl pci-attach sys-net
> '02:00.0,permissive=1'" (02:00.0 is the network controller pci
On Sat, March 24, 2018 10:10 pm, cooloutac wrote:
> Now I'm
> dealing with other issues.
Hope it goes well.
> I'm also upset the direction Qubes has been
> going and how influenced and off course its become.
I don't agree; their primary focus appears to remain on security.
> Worrying about
On Friday, March 23, 2018 at 5:25:59 PM UTC-4, haaber wrote:
> Dear Coolotac, I have trouble to imagine that the guy named cooloutac
> who was patiently helping many people here for longtime should be the
> cooloutac that employs such speech again and again. I do not know what
> happened to you. I
On Friday, March 23, 2018 at 5:08:56 PM UTC-4, steve.coleman wrote:
> On 03/22/18 21:25, cooloutac wrote:
> > Well Steve it worked. after formatting the usb to ext, changing ownership
> > of it to user, and using a non disposable template browser. I was able to
> > download the 4.4gb iso to
On Friday, March 23, 2018 at 5:42:16 PM UTC-4, tai...@gmx.com wrote:
> On 03/22/2018 10:01 PM, cooloutac wrote:
>
> > also just wanted to say the other reason I suggest the legacy ps2 port is
> > if you plan to use usb 3.0 ports most boards route all the usb controllers
> > into one when 3.0
On Friday, March 23, 2018 at 5:40:44 PM UTC-4, tai...@gmx.com wrote:
> On 03/23/2018 10:01 AM, cooloutac wrote:
>
> > secure boot is a gimmick, that even Richard Stallman admits is ok to use
> > for security purposes. a gimmick that when enabled stopped hacking teams
> > insyde bios attack. and
‐‐‐ Original Message ‐‐‐
On March 24, 2018 2:28 PM, Micah Lee wrote:
> When I installed Qubes 4.0 I chose to install all of my updates over Tor.
> Since then, I've opened Qubes Global Settings and changed UpdateVM to
> sys-firewall.
>
> When I install dom0
On 03/24/2018 11:24 PM, Michael Strasser wrote:
> I had the same error while using Whonix for updates.
> I noticed the issue right after a fresh install so I just reinstalled
> and did not select updates via whonix.
> If that's not an option for you can have a look at this thread:
>
When I installed Qubes 4.0 I chose to install all of my updates over Tor. Since
then, I've opened Qubes Global Settings and changed UpdateVM to sys-firewall.
When I install dom0 updates, this seems to work fine. It says `Using
sys-firewall as UpdateVM to download updates for Dom0`.
But when I
I had the same error while using Whonix for updates.
I noticed the issue right after a fresh install so I just reinstalled
and did not select updates via whonix.
If that's not an option for you can have a look at this thread:
On Saturday, 24 March 2018 23:18:33 UTC+3, Michael Strasser wrote:
> Are you trying to update via whonix?
> On Sat, Mar 24, 2018 at 01:08:49PM -0700, Roy Bernat wrote:
> > hi
> >
> > getting error while update template
> >
> > Failed to synchronize cache for repo 'qubes-vm-r4.0-current
> >
>
Are you trying to update via whonix?
On Sat, Mar 24, 2018 at 01:08:49PM -0700, Roy Bernat wrote:
> hi
>
> getting error while update template
>
> Failed to synchronize cache for repo 'qubes-vm-r4.0-current
>
> Someone ?
>
> R
>
> --
> You received this message because you are subscribed
hi
getting error while update template
Failed to synchronize cache for repo 'qubes-vm-r4.0-current
Someone ?
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
Hey,
On 03/24/2018 08:20 PM, daltong defourne wrote:
> Hello community!
>
> I need to achieve the following:
>
> A systemd unit that fires ONLY when user first logs in (not when bootup
> complete, so rc.local does not achieve what I want)
Found that (didn't even know that was possible):
Hello community!
I need to achieve the following:
A systemd unit that fires ONLY when user first logs in (not when bootup
complete, so rc.local does not achieve what I want)
And, related need, I want to be able to determine if a particular VM is already
running.
What I want to achieve:
On Sat, March 24, 2018 5:54 pm, sevas wrote:
> I have a very slow SSD and a very fast m.2.
>
>
> I am installing qubes on them together.
>
>
> Does qubes automatically install dom0 to the m.2?
>
>
> The boot partition is showing as m.2.
>
>
> I will be qvm-pci attach-ing the ssd to 1 or two
I have a very slow SSD and a very fast m.2.
I am installing qubes on them together.
Does qubes automatically install dom0 to the m.2?
The boot partition is showing as m.2.
I will be qvm-pci attach-ing the ssd to 1 or two specific qubes.
Everything else should be m.2.
--
You received this
On Tuesday, March 20, 2018 at 4:40:23 PM UTC-3, Unman wrote:
> On Tue, Mar 20, 2018 at 11:50:36AM -0700, Fernando wrote:
> > On Tuesday, March 20, 2018 at 3:24:56 PM UTC-3, Unman wrote:
> > > On Tue, Mar 20, 2018 at 06:43:49AM -0700, Fernando wrote:
> > > > This is more of a warning for those
I have managed to install by attaching a 2nd HDD to my PC.
in dom0, qvm-pci attach --persistent --option no-strict-reset=true
00:{myPCIsataDev}.0
Everything seems to be working... except for the mouse, of course. Otherwise,
drive-able. When I shut it down and restarted, it did not boot. I
On Fri, March 23, 2018 2:34 pm, mvbittar wrote:
> Hey awokd,
>
>
> It does says sys-net. :(
If you are still having trouble with this, you could try switching your
UpdateVM to sys-whonix instead. Usually those will be slower, but it might
work around whatever problem you are having. You can
27 matches
Mail list logo