Re: [ovirt-users] import qcow2 image to ovirt

[Amit Aviram]

On Thu, Aug 11, 2016 at 5:44 PM, Gianluca Cecchi 
wrote:

> On Thu, Aug 11, 2016 at 4:40 PM, Amit Aviram  wrote:
>
>>
>> On Thu, Aug 11, 2016 at 5:39 PM, Amit Aviram  wrote:
>>
>>> Due to bug:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1365451
>>>
>>> There will need to be special configurations to do, in order to run
>>> ovirt-imageio-proxy after upgrade. we are making best efforts to publish
>>> this fix asap
>>>
>>
>> ​(patch is merged in master, will be available in the next build)​
>>
>>
>>>
>>>
> Ok, I read the bug. for the missing pki. In fact in conf file I see
> reference to missing
>
> # Key file for SSL connections
> ssl_key_file = /etc/pki/ovirt-engine/keys/imageio-proxy.key.nopass
>
> # Certificate file for SSL connections
> ssl_cert_file = /etc/pki/ovirt-engine/certs/imageio-proxy.cer
>
>
> In the mean time I see that if I change the default in
>  /etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf
> from
>
> # Wrap incoming connections with SSL
> use_ssl = true
>
> to
>
> # Wrap incoming connections with SSL
> use_ssl = false
>
> The service starts and it seems it listens to tcp port 54323.
> Could it be a workaround (wit the limitations of not secure trasnport) or
> is it anyway designed to only work through SSL?
>
> ​
Yes, supposed to work. if not for HTTPS connection to ovirt, probably for
HTTP.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] import qcow2 image to ovirt

[Gianluca Cecchi]

On Thu, Aug 11, 2016 at 4:40 PM, Amit Aviram  wrote:

>
> On Thu, Aug 11, 2016 at 5:39 PM, Amit Aviram  wrote:
>
>> Due to bug:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1365451
>>
>> There will need to be special configurations to do, in order to run
>> ovirt-imageio-proxy after upgrade. we are making best efforts to publish
>> this fix asap
>>
>
> ​(patch is merged in master, will be available in the next build)​
>
>
>>
>>
Ok, I read the bug. for the missing pki. In fact in conf file I see
reference to missing

# Key file for SSL connections
ssl_key_file = /etc/pki/ovirt-engine/keys/imageio-proxy.key.nopass

# Certificate file for SSL connections
ssl_cert_file = /etc/pki/ovirt-engine/certs/imageio-proxy.cer


In the mean time I see that if I change the default in
 /etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf
from

# Wrap incoming connections with SSL
use_ssl = true

to

# Wrap incoming connections with SSL
use_ssl = false

The service starts and it seems it listens to tcp port 54323.
Could it be a workaround (wit the limitations of not secure trasnport) or
is it anyway designed to only work through SSL?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] import qcow2 image to ovirt

[Amit Aviram]

On Thu, Aug 11, 2016 at 5:39 PM, Amit Aviram  wrote:

> Due to bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1365451
>
> There will need to be special configurations to do, in order to run
> ovirt-imageio-proxy after upgrade. we are making best efforts to publish
> this fix asap
>

​(patch is merged in master, will be available in the next build)​


