Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch Test VHD to Ubuntu 24.04 #773

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

tjones60
Copy link
Contributor

@tjones60 tjones60 commented Feb 3, 2025

@smalis-msft tried this awhile back, trying again. Running CI to see what goes wrong and then hopefully fix any issues. In local testing, the switch reduced the ubuntu boot test from 157 seconds to 35 seconds, due to not waiting for network.

Fixes #385

@tjones60 tjones60 requested a review from a team as a code owner February 3, 2025 23:07
@microsoft microsoft deleted a comment from smmalis37 Feb 4, 2025
@smalis-msft
Copy link
Contributor

smalis-msft commented Feb 4, 2025

First run results look like what I remember, vbs failed, but fixing the networking issue makes everything else boot.

@smalis-msft
Copy link
Contributor

Things I see in a quick scan of the logs:

Unable to find the root filesystem (ultimately why we time out)

2025-02-04T00:37:21.6104147Z 2025-02-04T00:33:30.477196Z INFO uefi_log: Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6104231Z 2025-02-04T00:33:30.488663Z INFO uefi_log: done.
2025-02-04T00:37:21.6104420Z 2025-02-04T00:33:30.563855Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6104597Z 2025-02-04T00:33:30.636133Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6104779Z 2025-02-04T00:33:30.714420Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6104955Z 2025-02-04T00:33:30.790888Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6105132Z 2025-02-04T00:33:30.869749Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6105316Z 2025-02-04T00:33:30.948315Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6105492Z 2025-02-04T00:33:31.032873Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6105673Z 2025-02-04T00:33:31.112184Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6105949Z 2025-02-04T00:33:31.195246Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6106128Z 2025-02-04T00:33:31.259203Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6106303Z 2025-02-04T00:33:31.334194Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6106481Z 2025-02-04T00:33:31.404079Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6106659Z 2025-02-04T00:33:31.483595Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6106836Z 2025-02-04T00:33:31.559764Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6107015Z 2025-02-04T00:33:31.642192Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6107191Z 2025-02-04T00:33:31.720349Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6107373Z 2025-02-04T00:33:31.799665Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6107548Z 2025-02-04T00:33:31.876550Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6107727Z 2025-02-04T00:33:31.958589Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6107936Z 2025-02-04T00:33:32.029109Z INFO uefi_log: mdadm: error opening /dev/md?*: No such file or directory
2025-02-04T00:37:21.6108113Z 2025-02-04T00:33:32.093858Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6108373Z 2025-02-04T00:33:32.165775Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6108556Z 2025-02-04T00:33:32.243405Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6108734Z 2025-02-04T00:33:32.321751Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6108914Z 2025-02-04T00:33:32.402300Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6109093Z 2025-02-04T00:33:32.483309Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6109267Z 2025-02-04T00:33:32.571885Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6109446Z 2025-02-04T00:33:32.657530Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6109626Z 2025-02-04T00:33:32.744822Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6109803Z 2025-02-04T00:33:32.827489Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6109988Z 2025-02-04T00:33:32.909270Z INFO uefi_log: mdadm: No devices listed in conf file were found.
2025-02-04T00:37:21.6110072Z 2025-02-04T00:33:32.934686Z INFO uefi_log: done.
2025-02-04T00:37:21.6110302Z 2025-02-04T00:33:33.016776Z INFO uefi_log: Gave up waiting for root file system device. Common problems:
2025-02-04T00:37:21.6110459Z 2025-02-04T00:33:33.059053Z INFO uefi_log: - Boot args (cat /proc/cmdline)
2025-02-04T00:37:21.6110666Z 2025-02-04T00:33:33.129791Z INFO uefi_log: - Check rootdelay= (did the system wait long enough?)
2025-02-04T00:37:21.6110851Z 2025-02-04T00:33:33.187463Z INFO uefi_log: - Missing modules (cat /proc/modules; ls /dev)
2025-02-04T00:37:21.6111277Z 2025-02-04T00:33:33.269874Z INFO uefi_log: ALERT! LABEL=cloudimg-rootfs does not exist. Dropping to a shell!

Some MSR access error

