From: Richard C. <ric...@ai...> - 2011-05-13 17:26:39
|
Hi Giovanni, Thank you for the encouragement... at least I know someone out there has done this successfully. We're running Proxmox VE 1.8, and this is the exact error message we're getting: 5385 open("/mfs/pve/images/101/vm-101-disk-1.raw", O_RDWR|O_DIRECT|O_CLOEXEC) = -1 EINVAL (Invalid argument) What version of proxmox are you running? Thanks, Richard. On 11-05-13 12:45 PM, Giovanni Toraldo wrote: > Hi Richard, > > On 13/05/2011 16:24, Richard Chute wrote: >> Specifically, we're using proxmox for virtualization in our environment, >> and we seem to be hitting a snag when using KVM containers -- the >> virtual machines won't start. We currently believe that this may be >> because MFS (or FUSE, possibly) does not allow mmap'ing of files. >> I am wondering if anyone can shed some light on this type of >> situation (using MFS for storage of KVM virtual machines) and/or if >> anyone has any known or possibly unknown issues with mmap'ing files on MFS. > I am managing a Proxmox cluster of 2 nodes with raw disk images on a MFS > volume, and I haven't any problem with it. > > Actually I am mounting the mfs volume via an > /etc/network/if-up.d/moosefs-mount.sh, that mount the volume under > /srv/mfs, and on Proxmox I configured a new storage volume for virtual > images, that's all. > > Bye. > |