Search results

Hmm, this is exactly what I see on two system here. And take a look at these threads: https://forum.proxmox.com/threads/proxmox-4-4-13-restore-issue.34379/ https://forum.proxmox.com/threads/high-io-delay-on-restore.34358/ I think there's a general problem how the restore is writing data to the...

I also see these high IO delay while restoring to a zfs pool. I tried with and without dedup and/or compression. Regardless with settings I choose I get IO delays about 50%. The test system uses consumer grade SSD with SATA connections, but I see similar results with NVMe SSD. Maybe there's...

Hello, I would like to run latencytop but something is missing: I'm running proxmox 4.4 with latest updates applied:

Do you use virtio or scsi for the disks? I had the same issues with scsi, after changing to virtio everything is much smoother.

I can at least verify that the "vm stays locked after problems with a backup" also happends to me several times. This mostly happens when the target storage has some kind of trouble (disk full, network connection lost). But I didn't notices this the last few weeks so maybe the bug is "gone" due...

I just run your "test", here's the result: ls -l /mnt/vmfs-backup/dump/bla1test.txt ls: cannot access /mnt/vmfs-backup/dump/bla1test.txt: No such file or directory touch /mnt/vmfs-backup/dump/bla1test.txt ls -l /mnt/vmfs-backup/dump/bla1test.txt -rw-r--r-- 1 root root 0 Feb 2 09:39...

I have a strange issue while trying to backup one of my proxmox servers. Depending on how the backup is started I will get the error message: ERROR: vma_queue_write: write error - Invalid argument Backup target is a cifs (autofs) mounted filesystems in another data center. If I try to backup...

Sure no problem. Just playing around with LXC and the disk handling seems to be incomplete (no offense, just noticed). But just to make sure: This is a great improvement! I really like playing with proxmox. Keep up the good work.

Ok, that's the resize part. But how to add another virtual disk or even a existing block device seems to be much more complicated. With "pct --help" I didn't see anything that seems to be related to this topic. And asking google seems to bring up some solutions but they require bind mounts...

I just upgraded my test system to proxmox 4 and created a LXC container. It looks fine but how can I add another disk and/or resize the current root disk?

ttyUSBx devices are usally RS-232 <-> USB converters like this one: http://www.ftdichip.com/Products/Cables/USBRS232.htm BTW: I had the same problem a few days back. And maybe it makes sense to allow devices like /dev/ptyX (as used by many examples like this...

This is already reported as a bug (at 2014-06-13), see https://bugzilla.proxmox.com/show_bug.cgi?id=529

Hello Dietmar, good job, my token worked nearly out of the box. I still need to make the windows (the -w switch) bigger. I don't know how common such a "running ahead token" but the OTP provider for apache uses the last successful login time to adjust such tokens. I think you will need more...

Great news and very cool features! Maybe you can enhance the two factor authentication a litte bit to support my c200 token. To get it working I need to patch /usr/share/perl5/PVE/AccessControl.pm like this: diff -u /usr/share/perl5/PVE/AccessControl.pm...

You could try: qm set <vmid> -hotplug 1 But I would suggest that you use unpartioned space instead of a LVM volume inside the VM (eg /dev/vdc without any partition that maps to a host LVM Volume).

I didn't investigate this any further till now but I noticed that even using VLANs won't isolate all traffic, or to be more precise at least on my setup (which is maybe faulty). I got some DHCP request from the default VLAN into a specific VLAN which I didn't expect. I'm not sure why this...

You maybe need to reactivate your LVM volume with: lvchange /dev/lvm-ssd-01/vm-210-disk-1 -a y My (working) /etC/pve/qemu-server/210.conf looks like: args: -drive file=/dev/lvm-ssd-01/vm-210-disk-1,if=none,id=drive-virtio1,aio=native,cache=none -device...

I enabled qemu guest agent support with "qm set 170 -agent true" and verified that the agent option is used (kvm is running with -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0). So I assume the host part is ok. But if I try to install the client side (the qemu-ga-x64.msi from...

I followed the instructions on http://pve.proxmox.com/wiki/Windows_2012_guest_best_practices and http://pve.proxmox.com/wiki/SPICE#Windows_2008.2C_2008r2.2C_and_2012. But I wonder if there is something wrong/missing as there is no QXL driver for windows server 2012 yet. So I think the sentence...

Just a note. It seems that the kernel pve-kernel-3.10.0-1-pve: 3.10.0-5 seems to cause some trouble with my hardware. If a bridged network card is heavily used the proxmox host gets some error messages like: After these messages on the host the Ubuntu guest network transfer will be stalled. I...