2025-02-04T00:37:21.6089072Z 2025-02-04T00:32:54.339964Z INFO uefi_log: [ 44.058367] unchecked MSR access error: WRMSR to 0x40000092 (tried to write 0x00000000001000f3) at rIP: 0xffffffff86ec2b04 (native_write_msr+0x4/0x40)
2025-02-04T00:37:21.6089211Z 2025-02-04T00:32:54.371059Z INFO uefi_log: [ 44.231283] Call Trace:
2025-02-04T00:37:21.6089334Z 2025-02-04T00:32:54.397373Z INFO uefi_log: [ 44.262357]
2025-02-04T00:37:21.6089509Z 2025-02-04T00:32:54.446847Z INFO uefi_log: [ 44.288707] ? show_stack_regs+0x23/0x40
2025-02-04T00:37:21.6089675Z 2025-02-04T00:32:54.500070Z INFO uefi_log: [ 44.338326] ? ex_handler_msr+0x10a/0x180
2025-02-04T00:37:21.6089851Z 2025-02-04T00:32:54.551951Z INFO uefi_log: [ 44.391503] ? fixup_exception+0x183/0x390
2025-02-04T00:37:21.6090039Z 2025-02-04T00:32:54.609233Z INFO uefi_log: [ 44.443413] ? gp_try_fixup_and_notify+0x23/0xe0
2025-02-04T00:37:21.6090231Z 2025-02-04T00:32:54.669684Z INFO uefi_log: [ 44.500614] ? exc_general_protection+0x15e/0x480
2025-02-04T00:37:21.6090411Z 2025-02-04T00:32:54.722376Z INFO uefi_log: [ 44.561173] ? vmap_range_noflush+0x40e/0x6d0
2025-02-04T00:37:21.6090604Z 2025-02-04T00:32:54.781365Z INFO uefi_log: [ 44.613653] ? asm_exc_general_protection+0x27/0x30
2025-02-04T00:37:21.6090771Z 2025-02-04T00:32:54.827368Z INFO uefi_log: [ 44.672778] ? native_write_msr+0x4/0x40
2025-02-04T00:37:21.6091036Z 2025-02-04T00:32:54.884895Z INFO uefi_log: [ 44.718658] ? hv_set_non_nested_register+0x8f/0xa0
2025-02-04T00:37:21.6091209Z 2025-02-04T00:32:54.929144Z INFO uefi_log: [ 44.776355] hv_set_register+0x52/0x70
2025-02-04T00:37:21.6091407Z 2025-02-04T00:32:54.995042Z INFO uefi_log: [ 44.820473] hv_synic_enable_regs+0x179/0x260 [hv_vmbus]
2025-02-04T00:37:21.6091598Z 2025-02-04T00:32:55.054908Z INFO uefi_log: [ 44.886356] ? srso_alias_return_thunk+0x5/0xfbef5
2025-02-04T00:37:21.6091780Z 2025-02-04T00:32:55.112462Z INFO uefi_log: [ 44.946522] hv_synic_init+0x11/0x30 [hv_vmbus]
2025-02-04T00:37:21.6091969Z 2025-02-04T00:32:55.174886Z INFO uefi_log: [ 45.003681] ? __pfx_hv_synic_init+0x10/0x10 [hv_vmbus]
2025-02-04T00:37:21.6092152Z 2025-02-04T00:32:55.231067Z INFO uefi_log: [ 45.066128] cpuhp_invoke_callback+0x348/0x530
2025-02-04T00:37:21.6096099Z 2025-02-04T00:32:55.295429Z INFO uefi_log: [ 45.122462] ? srso_alias_return_thunk+0x5/0xfbef5
2025-02-04T00:37:21.6096328Z 2025-02-04T00:32:55.343309Z INFO uefi_log: [ 45.187042] ? __schedule+0x284/0x6b0
2025-02-04T00:37:21.6096532Z 2025-02-04T00:32:55.407380Z INFO uefi_log: [ 45.234456] ? srso_alias_return_thunk+0x5/0xfbef5
2025-02-04T00:37:21.6096717Z 2025-02-04T00:32:55.463022Z INFO uefi_log: [ 45.298635] cpuhp_thread_fun+0x144/0x1f0
2025-02-04T00:37:21.6096910Z 2025-02-04T00:32:55.521881Z INFO uefi_log: [ 45.354301] ? __pfx_smpboot_thread_fn+0x10/0x10
2025-02-04T00:37:21.6097092Z 2025-02-04T00:32:55.571114Z INFO uefi_log: [ 45.413049] smpboot_thread_fn+0xe3/0x1e0
2025-02-04T00:37:21.6097249Z 2025-02-04T00:32:55.610854Z INFO uefi_log: [ 45.462353] kthread+0xf2/0x120
2025-02-04T00:37:21.6097413Z 2025-02-04T00:32:55.658213Z INFO uefi_log: [ 45.502341] ? __pfx_kthread+0x10/0x10
2025-02-04T00:37:21.6097575Z 2025-02-04T00:32:55.704866Z INFO uefi_log: [ 45.549648] ret_from_fork+0x47/0x70
2025-02-04T00:37:21.6097736Z 2025-02-04T00:32:55.754595Z INFO uefi_log: [ 45.596343] ? __pfx_kthread+0x10/0x10
2025-02-04T00:37:21.6097908Z 2025-02-04T00:32:55.806956Z INFO uefi_log: [ 45.646034] ret_from_fork_asm+0x1b/0x30
2025-02-04T00:37:21.6098034Z 2025-02-04T00:32:55.837785Z INFO uefi_log: [ 45.698378]

