After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 736097 - Cannot add system broker's machine w/o main storage disk
Cannot add system broker's machine w/o main storage disk
Status: RESOLVED OBSOLETE
Product: gnome-boxes
Classification: Applications
Component: general
3.13.x
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
: 746766 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2014-09-05 06:30 UTC by vladimir benes
Modified: 2018-01-11 10:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description vladimir benes 2014-09-05 06:30:23 UTC 
Description of problem:
cannot add system broker machine to GB. it still yields empty location error. 

Version-Release number of selected component (if applicable):
3.13.91

How reproducible:
always

Steps to Reproduce:
1.create new machine via virt-install (to system broker)

virt-install -r 64 --name Core-5.3 --nodisks --cdrom Downloads/Core-5.3.iso --connect qemu:///system

2.try to connect to system broker machines in new box page

Actual results:
Empty Location

Expected results:
machines should be listed and import successful

Additional info:
Comment 1 Zeeshan Ali 2014-10-18 16:59:19 UTC 
Ok, so the issue is that virt-install command in comment#0 does not create a disk for the machine and the import feature of Boxes mainly imports the the vm image.

I think Boxes needs to handle the case of (cdrom only) like a new live machine but only taking the name/title from the original machine.
Comment 2 Zeeshan Ali 2015-08-06 13:50:45 UTC 
*** Bug 746766 has been marked as a duplicate of this bug. ***
Comment 3 GNOME Infrastructure Team 2018-01-11 10:11:00 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-boxes/issues/32.