flight 158093 qemu-mainline real [real]
flight 158098 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/158093/
http://logs.test-lab.xenproject.org/osstest/logs/158098/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not
Hi All,
Trying to debug Credit2
https://wiki.xenproject.org/wiki/Credit2_Scheduler#Dumping_Status_and_Params
It should be possible to get some debug output on what Credit2 is doing via
pressing 'r' on the Serial Debug port
Does anyone know if it's at all possible to use a USB-TTY adapter? The
flight 158089 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158089/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-xsm7 xen-install fail REGR. vs. 152332
flight 158087 qemu-mainline real [real]
flight 158091 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/158087/
http://logs.test-lab.xenproject.org/osstest/logs/158091/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not
Sure.
The goal is to emulate a scenario where a compromised guest attacks another
tenant in the same physical host reading/changing the memory content.
E.g., extract the RSA key.
I'll be in the domU kernel space. I'm assuming that the guest is able to
exploit
any vulnerability possible.
On 02/01/2021 17:02, Charles Gonçalves wrote:
> Hi,
>
> I'm building some attack loads targeting Xen to my PhD and need to
> identify the pages for a specific guest.
> Assuming that I'm able to traverse the pages in memory, how do I
> identify a guest (by ID or Name)?
>
> The dom0 is easy
Hi,
I'm building some attack loads targeting Xen to my PhD and need to
identify the pages for a specific guest.
Assuming that I'm able to traverse the pages in memory, how do I identify a
guest (by ID or Name)?
The dom0 is easy since I can inspect the start_info looking for
SIF_INITDOMAIN but I
flight 158082 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158082/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-xsm7 xen-install fail REGR. vs. 152332
flight 158079 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158079/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-ws16-amd64 19 guest-stopfail like 158067
flight 158078 qemu-mainline real [real]
flight 158086 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/158078/
http://logs.test-lab.xenproject.org/osstest/logs/158086/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not
flight 158083 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/158083/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-i386-libvirt
11 matches
Mail list logo