>
> On Thu, Aug 11, 2016 at 4:39 PM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> On Wed, Aug 10, 2016 at 4:20 PM, Amit Aviram  wrote:
>>
>>> It seems like you have an early version of ovirt-4.0, if you'll update
>>> your version it might solve some of your problems (such as the exception in
>>> the screenshot). soon, the size and format will be deduced from the image
>>> as well, so many things will be clearer.
>>>
>>> If you want to stay with your version, you'll need to do the following
>>> steps in order to upload the file:
>>> - At the engine's host, yum install ovirt-imageio-proxy
>>> - Then, run engine-setup.
>>> - Add the engine's CA to the Authorities list in your browser. (you can
>>> download it from https://%your_engine%/ovirt-engine/services/pki-resourc
>>> e?resource=ca-certificate=X509-PEM-CA
>>> 
>>> )
>>>
>>> regarding the size- you can choose a bigger size than the original
>>> file's size.
>>>
>>> Hope that works out for you!
>>>
>>>
>>>
>> Hello,
>> I updated both engine and host to 4.0.2 RC4 and during the engine-setup
>> phase I indeed see this:
>>
>> ...
>>
>>   PACKAGE: [install] ovirt-imageio-common-0.3.0-1.el7.noarch
>>   PACKAGE: [install] ovirt-imageio-proxy-0.3.0-0.20
>> 1606191345.git9f3d6d4.el7.centos.noarch
>>   PACKAGE: [install] ovirt-imageio-proxy-setup-0.3.
>> 0-0.201606191345.git9f3d6d4.el7.centos.noarch
>>
>> and the configuration preview appeared as
>>
>>
>>   --== CONFIGURATION PREVIEW ==--
>>
>>   Default SAN wipe after delete   : False
>>   Firewall manager: firewalld
>>   Update Firewall : True
>>   Host FQDN   : ractorshe.mydomain
>>   Upgrade packages: True
>>   Engine database secured connection  : False
>>   Engine database host: localhost
>>   Engine database user name   : engine
>>   Engine database name: engine
>>   Engine database port: 5432
>>   Engine database host name validation: False
>>   DWH database secured connection : False
>>   DWH database host   : localhost
>>   DWH database user name  : ovirt_engine_history
>>   DWH database name   : ovirt_engine_history
>>   DWH database port   : 5432
>>   DWH database host name validation   : False
>>   Engine installation : True
>>   PKI organization: mydomain
>>   DWH installation: True
>>   Backup DWH database : True
>>   Engine Host FQDN: ractorshe.mydomain
>>   Configure VMConsole Proxy   : True
>>   Configure WebSocket Proxy   : True
>>
>>
>> Should I have seen anything related to image proxy in engine-setup
>> configuration preview above?
>>
>> The version installed is:
>> ovirt-imageio-proxy-0.3.0-0.201606191345.git9f3d6d4.el7.centos.noarch
>>
>> I don't get anymore the exception in the GUI but again the upload goes
>> into paused mode as soon as it starts
>>
>> I see that part of the new package there is also a service
>>
>> [root@ractorshe log]# systemctl status ovirt-imageio-proxy.service
>> ● ovirt-imageio-proxy.service - oVirt ImageIO Proxy
>>Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service;
>> disabled; vendor preset: disabled)
>>Active: inactive (dead)
>> [root@ractorshe log]#
>>
>> Do I have to enable and start it?
>> What TCP ports does the upload use? Does the client communicate with the
>> engine or directly with the host?
>>
>
> ​The client uploads directly to ovirt-imageio-proxy, not through the
> engine. this proxy writes to the host.
>
>
>>
>> Thanks,
>> Gianluca
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] import qcow2 image to ovirt

[Amit Aviram]

Due to bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1365451

There will need to be special configurations to do, in order to run
ovirt-imageio-proxy after upgrade. we are making best efforts to publish
this fix asap

On Thu, Aug 11, 2016 at 4:39 PM, Gianluca Cecchi 
wrote:

