Bug 618922 - qemu could not load kernel '/home/user/.virtinst/boot/...' permission denied
Summary: qemu could not load kernel '/home/user/.virtinst/boot/...' permission denied
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.1
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
Keywords: RHELNAK
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-28 04:50 UTC by Andrew Ross
Modified: 2013-10-20 22:18 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2010-12-01 15:15:21 UTC

Attachments (Terms of Use)
Error message. (1.16 KB, text/plain)
2010-07-28 04:50 UTC, Andrew Ross
no flags Details

Description Andrew Ross 2010-07-28 04:50:34 UTC
Created attachment 434910 [details]
Error message.

Description of problem: Trying to create a virtual machine and got a warning that the emulator may not have permission to access /home/<user>/.virtinst/boot. 

Proceeded anyway as I haven't seen that in Fedora and managed to kill virt manager :-/ 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Follow steps to create a new vm (via http)
Actual results: See attachment

Expected results:

Additional info:

Comment 2 RHEL Product and Program Management 2010-07-28 05:17:47 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 3 Cole Robinson 2010-08-06 14:58:02 UTC
Can you provide ~/.virt-manager/virt-manager.log?

Is your home directory on NFS or any non-default setup?

Comment 4 Cole Robinson 2010-12-01 15:15:21 UTC
No response for a while, so closing as WORKSFORME. if you can still reproduce, please reopen with the info requested in Comment #3

Note You need to log in before you can comment on or make changes to this bug.