3:54 p.m.
On Tuesday, January 17, 2017 8:09:58 PM EST Beckman, Daniel wrote:
Strangely enough, I can’t reproduce that issue in 4.0.5.
Anantha, when you say “will not allow us to change anything” what exactly do
you mean?
Does it generate the same “unhandled exception” error as when adding
disks
or something else?
I was able to specify 4 vCPUs consisting of 2 sockets (each with dual
core)
and it worked fine.
If you specify a disk FIRST and then try to to change the virtual CPU
configuration it will no longer work. Basically if you edit/change/add a disk
and a new window pops up, some stuff that shouldn't have been cleaned up, is
cleaned up and breaks anything that relies on that, like the check to see if
the virtual CPU configuration is valid. A bunch of other stuff as well like
the exception mentioned below.
On 1/17/17, 12:56 PM, "Alexander Wels"
<awels(a)redhat.com> wrote:
On Tuesday, January 17, 2017 11:21:17 PM EST Anantha Raghava wrote:
> Hello Daniel,
>
> Thanks for inputs.
>
> Also, one more problem we observed in 4.0.5. When creating VM, we
> cannot
> change the CPU, sockets, cores. It will not allow us to change
> anything.
> We have to save the VM during creation with 1 vCPU. Again, edit VM
> and
> change the vCPU parameters. Have you or anyone observed this
> behaviour?
>
The cause of that is actually same, this is fixed in 4.0.6
> > I don’t know of a function built into oVirt for scheduling
> > snapshots.
> > If you don’t already you may want to setup an export domain (NFS
> > based), on separate storage.
> >
> > Just a reminder: snapshots are not backups and they should only be
> > kept temporarily. We use this tool for backups:
> >
> > https://github.com/wefixit-AT/oVirtBackup
> >
> > It’s not the most efficient as it clones a VM from a snapshot, then
> > exports the clone – so you’re transferring the same data twice. But
> > it
> > works for our purposes. We have this running in a cron job.
> >
> > If anyone has come up with a script that uses the newer API to
> > export
> > a snapshot directly, please share!
> >
> > We get the same error when adding a disk while creating the VM (In
> > Chrome, Firefox, and Safari on OS X Sierra client). This is
> > reportedly
> > fixed in 4.0.6 per this bug:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1394175
> >
> > Could someone with 4.0.6 confirm that?
> >
> > Best,
> >
> > Daniel
> >
> > *From: *<users-bounces(a)ovirt.org> on behalf of Anantha Raghava
> > <raghav(a)exzatechconsulting.com>
> > *Organization: *eXza Technology Consulting & Services
> > *Reply-To: *"raghav(a)exzatechconsulting.com"
> > <raghav(a)exzatechconsulting.com>
> > *Date: *Tuesday, January 17, 2017 at 8:27 AM
> > *To: *"users(a)ovirt.org" <users(a)ovirt.org>
> > *Subject: *[ovirt-users] Scheduled Snapshot and export
> >
> > Hello to oVirt Users,
> >
> > I have few questions.
> >
> >
> > a. Can we schedule the VM snapshots? If yes, please share the
> > procedure
> > b. Snapshots are stored on the same storage domain. Can we move
> > them
> > to another storage domain say NFS domain for additional safety? If,
> > yes, please share the procedure.
> >
> > Also, after upgrading to version 4.0.5, at many places, especially
> > when we are creating a new VM and trying to create a new Disk for
> > the
> > VM, we keep getting "uncought exception" and the process will
not
> > complete. We have to create a VM, without Disk and then create the
> > disk separately and attach it to VM.
> >
> > Is anyone else facing this issue? These sort of issues were not
> > there
> > in 4.0.4.
> >
> >
> > Thanks & Regards,
> >
> > Anantha Raghava
> >
> > eXza Technology Consulting & Services