Search results

I'm nearly out of ideas... the only other thing that comes to mind is that server and client OS components (samba, nfs, or their dependencies) types/versions could be so different to be not compatible... o_O check the server access logs to be sure the request comes from the right IP address...

I guess those above are typos only in the forum post, since there is no path, "abailable" instead of "available" "writeable" istead of "writable"... Marco

Hope this can help you, this is my samba share config on the ubuntu kvm server [htdocs] path = /var/www available = yes valid users = @domain\group read only = no browseable = yes public = yes writable = yes create mode = 0660 directory mode = 0770 as for nfs server, I...

I just double checked: I can mount on ubuntu a samba share offered by another ubuntu, both on the same pve cluster with: sudo mount -t cifs //<ipserver>/sharename /mnt/test -o username=<username>,workgroup=<workgroupname> Do you have this package installed on the client ubuntu (the one on...

Linuxes can mount remote resources using plenty of protocols, but afaik one of the most used is NFS, which also has server and client components. https://en.wikipedia.org/wiki/Network_File_System I would also try on some ubuntu forum to get more hints about that samba share... it should work...

Hi, I think proxmox has nothing to do with this, probably... and although I never used a samba share with linuxes only, but the error message says it's a permission denied problem... have you double checked login/password, and maybe tried to add also the workgroup name info into options...

Is it still possible to have a two node (not HA) with shared storage (like iscsi/nfs) and live migration, though? And if (hopefully) yes, apart from HA, would any other feature be missing from such a setup in term of just virtualization features / management (ie: not about CEPH or other...

ok, but would it be illegal? would one damage proxmox, doing so? suppose I have to reinstall a 3.1 node from scratch, now. Marco

...would it be illegal to share past official proxmox ISOs? I still have many of them and why past ISO are removed from the website, leaving only latest...? if one is running an older version (say, 3.1) and needs to repair a broken node, before upgrading to later versions, how is he supposed to...

Two without HA is possible, no problems. I run that since version 1.5... Marco

not specific of 4.0, but if the vm is under (working) HA mode, in that case it will be "restarted" on, not "moved" to, the node2 if node1 down suddenly, nothing can be "moved" from there (to have business continuity, you need a cluster at software level between two vm on different nodes (or...

4.2 kernel, of course ;) Marco

I'm not that techie :) but I think you could start trying the nearest, older or newer, or even then 3.x (note: no openvz support). If you're still in trouble, maybe asking pve support you'll have more chances to spot what is happening on your server, but they'll need any possible HW detail...

most people is running perfectly running vms on that pve so... if is not the hw, and not the hypervisor, it should be... the vms? you could try to install and test (at least for as long to match your freeze timing) a reproducible vm like a standard win/linux from iso or cd. That _must_ run...

I would try a totally different hw machine if possible... even just for a test to confirm this happens on different servers and/or I wuld try an older pve version, just to get an hint. Marco

!! well, I'm glad you're going to sort it out, finally... I always had good experiences with IBM X servers, in my limited experience (I sysadmin a small company), though. I hope they'll solve all kinds of troubles for you, and add some bonus to repay of all the head scratching trying to figure...

see http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.4 it should work. You could need to reboot to run the new kernel, though. Depending on many factors, live migration between 3.1 and 3.4 could work, in order to reboot an upgraded node without...

I see on search engines of many 0x3b errors on windows (many versions) itself, even on real hardware. In some cases is related to not stable drivers, like network cards... apart the above w2003 AD server, I run also w2008r2 without troubles, ran w2000 with minor issues and still run two nt4...

indeed... it even changed german to english... :)))))))) Marco

Not necessary. Going live (VM running) sometimes it fails: I usually just retry and it works. If it fails again, retrying after stopping the VM has never failed to me... anyway, it' so easy :) Marco