{"action":"created","issue":{"url":"https://api.github.com/repos/home-assistant/hassos/issues/151","repository_url":"https://api.github.com/repos/home-assistant/hassos","labels_url":"https://api.github.com/repos/home-assistant/hassos/issues/151/labels{/name}","comments_url":"https://api.github.com/repos/home-assistant/hassos/issues/151/comments","events_url":"https://api.github.com/repos/home-assistant/hassos/issues/151/events","html_url":"https://github.com/home-assistant/hassos/issues/151","id":348366017,"node_id":"MDU6SXNzdWUzNDgzNjYwMTc=","number":151,"title":"Stuck at boot menu when using VMDK image and QEMU","user":{"login":"move[bot]","id":33596368,"node_id":"MDM6Qm90MzM1OTYzNjg=","avatar_url":"https://avatars1.githubusercontent.com/in/6673?v=4","gravatar_id":"","url":"https://api.github.com/users/move%5Bbot%5D","html_url":"https://github.com/apps/move","followers_url":"https://api.github.com/users/move%5Bbot%5D/followers","following_url":"https://api.github.com/users/move%5Bbot%5D/following{/other_user}","gists_url":"https://api.github.com/users/move%5Bbot%5D/gists{/gist_id}","starred_url":"https://api.github.com/users/move%5Bbot%5D/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/move%5Bbot%5D/subscriptions","organizations_url":"https://api.github.com/users/move%5Bbot%5D/orgs","repos_url":"https://api.github.com/users/move%5Bbot%5D/repos","events_url":"https://api.github.com/users/move%5Bbot%5D/events{/privacy}","received_events_url":"https://api.github.com/users/move%5Bbot%5D/received_events","type":"Bot","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-08-07T15:11:38Z","updated_at":"2018-08-17T13:52:25Z","closed_at":null,"author_association":"NONE","body":"*@pjones commented on Aug 6, 2018, 8:56 PM UTC:*\n\nI have seen a few other people asking about this issue but none have been answered.\n\nI'm trying to boot the virtual appliance with QEMU (using OVMF for UEFI). Booting stops at the HassOS-boot menu. The only option that works is the shell option. When I try booting one of the two systems manually I get all sorts of errors:\n\n[![](https://camo.githubusercontent.com/0d9f9dbb4c7a0899190651f4f3378a581d94a7c7/68747470733a2f2f7777772e706d6164652e636f6d2f7374617469632f696d616765732f323031382f686173736f732d626f6f742e6a7067)](https://camo.githubusercontent.com/0d9f9dbb4c7a0899190651f4f3378a581d94a7c7/68747470733a2f2f7777772e706d6164652e636f6d2f7374617469632f696d616765732f323031382f686173736f732d626f6f742e6a7067)\n\nIs there a way to get more details about why this is failing to boot? Missing file system devices?\n\n*This issue was moved by [pvizeli](https://github.com/pvizeli) from [home-assistant/hassio#630](https://github.com/home-assistant/hassio/issues/630).*"},"comment":{"url":"https://api.github.com/repos/home-assistant/hassos/issues/comments/413872843","html_url":"https://github.com/home-assistant/hassos/issues/151#issuecomment-413872843","issue_url":"https://api.github.com/repos/home-assistant/hassos/issues/151","id":413872843,"node_id":"MDEyOklzc3VlQ29tbWVudDQxMzg3Mjg0Mw==","user":{"login":"dgz","id":43816,"node_id":"MDQ6VXNlcjQzODE2","avatar_url":"https://avatars3.githubusercontent.com/u/43816?v=4","gravatar_id":"","url":"https://api.github.com/users/dgz","html_url":"https://github.com/dgz","followers_url":"https://api.github.com/users/dgz/followers","following_url":"https://api.github.com/users/dgz/following{/other_user}","gists_url":"https://api.github.com/users/dgz/gists{/gist_id}","starred_url":"https://api.github.com/users/dgz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dgz/subscriptions","organizations_url":"https://api.github.com/users/dgz/orgs","repos_url":"https://api.github.com/users/dgz/repos","events_url":"https://api.github.com/users/dgz/events{/privacy}","received_events_url":"https://api.github.com/users/dgz/received_events","type":"User","site_admin":false},"created_at":"2018-08-17T13:52:25Z","updated_at":"2018-08-17T13:52:25Z","author_association":"NONE","body":"I ran into the same issue with a VirtualBox VM with both 1.9 and the 2.1 dev version. Deleting the CDROM drive and IDE controller that VirtualBox created by default also solved the issue for me.\r\n\r\nDynamic handling of connected drives sounds like a good long term fix but in the short term a note in ova.md under the Virtual Machine requirements would be helpful. Something like \"vmdk must be the first attached disk on the first storage controller, delete any automatically created CDROM drives and controllers\"."}}
{"actor":{"display_login":"dgz"}}