On Fri, Jul 14, 2017 at 10:54 AM, Mick <michaelkintz...@gmail.com> wrote: > On Friday 14 Jul 2017 10:43:23 R0b0t1 wrote: >> On Fri, Jul 14, 2017 at 10:31 AM, Mick <michaelkintz...@gmail.com> wrote: >> > I have followed the gentoo wiki to install and setup QEMU: >> > >> > https://wiki.gentoo.org/wiki/QEMU >> > >> > >> > Then I tried to start up a CoreOS image following this guide, but I must >> > be >> > doing something wrong: >> > >> > https://coreos.com/os/docs/latest/booting-with-qemu.html >> > >> > >> > This is the script's ownership and access rights: >> > >> > $ stat coreos_production_qemu.sh >> > >> > File: 'coreos_production_qemu.sh' >> > Size: 6635 Blocks: 24 IO Block: 4096 regular file >> > >> > Device: 80bh/2059d Inode: 13631491 Links: 1 >> > Access: (0755/-rwxr-xr-x) Uid: ( 1000/ michael) Gid: ( 1002/ michael) >> > Access: 2017-07-14 09:21:18.000000000 +0100 >> > Modify: 2017-07-06 19:41:30.000000000 +0100 >> > Change: 2017-07-14 14:38:55.104862083 +0100 >> > >> > Birth: - >> > >> > Trying to start it gives: >> > >> > $ ./coreos_production_qemu.sh -a /home/michael/.ssh/id_rsa.pub -p 2222 -- >> > - >> > curses >> > -bash: ./coreos_production_qemu.sh: Permission denied >> > >> > Any idea what permissions it refers to? I have not tried to run the above >> > as root. >> >> What options are you passing to QEMU? Are you using hardware >> virtualization? If running it as root solves the problem you need to >> add yourself to any virtualization groups QEMU or your manager >> expects, like "kvm." >> >> You might also need to chmod +x the script. >> >> R0b0t1. > > Thanks R0b0t1, I am not passing any options directly to QEMU other than what > the script does. >
Okay, you should probably look at the script considering it's not working. > I'd rather not run it as root, because there is no mention of needing to run > it as root in the URLs I have listed above. If I don't know what options are being to passed to QEMU then I can't help you figure out what you don't have the permission to do.
