native-image: Graal's ForeignAPISupport is amd64 only #46731

Karm · 2025-03-11T16:22:42Z

Summary:

We don't have MacOS support for AWT extension yet. It might be trivial, but it's not coded in yet, so the extension needs to bail out just like on Windows. I am afraid that not having MacOS excluded via UnsupportedOSBuildItem is an artifact of moving DarwinFeature to AWT extension. The result is that the build might pass, but the Quarkus app won't start. If that is the desired design, we should allow the same on Windows and remove its UnsupportedOSBuildItem. I think the DarwinFeature previously was in core on purpose, to allow for building apps that effectively won't need to initialize AWT at runtime, i.e. don't need full AWT extension. @zakkak ? Ideas?
GraalVM has FFI/FFM implemented for amd64 arch only, so effectively starting Mandrel/GraalVM 24.2, i.e. Mandrel for JDK 24, we are losing AWT support on Linux aarch64 where it used to work
UBI9's microdnf requires -y, so container tests hanged on Is this ok [y/N]:
I tested all combinations that made sense to me and where I had access to HW, e.g. I skipped natively amd64 based MacOS. I used either our Mandrel 24.2 / JDK 24 ea builds or GraalVM CE 25 ea dev builds.
🟢 - run went as expected; spoiler alert: All runs went as expected.

Tested

Windows amd64 hosted 🟢

Expected: 🟠 - SKIPPED, AWT Quarkus unsupported OS
Actual: 🟠

C:\tmp\quarkus(issue-46235 -> origin)
λ mvnw verify -f integration-tests/pom.xml -pl awt  -Pnative
    -Dquarkus.native.container-build=false -Dquarkus.container-image.build=false -DskipITs=false

[ERROR] Caused by: java.lang.UnsupportedOperationException:
Windows AWT integration is not ready in Quarkus native-image and would result in java.lang.UnsatisfiedLinkError: no awt in java.library.path.

Windows amd64 with Linux amd64 builder image 🟢

Expected: 🟢
Actual: 🟢

λ mvnw verify -f integration-tests/pom.xml -pl awt -Pnative 
    -Dquarkus.native.builder-image=quay.io/karmkarm/ubi9-quarkus-mandrel-builder-image:jdk-24-amd64
    -Dquarkus.native.container-build=true -Dquarkus.container-image.build=true 
...

Finished generating 'quarkus-integration-test-awt-999-SNAPSHOT-runner' in 15m 51s.
...
[INFO] [io.quarkus.container.image.docker.common.deployment.CommonProcessor]
Executing the following command to build image: 
'podman build -f C:\tmp\quarkus\integration-tests\awt\src\main\docker\Dockerfile.native -t karm/quarkus-integration-test-awt:999-SNAPSHOT C:\tmp\quarkus\integration-tests\awt'
...
INFO  [io.qua.tes.com.DefaultDockerContainerLauncher] (main) 
Executing "podman run --name quarkus-integration-test-GQcdk -i --rm -p 8081:8081 -p 8444:8444 --net=quarkus-integration-test-UNOtv --env QUARKUS_LOG_CATEGORY__IO_QUARKUS__LEVEL=INFO --env QUARKUS_HTTP_PORT=8081 --env QUARKUS_HTTP_SSL_PORT=8444 --env TEST_URL=http://localhost:8081 --env QUARKUS_PROFILE=prod --env QUARKUS_CONTAINER_IMAGE_BUILD=true --env QUARKUS_NATIVE_CONTAINER_BUILD=true --env QUARKUS_NATIVE_BUILDER_IMAGE=quay.io/karmkarm/ubi9-quarkus-mandrel-builder-image:jdk-24-amd64 karm/quarkus-integration-test-awt:999-SNAPSHOT"
...
[INFO] Tests run: 41, Failures: 0, Errors: 0, Skipped: 0

MacOS aarch64 hosted 🟢

Expected: 🟠 - SKIPPED, AWT Quarkus unsupported OS
Actual: 🟠

[ERROR] Caused by: java.lang.UnsupportedOperationException:
    MacOS AWT integration is not ready in Quarkus native-image and would result in
    java.lang.UnsatisfiedLinkError: Can't load library: awt | java.library.path = [.].,
    AWT needs JDK's JEP 454 FFI/FFM support and that is not available for AArch64 with GraalVM's native-image,
    see: https://www.graalvm.org/latest/reference-manual/native-image/native-code-interoperability/foreign-interface/#foreign-functions

