# Qemu Environments Not Booting Correctly **URL:** \ **Category:** Support\ **Created:** [June 8, 2022, 10:43pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354 "2022-06-08T22:43:40Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![ekaltman](https://avatars.discourse-cdn.com/v4/letter/e/87869e/32.png) [@ekaltman](https://forum.eaasi.cloud/u/ekaltman)\ **Post date:** [June 8, 2022, 10:43pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/1 "2022-06-08T22:43:40Z")
**Deployment** : Local installation (in local data center) **EaaSI Version** : v2021.10 **Browser** : N/A **Description:** Any environment I attempt to run based on Qemu are not booting. The same boot screen loads and then nothing else happens. I’ve attached a screenshot. ![eaasi-no-boot-message](https://us1.discourse-cdn.com/flex019/uploads/eaasi/original/1X/1c48add7b473927bc766a385662aabd6fdb1fdd4.jpeg) This issue first occurred when I tried following the EaaSI user guide to install a FreeDOS 1.2 resource. However, it also happens with both Windows environments I’ve tested. I think the issue may be related to me manually importing qemu before saving the environments to my local node. The environments that do not boot are: 1. Windows 95 Test Env 2. Windows XP Professional 2002 SP3 32 Bit + Microsoft Office Home and Student 6994 _Are you able to reproduce the issue or did it happen once? What steps can you take to repeat the issue? What did you expect to occur and what was the actual outcome?_ This happens whenever I try to boot either environment. I know the Windows 95 Test Env was previously working on my earlier installation. **Urgency:** _If possible, please give an indication of how urgently the issue needs to be addressed - is there a timeline or deadline (e.g. upcoming demo, researcher request, etc.) that EaaSI support staff should be aware of?_ I’m working on a summer research project with EaaSI and trying to get it functioning for student evaluative use. I can try a fresh installation again if needed. ---
**Author:** ![ethan.gates](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.eaasi.cloud/ethan.gates/32/15_2.png) [@ethan.gates](https://forum.eaasi.cloud/u/ethan.gates)\ **Post date:** [June 9, 2022, 6:06pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/2 "2022-06-09T18:06:16Z")
Hey @ekaltman - the process of saving environments to your node _should_ copy over any necessary QEMU container automatically, if that Public environment is configured to run a particular emulator/version that you don’t yet have in your node. And it seems like QEMU _is_ running here (we’ve seen issues with the emulators not copying over properly in the past and in such cases when trying to run the copied environment you get nothing in the Access interface at all and probably an error thrown by the UI) - it just can’t find the bootable device (system drive), so something may have gone wrong in copying over the underlying QCOW images of the environment. We could confirm that by taking QEMU/the emulators off the table - does a SheepShaver or Basilisk-based Mac environment work? E.g. “Apple Mac OS 7.5”? Either way - could you also try saving a different PC/QEMU-based environment to your node and then immediately download a server log from Manage Node → Troubleshooting → Download Server Log and provide? ---
**Author:** ![ekaltman](https://avatars.discourse-cdn.com/v4/letter/e/87869e/32.png) [@ekaltman](https://forum.eaasi.cloud/u/ekaltman)\ **Post date:** [June 9, 2022, 8:43pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/3 "2022-06-09T20:43:51Z")
I downloaded “Mac OS 7.5 + Ready Set GO 4.5a” and it failed to load. When I try to download the server.log file through the Web UI nothing happens, it goes to the error reporting URL and hangs. It does correctly return the front-end logs however. The server.log below shows the error reporting error: [eaasi\_error\_reporting\_issue\_20220609.log](https://forum.eaasi.cloud/uploads/short-url/1WgUdeoL7e3gDroZgFAgrv9dtCG.log) (1.8 MB) There also appears to be some local access errors in there, some of the /eaasi/ subfolders appear to be owned by root instead of the eaasi user? ![eaasi_base_directory_permissions](https://us1.discourse-cdn.com/flex019/uploads/eaasi/original/1X/50e0b95fd1d624d5e5752d99fc5896123823b711.png) I’m attaching the current server.log file as well. I initiated a save operation for “Windows 98 SE + Microsoft Works 8” around two hours ago that has still not finished. I can send another update early tomorrow once I’m back in the office. Current eaasi server.log: [eaasi\_error\_qemu\_import\_20220609.log](https://forum.eaasi.cloud/uploads/short-url/gLziF11onC6fs3xZsFUIEUi1Z5p.log) (1.9 MB) ---
**Author:** ![oooleg](https://avatars.discourse-cdn.com/v4/letter/o/aca169/32.png) [@oooleg](https://forum.eaasi.cloud/u/oooleg)\ **Post date:** [June 10, 2022, 3:52pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/4 "2022-06-10T15:52:16Z")
@ekaltman, according to the provided log, all of your attempts to import and replicate environments were successful. Your specific “Windows 98” image is about 20GB in size, so depending on your internet connection it might take longer to import. Please also make sure, that you have enough storage space available. But, starting emulation sessions with imported images indeed fail. The following output might contain more information: ```nohighlight $ sudo docker logs nginx > nginx.log ``` Generating error-reports fails because of file permission problems, which should not happen. Could you please post the output of the following command here too: ```nohighlight $ sudo tree -pugh /eaasi > eaasi-tree.txt ``` ---
**Author:** ![ekaltman](https://avatars.discourse-cdn.com/v4/letter/e/87869e/32.png) [@ekaltman](https://forum.eaasi.cloud/u/ekaltman)\ **Post date:** [June 10, 2022, 5:00pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/5 "2022-06-10T17:00:13Z")
Updated log after process completed: [eaasi\_error\_qemu\_import\_complete\_20220609.log](https://forum.eaasi.cloud/uploads/short-url/ce387MULzMEOWZfs5k3PCcWkDcu.log) (1.9 MB) Nginx Log and Tree Output [eaasi\_nginx\_20220609.log](https://forum.eaasi.cloud/uploads/short-url/uFXl3yT5Yd0TenbcaJWU5Jv2gnE.log) (883.7 KB) [eaasi\_tree\_20220609.txt](https://forum.eaasi.cloud/uploads/short-url/3ECeQwVhoTFukt6YvxD0ytbcejM.txt) (430.9 KB) My connection is from the data center so it should be rather fast. The VM I’m running EaaSI on has ~300GB of space available. ---
**Author:** ![ekaltman](https://avatars.discourse-cdn.com/v4/letter/e/87869e/32.png) [@ekaltman](https://forum.eaasi.cloud/u/ekaltman)\ **Post date:** [June 14, 2022, 5:05pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/6 "2022-06-14T17:05:15Z")
@oooleg it appears that the permissions for some of the tree are not owned by the eaasi user. I’m going to try changing the permissions to eaasi to see if that fixes anything. I guess let me know if the logs show any other potential issues. ---
**Author:** ![oooleg](https://avatars.discourse-cdn.com/v4/letter/o/aca169/32.png) [@oooleg](https://forum.eaasi.cloud/u/oooleg)\ **Post date:** [June 14, 2022, 6:24pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/7 "2022-06-14T18:24:37Z")
@ekaltman, what is the output of the following command executed on your server: ```auto $ sudo id eaasi ekaltman ``` It looks like some of the data was created under different users. We normally do not change filesystem ownership during installation. But it might also be caused by a mismatch of host vs. container users, under which the backend is run inside of the containers. ---
**Author:** ![ekaltman](https://avatars.discourse-cdn.com/v4/letter/e/87869e/32.png) [@ekaltman](https://forum.eaasi.cloud/u/ekaltman)\ **Post date:** [June 14, 2022, 6:44pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/8 "2022-06-14T18:44:19Z")
the exact command returns an error, individually however ```auto ekaltman@eaasi:~$ sudo id eaasi uid=1002(eaasi) gid=1002(eaasi) groups=1002(eaasi),27(sudo),108(lxd),999(docker) ekaltman@eaasi:~$ sudo id ekaltman uid=1000(ekaltman) gid=1000(ekaltman) groups=1000(ekaltman),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),108(lxd) ``` ---
**Author:** ![oooleg](https://avatars.discourse-cdn.com/v4/letter/o/aca169/32.png) [@oooleg](https://forum.eaasi.cloud/u/oooleg)\ **Post date:** [June 15, 2022, 12:28am UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/9 "2022-06-15T00:28:49Z")
OK, thanks. This looks like a user-id mismatch. Backend is always running under user 1000 in the container, which maps to `ekaltman` user on the host. Then, processes inside of the container running under user 1000 fail to read some files owned by 1002 (eaasi) user on the host. That is the reason why generating error-reports fails. If possible, could you try to install EaaSI as `ekaltman` user? It should be enough to run: ```nohighlight $ sudo systemctl stop eaas $ sudo chown -R ekaltman:ekaltman /eaasi $ sudo systemctl start eaas ``` ---
**Author:** ![oooleg](https://avatars.discourse-cdn.com/v4/letter/o/aca169/32.png) [@oooleg](https://forum.eaasi.cloud/u/oooleg)\ **Post date:** [June 15, 2022, 12:50am UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/10 "2022-06-15T00:50:07Z")
Currently, replication of environments is automatically aborted after a timeout of 1 hour. According to the log, importing “Windows 98” images seems to take longer on your server and you are running into that timeout there. I have increased the timeout for you to try. Just change your `eaasi.yaml` to: ```auto eaas: version: "v2021.10.1-eaasi" ``` and update your server: ```nohighlight $ ./scripts/update.sh ear ``` ---
**Author:** ![ekaltman](https://avatars.discourse-cdn.com/v4/letter/e/87869e/32.png) [@ekaltman](https://forum.eaasi.cloud/u/ekaltman)\ **Post date:** [June 15, 2022, 4:35pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/11 "2022-06-15T16:35:13Z")
I reinstalled and changed the version to enable the new timeout. I also changed ownership of the /eaasi folder to the “ekaltman” user. The server log download now works, though I’m not sure which key I need to use to decrypt the gpg file. I attempted to download the Windows 95 Test Env and it now failed rather quickly. Server log is attached below. [eaasi\_environment\_download\_error\_20220615.log](https://forum.eaasi.cloud/uploads/short-url/2ErpGvbECN7lEUWs11P904QzFjR.log) (715.1 KB) The error with QEMU not booting the environment is the same, I’m thinking that the node is not downloading the environments correctly. ---
**Author:** ![ekaltman](https://avatars.discourse-cdn.com/v4/letter/e/87869e/32.png) [@ekaltman](https://forum.eaasi.cloud/u/ekaltman)\ **Post date:** [June 15, 2022, 6:15pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/12 "2022-06-15T18:15:31Z")
Any environment I attempt to download claims to have finished and “Saved Locally” but still has the “Run in Emulator” faded. When I go into details I can try to run the emulation but for Qemu is just boots to a “no bootable device” screen. Mac environments immediately fail before boot, which seems similar to the CMU issue. There is definitely some issue with downloading the environments correctly, don’t know if that is on my end or the eaasi system end however. @ethan.gates I will probably try just installing and configuring environments locally, I’ll look out for office hours. At this point, I don’t really know what else to try, if we want to schedule some live debugging let me know. ---
**Author:** ![ekaltman](https://avatars.discourse-cdn.com/v4/letter/e/87869e/32.png) [@ekaltman](https://forum.eaasi.cloud/u/ekaltman)\ **Post date:** [June 16, 2022, 8:27pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/13 "2022-06-16T20:27:56Z")
I ran a tail on the server.log when I try to initialize the Windows 98 run-time. It appears to not be finding the correct data. [eaasi\_environment\_download\_error\_20220616.log](https://forum.eaasi.cloud/uploads/short-url/20fjWCvaqesiPc8gyZFgqT6cA6t.log) (40.6 KB) The Windows 98 image is downloaded to the server, as are the other images, so I’m not sure what the issue is. I’m doing a fresh reinstallation on a fresh VM to see if there are other issues. ---
**Author:** ![oooleg](https://avatars.discourse-cdn.com/v4/letter/o/aca169/32.png) [@oooleg](https://forum.eaasi.cloud/u/oooleg)\ **Post date:** [June 17, 2022, 6:48pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/14 "2022-06-17T18:48:27Z")
According to your log downloading Windows 95 environment was successful: ```auto 2022-06-15 16:22:23.175 |I| (EE-ManagedExecutorService-io-Thread-4) [IMAGE-ARCHIVE] (service:imports) Executing import-task 3 took 102 second(s) 2022-06-15 16:22:23.212 |I| (EE-ManagedExecutorService-io-Thread-4) [IMAGE-ARCHIVE] (service:imports) Executing import-task 2 took 111 second(s) 2022-06-15 16:22:23.251 |I| (EE-ManagedExecutorService-io-Thread-4) [IMAGE-ARCHIVE] (service:imports) Executing import-task 1 took 119 second(s) 2022-06-15 16:22:23.280 |I| (EE-ManagedExecutorService-io-Thread-3) [IMAGE-ARCHIVE-CLIENT] Replicated environment '56696004-84ff-4d5f-8596-407caa07c030' ``` ---
**Author:** ![ekaltman](https://avatars.discourse-cdn.com/v4/letter/e/87869e/32.png) [@ekaltman](https://forum.eaasi.cloud/u/ekaltman)\ **Post date:** [June 17, 2022, 7:09pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/15 "2022-06-17T19:09:48Z")
Hi @oooleg, yes, the environments were downloading but they loading into a “no bootable device” qemu screen. I tried to wipe the server and reinstall everything again but am now encountering a new issue. The setup fails again at: ```auto TASK [wait for eaas-server to start up] *************************************************************************************************************************************************************************************************** fatal: [eaas-gateway]: FAILED! => changed=false attempts: 1 content: '' elapsed: 0 msg: 'Status code was -1 and not [200]: Request failed: ' redirected: false status: -1 url: https://eaasi.csuci.edu/emil/environment-repository/actions/prepare ``` However, last time the EaaSI system was still reachable, it appears that now the nginx docker container (not eaasi-nginx) is failing to start. From `docker ps`: ```auto ekaltman@eaasi:/$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 321719e6fd07 nginx:stable "/docker-entrypoint.…" 5 minutes ago Restarting (1) 26 seconds ago eaasi-nginx da9ff1d72056 eaas/eaas-appserver:v2021.10-eaasi "/init" 5 minutes ago Up 5 minutes eaas 0fab64605bac registry.gitlab.com/eaasi/eaasi-client-pub/eaasi-web-api:v2021.10 "docker-entrypoint.s…" 5 minutes ago Up 5 minutes 0.0.0.0:8081->8081/tcp, :::8081->8081/tcp eaasi-web-api 5dfa2a6059b7 jboss/keycloak:15.0.2 "/opt/jboss/tools/do…" 5 minutes ago Up 5 minutes 8080/tcp, 8443/tcp keycloak 1c29c3068b13 registry.gitlab.com/eaasi/eaasi-client-pub/eaasi-front-end:v2021.10 "/docker-entrypoint.…" 5 minutes ago Up 5 minutes 0.0.0.0:8080->80/tcp, :::8080->80/tcp eaasi-front-end 0fe466dd0a0c registry.gitlab.com/eaasi/eaasi-client-pub/eaasi-database:v2021.10 "docker-entrypoint.s…" 5 minutes ago Up 5 minutes 0.0.0.0:5432->5432/tcp, :::5432->5432/tcp eaasi-database 638e6d1c543c minio/minio:RELEASE.2021-11-03T03-36-36Z "/usr/bin/docker-ent…" 5 minutes ago Up 5 minutes 9000/tcp minio ``` I can start a new ticket for this error if you like. `docker logs nginx` produces: ```auto 2022/06/17 19:03:09 [emerg] 1#1: unknown directive "js_include" in /etc/nginx/nginx.conf:20 nginx: [emerg] unknown directive "js_include" in /etc/nginx/nginx.conf:20 ``` ---
**Author:** ![oooleg](https://avatars.discourse-cdn.com/v4/letter/o/aca169/32.png) [@oooleg](https://forum.eaasi.cloud/u/oooleg)\ **Post date:** [June 17, 2022, 7:26pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/16 "2022-06-17T19:26:16Z")
@ekaltman, you probably have removed all containers recently. The new nginx container seems to be not compatible with the config from EaaSI anymore. As a workaround, you should now update the installer as follows: ```nohighlight $ cd /eaas/ansible $ git fetch origin $ git checkout origin master ``` Then re-run the installer again, ignoring the last startup error. ---
**Author:** ![oooleg](https://avatars.discourse-cdn.com/v4/letter/o/aca169/32.png) [@oooleg](https://forum.eaasi.cloud/u/oooleg)\ **Post date:** [June 17, 2022, 7:32pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/17 "2022-06-17T19:32:28Z")
Actually, images seem to be correctly replicated but are then not found when setting up an emulation session. I’m not yet sure what is the root cause for this in your case, especially if the server is constantly tweaked and modified 🙂 Is there any chance to get ssh-access to your machine? Or, alternatively, we could schedule a zoom call and share screen? That might be simpler to find the root cause for your issues. ---
**Author:** ![ekaltman](https://avatars.discourse-cdn.com/v4/letter/e/87869e/32.png) [@ekaltman](https://forum.eaasi.cloud/u/ekaltman)\ **Post date:** [June 17, 2022, 7:37pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/18 "2022-06-17T19:37:23Z")
Okay, that fixed the nginx issue and I appear to have access to the interface again. Just a note that the initial pull did not work: ```auto ➜ eaasi-installer git:(a2d2e9e) cd eaas/ansible ➜ ansible git:(60885d4) git fetch origin ➜ ansible git:(60885d4) git checkout origin master error: pathspec 'master' did not match any file(s) known to git ``` So I just ignored the `origin` for both commands and the pull worked. ---
**Author:** ![oooleg](https://avatars.discourse-cdn.com/v4/letter/o/aca169/32.png) [@oooleg](https://forum.eaasi.cloud/u/oooleg)\ **Post date:** [June 17, 2022, 7:39pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/19 "2022-06-17T19:39:41Z")
yeah, sorry… it should be: ```nohighlight $ git checkout origin/master ``` But, leaving out remote prefix should also work in this case. ---
**Author:** ![ekaltman](https://avatars.discourse-cdn.com/v4/letter/e/87869e/32.png) [@ekaltman](https://forum.eaasi.cloud/u/ekaltman)\ **Post date:** [June 17, 2022, 7:40pm UTC](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354/20 "2022-06-17T19:40:21Z")
@oooleg the ssh access is currently limited to our VPN, I could open up the ssh access publicly but I think a screenshare might be the most effective. I’m free for most of this afternoon until 4pm PT and again on Monday or Tuesday for middle of the day times (10am-3pm PT). And just an edit to say thank you for working through this with me! [Next page](https://forum.eaasi.cloud/t/qemu-environments-not-booting-correctly/354.md?page=2)