Re: [qubes-users] 'locking' a vm possible? (to prevent accidental shutdown)

2024-04-16 Thread Boryeu Mao
Thank you very much for the help.  Time for a crash course on
qubes-core-admin.

On Mon, Apr 15, 2024 at 9:30 AM Rusty Bird  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Rusty Bird:
> > Boryeu Mao:
> > > An attempt to shutdown `sys-firewall` in `Qube Manager` receive a
> warning
> > > about running processes in the qube; similarly on command line
> > > `qvm-shutdown sys-firewall` fails with an error.  Is it possible to
> > > designate an appVM to behave similarly so it won't get shutdown
> > > accidentally?
> >
> > Not as a user-facing feature AFAIK. But you could use the qubes.ext
> > Python entry point
> >
> >
> https://github.com/QubesOS/qubes-core-admin/blob/v4.2.21/qubes/ext/__init__.py#L57-L59
> >
> > to add another "domain-pre-shutdown" event handler like this one
> > (yours could e.g. check if the VM has a certain tag):
> >
> >
> https://github.com/QubesOS/qubes-core-admin/blob/v4.2.21/qubes/ext/audio.py#L65-L75
>
> Sorry, that second link should have been:
>
>
> https://github.com/QubesOS/qubes-core-admin/blob/v4.2.21/qubes/ext/audio.py#L31-L38
>
> Rusty
> -BEGIN PGP SIGNATURE-
>
> iQKTBAEBCAB9FiEEhLWbz8YrEp/hsG0ERp149HqvKt8FAmYdQPRfFIAALgAo
> aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg0
> QjU5QkNGQzYyQjEyOUZFMUIwNkQwNDQ2OUQ3OEY0N0FBRjJBREYACgkQRp149Hqv
> Kt9fGw/+JHmmCw+Ly/YXJ5uYJknlH/Z8hpViEwPnIGuuz7dkiHYa53BeKg+ub035
> EOt0Z2ir8NuhHGXdN77A4j1PA6gXypEBme3sxDoP0uHv1Tc3GSAgbR4NzF0qucxy
> EQisGL7LAw05raT5vFv8eWsHwfR1OHAupXZKJzHfjX3CBUce51K2N/eyPiuoX4es
> m/1lpLmLWJgXAk2MgvwNop4coRiexLuXGWYpeG+64SrDmB0oJhFZ+8rhUig5UZ41
> ImpkZl+cbFIxVL+j0tcWLlaDt8yTIJzR2lw0afOvHZcqNHlNo2OPSm4HiMfrThVP
> 9oAAU5fvTLQtnVJ0Qw49/wm6nr2IFuR3J3Zkz4PA0jVzxuXL6OGzjLuJuFlj01Sj
> qxK3oU9dsN2cXCkp0k8gq39UAyHZwaeViFnAxKNm/U/ykRlFhLiloTF3ZvJYl7Vv
> 1N54BKKY5RjjtVsBgbDfKVcfSR4UwNt6v2PECfp+l7SpJb4XFiCNb9AoU2UoPQjj
> icOPXw8r7AAMZdm+ANuMhTivGIi+7HR4MQ4xKRmD1bJ1qhQPGyuq+6loYJQQX+r4
> 1evr5+hCbQjapWN5IA7mRSgzaUEPC0Yrc5Ttirw81dbuCIPyv+B2c8LwQDvcorIR
> A5EhArjwq1nY1N1ArMUKVf5+ONcIu7K56fjnMxyZXer3zExcYyA=
> =mP8j
> -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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAOBBCnbBeizsTM9GfvMTc7S7TBUSzpE2KMs4zcvv_wCQ%2BqX8qA%40mail.gmail.com.


Re: [qubes-users] Re: Qubes 4.2 installation problems due to Salt alone - what to do?

2024-04-16 Thread Michael Singer

Thank you! The hardware clock had the wrong date. Therefore the error with salt.


Hmm,  You might find it more useful to join the Qubes Forum,

https://forum.qubes-os.org/

I wanted to reply, so you felt someone will help.

Perhaps Clarify some things.

Seems from your discussion of SALT, you know something of Linux.

If the standard install did not finish correctly.  I am not thinking
whatever is going on with SALT is the problem.  But SALT commands might
reveal to some what is happening?
So, for me in your situation, I would go through the detail of what I
assumed was true, but might not be.