MacOS amd64 (via Rosetta) hosted 🟢

Expected: 🟠 - SKIPPED, AWT Quarkus unsupported OS
Actual: 🟠

[ERROR] Caused by: java.lang.UnsupportedOperationException:
    MacOS AWT integration is not ready in Quarkus native-image and would result in
    java.lang.UnsatisfiedLinkError: Can't load library: awt | java.library.path = [.].

MacOS amd64 with Linux amd64 builder

N/A - I don't have access to such HW and I don't want to try to
remove Podman machine from my MacOS aarch64 systems and try to run
podman there via Rosetta. It should work just like Windows above :-)

MacOS aarch64 with Linux aarch64 builder image 🟢

Expected: 🟠 - SKIPPED, ForeignAPISupport is amd64 only
Actual: 🟠

[ERROR] Caused by: java.lang.UnsupportedOperationException:
    AWT needs JDK's JEP 454 FFI/FFM support and that is not available for AArch64 with GraalVM's native-image,
    see: https://www.graalvm.org/latest/reference-manual/native-image/native-code-interoperability/foreign-interface/#foreign-functions

Linux amd64 hosted 🟢

Expected: 🟢
Actual: 🟢

$ ./mvnw verify -f integration-tests/pom.xml -pl awt  -Pnative
    -Dquarkus.native.container-build=false -Dquarkus.container-image.build=false -DskipITs=false 
OK

Linux amd64 with Linux amd64 builder image 🟢

Expected: 🟢
Actual: 🟢

$ ./mvnw verify -f integration-tests/pom.xml -pl awt -Pnative
    -Dquarkus.native.builder-image=quay.io/karmkarm/ubi9-quarkus-mandrel-builder-image:jdk-24-amd64
    -Dquarkus.native.container-build=true -Dquarkus.container-image.build=true
OK

Linux aarch64 hosted 🟢

Expected: 🟠 - SKIPPED, ForeignAPISupport is amd64 only
Actual: 🟠

$ ./mvnw verify -f integration-tests/pom.xml -pl awt  -Pnative
    -Dquarkus.native.container-build=false -Dquarkus.container-image.build=false -DskipITs=false 

[ERROR] Caused by: java.lang.UnsupportedOperationException:
    AWT needs JDK's JEP 454 FFI/FFM support and that is not available for AArch64 with GraalVM's native-image,
    see: https://www.graalvm.org/latest/reference-manual/native-image/native-code-interoperability/foreign-interface/#foreign-functions

Linux aarch64 with Linux aarch64 builder image 🟢

Expected: 🟠 - SKIPPED, ForeignAPISupport is amd64 only
Actual: 🟠

$ ./mvnw verify -f integration-tests/pom.xml -pl awt -Pnative
    -Dquarkus.native.builder-image=quay.io/karmkarm/ubi9-quarkus-mandrel-builder-image:jdk-24-aarch64
    -Dquarkus.native.container-build=true -Dquarkus.container-image.build=true -DskipITs=false

[ERROR] Caused by: java.lang.UnsupportedOperationException:
    AWT needs JDK's JEP 454 FFI/FFM support and that is not available for AArch64 with GraalVM's native-image,
    see: https://www.graalvm.org/latest/reference-manual/native-image/native-code-interoperability/foreign-interface/#foreign-functions

Thanks for feedback

quarkus-bot · 2025-03-11T16:22:46Z

Thanks for your pull request!

Your pull request does not follow our editorial rules. Could you have a look?

title should preferably start with an uppercase character (if it makes sense!)

_{This message is automatically generated by a bot.}

quarkus-bot · 2025-03-11T16:23:03Z

/cc @galderz (awt)

github-actions · 2025-03-11T20:25:51Z

🎊 PR Preview 7843777 has been successfully built and deployed to https://quarkus-pr-main-46731-preview.surge.sh/version/main/guides/

Images of blog posts older than 3 months are not available.
Newsletters older than 3 months are not available.

Karm · 2025-03-12T07:26:34Z