> On Wed, Aug 10, 2016 at 4:20 PM, Amit Aviram  wrote:
>
>> It seems like you have an early version of ovirt-4.0, if you'll update
>> your version it might solve some of your problems (such as the exception in
>> the screenshot). soon, the size and format will be deduced from the image
>> as well, so many things will be clearer.
>>
>> If you want to stay with your version, you'll need to do the following
>> steps in order to upload the file:
>> - At the engine's host, yum install ovirt-imageio-proxy
>> - Then, run engine-setup.
>> - Add the engine's CA to the Authorities list in your browser. (you can
>> download it from https://%your_engine%/ovirt-engine/services/pki-resourc
>> e?resource=ca-certificate=X509-PEM-CA
>> 
>> )
>>
>> regarding the size- you can choose a bigger size than the original file's
>> size.
>>
>> Hope that works out for you!
>>
>>
>>
> Hello,
> I updated both engine and host to 4.0.2 RC4 and during the engine-setup
> phase I indeed see this:
>
> ...
>
>   PACKAGE: [install] ovirt-imageio-common-0.3.0-1.el7.noarch
>   PACKAGE: [install] ovirt-imageio-proxy-0.3.0-0.
> 201606191345.git9f3d6d4.el7.centos.noarch
>   PACKAGE: [install] ovirt-imageio-proxy-setup-0.3.
> 0-0.201606191345.git9f3d6d4.el7.centos.noarch
>
> and the configuration preview appeared as
>
>
>   --== CONFIGURATION PREVIEW ==--
>
>   Default SAN wipe after delete   : False
>   Firewall manager: firewalld
>   Update Firewall : True
>   Host FQDN   : ractorshe.mydomain
>   Upgrade packages: True
>   Engine database secured connection  : False
>   Engine database host: localhost
>   Engine database user name   : engine
>   Engine database name: engine
>   Engine database port: 5432
>   Engine database host name validation: False
>   DWH database secured connection : False
>   DWH database host   : localhost
>   DWH database user name  : ovirt_engine_history
>   DWH database name   : ovirt_engine_history
>   DWH database port   : 5432
>   DWH database host name validation   : False
>   Engine installation : True
>   PKI organization: mydomain
>   DWH installation: True
>   Backup DWH database : True
>   Engine Host FQDN: ractorshe.mydomain
>   Configure VMConsole Proxy   : True
>   Configure WebSocket Proxy   : True
>
>
> Should I have seen anything related to image proxy in engine-setup
> configuration preview above?
>
> The version installed is:
> ovirt-imageio-proxy-0.3.0-0.201606191345.git9f3d6d4.el7.centos.noarch
>
> I don't get anymore the exception in the GUI but again the upload goes
> into paused mode as soon as it starts
>
> I see that part of the new package there is also a service
>
> [root@ractorshe log]# systemctl status ovirt-imageio-proxy.service
> ● ovirt-imageio-proxy.service - oVirt ImageIO Proxy
>Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service;
> disabled; vendor preset: disabled)
>Active: inactive (dead)
> [root@ractorshe log]#
>
> Do I have to enable and start it?
> What TCP ports does the upload use? Does the client communicate with the
> engine or directly with the host?
>

​The client uploads directly to ovirt-imageio-proxy, not through the
engine. this proxy writes to the host.


>
> Thanks,
> Gianluca
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] import qcow2 image to ovirt

[Gianluca Cecchi]

On Thu, Aug 11, 2016 at 3:39 PM, Gianluca Cecchi 
wrote:

