[gem5-users] Re: "qemu: Error launching VM: Qenu failed to start" when using Packer to create a disk image and running Gem5 FS Sim

2022-11-12 Thread minhui via gem5-users
Respectful Hoa: Great insight info and tips! I am following up with correction. 1. Nested virtualization is not enabled in default, so I need to restart from scratch including VM Virtual Box, I believe that is the root cause. 2. I am trying the other option of no accelerator. Again, much appr

[gem5-users] Re: "qemu: Error launching VM: Qenu failed to start" when using Packer to create a disk image and running Gem5 FS Sim

2022-11-12 Thread Hoa Nguyen via gem5-users
Hi, I wanted to add that, if nested virtualization is not an option, you can remove the "accelerator": "kvm" line in the json file. Without kvm, the process might take a few hours. https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/x86-ubuntu/disk-image/x86-ubuntu/x86-ubu

[gem5-users] Re: "qemu: Error launching VM: Qenu failed to start" when using Packer to create a disk image and running Gem5 FS Sim

2022-11-12 Thread Chrysanthos Pepi via gem5-users
5.org> Cc: shuaimin...@ufl.edu<mailto:shuaimin...@ufl.edu> Subject: [gem5-users] Re: "qemu: Error launching VM: Qenu failed to start" when using Packer to create a disk image and running Gem5 FS Sim Chrysanthos and Mentors: The tip Chrysanthos provided is very helpful! 1,

[gem5-users] Re: "qemu: Error launching VM: Qenu failed to start" when using Packer to create a disk image and running Gem5 FS Sim

2022-11-12 Thread minhui via gem5-users
Advisor Chrysanthos: Much appreciated! will follow your guidance shortly Minhui ___ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] Re: "qemu: Error launching VM: Qenu failed to start" when using Packer to create a disk image and running Gem5 FS Sim

2022-11-12 Thread Chrysanthos Pepi via gem5-users
Hi minhui, Try to `$ export PACKER_LOG=1`, and then run it again to see more details. I had a similar issue recently and was about qemu permissions. I was able to fix it by `sudo`, or by changing permission to /dev/kvm ` sudo chown /dev/kvm` Kind regards, Chrysanthos Pepi From: minhui via gem