[qubes-users] Qubes OS Lexikon mit 1256 Domains aus dem ganzen Internet zusammengefasst
Hallo guten Tag liebe Mädels und liebe Jungs, ich habe diese Suchbegriffe im Internet zusammengesucht und habe 1256 Domain Seiten gefunden. Sicherlich sind hier auch noch Seiten dabei, die Sie noch nicht kennen. Aus diesem Grunde sollten Sie sich das Lexikon anschauen. Wenn Sie Fragen haben, können Sie es gleich reinschreiben ins Forum. Bitte seit so lieb und schreibt nicht in das Lexikon eure Fragen rein, da das Lexikon immer weiter ausgebaut wird! Das Lexikon finden Sie hier: https://qubes-deutschland-forum.gegenseitige-hilfe.org/viewtopic.php?f=185=65 Admin VM AdminVM App VM 1 App VM 2 AppVM1 AppVM2 debian Disposable Disposable VM fedora Firewall rules GUI VM Hypervisor Networking stack Personal VM sys firewall sys firewall VM sys net sys net VM sys usb sys usb VM sys whonix sys whonix VM sys-firewall sys-firewall VM sys-net sys-net VM sys-usb sys-usb VM sys-whonix sys-whonix VM Template VMs TemplateVM TemplateVMs Vault VM whonix Xen Hypervisor Xen Project -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/73311494-e8d7-4025-931a-42d0d34203c7%40googlegroups.com.
Re: [qubes-users] Desktop disappeared
Yeah it did manage to boot it, so it was a screw up in xfce. Since then realized that i3 is also trusted, so I moved to that one, diggin it so far! On Saturday, May 16, 2020 at 3:51:59 PM UTC+2, unman wrote: > > On Fri, May 15, 2020 at 11:18:37AM -0700, sair...@gmail.com > wrote: > > Hi fellas, > > I installed a new ram module to my computer and once turned on the pc, > now > > my desktop (wallpaper + shortcuts) is missing and all I see is a grey > > screen. > > What to do? thx > > > > You haven't said whether Qubes booted and you got to log in screen? > Take out the new RAM, put in the old, and restart - what result? > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0890af5d-6847-4b8f-a329-769ca6969760%40googlegroups.com.
Re: [qubes-users] Re: using salt - how to debug?
On Sun, May 17, 2020 at 09:55:00AM +0100, lik...@gmx.de wrote:
>
> >
> > You haven't included AppVmTobeChanged as a target:
> > qubesctl --show-output --targets=AppVmTobeChanged state.highstate
> >
> > You should check that you aren't getting a mistaken dom0 call.
> >
>
> That made the trick. Thanks unman!
>
> One step forward, but still a way to go:
> Currently I'm struggling to use pillars in my scripts. I have my scripts in
> /srv/salt/user_salt
> /srv/salt/user_pillar
>
> Trying to enable a script containing some constants doesn't work because they
> cannot be found.
> The only way to use pillars for me is passing them at the command line:
> qubesctl ... pillar='{"name": "value"}'
>
> But in this case I get errors in some scripts like this:
> TypeError encountered executing state.highstate: highstate() takes from 0 to
> 1 positional arguments but 2 were given
>
> after executing this commandline:
> sudo qubesctl --show-output --target AppVmTobeChanged state.highstate
> pillar='{"name": "value"}'
>
>
> Best case I'd manage to include pillars in my scripts. Any ideas how?
>
Can you post examples of the pillars you have written?
What exactly are you trying to do?
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/20200517160810.GA32033%40thirdeyesecurity.org.
Re: [qubes-users] AMD RX 5700 XT suddenly stopped working with Qubes
On 5/17/20 11:40 PM, Jarrah wrote: Doesn't seem likely that it's a kernel problem if 5.6.4 used to work and now it doesn't. What was the bios issue? A power fault caused it to drop all settings. I believe I have reset it to the previous config and, at a minimum, it is compatible with Qubes without the problem card. Ah, OK. Not sure what I'd do now in your situation. About all I can suggest is to research bios issues with that card via google. See if anyone else has had problems. Not necessarily exactly what you had, but just with that card. It might give you some clues. Mike. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fbceaa7b-fae1-287d-a01e-8e8f9b6abd3d%40keehan.net.
Re: [qubes-users] AMD RX 5700 XT suddenly stopped working with Qubes
> Doesn't seem likely that it's a kernel problem if 5.6.4 used to work > and now it doesn't. What was the bios issue? > A power fault caused it to drop all settings. I believe I have reset it to the previous config and, at a minimum, it is compatible with Qubes without the problem card. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/00a983f4-1c0c-4700-3a61-d68e818b6468%40undef.tools.
Re: [qubes-users] AMD RX 5700 XT suddenly stopped working with Qubes
On 5/17/20 11:04 PM, Jarrah wrote: At this point, I would rather suggest you to check in changelog of kernel if there would be related commits but still, post a BZ issue on kernel. There are a couple in 5.6.11 that I will have a better look at tomorrow. Not sure this will be it though. The system fails to boot on both 5.6.4 (previously working) and 5.6.11 (new). Doesn't seem likely that it's a kernel problem if 5.6.4 used to work and now it doesn't. What was the bios issue? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/870e7167-f472-544a-49c5-588fa06cab57%40keehan.net.
Re: [qubes-users] AMD RX 5700 XT suddenly stopped working with Qubes
> At this point, I would rather suggest you to check in changelog of kernel > if there would be related commits but still, post a BZ issue on kernel. > There are a couple in 5.6.11 that I will have a better look at tomorrow. Not sure this will be it though. The system fails to boot on both 5.6.4 (previously working) and 5.6.11 (new). -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bf47e1a2-d8fc-dd81-1fdc-aa7dba2045db%40undef.tools.
Re: [qubes-users] AMD RX 5700 XT suddenly stopped working with Qubes
On 2020-05-17 19:36, Jarrah wrote: > Good Morning, > > About a month ago, kernel-latest 5.6.4 was released which resolved the > issues booting Qubes on the RX 5700 XT. This has been working and stable > since this time. > > Yesterday I installed a number of updates (including Xen and > kernel-latest) and (after the updates had completed) had an issue which > reset my bios. Since then, I have been unable to boot Qubes using the > 5700 XT. System works fine in another OS. > > > The only error output I have seen is as follows (observed on different > boots): > > "[Firmware Bug]: cpu 2, try to use APIC520 (LVT offset 2) for vector > 0xF4, but the register is already in use for vector 0x0 on this cpu." > > A failure to start IOMMUv2 (does not occur with the other graphics card) > > > After fixing the bios settings, my next thought was to roll back the Xen > and kernel update. However, this did not solve the issue. > > Other attempts: > > * Boot the system with another GPU: Works fine > > * Boot the system without Xen (just the dom0 kernel): works fine. > > * Boot the system outputing to the hypervisor console: system boots to > login screen. All autostarted VMs boot. Keyboard entry does not get sent > to dom0, but ctl-alt-del reboots the system and outputs to screen. > > * Boot the system and let it sit after the screen locks up: All > autostarted VMs boot but I cannot interact with the system. I can tell > by the hvc above and the fact that my mouse turns on. > > * The error above has been connected to an ACPI issue. Adding the > "acpi=off" boot parameter resulted in a kernel panic probably unrelated > to the GPU issue. > > * Tested the just-released 5.6.13 kernel: Same issue now found on 5.6.4 > (previously good) through 5.6.13. > > * Set every IOMMU/ACS/SVM setting I can find in my bios. > > > I'm stuck for ideas at this point. Has anyone experienced something similar? At this point, I would rather suggest you to check in changelog of kernel if there would be related commits but still, post a BZ issue on kernel. > Thanks. > Frédéric -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d279318d-74ba-b83f-c78c-f1f99450195a%40qubes-os.org. signature.asc Description: OpenPGP digital signature
[qubes-users] Re: using salt - how to debug?
You haven't included AppVmTobeChanged as a target:
qubesctl --show-output --targets=AppVmTobeChanged state.highstate
You should check that you aren't getting a mistaken dom0 call.
That made the trick. Thanks unman!
One step forward, but still a way to go:
Currently I'm struggling to use pillars in my scripts. I have my scripts in
/srv/salt/user_salt
/srv/salt/user_pillar
Trying to enable a script containing some constants doesn't work because they
cannot be found.
The only way to use pillars for me is passing them at the command line:
qubesctl ... pillar='{"name": "value"}'
But in this case I get errors in some scripts like this:
TypeError encountered executing state.highstate: highstate() takes from 0 to 1
positional arguments but 2 were given
after executing this commandline:
sudo qubesctl --show-output --target AppVmTobeChanged state.highstate pillar='{"name":
"value"}'
Best case I'd manage to include pillars in my scripts. Any ideas how?
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/1dda186c-6270-028b-198a-c0fe039e9d63%40gmx.de.
Re: [qubes-users] Mistakenly deleted MBR & system partitions to install, can't boot Qubes
On Sat, May 16, 2020 at 07:25:59PM -0700, sjill...@gmail.com wrote: > nvme0n1p 953G (hd1) > nvme0n1p1 1MBIOS boot efi (hd1,1) this is WAY too small. make it at least 100M, better 500M or even 1GB. here a single set of xen+linux+initrd is about 35-40MB, and in general you want enough space for more than one, plus whatever is needed for booting your other systems. > nvme0n1p2 1GLinux Filesystem (hd1,2) > nvme0n1p3 324.8G Linux LVM(hd1,3) > 15 G Qubes-dom0-swap this indicates you manually changed the partition layout for qubes in too many ways to count, including removing the disk encrpytion. good luck with 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200517080916.GM1079%40priv-mua.
[qubes-users] AMD RX 5700 XT suddenly stopped working with Qubes
Good Morning, About a month ago, kernel-latest 5.6.4 was released which resolved the issues booting Qubes on the RX 5700 XT. This has been working and stable since this time. Yesterday I installed a number of updates (including Xen and kernel-latest) and (after the updates had completed) had an issue which reset my bios. Since then, I have been unable to boot Qubes using the 5700 XT. System works fine in another OS. The only error output I have seen is as follows (observed on different boots): "[Firmware Bug]: cpu 2, try to use APIC520 (LVT offset 2) for vector 0xF4, but the register is already in use for vector 0x0 on this cpu." A failure to start IOMMUv2 (does not occur with the other graphics card) After fixing the bios settings, my next thought was to roll back the Xen and kernel update. However, this did not solve the issue. Other attempts: * Boot the system with another GPU: Works fine * Boot the system without Xen (just the dom0 kernel): works fine. * Boot the system outputing to the hypervisor console: system boots to login screen. All autostarted VMs boot. Keyboard entry does not get sent to dom0, but ctl-alt-del reboots the system and outputs to screen. * Boot the system and let it sit after the screen locks up: All autostarted VMs boot but I cannot interact with the system. I can tell by the hvc above and the fact that my mouse turns on. * The error above has been connected to an ACPI issue. Adding the "acpi=off" boot parameter resulted in a kernel panic probably unrelated to the GPU issue. * Tested the just-released 5.6.13 kernel: Same issue now found on 5.6.4 (previously good) through 5.6.13. * Set every IOMMU/ACS/SVM setting I can find in my bios. I'm stuck for ideas at this point. Has anyone experienced something similar? 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/35b974a3-13f1-cabf-9731-5e9aa1fcbed2%40undef.tools.