> On Wed, Aug 10, 2016 at 4:20 PM, Amit Aviram  wrote:
>
>> It seems like you have an early version of ovirt-4.0, if you'll update
>> your version it might solve some of your problems (such as the exception in
>> the screenshot). soon, the size and format will be deduced from the image
>> as well, so many things will be clearer.
>>
>> If you want to stay with your version, you'll need to do the following
>> steps in order to upload the file:
>> - At the engine's host, yum install ovirt-imageio-proxy
>> - Then, run engine-setup.
>> - Add the engine's CA to the Authorities list in your browser. (you can
>> download it from https://%your_engine%/ovirt-engine/services/pki-resourc
>> e?resource=ca-certificate=X509-PEM-CA
>> 
>> )
>>
>> regarding the size- you can choose a bigger size than the original file's
>> size.
>>
>> Hope that works out for you!
>>
>>
>>
> Hello,
> I updated both engine and host to 4.0.2 RC4 and during the engine-setup
> phase I indeed see this:
>
> ...
>
>   PACKAGE: [install] ovirt-imageio-common-0.3.0-1.el7.noarch
>   PACKAGE: [install] ovirt-imageio-proxy-0.3.0-0.
> 201606191345.git9f3d6d4.el7.centos.noarch
>   PACKAGE: [install] ovirt-imageio-proxy-setup-0.3.
> 0-0.201606191345.git9f3d6d4.el7.centos.noarch
>
> and the configuration preview appeared as
>
>
>   --== CONFIGURATION PREVIEW ==--
>
>   Default SAN wipe after delete   : False
>   Firewall manager: firewalld
>   Update Firewall : True
>   Host FQDN   : ractorshe.mydomain
>   Upgrade packages: True
>   Engine database secured connection  : False
>   Engine database host: localhost
>   Engine database user name   : engine
>   Engine database name: engine
>   Engine database port: 5432
>   Engine database host name validation: False
>   DWH database secured connection : False
>   DWH database host   : localhost
>   DWH database user name  : ovirt_engine_history
>   DWH database name   : ovirt_engine_history
>   DWH database port   : 5432
>   DWH database host name validation   : False
>   Engine installation : True
>   PKI organization: mydomain
>   DWH installation: True
>   Backup DWH database : True
>   Engine Host FQDN: ractorshe.mydomain
>   Configure VMConsole Proxy   : True
>   Configure WebSocket Proxy   : True
>
>
> Should I have seen anything related to image proxy in engine-setup
> configuration preview above?
>
> The version installed is:
> ovirt-imageio-proxy-0.3.0-0.201606191345.git9f3d6d4.el7.centos.noarch
>
> I don't get anymore the exception in the GUI but again the upload goes
> into paused mode as soon as it starts
>
> I see that part of the new package there is also a service
>
> [root@ractorshe log]# systemctl status ovirt-imageio-proxy.service
> ● ovirt-imageio-proxy.service - oVirt ImageIO Proxy
>Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service;
> disabled; vendor preset: disabled)
>Active: inactive (dead)
> [root@ractorshe log]#
>
> Do I have to enable and start it?
> What TCP ports does the upload use? Does the client communicate with the
> engine or directly with the host?
>
> Thanks,
> Gianluca
>
>

Probably I have to run engine-setup two times: the first installs the
package and the second configures it.
But, at the second run, I do get a new answer

  --== PRODUCT OPTIONS ==--

  Configure Image I/O Proxy on this host? (Yes, No) [Yes]:

then

  --== CONFIGURATION PREVIEW ==--

  Default SAN wipe after delete   : False
  Firewall manager: firewalld
  Update Firewall : True
  Host FQDN   : ractorshe.mydomain
  Engine database secured connection  : False
  Engine database host: localhost
  Engine database user name   : engine
  Engine database name: engine
  Engine database port: 5432
  Engine database host name validation: False
  DWH database secured connection : False
  DWH database host   : localhost
  DWH database 

Re: [ovirt-users] import qcow2 image to ovirt

[Gianluca Cecchi]

On Wed, Aug 10, 2016 at 4:20 PM, Amit Aviram  wrote:

> It seems like you have an early version of ovirt-4.0, if you'll update
> your version it might solve some of your problems (such as the exception in
> the screenshot). soon, the size and format will be deduced from the image
> as well, so many things will be clearer.
>
> If you want to stay with your version, you'll need to do the following
> steps in order to upload the file:
> - At the engine's host, yum install ovirt-imageio-proxy
> - Then, run engine-setup.
> - Add the engine's CA to the Authorities list in your browser. (you can
> download it from https://%your_engine%/ovirt-engine/services/pki-
> resource?resource=ca-certificate=X509-PEM-CA
> 
> )
>
> regarding the size- you can choose a bigger size than the original file's
> size.
>
> Hope that works out for you!
>
>
>
Hello,
I updated both engine and host to 4.0.2 RC4 and during the engine-setup
phase I indeed see this:

...

  PACKAGE: [install] ovirt-imageio-common-0.3.0-1.el7.noarch
  PACKAGE: [install]
ovirt-imageio-proxy-0.3.0-0.201606191345.git9f3d6d4.el7.centos.noarch
  PACKAGE: [install]
ovirt-imageio-proxy-setup-0.3.0-0.201606191345.git9f3d6d4.el7.centos.noarch

