| Message ID | 5c7cf4c680200c37187b90eebc49f600865c65ec.1700790421.git-series.marmarek@invisiblethingslab.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | MSI-X support with qemu in stubdomain, and other related changes | expand |
On Fri, 24 Nov 2023, Marek Marczykowski-Górecki wrote: > /dev/mem access doesn't work in dom0 in lockdown and in stubdomain. > Simulate this environment with removing /dev/mem device node. Full test > for lockdown and stubdomain will come later, when all requirements will > be in place. > > Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com> Nice! I was going to suggest to do the same for other PCI Passthrough tests but this is the only one I believe? Acked-by: Stefano Stabellini <sstabellini@kernel.org> > --- > This can be applied only after QEMU change is committed. Otherwise the > test will fail. > --- > automation/scripts/qubes-x86-64.sh | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/automation/scripts/qubes-x86-64.sh b/automation/scripts/qubes-x86-64.sh > index d81ed7b931cf..7eabc1bd6ad4 100755 > --- a/automation/scripts/qubes-x86-64.sh > +++ b/automation/scripts/qubes-x86-64.sh > @@ -163,6 +163,8 @@ ifconfig eth0 up > ifconfig xenbr0 up > ifconfig xenbr0 192.168.0.1 > > +# ensure QEMU wont have access /dev/mem > +rm -f /dev/mem > # get domU console content into test log > tail -F /var/log/xen/console/guest-domU.log 2>/dev/null | sed -e \"s/^/(domU) /\" & > xl create /etc/xen/domU.cfg > -- > git-series 0.9.1 >
diff --git a/automation/scripts/qubes-x86-64.sh b/automation/scripts/qubes-x86-64.sh index d81ed7b931cf..7eabc1bd6ad4 100755 --- a/automation/scripts/qubes-x86-64.sh +++ b/automation/scripts/qubes-x86-64.sh @@ -163,6 +163,8 @@ ifconfig eth0 up ifconfig xenbr0 up ifconfig xenbr0 192.168.0.1 +# ensure QEMU wont have access /dev/mem +rm -f /dev/mem # get domU console content into test log tail -F /var/log/xen/console/guest-domU.log 2>/dev/null | sed -e \"s/^/(domU) /\" & xl create /etc/xen/domU.cfg
/dev/mem access doesn't work in dom0 in lockdown and in stubdomain. Simulate this environment with removing /dev/mem device node. Full test for lockdown and stubdomain will come later, when all requirements will be in place. Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com> --- This can be applied only after QEMU change is committed. Otherwise the test will fail. --- automation/scripts/qubes-x86-64.sh | 2 ++ 1 file changed, 2 insertions(+)