-boun...@lists.opennebula.org] On Behalf Of Rangababu
Chakravarthula
Sent: Sunday, 24 October 2010 2:38
To: Rich Wellner
Cc: users@lists.opennebula.org
Subject: Re: [one-users] Do not use qcow image format with latest ONE
Rich
It is libvirt that adds that flag. I am not exactly sure, starting which
Hi,
I also face this issue on an Ubuntu 10.10 which uses latest libvirt etc...
did you create a bug at opennebula ?
Olivier
Le 10/23/10 5:37 PM, Rangababu Chakravarthula a écrit :
Rich
It is libvirt that adds that flag. I am not exactly sure, starting
which version it started to do this.
Rich
It is libvirt that adds that flag. I am not exactly sure, starting which
version it started to do this. It wasn't doing this in libvirt 0.75. I think
starting 0.8 it has started to do this.
Unless specified otherwise, by default libvirt marks driver type as raw
which gets passed as format
Using RC1 I just ran across a bug that was reported in August. I've
included the text of the email below. I just wanted to give a heads up
that it's still there. The weird part is that I have no idea how it got
triggered. I was able to run images yesterday until about noon.
Started
Hello,
I am playing with latest checkout of ONE (branch one-2.0) and I found out
that my old images aren't working anymore (getting 'no bootable device' on
display). They were of type 'qcow2' which was no problem before (circa 3 weeks
ago). Anyway, I noticed that 'kvm' process does have