A bunch of post message failures

2025-02-04T00:37:21.6098242Z 2025-02-04T00:32:55.910406Z INFO uefi_log: [ 45.735636] hv_vmbus: hv_post_msg() failed; error code:5
2025-02-04T00:37:21.6099167Z 2025-02-04T00:32:55.978539Z INFO uefi_log: [ 45.801638] hv_vmbus: hv_post_msg() failed; error code:5
2025-02-04T00:37:21.6099370Z 2025-02-04T00:32:56.045324Z INFO uefi_log: [ 45.869945] hv_vmbus: hv_post_msg() failed; error code:5
2025-02-04T00:37:21.6099564Z 2025-02-04T00:32:56.113043Z INFO uefi_log: [ 45.936467] hv_vmbus: hv_post_msg() failed; error code:5
2025-02-04T00:37:21.6099751Z 2025-02-04T00:32:56.180081Z INFO uefi_log: [ 46.004300] hv_vmbus: hv_post_msg() failed; error code:5
2025-02-04T00:37:21.6099941Z 2025-02-04T00:32:56.250969Z INFO uefi_log: [ 46.071514] hv_vmbus: hv_post_msg() failed; error code:5
2025-02-04T00:37:21.6100133Z 2025-02-04T00:32:56.321602Z INFO uefi_log: [ 46.142352] hv_vmbus: hv_post_msg() failed; error code:5
2025-02-04T00:37:21.6100324Z 2025-02-04T00:32:56.392712Z INFO uefi_log: [ 46.213025] hv_vmbus: hv_post_msg() failed; error code:5

A bunch of PIO errors

