Search results

mmm yes, reading again, that part could be more as you say. But the point is openvz will not get any memory sharing help as kvm does, and the hyervisor needs memory of its own so, tak ealso that into account Marco

I think Udo means: this current thread is about having only Openvz, so KSM is not involved here. to the OP: int the suggested thread I read "you should leave a couple of GB free for the host system. With OpenVZ, it can be much more." so if your CTs (openvz) concurrently use even less than the...

good to know, thanks. Why not adding a wiki page for this (if there isn't one for pfsense already)? Marco

that means that you have commented the line in the .conf? I would try that, too. Of course also because nothing else worked :D on more thing: remember that any change you make to .conf (gui or cli) you MUST stop and start, not reset/restart from gui. Marco

yes, but I think that is not causing the crash, or you would have noticed... My guess is that other differences could be more involved: - memory: 640 not very high, but I guess you would have spotetd this from logs - scsihw: virtio-scsi-pc search the forums about this and w2k3... or try...

You can use that and/or also use two 1G link bonded (or more) to the storage. And also use different timings. Or, also, backup locally to the nodes, if you have local space, and then use a script to move them wherever when/how you like it. Or, also, use more than one backup storage (which could...

You could try to post more details about your troubled vm (conf, logs, etc.) and pve hosts detailed info, at least. As any OS project, it has no guarantee by itself. You can try to debug what is happening by yourself, asking others, and upstream providers too. But is a very difficult job, since...

Hi backup is done by vzdump tool, which has the parameter -bwlimit and global configuration is stored in /etc/vzdump.conf. https://pve.proxmox.com/wiki/Vzdump_manual afaik (using 1G link instead of 10G will take 10x time, anyway...) Marco

Hi, something really weird happened, because vm disks don't disappear in this way, usually. probably, the vm disk storage is involved. You didn't post much detail... Also, as usual, pve packages versions (use "#pveversion -v") could help to spot something... Marco

Hi, my W2003 AD is on pve 3.1 since years, quite stable. it was a P2V conversion. here is the .conf: acpi: 1 balloon: 0 boot: dc bootdisk: virtio0 cores: 1 cpuunits: 1000 freeze: 0 ide2: none,media=cdrom kvm: 1 memory: 2048 name: ADserver net0: e1000=XX:XX...XX,bridge=vmbr0 onboot: 1 ostype...

citing the http://pve.proxmox.com/wiki/Storage_Model wiki page: "LVM: this storage type is only used to store RAW VM disk images, and first needs an iSCSI "base storage" entry defined or local disks prepared as LVM storage." I can't see any place where it says that LVM storage can be used...

you could try to be sure that the repository are ok, and then try an "apt-get update" from the cli (ssh). but Dietmar (ie: pve devs) would know the best for you, I'm sure. Marco

I think that is the list of the turnkey templates available in the web gui. the list is update daily. "200 ok" means it worked. I get similar logs, every day, nearly at the same hour. Marco

I never said that. But saying: it seems you think all the others are mad. Isn't it? I think that someone who can access the server/cluster (or the lan) made some mistake, of which you are currently probably unaware, but you can find which posting configs and command outputs and also looking...

sorry but are you really thinking proxmox users around the world which are running thousands of cluster are so mad to run such an unstable system, in production? doesn't any other option come to your mind? if the packages are screwed, either it was wrongly installed or something else happened...

if it happens during post, could it mean you have to upgrade/patch your mb bios? if it happens during linux boot, it could be the kernel you're using? Marco

Yes, I agree on small nas "all in one" like synology and similars i have some rack qnap, similar to synology, but used also smaller ones for storage. the smaller units offer iscsi too, but smaller units horsepower is limited, high end rack units have better chips/ram, even xeon cpus and are...

yes true, fast typed. I meant that even a windows desktop could be used for that. Marco

or, mounting a network share (even a shared NTFS folder) as a proxmox local folder, and using that folder as "local" to back up Marco

Hi, any news about this? I already bought the two available books from symmcomm and others, but free learning materials from the makers could help many more people, perhaps... And it could help you manage basic forum request replying with the usual RTFM :D Marco