Search results

Well... well.. well... Ends up that the client Never mind... The client did not told me that the disk was not connected yet on the board. So I almost bang my head in the wall the I learn that. After the disk plugged, everything working properly. Thanks for your reply.

Hi. So, we have plugged Emulex interface card into a Dell R640 server. Apperently, the kernel already has support to this card, out-of-the-box. The DC people are insist that need to install drivers in order to make the HBA disk appears. I already used others HBA, like IBM, Pure Storage and never...

Anybody?

I don't think that has something to do with GlusterFS. Didn't get nothing in the logs and others VMs are backed up normaly. I am waiting for window to reboot the servers to see if this issue will be fix. Thanks

Hi... I have 2 server with initialy was Proxmox 8.1. I have update to 8.4.1 but still doesn't reboot server. Now, when I try to add a disk, I got this error: failed to update VM 102: 400 Parameter verification failed. scsi1: hotplug problem - VM 102 qmp command 'device_add' failed - Parameter...

Hi there. Got another Vm with the very same issue: INFO: scsi3: dirty-bitmap status: existing bitmap was invalid and has been cleared And than, State file handle. I don't know if this has something to do, but the 2 VM has 5 or 7 disks, and one of the disk has no discard enabled. After mark this...

Hi! I have partialy solved this issue. This VM in particular, has 7 disk: scsi0 scsi1 scsi2 scsi3 scsi4 scsi5 scsi6 So I market the last two disk to backup=0 and than the backup ran normaly. I am still doing research in order to know if this last two disk were assign from a different VM. But...

I already do a upgrade and now running 3.4.1 The VM are using a directory based storage, which is over GlusterFS volume. There is around 30 VMS in this storage. The backup is running smothly in all of this VMs. Only this one VM has this issue. I am doing a clone to see if I can backup the cloned...

Hi. I am running PBS 3.2-8 here, and the datastore is a SATA HDD. I got just one VM with this error: INFO: starting new backup job: vzdump 2221 --node proxmox01 --storage bkp --remove 0 --notification-mode auto --mode snapshot --notes-template '{{guestname}}' INFO: Starting Backup of VM 2221...

Forget it! It's a silly thread. Somebody can remove it? Sorry to disturb.

Yes! I got that! But my question is why show the total amount of ram if it's not been used in that moment? IMHO It should be display only when I started the VM. With the VM powered off, should display nothing. On the other hand, when I powered on the VM, so than the graphic should display the...

Nop!!! Somethings is not right! I have create a new VM and never powered on. This new VM has 4G of memory. I've started an old VM with has also 4G and bang! The new VM that never was powerded on, start to register memory usage! And I have created the VM with 2G first! Here a screenshot...

But the graphic is named "memory usage" and the VM is powered down. There is no memory usage at all! How could be that? A graphic showing memory usage in a VM that is not using memory? So weird.

Yes I am aware of that, but the thing is the VM is not running!

Hi... Thanks for you reply. Nop. No previously VM with the same ID. And the third screenshot, was create recently and with only one VM. >> Is the graph set to Hourly? Is set to default. I didn't touch it.

Hi there. I have a question about the graphic generated about Memory Usage. As you can see in the attach, I have several Vms but only one runing. Neverthless, the memory usage graphic is reflected to the others VMS. Why is that? Is that something to do with balloon? Thanks for any...

Well... It's ok. Sad, but ok. Usually I create a gluster volumes and mount both nodes. Then, I share this as type directory storage. Never use the glusterfs plugin. So, for qemu/kvm and proxmox standpoint, is always a directory, right? Like I do here...

[ SOLVED ] I just change from the GlusterFS plugin to directory pulgin and the warning message is gone. I usually to a gluster volume and define it inside /etc/fstab file, like this: serverA: gluster1:VMS /vms glusterfs defaults,_netdev,x-systemd.automount,backupvolfile-server=gluster2 0 0...

Hi Is the gluster not support properly anymore? I set two PVE box with Proxmox VE 8.4 and GlusterFS 10, which is shipped with Debian Bookworm. I have had used gluster for many years now, with no issues at all. You guys will, eventually kick off GlusterFS for good? More warning messages...

I wonder if this static file is executable via WSL in a Windows box!