2025-02-04T00:37:21.5982178Z 2025-02-04T00:32:43.799936Z INFO openhcl_log: <28>[ 79.700223] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io write error device="uefi" address=0x2e len=0x1 kind=Pio error="invalid access size" bytes=[aa]
2025-02-04T00:37:21.5982687Z 2025-02-04T00:32:43.831771Z INFO openhcl_log: <28>[ 79.734365] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io write error device="uefi" address=0x2e len=0x1 kind=Pio error="invalid access size" bytes=[77]
2025-02-04T00:37:21.5983602Z 2025-02-04T00:32:43.832597Z INFO openvmm_log: 82.685191600s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io write error" fields={"kind": "Pio", "device": "uefi", "len": 1, "error": "invalid access size", "bytes": "[170]", "address": 46} extra={"timestamp": "77.750786900s", "related_activity_id": "c74d51dc-0003-002e-0100-000040010800"}
2025-02-04T00:37:21.5984436Z 2025-02-04T00:32:43.832686Z INFO openvmm_log: 82.685352400s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io write error" fields={"device": "uefi", "kind": "Pio", "error": "invalid access size", "len": 1, "address": 46, "bytes": "[119]"} extra={"timestamp": "77.784803100s", "related_activity_id": "c74d51dc-0003-002e-0100-000040010800"}
2025-02-04T00:37:21.5984948Z 2025-02-04T00:32:43.863195Z INFO openhcl_log: <28>[ 79.766689] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io write error device="uefi" address=0x2e len=0x1 kind=Pio error="invalid access size" bytes=[77]
2025-02-04T00:37:21.5985766Z 2025-02-04T00:32:43.863906Z INFO openvmm_log: 82.716507200s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io write error" fields={"error": "invalid access size", "len": 1, "address": 46, "bytes": "[119]", "device": "uefi", "kind": "Pio"} extra={"timestamp": "77.817207300s", "related_activity_id": "c74d51dc-0003-002e-0100-000040010800"}
2025-02-04T00:37:21.5986274Z 2025-02-04T00:32:43.895551Z INFO openhcl_log: <28>[ 79.797759] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io write error device="uefi" address=0x2e len=0x1 kind=Pio error="invalid access size" bytes=[23]
2025-02-04T00:37:21.5986835Z 2025-02-04T00:32:43.924821Z INFO openhcl_log: <28>[ 79.830134] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io read error device="uefi" address=0x2f len=0x1 kind=Pio error="invalid access size"
2025-02-04T00:37:21.5987659Z 2025-02-04T00:32:43.925561Z INFO openvmm_log: 82.778161000s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io write error" fields={"len": 1, "device": "uefi", "error": "invalid access size", "bytes": "[35]", "address": 46, "kind": "Pio"} extra={"timestamp": "77.848306800s", "related_activity_id": "c74d51dc-0003-002e-0100-000040010800"}
2025-02-04T00:37:21.5988458Z 2025-02-04T00:32:43.925649Z INFO openvmm_log: 82.778308800s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io read error" fields={"device": "uefi", "address": 47, "len": 1, "kind": "Pio", "error": "invalid access size"} extra={"timestamp": "77.880607000s", "related_activity_id": "c74d51dc-0003-002e-0100-000040010800"}
2025-02-04T00:37:21.5988973Z 2025-02-04T00:32:43.956427Z INFO openhcl_log: <28>[ 79.859994] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io write error device="uefi" address=0x2e len=0x1 kind=Pio error="invalid access size" bytes=[aa]
2025-02-04T00:37:21.5990039Z 2025-02-04T00:32:43.957220Z INFO openvmm_log: 82.809823800s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io write error" fields={"kind": "Pio", "error": "invalid access size", "address": 46, "len": 1, "bytes": "[170]", "device": "uefi"} extra={"timestamp": "77.910488800s", "related_activity_id": "c74d51dc-0003-002e-0100-000040010800"}
2025-02-04T00:37:21.5990562Z 2025-02-04T00:32:43.990993Z INFO openhcl_log: <28>[ 79.891265] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io write error device="uefi" address=0x2e len=0x1 kind=Pio error="invalid access size" bytes=[aa]
2025-02-04T00:37:21.5991065Z 2025-02-04T00:32:44.023159Z INFO openhcl_log: <28>[ 79.925506] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io write error device="uefi" address=0x2e len=0x1 kind=Pio error="invalid access size" bytes=[a0]
2025-02-04T00:37:21.5991910Z 2025-02-04T00:32:44.023873Z INFO openvmm_log: 82.876487300s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io write error" fields={"kind": "Pio", "len": 1, "address": 46, "bytes": "[170]", "error": "invalid access size", "device": "uefi"} extra={"related_activity_id": "c74d51dc-0003-002e-0100-000040010800", "timestamp": "77.941790000s"}
2025-02-04T00:37:21.5992855Z 2025-02-04T00:32:44.023967Z INFO openvmm_log: 82.876633300s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io write error" fields={"kind": "Pio", "address": 46, "device": "uefi", "len": 1, "error": "invalid access size", "bytes": "[160]"} extra={"timestamp": "77.976027500s", "related_activity_id": "c74d51dc-0003-002e-0100-000040010800"}
2025-02-04T00:37:21.5993369Z 2025-02-04T00:32:44.055186Z INFO openhcl_log: <28>[ 79.958065] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io write error device="uefi" address=0x2e len=0x1 kind=Pio error="invalid access size" bytes=[a0]
2025-02-04T00:37:21.5993877Z 2025-02-04T00:32:44.086813Z INFO openhcl_log: <28>[ 79.989984] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io write error device="uefi" address=0x2e len=0x1 kind=Pio error="invalid access size" bytes=[23]
2025-02-04T00:37:21.5994721Z 2025-02-04T00:32:44.087551Z INFO openvmm_log: 82.940148000s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io write error" fields={"address": 46, "kind": "Pio", "device": "uefi", "error": "invalid access size", "bytes": "[160]", "len": 1} extra={"related_activity_id": "c74d51dc-0003-002e-0100-000040010800", "timestamp": "78.008496500s"}
2025-02-04T00:37:21.5995622Z 2025-02-04T00:32:44.087707Z INFO openvmm_log: 82.940301900s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io write error" fields={"device": "uefi", "kind": "Pio", "address": 46, "bytes": "[35]", "len": 1, "error": "invalid access size"} extra={"timestamp": "78.040222800s", "related_activity_id": "c74d51dc-0003-002e-0100-000040010800"}
2025-02-04T00:37:21.5996111Z 2025-02-04T00:32:44.117509Z INFO openhcl_log: <28>[ 80.021728] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io read error device="uefi" address=0x2f len=0x1 kind=Pio error="invalid access size"
2025-02-04T00:37:21.5996909Z 2025-02-04T00:32:44.118377Z INFO openvmm_log: 82.970964300s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io read error" fields={"error": "invalid access size", "device": "uefi", "address": 47, "kind": "Pio", "len": 1} extra={"timestamp": "78.072228000s", "related_activity_id": "c74d51dc-0003-002e-0100-000040010800"}
2025-02-04T00:37:21.5997490Z 2025-02-04T00:32:44.157021Z INFO openhcl_log: <28>[ 80.052506] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io write error dropped_ratelimited=0x0 device="uefi" address=0x2e len=0x1 kind=Pio error="invalid access size" bytes=[aa]
2025-02-04T00:37:21.5998385Z 2025-02-04T00:32:44.159400Z INFO openvmm_log: 83.011999800s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io write error" fields={"device": "uefi", "dropped_ratelimited": 0, "len": 1, "kind": "Pio", "error": "invalid access size", "address": 46, "bytes": "[170]"} extra={"timestamp": "78.102942700s", "related_activity_id": "c74d51dc-0003-002e-0100-000040010800"}
2025-02-04T00:37:21.5998875Z 2025-02-04T00:32:44.189148Z INFO openhcl_log: <28>[ 80.093587] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io read error device="uefi" address=0x2f len=0x1 kind=Pio error="invalid access size"
2025-02-04T00:37:21.5999347Z 2025-02-04T00:32:44.220499Z INFO openhcl_log: <28>[ 80.126140] vmotherboard::chipset: WARN run_vp{ vp_index=0x1}: device io read error device="uefi" address=0x2f len=0x1 kind=Pio error="invalid access size"
2025-02-04T00:37:21.6000163Z 2025-02-04T00:32:44.221283Z INFO openvmm_log: 83.073880800s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io read error" fields={"error": "invalid access size", "device": "uefi", "len": 1, "address": 47, "kind": "Pio"} extra={"related_activity_id": "c74d51dc-0003-002e-0100-000040010800", "timestamp": "78.144116400s"}
2025-02-04T00:37:21.6000950Z 2025-02-04T00:32:44.221439Z INFO openvmm_log: 83.074027200s WARN paravisor_log: inner_target="vmotherboard::chipset" "device io read error" fields={"device": "uefi", "address": 47, "error": "invalid access size", "len": 1, "kind": "Pio"} extra={"timestamp": "78.176569800s", "related_activity_id": "c74d51dc-0003-002e-0100-000040010800"}

