Bug 892765 - virt-manager needs to store Guest Image & Guest Settings in Home folder by Default
Summary: virt-manager needs to store Guest Image & Guest Settings in Home folder by De...
Keywords:
Status: CLOSED DUPLICATE of bug 557103
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 18
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-07 19:04 UTC by Moez Roy
Modified: 2013-04-08 20:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-01 10:04:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Moez Roy 2013-01-07 19:04:55 UTC
virt-manager needs to store Guest Image & Guest Settings in Home folder

Like how VirtualBox does by default:

/home/*username*/VirtualBox VMs

Inside folder 'VirtualBox VMs' there is Guest Image and Guest Settings.

This makes it easier for backup.

Example, when upgrading to Fedora 18, I just backed up my Home Folder.

Then if I need to use a Guest OS, I only need to copy the Guest OS folder from my backup into the "clean install" of Fedora 18.

Then I just click Add Machine in VirtualBox manager ==> Machine ==> Add (CTRL + A) and point it to the .vbox file which has the Guest OS settings and also states that the .vdi image is located in same folder.

Comment 1 Cole Robinson 2013-04-01 10:04:23 UTC
This really requires using qemu:///session, which we may never do by default, but we need to improve support for.

*** This bug has been marked as a duplicate of bug 557103 ***

Comment 2 Moez Roy 2013-04-06 02:03:24 UTC
Why would I want to run a qemu session which I believe is a software only virtualization? 

Why not KVM?

I really need to keep my virtual images on a separate hard-drive from OS.

Comment 3 Cole Robinson 2013-04-08 20:41:55 UTC
qemu:///session uses KVM so you should see comparable speeds


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