No idea why would Micrometer get flaky on this PR. Do you understand the CI results @ebullient @brunobat?

zakkak

LGTM.

I think the DarwinFeature previously was in core on purpose, to allow for building apps that effectively won't need to initialize AWT at runtime, i.e. don't need full AWT extension.

By DarwinFeature are you referring to https://github.com/quarkusio/quarkus/blob/main/extensions/awt/runtime/src/main/java/io/quarkus/awt/runtime/graal/DarwinAwtFeature.java ?

AFAIS it was always under the awt extension #21566

The result is that the build might pass, but the Quarkus app won't start. If that is the desired design,

No, I don't think this is desired. Reporting it as unsupported seems the right thing to me.

GraalVM has FFI/FFM implemented for amd64 arch only, so effectively starting Mandrel/GraalVM 24.2, i.e. Mandrel for JDK 24, we are losing AWT support on Linux aarch64 where it used to work

We will need to list this as a known issue, in the migration guide I guess.

UBI9's microdnf requires -y, so container tests hanged on Is this ok [y/N]:

Good catch, I think we need this in ASAP. So if this PR ends up being delayed I would suggest openning a separate PR with just 1de05f2

Thank you @Karm

core/deployment/src/main/java/io/quarkus/deployment/pkg/steps/NativeImageBuildStep.java

gsmet · 2025-03-12T09:10:51Z

@Karm could you create a specific PR for the microdnf changes? This is something we want to backport right away. The rest of the PR requires more thoughts.

Karm · 2025-03-12T12:57:00Z

@Karm could you create a specific PR for the microdnf changes? This is something we want to backport right away. The rest of the PR requires more thoughts.

@gsmet

#46763

Karm · 2025-03-12T14:16:31Z

@zakkak Thanks for the review

I think the DarwinFeature previously was in core on purpose, to allow for building apps that effectively won't need to initialize AWT at runtime, i.e. don't need full AWT extension.

By DarwinFeature are you referring to https://github.com/quarkusio/quarkus/blob/main/extensions/awt/runtime/src/main/java/io/quarkus/awt/runtime/graal/DarwinAwtFeature.java ?

AFAIS it was always under the awt extension #21566

Hmm, I confused it with AwtImageIO.java as I was trying to reason about why wasn't macOS excluded too. You are right.

The result is that the build might pass, but the Quarkus app won't start. If that is the desired design,

No, I don't think this is desired. Reporting it as unsupported seems the right thing to me.

Ack.

GraalVM has FFI/FFM implemented for amd64 arch only, so effectively starting Mandrel/GraalVM 24.2, i.e. Mandrel for JDK 24, we are losing AWT support on Linux aarch64 where it used to work

We will need to list this as a known issue, in the migration guide I guess.

Do I just edit this directly or is it generated?
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.19

UBI9's microdnf requires -y, so container tests hanged on Is this ok [y/N]:

Good catch, I think we need this in ASAP. So if this PR ends up being delayed I would suggest openning a separate PR with just 1de05f2

Ack. Done.

Karm · 2025-03-12T14:17:16Z

The rest of the PR requires more thoughts.

@gsmet , any specific pointers?

zakkak · 2025-03-12T18:37:45Z

Do I just edit this directly or is it generated?

Directly

brunobat · 2025-03-12T18:55:03Z

No idea why would Micrometer get flaky on this PR. Do you understand the CI results @ebullient @brunobat?

Nope.

gsmet · 2025-03-13T16:02:51Z

The rest of the PR requires more thoughts.

@Karm sorry, it was "more thoughts" as "if it was safe to be backported or not" :). Do you think we need a backport for this one?

I rebased to drop the additional commit and will merge when CI is green.

quarkus-bot · 2025-03-13T19:28:30Z

Status for workflow `Quarkus CI`

This is the status report for running Quarkus CI on commit a04a213.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17 Windows

📦 extensions/micrometer-opentelemetry/deployment

✖ io.quarkus.micrometer.opentelemetry.deployment.compatibility.MicrometerTimedInterceptorTest.testTimeMethod_Uni - History

Stream has no elements - java.lang.IllegalArgumentException

