flight 142320 linux-4.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142320/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-examine 11 examine-serial/bootloaderfail like 141640
test-amd64-i386-xl-pvshim12 guest-
flight 142318 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142318/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-examine 11 examine-serial/bootloaderfail like 141650
test-amd64-amd64-xl-qemut-win7-amd64 17
flight 142314 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142314/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail REGR. vs.
140282
test-amd64-amd
flight 142302 linux-4.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142302/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvshim 20 guest-start/debian.repeat fail REGR. vs. 139698
Tests which did not s
flight 142298 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142298/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-i386 7 xen-boot fail REGR. vs. 133580
test-amd64-i386-xl-
flight 142286 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142286/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-pair 22 guest-migrate/src_host/dst_host fail REGR.
vs. 141822
test-amd6
On Fri, 4 Oct 2019 at 17:42, Julien Grall wrote:
>
> flask_assign_{, dt}device() may be used to check whether you can test if
> a device is assigned. In this case, the domain will be NULL.
>
> However, flask_iommu_resource_use_perm() will be called and may end up
> to deference a NULL pointer. Thi
I was trying to understand the following things regarding the PV driver.
1. Who create frontend and backend instances?
2. When are these instances created?
3. How xenbus directories are created? What is the hierarchy of the
directories?
4. What is the role of "vifname" and who sets it?
Please l
flight 142270 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142270/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail REGR. vs.
140282
test-amd64-amd
