> Solaris 10U3, latest kqemu, qemu-0.9.0-CVS plus TAP patch.
>
> I'm aware that a fair amount of "rootish" access is required for the TAP and
bridge
> stuff, and I'm working on that. As kind of a secuirty thought, I figured
> I'd use setfacl to give myself access to the /dev/kqemu device instead
> of leaving it mode 664 or 666.
>
> However, that didn't work. "getfacl /dev/kqemu" output's this:
>
> # file: /dev/kqemu
> # owner: root
> # group: root
> user::rw-
> user:bent:rwx #effective:rw-
> group::rw- #effective:rw-
> mask:rw-
> other:r--
Works for me, on Nevada/snv_55b.
% getfacl /dev/kqemu
# file: /dev/kqemu
# owner: root
# group: root
user::rw-
user:jk:rwx #effective:rw-
group::r-- #effective:r--
mask:rw-
other:r--
% id
uid=109(jk) gid=20(usr)
% truss -s\!ALRM -t open /opt/SUNWqemu/bin/64/qemu-system-x86_64 -m 32 -fda
/files/tiger2/tmp/winme_floppy.img
...
open("/dev/kqemu", O_RDWR) = 8
...
% ls -l /dev/kqemu
crw-r--r--+ 1 root root 208, 0 Okt 27 11:31 /dev/kqemu
> However, running qemu with kqemu enabled shows me the message that
> kqemu acceleration is not enabled. Hmmm. Change to 664, it works. Argh.
Why does 664 work? Are you ("bent"?) a member of group "root"?
> This kind of hackery worked when I wanted to get read access to my real
> /dev/dsk/c0d0p0 so I could use DamnSmallLinux to read my NTFS XP partition.