@benhillis
Copy link
Member

Tests look like they are passing, is there more we need to do here?

@smalis-msft
Copy link
Contributor

We still want to do some investigation on why VBS fails on the new image, it'd be nice to only be downloading one image.

@benhillis
Copy link
Member

We still want to do some investigation on why VBS fails on the new image, it'd be nice to only be downloading one image.

Ah got it, that test is running on the old image.

@eric135
Copy link
Contributor

eric135 commented Feb 5, 2025

Is it planned to move all tests using Ubuntu to 24.04? I see some left at 22.04 (it looks like these were changed back to 22.04 in one of the updates to this PR - trying to understand why)

@mattkur
Copy link
Contributor

mattkur commented Feb 10, 2025

Is it planned to move all tests using Ubuntu to 24.04? I see some left at 22.04 (it looks like these were changed back to 22.04 in one of the updates to this PR - trying to understand why)

Looks like there's an issue where VBS does not seem to work with the 24.04 version, if I'm understanding the discussion correctly.

@mattkur
Copy link
Contributor

mattkur commented Feb 11, 2025

@smalis-msft tried this awhile back, trying again. Running CI to see what goes wrong and then hopefully fix any issues. In local testing, the switch reduced the ubuntu boot test from 157 seconds to 35 seconds, due to not waiting for network.

I came here to make an argument for pushing this change in, if running the tests was the dominant time vs. downloading the images. Look like downloading the images took 1min 29s, whereas running the tests took 7+ minutes in this CI run.
This is similar to this other run, without the move to 24.04: https://github.com/microsoft/openvmm/actions/runs/13256813101/job/37005374127

That being said: downloading the images is a one-time or few-times pain for devs, whereas running the tests is a frequent-time pain. If we're not going to prioritize the VBS investigation, I think there's a case to be made that completing this PR results in a strictly better experience.

But, what do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update vmm test ubuntu image from 22.04 to 24.04
5 participants