Search results

Hi all, I have a guest with it's virtual disk on a proxmox storage. I also have a hard disk that I wish to connet to this guest "as is", somehting like -drive file=/dev/sdb. Is there a way to do that? The only way I can thing is: - run the guest - enter on proxmox server by ssh - ps aux | grep...

Never mind, it was a problem with the mount point that wasn't mounted. Sorry for the noise.

Hi all, I have a host with a single guest. I noticed the backup (snapshot) has failed: vzdump 100 --mailto xxxxxxxxxxxx --mode snapshot --mailnotification always --storage backup --quiet 1 --compress lzo 100: gen 15 08:39:05 INFO: Starting Backup of VM 100 (qemu) 100: gen 15 08:39:05 INFO...

Hi all, I have a proxmox 5.1-41. I had a nfs storage named 'cubo' and I was saving in a subvoler of it. I chose to create a dedicated entry in /etc/exports (nfs side) instead of saving in a sub folder. The steps I followed are these: - removed the nfs storage from proxmox - stopped nfs server -...

proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve) pve-manager: 5.1-35 (running version: 5.1-35/722cc488) pve-kernel-4.13.4-1-pve: 4.13.4-25 libpve-http-server-perl: 2.0-6 lvm2: 2.02.168-pve6 corosync: 2.4.2-pve3 libqb0: 1.0.1-1 pve-cluster: 5.0-15 qemu-server: 5.0-17 pve-firmware: 2.0-3...

Hi, yesterday I installed a new supermicro server with 64G of ram with latst proxmox 5. As of now there's only a windows 2012 R2 guest with 48G of ram. As storage backend it's using SCSI (virtio). I installed the latest virtio driver available (0.1.141) and qemu guest agent. I have a script that...

MMMmmm. What Bus/device are you using for your guests? (IDE, Sata, Virtio Block, SCSI)

If you can also replicate the bug, please confirm my bug report.

Hi, could you try to change backup mode to "snapshot"?

I also forgot to mentions that the guest ha no problem restarting after it has been shut down by qem-guest-agent (right click, shutdown).

Well, I wrote to early. This time the guest was able to boot but it ended with a blue screen! This is my guest conf agent: 1 balloon: 2048 boot: cdn bootdisk: scsi0 cores: 12 cpu: host ide2: iso:iso/sql206_standard_ats.iso,media=cdrom,size=2893164K memory: 12288 name: win2016 net0...

It started fine, so I can't reproduce the problem...but I noticed it more than one time.

I tried to do a backup with SNAPHOST mode and the guest started fine. I forgot to mention that the guest was not running during backup. I'm groin to try once more to backup with STOP mode and see it replicates again.

Hi all, I noticed this problem after a backup (mode STOP). The guest is a windows 2016 and is using virtio-SCSI. In the past there has been problem with backup using STOP mode and VIRTIO. I suspect there may be problem with virtio-SCSI as well. Did you notice if the message appeared after a...

Cool explanation! Thank you very much. Next Saturday I'll talk about about Proxmox at the Linux Day, specifically about thin-provisioning and discard. Your help is really appreciated!

Correct me if I'm wrong but 'discard' is strictly related to thin provisioning. There's no meaning in discard option without thin provisioning. From wikipedia The topic title could be renamed "Question about raw and discard". But I still find confusing the sentence "This format do not support...

In my last post I've been testing the capability of qcow2 to shrink when data gets removed from the guest. As discussed before, the guest need to have use 'SCSI' as Bus/Scsi (virtio-scsi) and the 'dicard' option checked. Reading qm_virtual_machines_settings documentation page I see So I tried...

This is the key! I moved the vdi to local storage /var/lib/vz and shrink/discard works right away. I don't know why, but it doesn't work on NFS storage. If I create or convert a qcow2 file by qemu-img, the size shown is this: qemu-img create -f qcow2 test.qcow2 1G ls -lh test.qcow2 -rw-r--r-- 1...

I successfully tested thin provisioning on lvm-thin. I converted a lv into a qcow2 file. create full clone of drive scsi0 (vm:vm-107-disk-1) Formatting '/mnt/pve/nas-ufficio/images/107/vm-107-disk-1.qcow2', fmt=qcow2 size=10737418240 encryption=off cluster_size=65536 preallocation=metadata...

I found this bug has already been reported here. The bug report asks also other things that I suggested to move on a new bug request. I changed the 'component' from qemu-server to pve-manager.