On Mon, Dec 16, 2013 at 01:43:54PM +0100, Pino Toscano wrote:
> The current add_cdrom way basically appends a new raw "-cdrom /path"
> parameter to the qemu invocation (even when using libvirt as backend),
> hence such images are seen as "CD-ROM drives" inside the appliance.
> However, there is no
On Mon, Dec 16, 2013 at 01:42:51PM +0100, Pino Toscano wrote:
> On Saturday 14 December 2013 22:50:28 Richard W.M. Jones wrote:
> > Earlier in the test, you'll probably need to add this:
> >
> > if [ ! -s ../guests/fedora.img -o ! -s ../guests/debian.img ]; then
> > echo "$0: test skipped
The current add_cdrom way basically appends a new raw "-cdrom /path"
parameter to the qemu invocation (even when using libvirt as backend),
hence such images are seen as "CD-ROM drives" inside the appliance.
However, there is no need for such particular behaviour, as they need to
be handled as norm
On Saturday 14 December 2013 22:50:28 Richard W.M. Jones wrote:
> On Fri, Dec 13, 2013 at 04:32:49PM +0100, Pino Toscano wrote:
> > The current add_cdrom way basically appends a new raw "-cdrom /path"
> > parameter to the qemu invocation (even when using libvirt as
> > backend), hence such images a
