Bug 212449 – virt-manager deletes my new VM

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 212449 - virt-manager deletes my new VM

Summary:	virt-manager deletes my new VM

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	virt-manager (Show other bugs)
Sub Component:
Version:	6
Hardware:	All Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Daniel Berrange
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2006-10-26 16:13 EDT by Need Real Name
Modified:	2007-11-30 17:11 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:	virt-manager 0.4.0-2
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-06-14 14:20:18 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Need Real Name 2006-10-26 16:13:15 EDT

I created a VM on a 3 gigabyte disk file.
File> Restore Virtual Machine> Selected the disk file.
virt-manager deletes it.

Quality stuff.

Comment 1 Daniel Berrange 2006-10-26 16:47:00 EDT

The 'restore' menu options isn't for starting inactive domains, its actually for
restoring guests that have previously been suspended (aka hibernated/saved). So
it is not expecting a raw disk image, but instead a VM suspend image. That said
it ought to have detected that you supplied a bogus image & refused to proceed,
rather than deleting it.

Comment 2 Need Real Name 2006-10-26 16:52:40 EDT

It's amazing that it deleted it.

Maybe the restore option could be more explicit too.
I had powered off a VM and wanted to run it again. I presumed that was right.

Comment 3 Hugh Brock 2007-06-14 14:20:18 EDT

This is now fixed with validation that the image we are trying to get xen to
restore is in fact a valid Xen Paravirt image.

Note You need to log in before you can comment on or make changes to this bug.