>>> On 21.08.16 at 21:36, wrote:
>> --- 4.7-rc6-xen.orig/drivers/xen/xenbus/xenbus_dev_frontend.c
>> +++ 4.7-rc6-xen/drivers/xen/xenbus/xenbus_dev_frontend.c
>> @@ -316,11 +316,18 @@ static int xenbus_write_transaction(unsi
>> rc = -ENOMEM;
>> goto o
mcg...@kernel.org,a...@redhat.com,t...@linutronix.de,mi...@redhat.com,jpoim...@redhat.com,b...@alien8.de,li...@arm.linux.org.uk,mhira...@kernel.org,masami.hiramatsu...@hitachi.com,jba...@akamai.com,heiko.carst...@de.ibm.com,ana...@linux.vnet.ibm.com,anil.s.keshavamur...@intel.com,da...@davemloft.ne
The PV Calls (formerly XenSock) protocol design has recently attracted
interest within the OpenXT software development community, as it is a novel
interdomain communication mechanism and protocol.
We have a longstanding and active interest in interdomain communication
transport. v4v is a protocol
This run is configured for baseline tests only.
flight 67573 seabios real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67573/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop
Hi,
>> I'm trying to find out why just doing "xenstore-ls" doesn't work on my
>> 4.4.20 kernel and when stracing it, I see it doing :
>
> That looks like the same brokeness I reported earlier:
> https://lists.xenproject.org/archives/html/xen-devel/2016-08/msg02496.html
> Luckily I'm not alone with
## Sylvain Munaut (s.mun...@whatever-company.com):
> I'm trying to find out why just doing "xenstore-ls" doesn't work on my
> 4.4.20 kernel and when stracing it, I see it doing :
That looks like the same brokeness I reported earlier:
https://lists.xenproject.org/archives/html/xen-devel/2016-08/ms
Hi,
> --- 4.7-rc6-xen.orig/drivers/xen/xenbus/xenbus_dev_frontend.c
> +++ 4.7-rc6-xen/drivers/xen/xenbus/xenbus_dev_frontend.c
> @@ -316,11 +316,18 @@ static int xenbus_write_transaction(unsi
> rc = -ENOMEM;
> goto out;
> }
> +
flight 100577 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100577/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 100418
test-amd64-amd64-xl-qemuu-win7-a
From: Chris Patterson
The uart generates an interrupt whenever the transmit holding register is
empty and UART_IER_ETHREI is set in UART_IER. Currently, Xen's ns16550
driver does not currently mask this interrupt when transmit is stopped,
unlike other platforms such as Linux [1].
Toggle UART_IE
Hi Dmitry,
as long as you are testing with a HVM Linux guest you should be able
to just compile the Xen tools in the guest and then use libxc from
within the guest to issue that hypercall via
xc_altp2m_set_vcpu_enable_notify. You will need to load a couple Xen
related kernel-modules for it to work
Hello, how can i get write permission to update documentation on the Xen
Wiki?
--
My Blog: http://www.neilscomputerblog.blogspot.com/
Twitter: @neilsikka
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
flight 100576 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100576/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 2a99aa99fc84a45f505f84802af56b006d14c52e
baseline version:
xen c4e7
flight 100574 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100574/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-rtds 15 guest-start/debian.repeat fail in 100569 pass in
100574
test-amd64-amd64-xl-qemut-
flight 100575 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100575/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-amd64-amd64-libvirt-xsm 12 migrate-s
14 matches
Mail list logo
