flight 186770 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/186770/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf f122c6f639cd3babedc0dd9b38b279d94b087c7a
baseline version:
ovmf
flight 186764 xen-unstable real [real]
flight 186769 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/186764/
http://logs.test-lab.xenproject.org/osstest/logs/186769/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
flight 186767 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/186767/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
flight 186768 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/186768/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 5c86b0b57c153bde28f925de80cc011dd4ff1f9d
baseline version:
ovmf
On 11/07/2024 10:49 pm, Olaf Hering wrote:
> Thu, 11 Jul 2024 21:23:37 +0100 Andrew Cooper :
>
>> use the zypper long names for the benefit of those wondering what was being
>> referenced or duplicated.
> Names of rpm packages do change over time, configure already searches for
> "something"
Thu, 11 Jul 2024 21:23:37 +0100 Andrew Cooper :
> use the zypper long names for the benefit of those wondering what was being
> referenced or duplicated.
Names of rpm packages do change over time, configure already searches for
"something" where it is available, instead of some library or
flight 186765 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/186765/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
See prior patch for most discussion.
Despite appearing to a fixed release (and therefore not marked as permitted
failure), the dockerfile references the `leap` tag which is rolling in
practice. Switch to 15.6 explicitly, for better test stability.
Vs tumbleweed, use `zypper update` rather than
On 11/07/2024 9:23 pm, Andrew Cooper wrote:
> Existing as suse:opensuse-tumbleweed is a historical quirk, and adjusted for
> consistency with all the other containers.
>
> Make it non-root, use heredocs for legibility, and use the zypper long names
> for the benefit of those wondering what was
flight 186763 linux-6.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/186763/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 186712
test-amd64-amd64-xl-qemuu-win7-amd64
Existing as suse:opensuse-tumbleweed is a historical quirk, and adjusted for
consistency with all the other containers.
Make it non-root, use heredocs for legibility, and use the zypper long names
for the benefit of those wondering what was being referenced or duplicated.
Trim the dependencies
On Thu Jul 11, 2024 at 3:04 PM BST, Teddy Astie wrote:
> Introduce a new pv interface to manage the underlying IOMMU and manage
> contexts
> and devices. This interface allows creation of new contexts from Dom0 and
> addition of IOMMU mappings using guest PoV.
>
> This interface doesn't allow
Disclaimer: I haven't looked at the code yet.
On Thu Jul 11, 2024 at 3:04 PM BST, Teddy Astie wrote:
> Some operating systems want to use IOMMU to implement various features (e.g
> VFIO) or DMA protection.
> This patch introduce a proposal for IOMMU paravirtualization for Dom0.
>
> Signed-off-by
On 11/07/2024 5:22 pm, Anthony PERARD wrote:
> On Thu, Jul 11, 2024 at 12:15:13PM +0100, Andrew Cooper wrote:
>> qemu-system-ppc64/8.1.0-ppc64 was added because bullseye's Qemu didn't
> QEMU is normally spelled "QEMU" unless we are in camel case context, or
> lower case context.
>
>> understand
On Thu, Jul 11, 2024 at 12:15:17PM +0100, Andrew Cooper wrote:
> Upgrade from Debian buster to bookworm, GCC 11.3 to 11.4 and to be a non-root
> container.
>
> Signed-off-by: Andrew Cooper
Reviewed-by: Anthony PERARD
Thanks,
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen
On Thu, Jul 11, 2024 at 12:15:16PM +0100, Andrew Cooper wrote:
> The containers are both much smaller, with stable toolchains over time, and
> this at least means we're not doing all testing with a single compiler.
>
> Rename the jobs to follow to sort coherently ($DISTRO-$VERSION-$ARCH-*) and
>
On Thu, Jul 11, 2024 at 12:15:15PM +0100, Andrew Cooper wrote:
> For starters, they're slightly smaller:
>
> $ docker image list
> registry.gitlab.com/xen-project/xen/debian 12-riscv64 772MB
> registry.gitlab.com/xen-project/xen/debian 11-riscv64 422MB
>
On Thu, Jul 11, 2024 at 12:15:14PM +0100, Andrew Cooper wrote:
> ... in the style of bookworm-ppc64le
>
> Signed-off-by: Andrew Cooper
Reviewed-by: Anthony PERARD
Thanks,
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
On Thu, Jul 11, 2024 at 12:15:13PM +0100, Andrew Cooper wrote:
> qemu-system-ppc64/8.1.0-ppc64 was added because bullseye's Qemu didn't
QEMU is normally spelled "QEMU" unless we are in camel case context, or
lower case context.
> understand the powernv9 machine.
>
> However, bookworm's Qemu
On 11/07/2024 4:50 pm, Anthony PERARD wrote:
> On Thu, Jul 11, 2024 at 04:16:29PM +0100, Andrew Cooper wrote:
>> On 11/07/2024 2:09 pm, Anthony PERARD wrote:
>>> We already have "parallel: 2" on the whole pipeline, give or take, but
>>> those are quick jobs so it might be worth it to run them a
On 11/07/2024 3:41 pm, Anthony PERARD wrote:
> On Thu, Jul 11, 2024 at 12:15:12PM +0100, Andrew Cooper wrote:
>> diff --git a/automation/build/debian/12-ppc64le.dockerfile
>> b/automation/build/debian/12-ppc64le.dockerfile
>> new file mode 100644
>> index ..3b311e675ef5
>> ---
On Thu, Jul 11, 2024 at 04:16:29PM +0100, Andrew Cooper wrote:
> On 11/07/2024 2:09 pm, Anthony PERARD wrote:
> > We already have "parallel: 2" on the whole pipeline, give or take, but
> > those are quick jobs so it might be worth it to run them a few more time
> > on a pipeline.
>
> I'm afraid I
On Thu, Jul 11, 2024 at 12:15:08PM +0100, Andrew Cooper wrote:
> These were removed from testing in Xen 4.18.
>
> Fixes: 3817e3c1b4b8 ("automation: Remove testing on Debian Jessie")
> Signed-off-by: Andrew Cooper
Reviewed-by: Anthony PERARD
Thanks,
--
Anthony Perard | Vates XCP-ng
flight 186761 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/186761/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl-raw 8 xen-boot fail like 186753
test-amd64-amd64-xl-qemut-win7-amd64
On 11/07/2024 2:37 pm, Anthony PERARD wrote:
> On Thu, Jul 11, 2024 at 12:15:11PM +0100, Andrew Cooper wrote:
>> Archlinux is a rolling distro, and is subject to arbitrary changes as the
>> container is rebuilt.
> I disagree about the changes been arbitrary, it is just new version of
> software.
On 11/07/2024 2:09 pm, Anthony PERARD wrote:
> On Thu, Jul 11, 2024 at 12:15:07PM +0100, Andrew Cooper wrote:
>> Randconfig builds pick CONFIG_DEBUG with 50% probability. Therefore
>> $foo{,-debug}-randconfig are two identical jobs with misleading names.
>>
>> Furthermore, arm64 has a randconfig
On Thu, Jul 11, 2024 at 12:15:12PM +0100, Andrew Cooper wrote:
> diff --git a/automation/build/debian/12-ppc64le.dockerfile
> b/automation/build/debian/12-ppc64le.dockerfile
> new file mode 100644
> index ..3b311e675ef5
> --- /dev/null
> +++
On 11.07.2024 13:28, Oleksii wrote:
> On Thu, 2024-07-11 at 12:50 +0200, Jan Beulich wrote:
>> On 11.07.2024 12:26, Oleksii wrote:
>>> On Thu, 2024-07-11 at 11:54 +0200, Jan Beulich wrote:
On 11.07.2024 11:40, Oleksii wrote:
> On Wed, 2024-07-10 at 14:38 +0200, Jan Beulich wrote:
>>
On 11.07.2024 14:14, Oleksii wrote:
> On Thu, 2024-07-11 at 11:25 +0200, Jan Beulich wrote:
>> On 11.07.2024 10:50, Oleksii wrote:
>>> On Wed, 2024-07-10 at 12:01 +0200, Jan Beulich wrote:
On 02.07.2024 13:23, Oleksii Kurochko wrote:
> @@ -101,8 +102,38 @@ static void
This work has been presented at Xen Summit 2024 during the
IOMMU paravirtualization and Xen IOMMU subsystem rework
design session.
Operating systems may want to have access to a IOMMU in order to do DMA
protection or implement certain features (e.g VFIO on Linux).
VFIO support is mandatory for
Introduce a new pv interface to manage the underlying IOMMU and manage contexts
and devices. This interface allows creation of new contexts from Dom0 and
addition of IOMMU mappings using guest PoV.
This interface doesn't allow creation of mapping to other domains.
Signed-off-by Teddy Astie
---
Current IOMMU subsystem has some limitations that make PV-IOMMU practically
impossible.
One of them is the assumtion that each domain is bound to a single "IOMMU
domain", which
also causes complications with quarantine implementation.
Moreover, current IOMMU subsystem is not entirely
Port the driver with guidances specified in iommu-contexts.md.
Add a arena-based allocator for allocating a fixed chunk of memory and
split it into 4k pages for use by the IOMMU contexts. This chunk size
is configurable with X86_ARENA_ORDER and dom0-iommu=arena-order=N.
Signed-off-by Teddy Astie
Based on docs/designs/iommu-contexts.md, implement the redesigned IOMMU
subsystem.
Signed-off-by Teddy Astie
---
Changed in V2:
* cleanup some unneeded includes
* fix dangling devices in context on detach
Changed in V3:
* add unlocked _iommu_lookup_page
* iommu_check_context+iommu_get_context
Some operating systems want to use IOMMU to implement various features (e.g
VFIO) or DMA protection.
This patch introduce a proposal for IOMMU paravirtualization for Dom0.
Signed-off-by Teddy Astie
---
docs/designs/pv-iommu.md | 105 +++
1 file changed, 105
flight 186762 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/186762/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
On Thu, Jul 11, 2024 at 12:15:11PM +0100, Andrew Cooper wrote:
> Archlinux is a rolling distro, and is subject to arbitrary changes as the
> container is rebuilt.
I disagree about the changes been arbitrary, it is just new version of
software. :-)
But I guess "arbirary changes" could be a
On 7/10/24 7:01 AM, Juergen Gross wrote:
The xen_nopvspin boot parameter is deprecated since 2019. nopvspin
can be used instead.
Remove the xen_nopvspin boot parameter and replace the xen_pvspin
variable use cases with nopvspin.
This requires to move the nopvspin variable out of the
On 7/10/24 5:37 AM, Juergen Gross wrote:
Cleanup the private header files in arch/x86/xen by merging them into
one file and by removing unneeded stuff.
Juergen Gross (2):
x86/xen: make some functions static
x86/xen: eliminate some private header files
arch/x86/xen/apic.c |
Release-Acked-By: Oleksii Kurochko
~ Oleksii
On Thu, 2024-07-11 at 12:15 +0100, Andrew Cooper wrote:
> Patch 1 fixes a bug in the containerize script
>
> Patches 2-5 remove useless/obsolete testing
>
> Patch 6 fixes a bug with the archlinux testing configuration
>
> Patches 7-9 adjust the
On Thu, Jul 11, 2024 at 12:15:10PM +0100, Andrew Cooper wrote:
> This is also End of Life.
>
> Signed-off-by: Andrew Cooper
Reviewed-by: Anthony PERARD
Thanks,
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
On 7/10/24 5:27 AM, Juergen Gross wrote:
Today Xen multicall debugging needs to be enabled via modifying a
define in a source file for getting debug data of multicall errors
encountered by users.
Switch multicall debugging to depend on a boot parameter "xen_mc_debug"
instead, enabling
On Thu, Jul 11, 2024 at 12:15:09PM +0100, Andrew Cooper wrote:
> Debian stretch is also End of Life. Update a couple of test steps to use
> bookworm instead.
>
> Signed-off-by: Andrew Cooper
Reviewed-by: Anthony PERARD
Thanks,
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen
On Thu, 2024-07-11 at 13:44 +0100, Julien Grall wrote:
> Hi Oleksii,
Hi Julien,
>
> On 11/07/2024 13:29, Oleksii wrote:
> > On Thu, 2024-07-11 at 12:54 +0100, Julien Grall wrote:
> > > Hi,
> > >
> > > On 11/07/2024 12:28, Oleksii wrote:
> > > > Add Julien as he asked basically the same question
- Original Message -
> From: "Andrew Cooper"
> To: "Fonyuy-Asheri Caleb"
> Cc: "xen-devel" , "Jan Beulich"
> , "Roger Pau Monné"
>
> Sent: Thursday, July 11, 2024 3:04:05 PM
> Subject: Re: Help with Understanding vcpu xstate restore error during vm
> migration
> On 11/07/2024 1:18
On Thu, Jul 11, 2024 at 12:15:07PM +0100, Andrew Cooper wrote:
> Randconfig builds pick CONFIG_DEBUG with 50% probability. Therefore
> $foo{,-debug}-randconfig are two identical jobs with misleading names.
>
> Furthermore, arm64 has a randconfig jobs for both the alpine and bookworm
> build
On 11/07/2024 1:18 pm, Fonyuy-Asheri Caleb wrote:
>>> Please do you mind giving me more insight on the logic currently implemented
>>> and maybe what is wrong with it? It will be important for me since what I'm
>>> doing is research work.
>> See 9e6dbbe8bf40^..267122a24c49
> What reference is this
On Thu, Jul 11, 2024 at 12:15:06PM +0100, Andrew Cooper wrote:
> Right now, most build containers use root. Archlinux, Fedora and Yocto set up
> a regular user called `user`.
>
> For those containers, trying to containerize as root fails, because
> CONTAINER_UID0=1 does nothing, whereas
Hi Oleksii,
On 11/07/2024 13:29, Oleksii wrote:
On Thu, 2024-07-11 at 12:54 +0100, Julien Grall wrote:
Hi,
On 11/07/2024 12:28, Oleksii wrote:
Add Julien as he asked basically the same question in another
thread.
Thanks!
On Thu, 2024-07-11 at 12:50 +0200, Jan Beulich wrote:
On
On Thu, 2024-07-11 at 12:54 +0100, Julien Grall wrote:
> Hi,
>
> On 11/07/2024 12:28, Oleksii wrote:
> > Add Julien as he asked basically the same question in another
> > thread.
>
> Thanks!
>
> >
> > On Thu, 2024-07-11 at 12:50 +0200, Jan Beulich wrote:
> > > On 11.07.2024 12:26, Oleksii
>> Please do you mind giving me more insight on the logic currently implemented
>> and maybe what is wrong with it? It will be important for me since what I'm
>> doing is research work.
>
> See 9e6dbbe8bf40^..267122a24c49
What reference is this please?
>
>> How do the values evc->size and
On Thu, 2024-07-11 at 11:25 +0200, Jan Beulich wrote:
> On 11.07.2024 10:50, Oleksii wrote:
> > On Wed, 2024-07-10 at 12:01 +0200, Jan Beulich wrote:
> > > On 02.07.2024 13:23, Oleksii Kurochko wrote:
> > > > @@ -101,8 +102,38 @@ static void do_unexpected_trap(const
> > > > struct
> > > >
Hi,
On 11/07/2024 12:28, Oleksii wrote:
Add Julien as he asked basically the same question in another thread.
Thanks!
On Thu, 2024-07-11 at 12:50 +0200, Jan Beulich wrote:
On 11.07.2024 12:26, Oleksii wrote:
On Thu, 2024-07-11 at 11:54 +0200, Jan Beulich wrote:
On 11.07.2024 11:40,
On Thu, 2024-07-11 at 11:50 +0100, Julien Grall wrote:
> Hi,
Hi Julien,
>
> On 11/07/2024 10:40, Oleksii wrote:
> > On Wed, 2024-07-10 at 14:38 +0200, Jan Beulich wrote:
> > > On 03.07.2024 12:42, Oleksii Kurochko wrote:
> > > > Except mapping of FDT, it is also printing command line passed
> >
On 11/07/2024 12:09 pm, Fonyuy-Asheri Caleb wrote:
> - Original Message -
>> From: "Andrew Cooper"
>> To: "Fonyuy-Asheri Caleb" , "xen-devel"
>>
>> Sent: Thursday, July 11, 2024 12:45:18 PM
>> Subject: Re: Help with Understanding vcpu xstate restore error during vm
>> migration
>> On
Add Julien as he asked basically the same question in another thread.
On Thu, 2024-07-11 at 12:50 +0200, Jan Beulich wrote:
> On 11.07.2024 12:26, Oleksii wrote:
> > On Thu, 2024-07-11 at 11:54 +0200, Jan Beulich wrote:
> > > On 11.07.2024 11:40, Oleksii wrote:
> > > > On Wed, 2024-07-10 at 14:38
Upgrade from Debian buster to bookworm, GCC 11.3 to 11.4 and to be a non-root
container.
Signed-off-by: Andrew Cooper
---
CC: Anthony PERARD
CC: Juergen Gross
CC: Roger Pau Monné
CC: Jan Beulich
CC: Stefano Stabellini
CC: Julien Grall
CC: Oleksii Kurochko
CC: Shawn Anastasio
---
Archlinux is a rolling distro, and is subject to arbitrary changes as the
container is rebuilt.
Signed-off-by: Andrew Cooper
---
CC: Anthony PERARD
CC: Juergen Gross
CC: Roger Pau Monné
CC: Jan Beulich
CC: Stefano Stabellini
CC: Julien Grall
CC: Oleksii Kurochko
CC: Shawn Anastasio
---
For starters, they're slightly smaller:
$ docker image list
registry.gitlab.com/xen-project/xen/debian 12-riscv64 772MB
registry.gitlab.com/xen-project/xen/debian 11-riscv64 422MB
registry.gitlab.com/xen-project/xen/archlinux current-riscv642.32GB
They
Debian stretch is also End of Life. Update a couple of test steps to use
bookworm instead.
Signed-off-by: Andrew Cooper
---
CC: Anthony PERARD
CC: Juergen Gross
CC: Roger Pau Monné
CC: Jan Beulich
CC: Stefano Stabellini
CC: Julien Grall
CC: Oleksii Kurochko
CC: Shawn Anastasio
---
qemu-system-ppc64/8.1.0-ppc64 was added because bullseye's Qemu didn't
understand the powernv9 machine.
However, bookworm's Qemu does, and this is preforable to maintaining a random
build of Qemu ourselves.
Add bookworm builds, and retain bullseye to keep our lower-bound toolchain
testing.
Right now, most build containers use root. Archlinux, Fedora and Yocto set up
a regular user called `user`.
For those containers, trying to containerize as root fails, because
CONTAINER_UID0=1 does nothing, whereas CONTAINER_UID0=0 forces the user away
from root.
To make CONTAINER_UID0=1 work
The containers are both much smaller, with stable toolchains over time, and
this at least means we're not doing all testing with a single compiler.
Rename the jobs to follow to sort coherently ($DISTRO-$VERSION-$ARCH-*) and
reposition the jobs to optimise starting the smoke test.
Signed-off-by:
These were removed from testing in Xen 4.18.
Fixes: 3817e3c1b4b8 ("automation: Remove testing on Debian Jessie")
Signed-off-by: Andrew Cooper
---
CC: Anthony PERARD
CC: Juergen Gross
CC: Roger Pau Monné
CC: Jan Beulich
CC: Stefano Stabellini
CC: Julien Grall
CC: Oleksii Kurochko
CC: Shawn
Make it non-root by default, and set XEN_TARGET_ARCH=ppc64 too.
Signed-off-by: Andrew Cooper
---
CC: Anthony PERARD
CC: Juergen Gross
CC: Roger Pau Monné
CC: Jan Beulich
CC: Stefano Stabellini
CC: Julien Grall
CC: Oleksii Kurochko
CC: Shawn Anastasio
---
This is also End of Life.
Signed-off-by: Andrew Cooper
---
CC: Anthony PERARD
CC: Juergen Gross
CC: Roger Pau Monné
CC: Jan Beulich
CC: Stefano Stabellini
CC: Julien Grall
CC: Oleksii Kurochko
CC: Shawn Anastasio
---
automation/build/ubuntu/trusty.dockerfile | 51 ---
... in the style of bookworm-ppc64le
Signed-off-by: Andrew Cooper
---
CC: Anthony PERARD
CC: Juergen Gross
CC: Roger Pau Monné
CC: Jan Beulich
CC: Stefano Stabellini
CC: Julien Grall
CC: Oleksii Kurochko
CC: Shawn Anastasio
---
automation/build/debian/11-ppc64le.dockerfile | 33
Patch 1 fixes a bug in the containerize script
Patches 2-5 remove useless/obsolete testing
Patch 6 fixes a bug with the archlinux testing configuration
Patches 7-9 adjust the PPC64 testing
Patches 10-11 adjust the RISCV64 testing
Patch 12 refreshes the custom GCC-IBT container
All changes
Randconfig builds pick CONFIG_DEBUG with 50% probability. Therefore
$foo{,-debug}-randconfig are two identical jobs with misleading names.
Furthermore, arm64 has a randconfig jobs for both the alpine and bookworm
build environments. Both use GCC 12.2, so we have 4 identical jobs. Delete 3
of
- Original Message -
> From: "Andrew Cooper"
> To: "Fonyuy-Asheri Caleb" , "xen-devel"
>
> Sent: Thursday, July 11, 2024 12:45:18 PM
> Subject: Re: Help with Understanding vcpu xstate restore error during vm
> migration
> On 11/07/2024 11:38 am, Fonyuy-Asheri Caleb wrote:
>> Hello,
>>
Hi,
On 11/07/2024 10:40, Oleksii wrote:
On Wed, 2024-07-10 at 14:38 +0200, Jan Beulich wrote:
On 03.07.2024 12:42, Oleksii Kurochko wrote:
Except mapping of FDT, it is also printing command line passed by
a DTB and initialize bootinfo from a DTB.
I'm glad the description isn't empty here.
On 11.07.2024 12:26, Oleksii wrote:
> On Thu, 2024-07-11 at 11:54 +0200, Jan Beulich wrote:
>> On 11.07.2024 11:40, Oleksii wrote:
>>> On Wed, 2024-07-10 at 14:38 +0200, Jan Beulich wrote:
On 03.07.2024 12:42, Oleksii Kurochko wrote:
> Except mapping of FDT, it is also printing command
flight 186760 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/186760/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 186748
test-amd64-amd64-libvirt-xsm 15
On 11/07/2024 11:38 am, Fonyuy-Asheri Caleb wrote:
> Hello,
>
> I am trying to understand the causes of the vcpu xstate restore error
> during live migration.
> I get the following error during live migration:
>
> xc: error: Failed to set vcpu0's xsave info (22 = Invalid argument):
> Internal
Hello,
I am trying to understand the causes of the vcpu xstate restore error during
live migration.
I get the following error during live migration:
xc: error: Failed to set vcpu0's xsave info (22 = Invalid argument): Internal
error
I was able to locate the failure point to the file
On Thu, 2024-07-11 at 11:54 +0200, Jan Beulich wrote:
> On 11.07.2024 11:40, Oleksii wrote:
> > On Wed, 2024-07-10 at 14:38 +0200, Jan Beulich wrote:
> > > On 03.07.2024 12:42, Oleksii Kurochko wrote:
> > > > Except mapping of FDT, it is also printing command line passed
> > > > by
> > > > a DTB
On 11.07.2024 11:55, Andrew Cooper wrote:
> So I was playing with rebuilding the OpenSUSE Tumbleweed container from
> scratch. (I've ~halfed it's size by correcting the dependencies).
>
> When diffutils is missing (package containing the `cmp` utility), a
> build of Xen proceeds as:
>
> make:
Bah - correcting Anthony's email (again).
(I clearly need to purge my address book more thoroughly.)
On 11/07/2024 10:55 am, Andrew Cooper wrote:
> So I was playing with rebuilding the OpenSUSE Tumbleweed container from
> scratch. (I've ~halfed it's size by correcting the dependencies).
>
>
So I was playing with rebuilding the OpenSUSE Tumbleweed container from
scratch. (I've ~halfed it's size by correcting the dependencies).
When diffutils is missing (package containing the `cmp` utility), a
build of Xen proceeds as:
make: Entering directory '/build/xen'
make: hostname: No such
On 11.07.2024 11:40, Oleksii wrote:
> On Wed, 2024-07-10 at 14:38 +0200, Jan Beulich wrote:
>> On 03.07.2024 12:42, Oleksii Kurochko wrote:
>>> Except mapping of FDT, it is also printing command line passed by
>>> a DTB and initialize bootinfo from a DTB.
>>
>> I'm glad the description isn't empty
On 11.07.2024 11:31, Oleksii wrote:
> On Wed, 2024-07-10 at 12:38 +0200, Jan Beulich wrote:
>> On 03.07.2024 12:42, Oleksii Kurochko wrote:
>>> --- a/xen/arch/riscv/include/asm/config.h
>>> +++ b/xen/arch/riscv/include/asm/config.h
>>> @@ -74,6 +74,9 @@
>>> #error "unsupported RV_STAGE1_MODE"
>>>
On Thu, 2024-07-11 at 11:21 +0200, Jan Beulich wrote:
> On 11.07.2024 11:00, Oleksii wrote:
> > On Wed, 2024-07-10 at 12:23 +0200, Jan Beulich wrote:
> > > On 03.07.2024 12:42, Oleksii Kurochko wrote:
> > > > From: Shawn Anastasio
> > > >
> > > > Arm's setup.c contains a collection of functions
On Wed, 2024-07-10 at 14:38 +0200, Jan Beulich wrote:
> On 03.07.2024 12:42, Oleksii Kurochko wrote:
> > Except mapping of FDT, it is also printing command line passed by
> > a DTB and initialize bootinfo from a DTB.
>
> I'm glad the description isn't empty here. However, ...
>
> > ---
On Wed, 2024-07-10 at 12:38 +0200, Jan Beulich wrote:
> On 03.07.2024 12:42, Oleksii Kurochko wrote:
> > Signed-off-by: Oleksii Kurochko
> > ---
> > xen/arch/riscv/include/asm/config.h | 6 +
> > xen/arch/riscv/include/asm/mm.h | 2 ++
> > xen/arch/riscv/mm.c | 37
> >
On 11.07.2024 10:50, Oleksii wrote:
> On Wed, 2024-07-10 at 12:01 +0200, Jan Beulich wrote:
>> On 02.07.2024 13:23, Oleksii Kurochko wrote:
>>> @@ -101,8 +102,38 @@ static void do_unexpected_trap(const struct
>>> cpu_user_regs *regs)
>>> die();
>>> }
>>>
>>> +static bool
On 11.07.2024 11:00, Oleksii wrote:
> On Wed, 2024-07-10 at 12:23 +0200, Jan Beulich wrote:
>> On 03.07.2024 12:42, Oleksii Kurochko wrote:
>>> From: Shawn Anastasio
>>>
>>> Arm's setup.c contains a collection of functions for parsing memory
>>> map
>>> and other boot information from a device
On Wed, 2024-07-10 at 12:23 +0200, Jan Beulich wrote:
> On 03.07.2024 12:42, Oleksii Kurochko wrote:
> > From: Shawn Anastasio
> >
> > Arm's setup.c contains a collection of functions for parsing memory
> > map
> > and other boot information from a device tree. Since these routines
> > are
> >
flight 186757 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/186757/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-qemuu-freebsd12-amd64 19 guest-localmigrate/x10 fail in
186750 pass in 186757
On Thu, 2024-07-11 at 10:14 +0200, Michal Orzel wrote:
> Hi Oleksii,
>
> On 11/07/2024 10:11, Oleksii wrote:
> >
> >
> > On Wed, 2024-07-10 at 10:44 +0100, Andrew Cooper wrote:
> > > On 10/07/2024 10:37 am, Michal Orzel wrote:
> > > > Switch to using
> > > >
On Wed, 2024-07-10 at 12:07 +0200, Jan Beulich wrote:
> On 10.07.2024 12:06, Jan Beulich wrote:
> > On 02.07.2024 13:23, Oleksii Kurochko wrote:
> > > Signed-off-by: Oleksii Kurochko
> > > Acked-by: Alistair Francis
> > > ---
> > > xen/arch/riscv/setup.c | 16
> > > 1 file
On Wed, 2024-07-10 at 12:01 +0200, Jan Beulich wrote:
> On 02.07.2024 13:23, Oleksii Kurochko wrote:
> > Signed-off-by: Oleksii Kurochko
> > ---
> > xen/arch/riscv/Kconfig | 1 +
> > xen/arch/riscv/traps.c | 31 +++
> > xen/common/bug.c | 1 +
> > 3 files
On 11/07/2024 9:19 am, Oleksii wrote:
> On Wed, 2024-07-10 at 11:50 +0200, Jan Beulich wrote:
>> On 02.07.2024 13:23, Oleksii Kurochko wrote:
>>> --- a/xen/arch/riscv/traps.c
>>> +++ b/xen/arch/riscv/traps.c
>>> @@ -12,6 +12,18 @@
>>> #include
>>> #include
>>>
>>> +/*
>>> + * Initialize the
On Wed, 2024-07-10 at 11:50 +0200, Jan Beulich wrote:
> On 02.07.2024 13:23, Oleksii Kurochko wrote:
> > --- a/xen/arch/riscv/traps.c
> > +++ b/xen/arch/riscv/traps.c
> > @@ -12,6 +12,18 @@
> > #include
> > #include
> >
> > +/*
> > + * Initialize the trap handling.
> > + *
> > + * The
On Wed, 2024-07-10 at 11:46 +0200, Jan Beulich wrote:
> On 02.07.2024 13:23, Oleksii Kurochko wrote:
> > As common code is available it is better to use printk() instead
> > of early_printk().
>
> IOW the function is not just available (allowing linking to succeed),
> but is also fully functional
Hi Oleksii,
On 11/07/2024 10:11, Oleksii wrote:
>
>
> On Wed, 2024-07-10 at 10:44 +0100, Andrew Cooper wrote:
>> On 10/07/2024 10:37 am, Michal Orzel wrote:
>>> Switch to using
>>> https://gitlab.com/xen-project/imagebuilder.git which
>>> should be considered official ImageBuilder repo.
>>>
>>>
On Wed, 2024-07-10 at 10:44 +0100, Andrew Cooper wrote:
> On 10/07/2024 10:37 am, Michal Orzel wrote:
> > Switch to using
> > https://gitlab.com/xen-project/imagebuilder.git which
> > should be considered official ImageBuilder repo.
> >
> > Take the opportunity to truncate the git history when
Hi all,
On 2024/7/8 19:41, Jiqian Chen wrote:
> The gsi of a passthrough device must be configured for it to be
> able to be mapped into a hvm domU.
> But When dom0 is PVH, the gsis may not get registered(see below
> clarification), it causes the info of apic, pin and irq not be
> added into
97 matches
Mail list logo
