Search results

If I keep getting IO errors (and FS gets mounted as read only) does that mean the virtual disk is corrupt or the underlying physical disk on the server itself has issues. I am trying to make backups (creating copies of files) on a VM but during the creation of the copies on the VM I keep...

Not sure if this is related, but the same VM had an issue w/ the backup last night after doing an update via dist-upgrade: 110: 2019-02-27 18:27:06 INFO: Starting Backup of VM 110 (qemu) 110: 2019-02-27 18:27:06 INFO: status = running 110: 2019-02-27 18:27:08 INFO: update VM 110: -lock backup...

agent: 1 balloon: 2048 boot: dc bootdisk: virtio0 cores: 8 ide2: cdrom,media=cdrom memory: 12288 name: iddemo net0: e1000=2A:80:53:BB:21:E0,bridge=vmbr0 numa: 0 onboot: 1 ostype: l26 scsihw: virtio-scsi-pci sockets: 2 vga: std virtio0: local-lvm:vm-110-disk-1,size=50G

I have seen some older posts (version 5.2) with this error. The solution was to update. I am running the current 5.3 version and got this error on a backup last night. This file does exist, and the VM is running so not sure why we got this error. 2019-02-14 18:27:23 ERROR: Backup of VM 110...

YES!! It took a while to find it (the man page could use some work) but for anyone else trying to do the same: # pvesh create /nodes/{nodename}/startall From here: http://vasilisc.com/proxmox-ve-api-nodes#_nodes_{node}_startall

Does the equivalent exist command line? The backups are controlled by a script.

How can I start all VMs that have the 'start at boot' option checked? We weekly shut down all VMs and do a backup while shut down and the previous method we used to start all back up is no longer working in version 5.x. We were stopping the pve-manager service and then starting again. This no...

Sorry - I thought that qcow2 was the only way to get snapshots - that may be old info in the wiki or I misunderstood/misread.

Hi Been testing latest 5.1, trying to get all the settings correct so that shapshots will work (VMs with qcow2 disks as I have read). But, I can't seem to get the right combination of file system type (ext4, xfs, etc) and lvm-thin and Bus/Device. All seem to have the options for disk format...

Ok I figured out my issue - I had the info in the storage.cfg file twice somehow. dir: local path /var/lib/vz content backup,vztmpl,iso lvm: localLVM vgname pve shared 0 content images,rootdir

I guess my understanding of the logical volumes is not complete. I was under the impression that you needed a physcial volume, and then a logical volume for LVM (my experience comes from CentOS where you take the physical disk, add a physical volume then a logical volume and then your system...

It works only if there isn't a logical volume?

What was the solution here? I am experiencing the same issue, have added new disks, they show as empty via 'df -v' but full in the web GUI.

I have upgraded to 4.4. Disks appear to be fine. Will have to wait and see I guess. Were there any known bugs there in 4.3?

Not too sure what is happening with our system. Seems to be quite slow. In /var/log/syslog we have a lot of system-udevd timeout messages: Oct 31 02:48:34 servername pvedaemon[16994]: <root@pam> successful auth for user 'root@pam' Oct 31 02:50:52 servername systemd-udevd[27508]: timeout...

After the reboot, the times were much shorter: Oct 30 09:36:16 servername systemd-timesyncd[906]: interval/delta/delay/jitter/drift 2048s/+0.002s/0.016s/0.004s/+9ppm Oct 30 09:36:18 servername pvestatd[1399]: status update time (5.212 seconds) Oct 30 09:36:29 servername pvestatd[1399]: status...

I had the same experience again on Friday. Extremely slow backup - after a reboot it worked fine. Same results in the /var/log/syslog: Oct 29 06:32:03 servername pvestatd[1394]: status update time (194.423 seconds) Oct 29 06:32:05 servername systemd-timesyncd[907]...

No. I had to reboot to get the backup to actually finish. Just says: (Nothing has been logged yet.)

We occasionally experience a backup to disk (not a vzdump - a copy of the vzdump files, after the vzdump backup has finished) that is very slow. The syslog is full of: pvestatd[1387]: status update time (286.687 seconds) It is not always the same disk (there is a rotation). And after a...

Tried VMware compatible, worked as well. For anyone else w/ issues using CentOS 5 VMs, the best combo so far is the standard VGA video driver, then to fix the mouse issue using the vmware mouse driver as per this thread. Thanks everyone!