Search results

Hi, I created new role pveum roleadd PVE_Power-only-Clientes -privs "VM.PowerMgmt VM.Console" but with permissions the user not show VM on web. To see the VM on the web, the role VM.Audit necessary but this role allows you to resize the hard drive. This is a bug?. Best regards.

This is an example of how bad it works (NAS Storage to Local hard disk). INFO: starting new backup job: vzdump 113 --remove 0 --node noc --compress lzo --mode snapshot --storage BackupLocal INFO: Starting Backup of VM 113 (qemu) INFO: status = stopped INFO: update VM 113: -lock backup INFO...

(sorry my bad english) Amil, I have the same problem with OVH (Canada). Low speed and problem with storage latency and performance. Is a disaster!. OVH is currently being attacked, but that should not affect all customers of OVH. Tickets the answer when they want and do not cooperate with...

Hi, can disable the option resize disk for rol PVEVMUser ? This rol read only and PowerMgmt with boot options. Best regards.

Ok, thanks for your help like. I will continue investigating what happens. I started a ticket at OVH to analyze latency storage but still got no answer. Best regards

No, I not modified, only changed the name. noc:~# cat /etc/pve/qemu-server/113.conf balloon: 3072 bootdisk: virtio0 cores: 1 memory: 4096 name: gabrielbrahim net0: bridge=vmbr2,virtio=66:36:65:31:30:65,tag=10 numa: 0 ostype: l26 smbios1: uuid=3a98f903-9f66-4a09-a46d-3c0d3f72d1df sockets: 4...

noc:~# ll /opt/scripts/vzdump_mod.sh -rwxr-xr-x 1 root root 4650 Aug 30 16:59 /opt/scripts/vzdump_mod.sh Task viewer: Backup OutputStatus Stop INFO: starting new backup job: vzdump 113 --mode snapshot --storage BackupsVMS --remove 0 --node noc --compress lzo INFO: Starting Backup of VM 113...

Hi, thanks for the script!. Tested with one QEMU VM offline and not work. I have NFS Storage (SAS - 10000 rpm, 2.5) with 10 Gbps connection. Last week running, but this week stopped walking well. I use Proxmox VE 4.2 up to date. My vzdump.conf is correct?. noc:~# cat /etc/vzdump.conf # vzdump...

Hi @robhost , Can you shared the script?. I have the same problem with backups (kvm and lxc). Thanks, Best regards

He had tried to use this method but at the time I had not worked. I have only two nodes because that's what I can use for now. The switch supports multicast. Where are the logs cman?.

Make 2 migration, comment in this thread that gave me the final error of migration and the VM I was blocked, the other migratedsuccessfully. They were at different times, both delayed! How to unlock vm?. I have another problem, node 2 gets a red dot. I have to restart the cman to be properly...

Switch: Trednet TEG-S2600i IBM M2: HDD 500 Gb, 2x Intel Xeon CPU E3110 @ 3.00 Ghz, RAM 2 Gb. IBM M3: HDD 500 Gb, 4x Intel Xeon CPU X3430 @ 2.40 Ghz, RAM 6 Gb. Make 2 migration, comment in this thread that gave me the final error of migration and the VM I was blocked, the other...

Sorry! I thought it worked differently. I think a 160 GB virtual disk, but I thought I was just going to spend the occupied space. I'm in an experimental stage and then put into production.

For offline migration is so slow?. Very few megs and took almost 4 hours. Jan 23 20:25:54 starting migration of VM 150 to node 'proxmox-2' (192.168.200.72) Jan 23 20:25:54 copying disk images vm-150-disk-1.raw rsync status: 32768 0% 0.00kB/s 0:00:00 rsync status: 1720221696 1%...

CLOSED THREAD! The problem was the switch. Replace with a SWITCH seriously and works perfect!. Thanks for your help dietmar!

I am using a conventional switch, it may be that my problem?

Yes. I downloaded this iso: proxmox-ve_2.0-784729f4-19.iso I try with two servers IBM M2 and IBM M3.

Re-install Proxmox on both servers, and then I followed the wiki article you told me. And he gave me this error.

New problem :) haha I can visualize the nodes from the website but I can not create VMs on the remote node, I can't upload files isos and migrate vms on remote node. The error I get when I go to migrate a vm is as follows: Jan 23 15:01:11 # /usr/bin/ssh -c blowfish -o 'BatchMode=yes'...

I just did, I am updating both servers. :)