Solved

Where is my VirtIO ISO file in container?

  • 30 October 2019
  • 6 replies
  • 2172 views

Userlevel 3
Badge +17

Hey guys,

I have uploaded some of ISO and disk image files including VirtIO to container via Prism Central and they all are marked as ACTIVE means that the upload process has completed successfully.

But when I looked into the container to find the uploaded files via command line or WinSCP, all of them are being kept in container except for VirtIO iso file. Do you know how I can find it?

 

Thanks and Regards. 

icon

Best answer by Mutahir 31 October 2019, 10:19

Hi@sbarab @Mutahir 

Thanks a lot for your recommendation,

Do you know how can I confirm that which container I have uploaded it to?

As you know, when using Prism Central to upload image, it does not allow us to specify any container so far.

Hi Hienle,

thank you for the update.

  1. Can you share the Prism central version and AOS version you are using?
  1. Were you able to confirm via Prism Central > virtual infrastructure > Images that virtio.iso was there?

you can also try to list the images on this cluster via:

acli image.list | grep <isoname>

This should list the iso with it’s image uuid - you can than use the following command to get more details about that iso / image:

acli image.get <image uuid we got from the first command output>

I would first confirm whether the ISO is visible via prism central > images in order to ensure it was successfully uploaded.

 

Kind regards

View original

6 replies

Hi,

 

on my side I can find it with PC Rest API (Image - Put images/list).

 

My VirtIO is store on my foundation VM.

 

Regards,

Olivier

Userlevel 3
Badge +4

Hey guys,

I have uploaded some of ISO and disk image files including VirtIO to container via Prism Central and they all are marked as ACTIVE means that the upload process has completed successfully.

But when I looked into the container to find the uploaded files via command line or WinSCP, all of them are being kept in container except for VirtIO iso file. Do you know how I can find it?

Thanks and Regards. 

Hi Hienle, 

can you browse to Prism Central > virtual infrastructure > Images and see if you can find virtio.iso? 

the file should be there as long as it has uploaded., or can you try re-uploading virtio.iso and see if it is visible?

 

Userlevel 3
Badge +3

@hienle  you mentioned:

But when I looked into the container to find the uploaded files via command line

 

Could you please let us know what command you run and where did you run it.

As you may know, on PC (Prism Central), you can run:

nuclei image.list

to make sure you have the VirtIO on the PC.

This is basically the “PC command line” version of what @Mutahir mentioned in the above note. If it is not there re-upload it.

 

Userlevel 3
Badge +17

Hi @sbarab  @Mutahir 

Thanks a lot for your recommendation,

Do you know how can I confirm that which container I have uploaded it to?

As you know, when using Prism Central to upload image, it does not allow us to specify any container so far.

Userlevel 3
Badge +4

Hi@sbarab @Mutahir 

Thanks a lot for your recommendation,

Do you know how can I confirm that which container I have uploaded it to?

As you know, when using Prism Central to upload image, it does not allow us to specify any container so far.

Hi Hienle,

thank you for the update.

  1. Can you share the Prism central version and AOS version you are using?
  1. Were you able to confirm via Prism Central > virtual infrastructure > Images that virtio.iso was there?

you can also try to list the images on this cluster via:

acli image.list | grep <isoname>

This should list the iso with it’s image uuid - you can than use the following command to get more details about that iso / image:

acli image.get <image uuid we got from the first command output>

I would first confirm whether the ISO is visible via prism central > images in order to ensure it was successfully uploaded.

 

Kind regards

Userlevel 3
Badge +17

Hi @Mutahir 

I also tried with these commands before but it was so strange that the VirtIO was not listed by the image.list command as expected.

Anyway, this time, it worked like a charm. 

 

Thanks and Regards.

Reply