atrium is a shared system in the lab that does not have a VMM reservoir configured. I tried to run the PHD tests locally (via cargo xtask phd run) against what's currently on propolis master (4458148) and the migration tests fail:
failures:
phd_tests::migrate::running_process::export_failure
phd_tests::migrate::from_base::can_migrate_from_base
phd_tests::migrate::from_base::serial_history
phd_tests::migrate::from_base::migration_from_base_and_back
test result: FAILED. 42 passed; 4 failed; 3 skipped; 0 not run; finished in 488.42s
The tests for from_base all fail like this:
00:48:36.994Z ERRO propolis-server (vm_state_driver): failed to activate new VM
error = creating VM objects for new instance: failed to join VM object creation task: failed to add low memory region
00:48:36.995Z INFO propolis-server: request completed
error_message_external = Internal Server Error
error_message_internal = VM initialization failed: failed to join VM object creation task: failed to add low memory region
latency_us = 28320
local_addr = 127.0.0.1:9000
method = PUT
remote_addr = 127.0.0.1:58585
req_id = 9a03ed6d-0dea-4436-bad7-cc387620267b
response_code = 500
uri = /instance
It was suggested in hypervisor channel chatter that this might be because there is no reservoir configured on this system. It would be good to figure that out for sure and perhaps improve things a bit here.
atriumis a shared system in the lab that does not have a VMM reservoir configured. I tried to run the PHD tests locally (viacargo xtask phd run) against what's currently on propolis master (4458148) and the migration tests fail:The tests for
from_baseall fail like this:It was suggested in hypervisor channel chatter that this might be because there is no reservoir configured on this system. It would be good to figure that out for sure and perhaps improve things a bit here.