java.lang.IllegalArgumentException: Stream has no elements
	at io.quarkus.micrometer.opentelemetry.deployment.common.MetricDataFilter.lambda$lastReading$2(MetricDataFilter.java:213)
	at java.base/java.util.Optional.orElseThrow(Optional.java:403)
	at io.quarkus.micrometer.opentelemetry.deployment.common.MetricDataFilter.lastReading(MetricDataFilter.java:213)
	at io.quarkus.micrometer.opentelemetry.deployment.common.MetricDataFilter.lastReadingDataPoint(MetricDataFilter.java:231)
	at io.quarkus.micrometer.opentelemetry.deployment.compatibility.MicrometerTimedInterceptorTest.testTimeMethod_Uni(MicrometerTimedInterceptorTest.java:174)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)
	at io.quarkus.test.QuarkusUnitTest.runExtensionMethod(QuarkusUnitTest.java:521)

zakkak · 2025-03-13T19:51:18Z

@gsmet I would only consider the part that handles

We don't have MacOS support for AWT extension yet. It might be trivial, but it's not coded in yet, so the extension needs to bail out just like on Windows.

for backporting, but IMO it's not worth it.

zakkak · 2025-03-13T20:57:02Z

@Karm it looks like AArch64 support will land in GraalVM for JDK 25, see oracle/graal#10856

Karm · 2025-03-14T00:35:00Z

@gsmet

@Karm sorry, it was "more thoughts" as "if it was safe to be backported or not" :). Do you think we need a backport for this one?

I don't think so.

Karm · 2025-03-14T00:37:25Z

@Karm it looks like AArch64 support will land in GraalVM for JDK 25, see oracle/graal#10856

@zakkak

Aww, great. Gonna give their branch a shot. I will make a note to see to removing these if-else version checks for 25 if it's sound.

Karm · 2025-03-14T07:33:50Z

@zakkak

Migration guide updated as https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.19/_compare/8ffa458b7951b8da1e26a86958243dd6edb4b55d...0d6004747c902b7e230e8e8a3209c765d6e8266c

zakkak · 2025-03-14T12:16:23Z

@zakkak

Migration guide updated as https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.19/_compare/8ffa458b7951b8da1e26a86958243dd6edb4b55d...0d6004747c902b7e230e8e8a3209c765d6e8266c

@Karm there is a typo in your update. "To switch back to UBI 8" suggests using ubi9

Furthermore, we need to add a note about

GraalVM has FFI/FFM implemented for amd64 arch only, so effectively starting Mandrel/GraalVM 24.2, i.e. Mandrel for JDK 24, we are losing AWT support on Linux aarch64 where it used to work

Karm · 2025-03-14T12:20:19Z

@zakkak
Migration guide updated as https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.19/_compare/8ffa458b7951b8da1e26a86958243dd6edb4b55d...0d6004747c902b7e230e8e8a3209c765d6e8266c

@Karm there is a typo in your update. "To switch back to UBI 8" suggests using ubi9

Furthermore, we need to add a note about

GraalVM has FFI/FFM implemented for amd64 arch only, so effectively starting Mandrel/GraalVM 24.2, i.e. Mandrel for JDK 24, we are losing AWT support on Linux aarch64 where it used to work

gonna fix copy-paste typo
I'm waiting for my build to test AWT with the recently merged FFM/FFI aarch64 JDK 25 support, gonna update text presently

Karm · 2025-03-14T15:36:15Z

@zakkak @gsmet

AWT Linux aarch64 note regarding JDK 24:

https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.19/_compare/2ae1c89052997e6679e3e970035f8b5cd02c5395...7b5faaeccbec05c436d19fb8f0f940a381376d72

zakkak · 2025-03-14T18:23:04Z

Thank you @Karm

Karm · 2025-04-02T11:30:30Z

@zakkak @gsmet added backport label to help with adopting JDK 24.

Karm · 2025-04-02T11:31:25Z

JDK 25 won't have this limitation any more though...

quarkus-bot bot added area/core area/graphics labels Mar 11, 2025

Karm marked this pull request as draft March 11, 2025 16:23

Karm requested a review from zakkak March 11, 2025 16:28

Karm self-assigned this Mar 11, 2025

quarkus-bot bot added the area/documentation label Mar 11, 2025

Karm requested a review from galderz March 11, 2025 20:32