Can you clarify.
Why are you sure the computer in question is compaitble with Qubes?  Have
you used Qubes on it before?
Did you install UEFI or Legacy?   I use Legacy, UEFI is a different set of
problems.
Does your computer have one or two drives?  (I have one computer, with two
drives, that will only let me install Qubes to one drive, and the other
drive must not have anything on it.  Other computers don't care.  and I did
not say it made sense)
Are you trying to accomplish a dual boot?  (Qubes wants to be alone on the
drive.   Some folks have gotten dual boot to work.  I have not tried)

Did you try to install Qubes on a drive that already had -something?
(I have discovered that sometimes Qubes does not like to installed over
something else.  Sometimes does not care.)

Can  you devote this computer to using Qubes right now?   Or is it a
computer you use daily with another OS?
(helps to limit suggestions to something that is more reasonable for you to
try)

I think someone more knowledgeable than myself will come by and recognize
your symptoms, and you don't have to worry about answering this.  But it
can't hurt.

In a coupla days, If you have not gotten it going, I will come back and add
more suggetions.   More confusion.

but someone might recognize symptoms and make an easier fix.

Cheers.


On Sunday, April 14, 2024 at 12:58:26 PM UTC-4 Michael Singer wrote:


Dear Qubes Community,

I am trying to install Qubes 4.2. in vain, not because the hardware is
incompatible, but because of Salt problems. I verified the downloaded ISO
according to the instructions, burned the ISO with various programs on a
USB stick, among others with the DD command:


dd if="./Qubes-R4.2.1-x86_64.iso" of="/dev/sda" status="progress"

conv="fsync"

I have checked the result and it shows that the hash sum of the USB stick
under /dev/sda is the same as the downloaded file:


sudo dd if=/dev/sda bs=1M count=$(stat -c %s

/home/user/QubesIncoming/XXX/Qubes-R4.2.1-x86_64.iso) iflag=count_bytes |
sha256sum

a942911a3a4975831324a064f70b34c6965c4e9f6c95afbc531f04d55f947376


When I start the computer with the USB stick and test the medium, the
following appears first:


Fragment sums: 2695f8d1(...)
supported iso: no


Then, when the test has run 100 percent, the following appears:


[FAILED]


If I install anyway, I have to cancel the automatic creation of sys-net,
sys-usb and personal AppVMs, because otherwise I get an installation error
because the installer does not set the PCI devices to disable strict reset.
At the end of the setup it still says:


"initial config failed", see /var/log/salt/minion


The log there says:


Specified ext_pillar interface qvm_prefs unavailable


And when I try to update dom0, it fails. The reason is noted in the same
log file:


Unable to detect release version
Cannot prepare internal mirror list: SSL peer certificate or SSH remote

key was not OK for https://mirrors.fedora(...)

Everything otherwise works according to the HCL report, including Suspend,
Ethernet, USB, Speaker. Strange thing was that no default-mgmt-dvm seemed
to be present and was not started during update attempts.

I have already tried the installation with 4.2.0 and 4.2.1, with standard
kernel and with the latest kernel.

How could I solve the problem?

Thank you,
Michael Singer



--
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/04644821-831b-4657-990d-84ab2c56309f%40posteo.de.


[qubes-users] HCL : NitroPC 2 - MSI Z790-P Intel i9 14900K

2024-04-16 Thread code9n
HCL report  NitroPC 2  -  MSI Z790-P  Intel i9 14900K

This is Qubes certified, of course, but here's an HCL report anyway.
---
layout:
  'hcl'
type:
  'Desktop'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  'unknown'
remap:
  'yes'
brand: |
  Micro-Star International Co., Ltd.
model: |
  MS-7E06
bios: |
  Dasharo (coreboot+UEFI) v0.9.1
cpu: |
  Intel(R) Core(TM) i9-14900K
cpu-short: |
  FIXME
chipset: |
  Intel Corporation Device [8086:a700] (rev 01)
chipset-short: |
  FIXME
gpu: |
  Intel Corporation Raptor Lake-S GT1 [UHD Graphics 770] [8086:a780] (rev 
04) (prog-if 00 [VGA controller])
 
gpu-short: |
  FIXME
network: |
  Intel Corporation Ethernet Controller I225-V [8086:15f3] (rev 03)
memory: |
  65376
scsi: |

usb: |
  1
certified:
  'no'
versions:
  - works:
  'yes'
qubes: |
  R4.2.1
xen: |
  4.17.3
kernel: |
  6.6.21-1
remark: |
  No problems noticed.  Qubes certified.  Very Fast.
credit: |
  code9n
link: |
  FIXLINK

-- 
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/54d6b847-4390-45c1-ac7a-b35347d76713n%40googlegroups.com.