Search results

Why is this still an issue ? I stumbled on this issue a few days ago and if there was a fix created to solve the conflict between Spice vdagent and Citrix close to 4 years ago, one could imagine the virt driver iso having a working driver. Removing Citrix might not be a solution for everyone...

Vmware converter can be used to migrate the machine and possibly other backup solutions like veeam but those will not make the switch so easy since they will not keep the both machines (source and target) in sync. What is the server serving ? If the content on the server is not changing you...

in my case I have working audio on my client computer. Adding a virtual audio card to the vm (windows or Linux) will make everything work right away since most operating systems support intel-hda chips naitively. The key is to use virt-viewer and spice. The rest is automatic /Anders

My colleague just managed to work around the issue and will write down what he did so we can help solving this... Here is the solution: Start the 6.4 installer iso Let it fail. manually configure networking interface, gw and dns start the interface chmod 1777 /tmp apt update Xorg -configure...

I am using Linux for pro audio stuff and also Proxmox but not much in combination. I have tried to run Ardour with sample buffer 1024 or higher and it kinda works but still some dropouts so don't expect good realtime audio but I think you could do some audio stuff with vm's if you want to...

We have a few Huawei servers (1288H V5) that was going to run Proxmox. However the installer 6.4 does not work on these. It ends with Installation aborted - unable to continue This seems to happen just before the Installer Gui is about to start. Searching the internet reveals this is a problem...

If you can reboot the remote server using a virtual iso (using idrac or similar management) you could boot a clonezilla live CD and clone the server to your target vm. This means of course that you must get a working ssh connection between the two clonezilla instances...

That is super nice !! That is how most backup systems that I have come across do it. a bitmap tracking file... They are not backed up because: 1. Non important machines that are just for lab usage 2. Had no good way to back them up until PBS happend :) I am arguing just for the good cause to...

My test environment is a single node backing up to a vm in another single node Ok, makes sense but.... I have two larger VMs on the same PVE that consumes over 7TB each and the initial backup seems to take 21hours per VM so my question is. Will the dirty-bit tracking persist if I reboot the...

I think you want to have a nice desktop and run VMs as you please and perhaps Proxmox is not the best approach in that case. Proxmox is by default a non-gui installation but I guess you could go for a Debian with desktop environment and add procmoc too it but I would probably go for a more...

I my case the VM currently backing up has progressed 47% in 4hours and 15 minutes and was backed up yesterday and have not been used since last backup..

So I am testing backups of my VMs too and have a few VM's that are shut down. Will those take a lot of time like many hours (one VM is 3.1 TB) every time the backup is run since there is no dirty-bit support ? If so, any VM not running during backup will potentially render the backup...

That is awesome. Unfortunately I cannot do this unsupported reflashing of the embedded sas controllers on my fairly expensive Huawei servers.. I would rather solve the issue the software way and that doesn't include switching to esx or other supposedly working hypervisors. Thanks for reporting...

I finally had to give Up trying. If this was a home brew system with regular HBAs I could have tried reflash them without the ROM part but my two systems where brand new Huawei servers intended for production and since there was limited interest in this issue I had to ditch using Proxmoxen as...

I have for days tried to run Freenas under Proxmox and using HBA passthrough without total success. My approach is two brand new storage servers Huawei 5288 V5 (manufactured early 2019) with onboard LSI HBA (LSI SAS3 MPT Controller sas3008 (TI-Mode)) as well as an onboard LSI based...

To be more clear. I will create a huge zfs pool but will not use Proxmox as the owner of the pool. Dedicated VM will own all disks and the pool. As of now, the pool is successfully created and things seems OK, except Proxmox not showing the disks assigned to the VM qm config shows them /Helle

After some more test... The gui shows up to 16 scsi-disks if i name them from scsi0-15. Disks with higher id will not be presented visually but will still be available to the VM Anyone knows where to change the limit to allow the gui to show all scsi disks ? Thanks

This is great information ! This is my first post and I registered just to make my point. I have a couple of storage servers with 32 disk slots and the purpose is to build dedicated storage servers but have Proxmox just to monitor the storage vm and be able to upgrade the storage os and test...