On Wed, May 30, 2018 at 03:35:11PM +0300, Nir Soffer wrote:
> This is not the flow we are looking for. We need a way to read qcow2 data
> from a pipe.
The flow you asked for:
> > > image in any format -> qemu-img -> [qcow2 byte stream] -> imageio http
> > > server -> http client
is exactly what
On Wed, May 30, 2018 at 11:58 AM Richard W.M. Jones
wrote:
> On Wed, May 30, 2018 at 12:11:21AM +0300, Nir Soffer wrote:
> > Exporting images or ova files:
> >
> > image in any format -> qemu-img -> [qcow2 byte stream] -> imageio http
> > server -> http client
>
> You can do this with nbdkit +
On Wed, May 30, 2018 at 12:11:21AM +0300, Nir Soffer wrote:
> Exporting images or ova files:
>
> image in any format -> qemu-img -> [qcow2 byte stream] -> imageio http
> server -> http client
You can do this with nbdkit + plugin, it's exactly what we do today
for virt-v2v:
On Mon, May 28, 2018 at 2:38 PM Kevin Wolf wrote:
> Am 28.05.2018 um 12:27 hat Arik Hadas geschrieben:
> > On Mon, May 28, 2018 at 11:25 AM, Kevin Wolf wrote:
> >
> > > [ Adding qemu-block ]
> > >
> > > Am 27.05.2018 um 10:36 hat Arik Hadas geschrieben:
> > > > On Thu, May 24, 2018 at 6:13 PM,
Am 29.05.2018 um 11:27 hat Richard W.M. Jones geschrieben:
> On Mon, May 28, 2018 at 01:27:21PM +0300, Arik Hadas wrote:
> > Let me demonstrate briefly the flow for OVA:
> > Let's say that we have a VM that is based on a template and has one disk
> > and one snapshot, so its volume-chain would be:
On Mon, May 28, 2018 at 01:27:21PM +0300, Arik Hadas wrote:
> Let me demonstrate briefly the flow for OVA:
> Let's say that we have a VM that is based on a template and has one disk
> and one snapshot, so its volume-chain would be:
> T -> S -> V
> (V is the volume the VM writes to, S is the
Am 28.05.2018 um 16:06 hat Tomáš Golembiovský geschrieben:
>
> On Mon, 28 May 2018 13:37:59 +0200
> Kevin Wolf wrote:
>
> > Am 28.05.2018 um 12:27 hat Arik Hadas geschrieben:
> > > On Mon, May 28, 2018 at 11:25 AM, Kevin Wolf wrote:
> > >
> > > > [ Adding
On Mon, 28 May 2018 13:37:59 +0200
Kevin Wolf wrote:
> Am 28.05.2018 um 12:27 hat Arik Hadas geschrieben:
> > On Mon, May 28, 2018 at 11:25 AM, Kevin Wolf wrote:
> >
> > > [ Adding qemu-block ]
> > >
> > > Am 27.05.2018 um 10:36 hat Arik Hadas
Bug submitted:
https://bugzilla.redhat.com/show_bug.cgi?id=1583176
Kind regards,
Marko
On 25/05/2018, 16:57, "Tomáš Golembiovský" wrote:
On Fri, 25 May 2018 12:13:33 +
"Vrgotic, Marko" wrote:
>
>
> On
Am 28.05.2018 um 12:27 hat Arik Hadas geschrieben:
> On Mon, May 28, 2018 at 11:25 AM, Kevin Wolf wrote:
>
> > [ Adding qemu-block ]
> >
> > Am 27.05.2018 um 10:36 hat Arik Hadas geschrieben:
> > > On Thu, May 24, 2018 at 6:13 PM, Nir Soffer wrote:
> > >
>
On Mon, May 28, 2018 at 11:25 AM, Kevin Wolf wrote:
> [ Adding qemu-block ]
>
> Am 27.05.2018 um 10:36 hat Arik Hadas geschrieben:
> > On Thu, May 24, 2018 at 6:13 PM, Nir Soffer wrote:
> >
> > > On Thu, May 24, 2018 at 6:06 PM Vrgotic, Marko <
>
Apologies for delay,
I am reporting a bug atm.
Will send the bug number id afterwards.
On 25/05/2018, 16:57, "Tomáš Golembiovský" wrote:
On Fri, 25 May 2018 12:13:33 +
"Vrgotic, Marko" wrote:
>
>
> On
[ Adding qemu-block ]
Am 27.05.2018 um 10:36 hat Arik Hadas geschrieben:
> On Thu, May 24, 2018 at 6:13 PM, Nir Soffer wrote:
>
> > On Thu, May 24, 2018 at 6:06 PM Vrgotic, Marko
> > wrote:
> >
> >> Dear Nir,
> >>
> >> Thank you for quick reply.
>
On Thu, May 24, 2018 at 6:13 PM, Nir Soffer wrote:
> On Thu, May 24, 2018 at 6:06 PM Vrgotic, Marko
> wrote:
>
>> Dear Nir,
>>
>> Thank you for quick reply.
>>
>> Ok, why it will not work?
>>
>
> Because the image has a backing file which is not
On Fri, 25 May 2018 12:13:33 +
"Vrgotic, Marko" wrote:
>
>
> On 25/05/2018, 12:29, "Tomáš Golembiovský" wrote:
>
> Hi,
>
> On Fri, 25 May 2018 08:11:13 +
> "Vrgotic, Marko" wrote:
>
>
On 25/05/2018, 12:29, "Tomáš Golembiovský" wrote:
Hi,
On Fri, 25 May 2018 08:11:13 +
"Vrgotic, Marko" wrote:
> Dear Nir, Arik and Richard,
>
> I hope discussion will continue somewhere where i am able to
Hi,
On Fri, 25 May 2018 08:11:13 +
"Vrgotic, Marko" wrote:
> Dear Nir, Arik and Richard,
>
> I hope discussion will continue somewhere where i am able to join as watcher
> at least.
please open a bug on VDSM. This is something we need to deal with during
import
Dear Nir, Arik and Richard,
I hope discussion will continue somewhere where i am able to join as watcher at
least.
I have not seen any communication since Nir’s proposal. Please, if possible
allow me to somehow track in which direction you are leaning.
In the meantime, as experienced
Dear Nir,
I believe i understand now. The image imported is not base image, but required
backing file to be able to work properly.
Maybe silly move, but i have tried to “solve/workaround” around the problem by
rebasing image to remove backing file dependency, but it’s clear now why I than
saw
On Thu, May 24, 2018 at 6:06 PM Vrgotic, Marko
wrote:
> Dear Nir,
>
> Thank you for quick reply.
>
> Ok, why it will not work?
>
Because the image has a backing file which is not accessible to oVirt.
> I used qemu+tcp connection, via import method through engine
Dear Nir,
Thank you for quick reply.
Ok, why it will not work?
I used qemu+tcp connection, via import method through engine admin UI.
Images was imported and converted according logs, still “backing file” invalid
entry remained.
Also, I did use same method before, connecting to plain
On Thu, May 24, 2018 at 5:05 PM Vrgotic, Marko
wrote:
> Dear oVirt team,
>
>
>
> When trying to start imported VM, it fails with following message:
>
>
>
> ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ForkJoinPool-1-worker-2) []
22 matches
Mail list logo