Unable to create VM using NFS storage (Fedora build 29)

asked 2019-01-19 13:14:02 -0500

meidan gravatar image

Have three systems with identical hardware other than one which has an additional 1 terrabyte internal disk. Two are running Fedora 29 Workstation, the third server with the additional disk is running Fedora 29 server. All have the latest updates as of the time this post is being written. All three are virtualization capable and enabled. The three systems are on gigabit ethernet connected to the same network hub. All have static IP addresses which are defined in each system's local host file.

The idea was to have a test environment with two systems serving as hypervisors and the third with the additional disk providing storage via an nfs mount to the two hypervisors. When QEM/KVM is used to create a new virtual machine using "local" disk on the two hypervisors there is no issue--the image is created, and ownership is "qemu/qemu". I am executing all this as root user.

When I attempt to use the NFS mount it always fails with a "permission error". However, it does not fail until after the disk allocation is made (ie there is a 20 gig "<systemname>qcow2" file in /var/lib/libvirt/images, perms 600 root/root) The error(s) appear right after the file was created and as the message "create domain" flashes on the QEM/KVM gui.

The NFS file system being used is mounted on the NFS server as " type ext4 (rw,relatime,seclabel)" The exportfs on the NFS file server has an entry for each of the hypervisor systems of the form: /cloud <ipaddress> (no_root_squash,rw,sync) Neither system used as hypervisors seems to have any issue using the NFS share outside of trying to create the VM images.

The image file being tested with to create VM is "Fedora-Workstation-Live-x86_64-29-1.2.iso" and is sitting in the NFS share on "/var/lib/libvirt/images".

I do not know if the fact selinux is "enforced" has anything to do with this. The actual messages I get when the attempted build using the NFS mounted file system fails is as follows:

Unable to complete install: 'internal error: process exited while connecting to monitor: 2019-01-19T15:43:44.576789Z qemu-system-x86_64: -drive file=/var/lib/libvirt/images/fedora29.qcow2,format=qcow2,if=none,id=drive-virtio-disk0: Could not open '/var/lib/libvirt/images/fedora29.qcow2': Permission denied'

Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper callback(asyncjob, args, *kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 2559, in _do_async_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 465, in start_install doboot, transient) File "/usr/share/virt-manager/virtinst/guest.py", line 401, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/lib64/python3.7/site-packages/libvirt.py", line 3718, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirt.libvirtError: internal error: process exited while connecting to monitor: 2019-01-19T15:43:44.576789Z qemu-system-x86_64: -drive file=/var/lib/libvirt/images/fedora29.qcow2,format=qcow2,if ... (more)

edit retag flag offensive close merge delete


Try to use iscsi instead of ntfs if you are creating virtual machines on it

aeperezt gravatar imageaeperezt ( 2019-01-19 13:37:37 -0500 )edit