interesting - I'm looking at it right now and will try to give it a shot when I get home. Thanks! I knew there had to be SOME way to do this...
http://wiki.openvz.org/Bind_mounts
OK the upgrade to 1.8 went well - those modprobe errors are gone. Still can't mount nfs inside of the openVZ containers, but I kind of figured that. I also went ahead and tried the 2.6.32 kernel as well. So far, so good.
I certainly would love to, I have a whole bunch of them for various small servers, development and test machines, and other stuff. But this mounting thing is killing me. I even tried using sshfs (first time ever) and realized that fuse is required as a kernel module as well.
is there anyone...
hmm.. I did some digging on my host machine and ran cat /proc/filesystems and pulled back this:
so just for grins, I ran modprobe nfs on the proxmox host and this happened:
is that expected behavior too?
hmm - as a last ditch effort, I tried to mount it as a samba share (it's on an openfiler NAS and shared out as both). trying both a manual mount and via fstab, I get the same sort of error
I think it's about time I give up on this appliance and use a KVM VM
ah - that makes sense. Thanks for the clarification. I'll keep digging, but if I can't make this work soon, I might end up just saying screw it and making a KVM machine to do what I need.
hmm.. thanks for that. I didn't see that in the wiki. It did not help, however. Portmap was already running, and I actually was able to install nfs-common without any errors. It just errors when I try to mount something. for example, mount -a returns "mount.nfs: No such device" when /etc/fstab...
I am currently running VE 1.5 (yes, I know I need to upgrade) with the 2.6.18.4-pve kernel. I have an Ubuntu 8.04 guest that I am trying to give myself the ability to access an NFS mount. I've installed nfs-common inside the guest, but whenever I try to mount, I get this:
now, I did some...
I think I found the source of my issue... it was actually the switch that the box was plugged into. Every now and then, it would freak out and down all the ports. When this would happen, it would cause Proxmox to think that the link went down. I moved the cable to a new switch and so far all is...
I have been running Proxmox VE 1.5 since it's release and have recently run into an issue. Occasionally, I will lose the host network, requiring me to run ifconfig eth0 down && ifconfig eth0 up in order for it to gain connectivity again. There are multiple nics on the server itself, but I'm only...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.