and the configuration preview appeared as


  --== CONFIGURATION PREVIEW ==--

  Default SAN wipe after delete   : False
  Firewall manager: firewalld
  Update Firewall : True
  Host FQDN   : ractorshe.mydomain
  Upgrade packages: True
  Engine database secured connection  : False
  Engine database host: localhost
  Engine database user name   : engine
  Engine database name: engine
  Engine database port: 5432
  Engine database host name validation: False
  DWH database secured connection : False
  DWH database host   : localhost
  DWH database user name  : ovirt_engine_history
  DWH database name   : ovirt_engine_history
  DWH database port   : 5432
  DWH database host name validation   : False
  Engine installation : True
  PKI organization: mydomain
  DWH installation: True
  Backup DWH database : True
  Engine Host FQDN: ractorshe.mydomain
  Configure VMConsole Proxy   : True
  Configure WebSocket Proxy   : True


Should I have seen anything related to image proxy in engine-setup
configuration preview above?

The version installed is:
ovirt-imageio-proxy-0.3.0-0.201606191345.git9f3d6d4.el7.centos.noarch

I don't get anymore the exception in the GUI but again the upload goes into
paused mode as soon as it starts

I see that part of the new package there is also a service

[root@ractorshe log]# systemctl status ovirt-imageio-proxy.service
● ovirt-imageio-proxy.service - oVirt ImageIO Proxy
   Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service;
disabled; vendor preset: disabled)
   Active: inactive (dead)
[root@ractorshe log]#

Do I have to enable and start it?
What TCP ports does the upload use? Does the client communicate with the
engine or directly with the host?

Thanks,
Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] import qcow2 image to ovirt

[Amit Aviram]

It seems like you have an early version of ovirt-4.0, if you'll update your
version it might solve some of your problems (such as the exception in the
screenshot). soon, the size and format will be deduced from the image as
well, so many things will be clearer.

If you want to stay with your version, you'll need to do the following
steps in order to upload the file:
- At the engine's host, yum install ovirt-imageio-proxy
- Then, run engine-setup.
- Add the engine's CA to the Authorities list in your browser. (you can
download it from
https://%your_engine%/ovirt-engine/services/pki-resource?resource=ca-certificate=X509-PEM-CA

)

regarding the size- you can choose a bigger size than the original file's
size.

Hope that works out for you!







On Wed, Aug 10, 2016 at 1:32 PM, Gianluca Cecchi 
wrote:

>
>
> On Wed, Aug 10, 2016 at 12:26 PM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> On Wed, Aug 10, 2016 at 12:13 PM, Amit Aviram  wrote:
>>
>>> If you are using ovirt-4.0, you can just upload it to any storage domain
>>> you have, from
>>> Storage->domain->disks tab->Upload->Start
>>> or:
>>> Disks->Upload->Start
>>>
>>> Thanks, Amit.
>>>
>>>
>>>
>>>
>> I didn't know about it so I just tested uploading a local file.
>> Can I only select and put nothing in the lower part of the screen?
>> Because I get this error with both the options:
>> https://drive.google.com/file/d/0BwoPbcrMv8mvNzliUWs5a0dGV2c
>> /view?usp=sharing
>> It seems nothing in engine.log or events
>>
>> $ qemu-img info /tmp/manageiq_01.qcow2
>> image: /tmp/manageiq_01.qcow2
>> file format: qcow2
>> virtual size: 40G (42949672960 bytes)
>> disk size: 1.5G
>> cluster_size: 65536
>> Format specific information:
>> compat: 0.10
>> refcount bits: 16
>>
>> On storage domain I have 11Gb free. Would it calculate 40Gb of necessary
>> storage or 1.5Gb?
>>
>> Gianluca
>>
>
> Ok, self answer.
> As I have visual problems to notice the square border changes (and didn't
> notice the dotted lines under the required fields).
> Putting now data inside the upload starts, but then I see message "Paused
> by System" in disks page
> and in engine.log many mlines of type
> 2016-08-10 12:28:02,410 WARN  [org.ovirt.engine.core.bll.
> storage.disk.image.UploadDiskImageCommand] (DefaultQuartzScheduler9)
> [4a24dd69] Failed to stop image transfer session. Ticket does not exist for
> image '53e2ee54-b710-4872-bea6-fbecfa767bf9'
>
> Also, as I have to specify a size, does that mean that I can use a
> different virtual size from the original qcow2 file I'm uploding?
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] import qcow2 image to ovirt

