Hi all,
I've noticed recently that once every now and again I get a kernel traceback
when attaching a drive to a DomU.
The drive in question is attached to the system via eSATA, opened via
cryptsetup, then added to the DomU. When this crash occurs, any process trying
to access either the
On 3/15/18 9:16 PM, John Thomson wrote:
> Hi,
>
> Could there please be a branch of the Xen SeaBIOS repository to track or
> include the latest tag used by Xen staging?
> Just for ease of use. All the other Xen dependency repositories do this.
>
> Xen staging currently points to SeaBIOS
flight 120830 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120830/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm broken in
120734
On 3/15/18 12:31 PM, Anoob Soman wrote:
> Load iPXE ROM from a file pointed to by IPXE_PATH. If --with-system-ipxe
> is not specified default Xen firmware directory is picked up as
> IPXE_PATH
>
> Signed-off-by: Anoob Soman
Reviewed-by: Doug Goldstein
On 3/16/18 6:18 AM, Jan Beulich wrote:
On 15.03.18 at 18:31, wrote:
>> @@ -71,7 +72,7 @@ all: acpi subdirs-all
>> acpi:
>> $(MAKE) -C $(ACPI_PATH) ACPI_BUILD_DIR=$(CURDIR)
>> DSDT_FILES="$(DSDT_FILES)"
>>
>> -rombios.o: roms.inc
>> +rombios.o:
flight 120821 xen-4.10-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120821/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-amd64 broken in 120706
build-armhf-pvops
On 17/03/18 21:11, Razvan Cojocaru wrote:
> On 03/14/2018 07:06 PM, Andrew Cooper wrote:
>> On 14/03/18 15:53, Jan Beulich wrote:
>> On 14.03.18 at 15:56, wrote:
We'd like to retrieve the length of the current instruction in
svm_vmexit_handler(),
On 03/14/2018 07:06 PM, Andrew Cooper wrote:
> On 14/03/18 15:53, Jan Beulich wrote:
> On 14.03.18 at 15:56, wrote:
>>> We'd like to retrieve the length of the current instruction in
>>> svm_vmexit_handler(), specifically for the VMEXIT_EXCEPTION_DB and
>>>
flight 120815 xen-4.8-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120815/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-amd64-pvgrub broken in 120695
On 3/15/18 8:55 PM, John Thomson wrote:
> Hi,
>
> I have some suggestions / queries.
> I package Xen using GitLab CI for my use:
> https://gitlab.com/archlinux-packages-johnth/xen/pipelines
> My examples here are just mock-ups and not tested.
>
> On Fri, 16 Mar 2018, at 04:21, Doug Goldstein
On 3/16/18 6:44 AM, Andrew Cooper wrote:
> On 16/03/18 11:26, Jan Beulich wrote:
> On 15.03.18 at 18:31, wrote:
>>> --- a/tools/firmware/hvmloader/config.h
>>> +++ b/tools/firmware/hvmloader/config.h
>>> @@ -33,6 +33,11 @@ struct bios_config {
>>> void
flight 120819 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120819/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf dc080d3b61e570e7a3163fc24afa6f8388d0c0bf
baseline version:
ovmf
flight 120803 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120803/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-ws16-amd64 10 windows-install fail REGR. vs. 12
flight 120818 rumprun real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120818/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumprun 6 rumprun-buildfail REGR. vs. 106754
build-i386-rumprun
> earlycon=xenboot enables the early console for the hardware domain only.
> What I meant is having earlyprintk for Xen (see CONFIG_EARLY_PRINTK). This
> is used for low-level debug when booting the hypervisor.
Ok, Thanks. It's now clear to me.
Thanks
Amit
flight 120795 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120795/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-nested-intel 14 xen-boot/l1 fail REGR. vs. 120095
flight 120787 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120787/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail REGR. vs. 115539
Tests which did not
flight 120779 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120779/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-xsm7 xen-boot fail REGR. vs. 118324
flight 120785 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120785/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt-xsm 14 saverestore-support-checkfail like 120666
test-armhf-armhf-libvirt 14
flight 120780 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120780/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-qemuu-ws16-amd64 7 xen-boot fail in 120665 pass in 120780
20 matches
Mail list logo