As I've described before I had issues with my deployment and had to recreate the engine. I never had a chance to export my VMs, but I did back up the files. Now I would like to import the old VMs into the new engine. Is there a way to 'slurp' in the old images ? I see different way to import from an export domain, form VMWare, etc., but I don't see a way to import directly from disk. Do I need to convert them ? To what and how ? Thanks,
On Mon, Mar 29, 2021 at 05:32:50PM -0000, valerio.luccio@nyu.edu wrote:
As I've described before I had issues with my deployment and had to recreate the engine. I never had a chance to export my VMs, but I did back up the files. Now I would like to import the old VMs into the new engine. Is there a way to 'slurp' in the old images ? I see different way to import from an export domain, form VMWare, etc., but I don't see a way to import directly from disk. Do I need to convert them ? To what and how ?
Go to the Storage -> Disks page, from there you can upload your disks to the storage domain. Then you can create a new VM and attach existing disks to it. If that's what you're looking for. Tomas
Thanks, _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SJJPKRP5PVGRHS...
-- Tomáš Golembiovský <tgolembi@redhat.com>
Kind of ... First I had to run remotely a browser on the server, the only way to upload files on the storage attached to it. I then created a new VM and attached the disk, but when it boots up it tells me that it does not find a bootable device. What am I missing ? Thanks,
On Mon, Mar 29, 2021 at 09:03:41PM -0000, valerio.luccio@nyu.edu wrote:
Kind of ...
First I had to run remotely a browser on the server, the only way to upload files on the storage attached to it.
This does not seem right. The whole idea behind disk upload is that you can do that remotely from any machine that has access to the REST API. If this is not working for you (but works when performed from the server) you're probably missing the oVirt CA certificates in your browser.
I then created a new VM and attached the disk, but when it boots up it tells me that it does not find a bootable device. What am I missing ?
The VM is most likely misconfigured. Make sure the attached disk is marked as bootable in web UI. Also verify that the chipset/firmware for your VM or cluster is correct. Tomas
Thanks, _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/Z4EEIW2IPJWUK4...
-- Tomáš Golembiovský <tgolembi@redhat.com>
On Mon, Mar 29, 2021 at 09:03:41PM -0000, valerio.luccio(a)nyu.edu wrote:
This does not seem right. The whole idea behind disk upload is that you can do that remotely from any machine that has access to the REST API. If this is not working for you (but works when performed from the server) you're probably missing the oVirt CA certificates in your browser.
I do "Upload Image" and then hit "Chose File", the file selector opens up on my laptop, which does not have access to the gluster storage.
The VM is most likely misconfigured. Make sure the attached disk is marked as bootable in web UI. Also verify that the chipset/firmware for your VM or cluster is correct.
Tomas
Sorry, where do you mark a disk to be bootable ? I didn't notice any such option when loading the disk. The chipset/firmware should be correct since this this is the same server where the VM was working a week ago and I haven't modified the VM image. Thanks Tomas,
I do "Upload Image" and then hit "Chose File", the file selector opens up on my laptop, which does not have access to the gluster storage.
I did "Test Connection" in the "Upload Image" window and it works.
Sorry, where do you mark a disk to be bootable ? I didn't notice any such option when loading the disk.
When I try to detach the image from the VM instance it states "Note that the disk is bootable".
I might have some more details, but I don't know what it means. When I do 'qemu-img info' on the VM image in backup I get: file format: raw virtual size: 128 GiB (137438953472 bytes) disk size: 128 GiB When I do the same on the VM image that was copied to the new storage I get: file format: raw virtual size: 128 GiB (137438953472 bytes) disk size: 4 KiB Am I reading this wrong, or did something go wrong in the import ?
On Tue, Mar 30, 2021 at 02:19:22PM -0000, Valerio Luccio wrote:
I might have some more details, but I don't know what it means.
When I do 'qemu-img info' on the VM image in backup I get:
file format: raw virtual size: 128 GiB (137438953472 bytes) disk size: 128 GiB
When I do the same on the VM image that was copied to the new storage I get:
file format: raw virtual size: 128 GiB (137438953472 bytes) disk size: 4 KiB
Am I reading this wrong, or did something go wrong in the import ?
Something went wrong and the upload did not happen. It seems that the image is empty. Tomas
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/P35LA2ZRUQ5W25...
-- Tomáš Golembiovský <tgolembi@redhat.com>
On Tue, Mar 30, 2021 at 12:55:36PM -0000, Valerio Luccio wrote:
On Mon, Mar 29, 2021 at 09:03:41PM -0000, valerio.luccio(a)nyu.edu wrote:
This does not seem right. The whole idea behind disk upload is that you can do that remotely from any machine that has access to the REST API. If this is not working for you (but works when performed from the server) you're probably missing the oVirt CA certificates in your browser.
I do "Upload Image" and then hit "Chose File", the file selector opens up on my laptop, which does not have access to the gluster storage.
Ok, I understand now.
The VM is most likely misconfigured. Make sure the attached disk is marked as bootable in web UI. Also verify that the chipset/firmware for your VM or cluster is correct.
Tomas
Sorry, where do you mark a disk to be bootable ? I didn't notice any such option when loading the disk.
In the VM edit dialog if you choose to Attach a disk the list contains column with checkboxes denoted 'OS'. Alternatively if you use Create or Edit action there are checkboxes on the right hand side of the dialog and one of them is named 'Bootable' Tomas
The chipset/firmware should be correct since this this is the same server where the VM was working a week ago and I haven't modified the VM image.
Thanks Tomas, _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GW4NENV6BIAIVR...
-- Tomáš Golembiovský <tgolembi@redhat.com>
On Tue, Mar 30, 2021 at 12:55:36PM -0000, Valerio Luccio wrote:
Ok, I understand now.
In the VM edit dialog if you choose to Attach a disk the list contains column with checkboxes denoted 'OS'. Alternatively if you use Create or Edit action there are checkboxes on the right hand side of the dialog and one of them is named 'Bootable'
Tomas
OK, I had done that. I thought you meant that the image itself had to be 'tagged' somehow.
I might have some more details, but I don't know what it means.
When I do 'qemu-img info' on the VM image in backup I get:
file format: raw virtual size: 128 GiB (137438953472 bytes) disk size: 128 GiB
When I do the same on the VM image that was copied to the new storage I get:
file format: raw virtual size: 128 GiB (137438953472 bytes) disk size: 4 KiB
Am I reading this wrong, or did something go wrong in the import ?
Something went wrong and the upload did not happen. It seems that the image is empty.
That's what I figured, I'll look at the log files to see if I spot anything. Is there a way to do it from command line on the server ? Sometimes it's easier to spot issues from command line. Tomas
That's what I figured, I'll look at the log files to see if I spot anything. Is there a way to do it from command line on the server ? Sometimes it's easier to spot issues from command line.
OK, so I cheated: I copied the image from backup to the current storage overwriting the image and it works. It's a hack, but right now I'll take it.
Command line. I first did the import, then checked the image with 'qemu-img info' and verified that the size was wrong and then copied, making sure to use the same filename generated by the import. On 3/30/21 1:35 PM, miguel.garcia@toshibagcs.com wrote:
I have the same problem, did you ovirwrite by copying through the GUI ? _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_privacy-2Dpolicy.html&d=DwIGaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=DUlROuWuBf1rSF9IoOZ7htX5bybEgPBTfDFXBM5VOGE&s=blJO59mtLMtyMcMCAMbS72Ephz7M8JPI6tSCEFxzw48&e= oVirt Code of Conduct: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_community_about_community-2Dguidelines_&d=DwIGaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=DUlROuWuBf1rSF9IoOZ7htX5bybEgPBTfDFXBM5VOGE&s=e3j_QbsT--VaHh-PfA5kVpMS2m9F5MkkFauIHSTTSTg&e= List Archives: https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ovirt.org_archives_list_users-40ovirt.org_message_BE57WYHMRXMAZG2IKD5NPLVALZV25ZPL_&d=DwIGaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=DUlROuWuBf1rSF9IoOZ7htX5bybEgPBTfDFXBM5VOGE&s=INqLBZBoZweZ1_YWd4DXrpz4aO3324pFJmR-Y_BvGT4&e=
-- As a result of Coronavirus-related precautions, NYU and the Center for Brain Imaging operations will be managed remotely until further notice. All telephone calls and e-mail correspondence are being monitored remotely during our normal business hours of 9am-5pm, Monday through Friday. For MRI scanner-related emergency, please contact: Keith Sanzenbach at keith.sanzenbach@nyu.edu and/or Pablo Velasco at pablo.velasco@nyu.edu For computer/hardware/software emergency, please contact: Valerio Luccio at valerio.luccio@nyu.edu For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at chrysa@nyu.edu For CBI-related administrative emergency, please contact: Jennifer Mangan at jennifer.mangan@nyu.edu Valerio Luccio (212) 998-8736 Center for Brain Imaging 4 Washington Place, Room 158 New York University New York, NY 10003 "In an open world, who needs windows or gates ?"
First I had to run remotely a browser on the server, the only way to upload files on the storage attached to it.
Probably too late, but FIY, there's also an option to do it from command line using ovirt-sdk [1]. You can use upload_disk example [2]. This is also very use useful when you need to upload many images. [1] https://github.com/oVirt/ovirt-engine-sdk/ [2] https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/ upload_disk.py
Thanks, I'll keep it in mind for the future. On 3/31/21 2:52 AM, Vojtech Juranek wrote:
First I had to run remotely a browser on the server, the only way to upload files on the storage attached to it.
Probably too late, but FIY, there's also an option to do it from command line using ovirt-sdk [1]. You can use upload_disk example [2]. This is also very use useful when you need to upload many images.
[1] https://github.com/oVirt/ovirt-engine-sdk/ [2] https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/ upload_disk.py
-- As a result of Coronavirus-related precautions, NYU and the Center for Brain Imaging operations will be managed remotely until further notice. All telephone calls and e-mail correspondence are being monitored remotely during our normal business hours of 9am-5pm, Monday through Friday. For MRI scanner-related emergency, please contact: Keith Sanzenbach at keith.sanzenbach@nyu.edu and/or Pablo Velasco at pablo.velasco@nyu.edu For computer/hardware/software emergency, please contact: Valerio Luccio at valerio.luccio@nyu.edu For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at chrysa@nyu.edu For CBI-related administrative emergency, please contact: Jennifer Mangan at jennifer.mangan@nyu.edu Valerio Luccio (212) 998-8736 Center for Brain Imaging 4 Washington Place, Room 158 New York University New York, NY 10003 "In an open world, who needs windows or gates ?"
participants (6)
-
miguel.garcia＠toshibagcs.com -
Tomáš Golembiovský -
Valerio Luccio -
Valerio Luccio -
valerio.luccio＠nyu.edu
-
Vojtech Juranek