[Gianluca Cecchi]

On Wed, Aug 10, 2016 at 12:26 PM, Gianluca Cecchi  wrote:

> On Wed, Aug 10, 2016 at 12:13 PM, Amit Aviram  wrote:
>
>> If you are using ovirt-4.0, you can just upload it to any storage domain
>> you have, from
>> Storage->domain->disks tab->Upload->Start
>> or:
>> Disks->Upload->Start
>>
>> Thanks, Amit.
>>
>>
>>
>>
> I didn't know about it so I just tested uploading a local file.
> Can I only select and put nothing in the lower part of the screen?
> Because I get this error with both the options:
> https://drive.google.com/file/d/0BwoPbcrMv8mvNzliUWs5a0dGV2c/
> view?usp=sharing
> It seems nothing in engine.log or events
>
> $ qemu-img info /tmp/manageiq_01.qcow2
> image: /tmp/manageiq_01.qcow2
> file format: qcow2
> virtual size: 40G (42949672960 bytes)
> disk size: 1.5G
> cluster_size: 65536
> Format specific information:
> compat: 0.10
> refcount bits: 16
>
> On storage domain I have 11Gb free. Would it calculate 40Gb of necessary
> storage or 1.5Gb?
>
> Gianluca
>

Ok, self answer.
As I have visual problems to notice the square border changes (and didn't
notice the dotted lines under the required fields).
Putting now data inside the upload starts, but then I see message "Paused
by System" in disks page
and in engine.log many mlines of type
2016-08-10 12:28:02,410 WARN
 [org.ovirt.engine.core.bll.storage.disk.image.UploadDiskImageCommand]
(DefaultQuartzScheduler9) [4a24dd69] Failed to stop image transfer session.
Ticket does not exist for image '53e2ee54-b710-4872-bea6-fbecfa767bf9'

Also, as I have to specify a size, does that mean that I can use a
different virtual size from the original qcow2 file I'm uploding?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] import qcow2 image to ovirt

[Gianluca Cecchi]

On Wed, Aug 10, 2016 at 12:13 PM, Amit Aviram  wrote:

> If you are using ovirt-4.0, you can just upload it to any storage domain
> you have, from
> Storage->domain->disks tab->Upload->Start
> or:
> Disks->Upload->Start
>
> Thanks, Amit.
>
>
>
>
I didn't know about it so I just tested uploading a local file.
Can I only select and put nothing in the lower part of the screen?
Because I get this error with both the options:
https://drive.google.com/file/d/0BwoPbcrMv8mvNzliUWs5a0dGV2c/view?usp=sharing
It seems nothing in engine.log or events

$ qemu-img info /tmp/manageiq_01.qcow2
image: /tmp/manageiq_01.qcow2
file format: qcow2
virtual size: 40G (42949672960 bytes)
disk size: 1.5G
cluster_size: 65536
Format specific information:
compat: 0.10
refcount bits: 16

On storage domain I have 11Gb free. Would it calculate 40Gb of necessary
storage or 1.5Gb?

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] import qcow2 image to ovirt

[Amit Aviram]

If you are using ovirt-4.0, you can just upload it to any storage domain
you have, from
Storage->domain->disks tab->Upload->Start
or:
Disks->Upload->Start

Thanks, Amit.

On Wed, Aug 10, 2016 at 11:26 AM, David David  wrote:

> Hi all
>
> ovirt 4.0
>
> there is KVM qcow2 image:
>
> file format: qcow2
> virtual size: 466G (500106788864 bytes)
> disk size: 86G
> cluster_size: 65536
>
> How to import the image with the same disk size, 86 GB, to ovirt ?
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users