Den 14. des. 2017 21:22, skrev Govinda Tatti:
>
In which case, xl needs to be backwards-compatible with kernels that
don't have your new feature: it will have to check for %s/reset, and
if it's not there, then try %/do_flr.
>>> I think this fix was planned more than a year back an
Den 01.04.2019 11:34, skrev Kevin Wolf:
Yes, for 512 accesses on native 4k disks with O_DIRECT, the QEMU block
layer performs the necessary RMW. Of course, it still comes with a
performance penalty, so you want to avoid such setups, but they do work.
I suspect that the approximately 1/10 -th
Got this just now, as my windows domU died:
(XEN) [2019-10-15 21:23:44] d7v0 vmentry failure (reason 0x8021):
Invalid guest state (0)
(XEN) [2019-10-15 21:23:44] * VMCS Area **
(XEN) [2019-10-15 21:23:44] *** Guest State ***
(XEN) [2019-10-15 21:23:44] CR0: actual=0x
Den 04.11.2019 14:31, skrev Andrew Cooper:
On 03/11/2019 10:23, Håkon Alstadheim wrote:
(XEN) [2019-11-02 14:09:46] d2v0 vmentry failure (reason 0x8021):
Invalid guest state (0)
(XEN) [2019-11-02 14:09:46] * VMCS Area **
(XEN) [2019-11-02 14:09:46] *** Guest State
Den 05.11.2019 02:15, skrev Andrew Cooper:
On 05/11/2019 00:25, Andrew Cooper wrote:
On 04/11/2019 23:42, Andrew Cooper wrote:
On 04/11/2019 23:20, Håkon Alstadheim wrote:
(XEN) RFLAGS=0x0193 (0x0193) DR7 = 0x0400
(XEN) *** Insn bytes from b8868f61d69a: 44 00 00 8c
Den 08. okt. 2018 16:32, skrev Boris Ostrovsky:
>
> Are these two patches still needed? ISTR they were written originally
> to deal with guest trying to use device that was previously assigned to
> another guest. But pcistub_put_pci_dev() calls
> __pci_reset_function_locked() which first tries F
Den 23.10.2018 20:40, skrev Håkon Alstadheim:
Den 08. okt. 2018 16:32, skrev Boris Ostrovsky:
Are these two patches still needed? ISTR they were written originally
to deal with guest trying to use device that was previously assigned to
another guest. But pcistub_put_pci_dev() calls
Den 18. des. 2017 19:33, skrev Govinda Tatti:
Are you saying do_flr doesn't exist at all in any version of Linux,
and as such the line you're removing is currently pointless?
>>> Yes, that's correct. In other-words, it will not break any existing code
>>> or functionality.
>> Except for
Den 25. jan. 2018 12:29, skrev Anthony PERARD:
> On Thu, Jan 25, 2018 at 10:28:14AM +, George Dunlap wrote:
>> On Wed, Jan 24, 2018 at 9:59 PM, Håkon Alstadheim
>> wrote:
>>> I'm trying, and failing, to launch a vm with bios = 'ovmf' under xen 4.10.
&g
Den 19.10.2020 13:00, skrev George Dunlap:
On Jan 31, 2020, at 3:33 PM, Wei Liu wrote:
On Fri, Jan 17, 2020 at 02:13:04PM -0500, Rich Persaud wrote:
On Aug 26, 2019, at 17:08, Pasi Kärkkäinen wrote:
Hi,
On Mon, Oct 08, 2018 at 10:32:45AM -0400, Boris Ostrovsky wrote:
On 10/3/18 11:51 A
Den 19.10.2020 17:16, skrev Håkon Alstadheim:
Den 19.10.2020 13:00, skrev George Dunlap:
On Jan 31, 2020, at 3:33 PM, Wei Liu wrote:
On Fri, Jan 17, 2020 at 02:13:04PM -0500, Rich Persaud wrote:
On Aug 26, 2019, at 17:08, Pasi Kärkkäinen wrote:
Hi,
On Mon, Oct 08, 2018 at 10:32:45AM
I follow the bleeding edge on Dom0 kernels and Xen pretty closely, and
for the past 6 months I have been encountering increasingly frequent
hangs&crashes in the most heavily used domUs. I have tried downgrading
both dom0 kernel and xen, but can't seem to find any where the bug does
not material
12 matches
Mail list logo
