Search results

Hi, your english is fine :) I don't know what is the issue but, - are all the nodes and NFS server on the same lan? - from the node3 are you able to reach the storage? - are you sure there is no block on the NFS server (ip list, permissions)? - have you checked the logs (/var/log/syslog or...

see this http://pve.proxmox.com/wiki/Nested_Virtualization it might help you Marco

Hi, it could depend on so many factors... you gave no detail on your host(s?), storage, vpe versions, vm configs... the easiest reason could be that your storage has become slower. - if it is network base, check that - if t is local, check its performance also, see "man pveverf" and report...

see this for reference http://en.wikipedia.org/wiki/Network_File_System#Typical_implementation a NFS share is a way for a server to allow access to its storage from the network. It is done "exporting" a folder with a name, roughly said. So the "export" you must provide is the name of the NFS...

not always: this happened a me a couple of times. Adding the lazy option, changed all. Marco

you should probably familiarize yourself with this http://pve.proxmox.com/wiki/Storage_Model Marco

I'm sure you are right, but in order to fully understand, could you please elaborate a bit more on why you think so? Thanks, Marco

I am learning zfs and would like to know better how to use it for the same purpose: storing raw disks on zfs to be able to take snapshots (like qcow2 ones?) the zfs_over_iscsi wiki page seems to suggest that you can use proxmoxm zfs_over_iscsi storage plugin if you have one of the supported zfs...

... how did you got a fat32 boot partition? the 3.4 installer allows for ext3, ext4 and zfs (new for 3.4)... Marco

yes it's normal, you can keep multiple kernels, and switch at boot (they're all listed in grub menu). if you're sure to remove an unused kernel, you can remove it from CLI using "apt-get remove <packagename>" like "apt-get remove pve-kernel-2.6.32-27-pv" if you wish to remove that. no need to...

I suggest you to start simple: create a test proxmox vm and choose the smallest vmdk disk (say, 1GB), choose the "shared storage" as storage. look at where it is and how it's named. say 123 is your VM VMID. your new 1gb empty vmdk disk should be <storagename>:/123/vm-123-disk-1.vmdk keep the...

Well, if you try to create a new vm in proxmox, you should see that when you have to choose an hard disk option, you have three choices: qcow2, raw, vmdk. Simply put, you could just run your vmdk in proxmox, you just need to tell your config to use it. It is not the preferred choice for most...

Sorry I missed why you need the vma at all. You could do just the reverse disk conversion from vmdk to raw or qcow2 or even just use the vmdk in proxmox, since it's supported. And when the vmdk is running in proxmox, you can convert it online (live) with the move disk feature, eve from the...

and, if your virtual OS doesn't know of virtio, you should load virtio drivers in it BEFORE converting the disk... and, when adding/readding disks, check the vm boot order... Marco

you should probably use the fastest for which your os has best support (drivers). vitrio means paravirtualized, ie: using your pve host real hardware directly, see http://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows as an example usually linuxes can run all of them but that...

I'm sorry but I'm not that expert... and this never happened to me, in 5 years through several versions... A quick google search shows that something similar happened in the past on various linux systems... this seems not a pve specific problem, and I'm sure pve it's used in so many clusters...

sorry but if you place one remote server on a single ssd and all the company depends on it... it is a bad choice. shit happens :) anyway, have you tried booting from livecd, checking disks and maybe tried reinstalling grub to the hard drive? is it possible that boot order changed so that (say)...

on any wiki page, top right, click "Log in / create account" then you will finda link under the words "To obtain a user account, you must request one." soon they will check you rrequest and allow you to log in Marco

just to help everyone understand: your answer is that this problem is not to be solved on proxmox ve side, but on libiscsi? from the initial post, it seemed that the rtequest was <<ask the Proxmox maintainers to modify how SCSI unit attention conditions are handled in Proxmox>>..? I'm lost Marco

happened the same to me and others. already asked here, no feedback, wish you luck :) Marco