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
> 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
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.gar...@toshibagcs.com wrote:
I have the same problem, did you
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-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
>
> 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
> On Tue, Mar 30, 2021 at 12:55:36PM -, 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
On Tue, Mar 30, 2021 at 02:19:22PM -, 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
>
>
On Tue, Mar 30, 2021 at 12:55:36PM -, Valerio Luccio wrote:
> > On Mon, Mar 29, 2021 at 09:03:41PM -, 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.
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:
> 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
>
> On Mon, Mar 29, 2021 at 09:03:41PM -, 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
>
On Mon, Mar 29, 2021 at 09:03:41PM -, valerio.luc...@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
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 05:32:50PM -, valerio.luc...@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.
14 matches
Mail list logo