Karm marked this pull request as ready for review March 11, 2025 20:32

This comment has been minimized.

Sign in to view

quarkus-bot bot added the triage/flaky-test label Mar 11, 2025

zakkak approved these changes Mar 12, 2025

View reviewed changes

core/deployment/src/main/java/io/quarkus/deployment/pkg/steps/NativeImageBuildStep.java Show resolved Hide resolved

Karm mentioned this pull request Mar 12, 2025

UBI9 microdnf requires -y #46763

Merged

Graal's ForeignAPISupport is amd64 only

a04a213

gsmet force-pushed the issue-46235 branch from 1de05f2 to a04a213 Compare March 13, 2025 16:00

zakkak merged commit 52b28e2 into quarkusio:main Mar 14, 2025
58 checks passed

quarkus-bot bot added this to the 3.22 - main milestone Mar 14, 2025

quarkus-bot bot added the kind/bugfix label Mar 14, 2025

zakkak mentioned this pull request Mar 26, 2025

Native image build fails on Mac M2 with GraalVM 24 #46988

Closed

Karm added the triage/backport-3.20 label Apr 2, 2025

Karm mentioned this pull request Apr 8, 2025

Versions, CI cleanup, Linux & MacOS aarch64 GHA Karm/mandrel-integration-tests#322

Merged

gsmet added the triage/backport label Apr 14, 2025

gsmet modified the milestones: 3.22 - main, 3.21.3 Apr 15, 2025

gsmet removed the triage/backport label Apr 15, 2025

gastaldi mentioned this pull request Jun 17, 2025

MacOS AWT integration error with quarkus-pdfbox in native image build #48422

Closed

native-image: Graal's ForeignAPISupport is amd64 only #46731

native-image: Graal's ForeignAPISupport is amd64 only #46731

Uh oh!

Conversation

Karm commented Mar 11, 2025 • edited by gsmet Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Tested

Windows amd64 hosted 🟢

Windows amd64 with Linux amd64 builder image 🟢

MacOS aarch64 hosted 🟢

MacOS amd64 (via Rosetta) hosted 🟢

MacOS amd64 with Linux amd64 builder

MacOS aarch64 with Linux aarch64 builder image 🟢

Linux amd64 hosted 🟢

Linux amd64 with Linux amd64 builder image 🟢

Linux aarch64 hosted 🟢

Linux aarch64 with Linux aarch64 builder image 🟢

Uh oh!

quarkus-bot bot commented Mar 11, 2025

Uh oh!

quarkus-bot bot commented Mar 11, 2025

Uh oh!

github-actions bot commented Mar 11, 2025

Uh oh!

This comment has been minimized.

Karm commented Mar 12, 2025

Uh oh!

zakkak left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

gsmet commented Mar 12, 2025

Uh oh!

Karm commented Mar 12, 2025

Uh oh!

Karm commented Mar 12, 2025

Uh oh!

Karm commented Mar 12, 2025

Uh oh!

zakkak commented Mar 12, 2025

Uh oh!

brunobat commented Mar 12, 2025

Uh oh!

gsmet commented Mar 13, 2025

Uh oh!

quarkus-bot bot commented Mar 13, 2025 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Status for workflow Quarkus CI

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17 Windows

📦 extensions/micrometer-opentelemetry/deployment

Uh oh!

zakkak commented Mar 13, 2025

Uh oh!

zakkak commented Mar 13, 2025

Uh oh!

Karm commented Mar 14, 2025

Uh oh!

Karm commented Mar 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Karm commented Mar 14, 2025

Uh oh!

zakkak commented Mar 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Karm commented Mar 14, 2025

Uh oh!

Karm commented Mar 14, 2025

Uh oh!

zakkak commented Mar 14, 2025

Uh oh!

Karm commented Apr 2, 2025

Uh oh!

Karm commented Apr 2, 2025

Uh oh!

Reviewers

Assignees

Labels

Karm commented Mar 11, 2025 •

edited by gsmet

Loading

quarkus-bot bot commented Mar 13, 2025 •

edited by github-actions bot

Loading

Status for workflow `Quarkus CI`

Karm commented Mar 14, 2025 •

edited

Loading

zakkak commented Mar 14, 2025 •

edited

Loading