Comment 7 for bug 619843

Nothing in Eucalyptus changed in this regard between 1.6.2 and 2.0.0, I believe. On two other KVM-based distros the console.log file, which is produced by KVM, is readable to Eucalyptus. We can add a patch to chown or chmod the file via euca_rootwrap every time prior to reading it, but that is a hack. Ideally, we would figure out why this is happening on Maverick. Could apparmor profile for KVM (or libvirt?) have something to do with this? (I agree that root ownership of "disk" and "kernel" is surprising and not consistent with other distros - those files are written by the NC directly.)