Ownership transfer bypasses quota check

Bug #403373 reported by Chris Post on 2009-07-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Invirt Project

Bug Description

Transferring ownership of an existing VM appears to bypass both the RAM and disk quota checks.

Specifically, a running VM with 50 gigs disk and 512 megs RAM was transferred successfully from a group locker to a user locker where the user locker had an already running VM using around 10 gigs disk and 256 megs RAM.

Peter Iannucci (iannucci) wrote :

Possible resolutions include refusing to transfer ownership until the user requests a quota bump, declaring this the intended behavior, and transferring quota amounts along with the vm. The latter seems prone to abuse.

Chris Post (ccpost) wrote :

You could eat up arbitrary amounts of disk this way, which you would have across VM reboots. The RAM quota should get checked if any machine gets turned back on after turning off, but you could temporarily eat up all the available RAM on the hosts if you felt malicious, potentially preventing other VMs from booting.

I think the most correct behavior here is to refuse the transfer if it violates either quota limit on the receiving end.

Greg Price (gregprice) on 2009-09-20
Changed in invirt:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers