Windows virtual machine : non persistent drive possible ?

Marc Ballat

Well-Known Member
Dec 28, 2015
33
3
48
55
Hi,

I would like to know if Proxmox has a feature similar to a non-persistent drive in VMWare Workstation. I remember that a similar question has already been asked and answered negatively in the past. But things may have changed though searching both the internet and this forum hasn't given me any positive answer.

The Windows virtual machine is configured with two volumes (one for the OS and the other for data). I use LVM-thin and virtio. I would like the OS to reside on a non-persistent volume (i.e. one whose changes are not permanent and returns to its previous status every time I boot).

Thanks in advance.

Marc
 
Thanks. If I can vote somehow for this feature, let me know. It is really useful for Windows machines that tend otherwise to slow down over time and update or reset settings by themselves.
 
just comment in the enhancement request that you would like it as well - we try to take into consideration if many people want to see a feature

Of course we cannot give any timeframe when it will be done.
 
Alex,

Doesn't a snapshot apply to all drives ? I only one the C: drive, where the OS and programs are, to be frozen. The other drive(s) contain data and must be able to change permanently.

Marc
 
Normally, yes, but if thats the requirement you dont need to use the proxmox snapshot mechanism; revert to snapshot of only the disk you wish using whatever storage method you use snapshot mechanism- presuming you create seperate vdisks for volume(s) you wish to control seperately.

For example, assuming you're using ceph, you'd create two disks (one for disk c, and one for the rest of your partitions;) you hook script will call

rbd snap rollback [poolname]/vm-[vmid]-disk-0@[your original snap name]

disk 1 will remain unaffected.
 
No offence Alex, but suggesting that each user spend time building a custom "Hookscript" when this has been a feature in competing hypervisors for over a decade is a bit ridiculous, and very hacky. This feature is clearly desirable, and shouldn't require new infrastructure (as your script/hack suggests) to have it developed in Proxmox. I also see this feature as being very useful as VDI continues to become a big deal, along with GPU support and advanced storage (NVMe) support...
 
No offence Alex, but suggesting that each user spend time building a custom "Hookscript" when this has been a feature in competing hypervisors for over a decade is a bit ridiculous, and very hacky.
None taken- I'm not a proxmox dev ;)

My point was, is and continues to be that the true strength of Proxmox is its extensibility- if there is no proxmox canonical solution provided, feel free to make your own.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!