Hello,
I have installed a windows 10 standalone HVM qube, which works as expected.
Now if I clone it, the cloned qube cannot even ping his default gateway.
Digging a bit I can see that:
- sys-firewall has a route, through the proper iface, to the IP associated
with the cloned HVM, but the IP
Hi all,
(resent here since something seems to block with qubes-devel)
I'm probably missing something in how the build is supposed to work:
Following the build instructions at
https://www.qubes-os.org/doc/qubes-iso-building/,
configuring with ./setup, first with NO_SIGN=1. The build of
> I was finally able to boot kernel-latest (running 5.12 now), by
> hiding the dGPU
> from the amdgpu module (with "pci-stub.ids=1002:7340"), and
> installing the linux-firmware
> package from current 4.1 snapshot.
Oh and I forgot, resuming after suspend does not work either,
with 5.12 or 5.4. I
I was finally able to boot kernel-latest (running 5.12 now), by hiding the dGPU
from the amdgpu module (with "pci-stub.ids=1002:7340"), and installing the
linux-firmware
package from current 4.1 snapshot.
We can note that this does not give proper GPU support
even for the iGPU, as dom0 Xorg
- Mail original -
De: "mailinglist_bot via Qubes OS Forum"
À: ydir...@free.fr
Envoyé: Lundi 5 Juillet 2021 16:20:57
Objet: [Qubes Forum] [qubes-users] Issues building dom0, "Package rpm-devel is
not signed" [Mailing Lists/qubes-users]
mailinglist_bot
July 5
> The two big issues in this report (aside for the need to modify the
> config in
> the install media, which is not obviously transposable to 4.1
> snapshots) are
> the lack of detection of TPM and SLAT. Will be happy to help with
> these.
Another issue is that the default 5.4 kernel does not
> > The two big issues in this report (aside for the need to modify the
> > config in
> > the install media, which is not obviously transposable to 4.1
> > snapshots) are
> > the lack of detection of TPM and SLAT. Will be happy to help with
> > these.
>
> Another issue is that the default 5.4
Hello,
Did my best to replace generated FIXME's with accurate info, just tell me if
the level of information is inadequate.
The two big issues in this report (aside for the need to modify the config in
the install media, which is not obviously transposable to 4.1 snapshots) are
the lack of
> Sven wrote:
> > Is there any kernel with which VFIO is supported, or is it simply
> > "VFIO not supported"?
>
> Even with 5.12-9 the kernel logs show "AMD IOMMUv2 functionality not
> available on this system",
> although lspci does show a 1022:1631 device, which recent pci.ids
> identify as
