Bug 215413

Summary: Incorrect Xen vm disk size brings the system to its knees
Product: [Fedora] Fedora Reporter: Daniel Qarras <dqarras>
Component: virt-managerAssignee: Daniel Berrangé <berrange>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Jenner <mjenner>
Severity: medium Docs Contact:
Priority: medium    
Version: 6CC: xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 0.5.3-1.f8 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-22 21:39:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Daniel Qarras 2006-11-13 20:52:15 UTC
Description of problem:
I was testing FC6/Xen on a laptop with 100GB HDD. I ran virt-install and
accidentally gave disk size 2000 (gigabytes). virt-manager merrily continues its
journey to install a virtual machine until it start formatting the / partition,
it seems to take eons and will bring the system to its knees, nothing is
responding under GNOME. After a forced reboot I found the disk image file being
2TB size(!).

The same absurd behaviour can also be triggered with virt-manager.

Version-Release number of selected component (if applicable):
xen-3.0.3-0.1.rc3
kernel-xen-2.6.18-1.2849.fc6
virt-manager-0.2.3-2.fc6
libvirt-0.1.7-2

How reproducible:
Always.

Steps to Reproduce:
1. Create a new Xen virtual machine
2. Enter some hilarious disk size, e.g., 10 times your physical disk size
3. See the system crawling until the userr frustrates completely
  
Actual results:
System dying slowly.

Expected results:
Bizarre disk size rejected before proceding to OS install.

Additional info:
With sane disk size everything is working all ok.

Comment 1 Daniel Qarras 2006-11-13 20:53:57 UTC
To add confustion, virt-manager wants file size in megabytes, virt-install in
gigabytes.

Comment 2 Jeremy Katz 2006-11-16 16:53:07 UTC
virt-manager should probably some sanity checking here and at least get
confirmation; virt-install allows things like this somewhat intentionally (makes
it easier to do testing of large disks, etc)

Comment 3 Hugh Brock 2007-06-18 18:21:45 UTC
Just to save me some testing, was the absurdly large storage file sparse or
non-sparse? I assume non-sparse, but can you say for sure?

Comment 4 Daniel Qarras 2007-06-19 13:53:41 UTC
I can say for sure only that I was using default values and not doing any sparse
settings by hand.

Comment 5 Red Hat Bugzilla 2007-07-25 02:06:57 UTC
change QA contact

Comment 6 Cole Robinson 2008-01-22 21:39:56 UTC
F6 is end of life, but this certainly should not be an issue in F7 or F8, as
there is sanity checking in virt-install and virt-manager to ensure we do not
attempt to create a disk that is larger than available space on the host.
Closing this as CURRENTRELEASE.