Seems I found out the problem.
This user had a permission as InstanceCreator over a VM. If I remove
this permission, he can successfully create new VMs.
This seems a bug, not sure if known or not.
Should I file a BZ?
Thanks.
El 2017-10-18 11:04, nico...@devels.es escribió:
Hi,
We're
Hi,
Not sure if this is the only one way, but this works for us (run as
root):
PGPASSWORD=... /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh
-t all -u engine
Note that unlock_entity.sh has many flags and this is just an example.
You can find the PGPASSWORD value in the
Hi,
I opened this BZ [1] a time ago. Feel free to vote for it if you wish.
Regards,
Nicolás
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1322137
El 2017-12-18 14:48, Florian Schmid escribió:
Hi,
would it be possible for future releases to add an option to the add
new host tab to put
El 2017-11-10 14:41, Gianluca Cecchi escribió:
On Fri, Nov 10, 2017 at 3:34 PM, wrote:
oVirt upgrade to 4.1.7 will probably cleanup this stale task.
However, if you want to do it before upgrading, run this command:
PGPASSWORD=...
oVirt upgrade to 4.1.7 will probably cleanup this stale task. However,
if you want to do it before upgrading, run this command:
PGPASSWORD=... /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh
-t all -u engine
Note that unlock_entity.sh has many flags and this is just an example
Hi Alona,
El 2017-11-19 08:31, Alona Kaplan escribió:
Hi Nicolas,
There was a bug in oVirt [1] that in some cases a mac pool that
doesn't support duplicate macs could get duplicates.
The bug was (hopefully) fixed.
The error that you see means that you have a mac pool that was
affected
Hi,
We just upgraded from 4.1.6 to 4.1.7 and just after the engine was
brought back the following event showed up:
Duplicate MAC addresses had to be introduced into mac pool violating
no duplicates setting.
Can someone explain why is that?
Thanks.
Nicolás
Hi,
We're getting closer to solve it :-)
I'll answer below with my steps, there's one that fails and I don't know
why (probably I missed something).
El 2018-05-17 15:47, Benny Zlotnik escribió:
Sorry, I forgot it's ISCSI, it's a bit different
In my case it would look something like:
Hi,
We're running oVirt 4.1.9 (I know it's not the recommended version, but
we can't upgrade yet) and recently we had an issue with a Storage Domain
while a VM was moving a disk. The Storage Domain went down for a few
minutes, then it got back.
However, the disk's state has stuck in a
Hi,
Thanks. I've checked vdsm logs on all my hosts but the only entry I can
find grepping by Volume.getInfo is like this:
2018-05-17 10:14:54,892+0100 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer]
RPC call Volume.getInfo succeeded in 0.30 seconds (__init__:539)
I cannot find a line like
Please disregard the last e-mail. I re-run the command and now the exit
code was 0, and the migration process is not stuck anymore.
Thanks so much for all the help, Benny!
Regards.
El 2018-05-18 08:42, nico...@devels.es escribió:
Hi,
We're getting closer to solve it :-)
I'll answer below
Thanks.
I've been able to see the line in the log, however, the format differs
slightly from yours.
2018-05-17 12:24:44,132+0100 DEBUG (jsonrpc/6) [jsonrpc.JsonRpcServer]
Calling 'Volume.getInfo' in bridge with {u'storagepoolID':
u'75bf8f48-970f-42bc-8596-f8ab6efb2b63', u'imageID':
The issue is present in the logs:
2018-05-17 11:50:44,822+01 INFO
[org.ovirt.engine.core.bll.storage.disk.image.VdsmImagePoller]
(DefaultQuartzScheduler1) [39755bb7-9082-40d6-ae5e-64b5b2b5f98e] Command
CopyData id: '84a49b25-0e37-4338-834e-08bd67c42860': the volume lease is
not FREE - the
This is vdsm 4.19.45. I grepped the disk uuid in /var/log/sanlock.log
but unfortunately no entry there...
El 2018-05-17 13:11, Benny Zlotnik escribió:
Which vdsm version are you using?
You can try looking for the image uuid in /var/log/sanlock.log
On Thu, May 17, 2018 at 2:40 PM,
Hi Benny,
Please find the logs at [1].
Thank you.
[1]:
https://wetransfer.com/downloads/12208fb4a6a5df3114bbbc10af194c8820180618101223/647c066b7b91096570def304da86dbca20180618101223/583d3d
El 2018-06-18 09:28, Benny Zlotnik escribió:
Can you provide full engine and vdsm logs?
On Mon,
Hi Marcelo,
Do you mean copying the whole disk block to a different device and
attaching it to a new VM?
Anything will be appreciated, as currently we're facing a distressing
situation, so if you can describe what you mean I'd be grateful.
Thanks.
El 2018-06-18 16:19, Marcelo Leandro
Indeed, when the problem started I think the SPM was the host I added as
VDSM log in the first e-mail. Currently it is the one I sent in the
second mail.
FWIW, if it helps to debug more fluently, we can provide VPN access to
our infrastructure so you can access and see whateve you need (all
Hi Benny,
Please find the SPM logs at [1].
Thank you
[1]:
https://wetransfer.com/downloads/62bf649462aabbc2ef21824682b0a08320180618131825/036b7782f58d337baf909a7220d8455320180618131825/5550ee
El 2018-06-18 13:19, Benny Zlotnik escribió:
Can you send the SPM logs as well?
On Mon, Jun 18,
Hi,
We're running oVirt 4.1.9 (we cannot upgrade at this time) and we're
having a major problem in our infrastructure. On friday, a snapshots
were automatically created on more than 200 VMs and as this was just a
test task, all of them were deleted at the same time, which seems to
have
There's no such field in the output. There's a similar one called
commandId (maybe because this is 4.1.9?).
An output has this format:
{
+
"@class" :
Hi Ala,
All vmSnapshotId fields are null.
Could it be that this could be solved by running what there's on comment
19 in [1]?
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=145#c19
El 2018-06-25 10:20, Ala Hino escribió:
I understand.
Back to command entities.
For each active
Yes, it returned 0 rows:
engine=# select command_parameters from command_entities where
command_params_class =
'org.ovirt.engine.core.common.action.RemoveSnapshotParameters' and
status = 'ACTIVE';
command_parameters
(0 rows)
El 2018-06-25 11:55, Ala Hino escribió:
I tried cloning the VM and deleting the original so maybe it would also
delete the related tasks... but it didn't, instead of:
Failed to delete snapshot '' for VM 'vmname'.
It now shows:
Failed to delete snapshot '' for VM ''.
Any tip on how to solve this, please?
Thanks
El
engine=# SELECT status FROM command_entities;
status
FAILED
ENDED_SUCCESSFULLY
FAILED
FAILED
UNKNOWN
UNKNOWN
ENDED_WITH_FAILURE
ENDED_WITH_FAILURE
ENDED_WITH_FAILURE
ENDED_WITH_FAILURE
ACTIVE
ACTIVE
SUCCEEDED
SUCCEEDED
ACTIVE
ACTIVE
ACTIVE
SUCCEEDED
So if I have this entry, for example, what should I do next?
cc7764c5-dbc3-4886-bdd6-dabcc756cf6a | 235 |
cc7764c5-dbc3-4886-bdd6-dabcc756cf6a | {
+| org.ovir
Hi,
We're running oVirt 4.1.9, recently we had an issue with snapshots so we
had to fix them manually. The issue is mostly solved but now we're
seeing a lot of events like this one:
2018-06-25 07:58:06,637+01 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
Currently there are no merge related commands running, if you mean that
we're aware of some merge should be happening (it shouldn't). I
restarted the engine but the event is still showing up every 10 seconds.
El 2018-06-25 09:39, Ala Hino escribió:
Do you have any running merge related
Hi Ala,
Yes, there's no way to remove it. I actually found a way to workaround
the issue, I'm posting it so other people can have a clue how to solve
it...
I'm fully aware that touching the DB directly is not a good idea but
I've been unable to find an alternative way.
1) Find the broken
El 2018-02-05 14:03, Simone Tiraboschi escribió:
On Mon, Feb 5, 2018 at 2:46 PM, wrote:
Hi,
We're trying to upgrade from 4.1.9 to 4.2.x and we're bumping into
an error we don't know how to solve. As per [1] we run the
'engine-setup' command and it fails with:
[ INFO ]
Hi,
We're trying to upgrade from 4.1.9 to 4.2.x and we're bumping into an
error we don't know how to solve. As per [1] we run the 'engine-setup'
command and it fails with:
[ INFO ] Rolling back to the previous PostgreSQL instance (postgresql).
[ ERROR ] Failed to execute stage 'Misc
Hi,
We recently upgraded to oVirt 4.2.0 and we're testing things so we can
determine if our production system might also be upgraded or not. We do
an extensive use of the User Portal, I've granted the VmCreator and
DiskProfileUser privileges on a user (the user has a quota as well), I
logged
I can't even see other options, like adding NICs, or changing the
machine type (server, desktop)... Was this removed on purpose or there's
some permission(s) to grant?
El 2018-02-06 11:45, nico...@devels.es escribió:
Hi,
We recently upgraded to oVirt 4.2.0 and we're testing things so we can
El 2018-02-05 14:48, Martin Perina escribió:
On Mon, Feb 5, 2018 at 3:08 PM, wrote:
El 2018-02-05 14:03, Simone Tiraboschi escribió:
On Mon, Feb 5, 2018 at 2:46 PM, wrote:
Hi,
We're trying to upgrade from 4.1.9 to 4.2.x and we're bumping into
an error
Sorry, but I don't understand what's the new VM portal purpose then... I
mean, you can create a VM but you can't modify the console type, nor add
disks, nor add NIC interfaces?
If that's how the new VM portal works, we can't upgrade our oVirt
infrastructure because as I said, we extensively
El 2018-02-07 10:54, Michal Skrivanek escribió:
On 6 Feb 2018, at 13:13, nico...@devels.es wrote:
I can't even see other options, like adding NICs, or changing the
machine type (server, desktop)... Was this removed on purpose or
there's some permission(s) to grant?
it just hasn’t been
February 2018 at 12:28, John Taylor <jtt77...@gmail.com> wrote:
On Thu, Feb 15, 2018 at 11:54 AM, Michal Skrivanek
<michal.skriva...@redhat.com> wrote:
On 15 Feb 2018, at 15:58, John Taylor <jtt77...@gmail.com>
wrote:
Hi Nicolas,
I had the same problem and it looked like it w
Hi,
We upgraded one of our infrastructures to 4.2.0 recently and since then
some of our machines have the "Console" button greyed-out in the Admin
UI, like they were disabled.
I changed their compatibility to 4.2 but with no luck, as they're still
disabled.
Is there a way to know why is
Hi,
We're running 4.1.9 and during the weekend we had a storage issue that
seemed to leave some hosts in an strange state. One of the hosts has
almost all VMs migrating (although it seems to not actually being
migrating them) and the migration state cannot be cancelled.
When clicking on one
Hi Benny,
I used the tool to track one of the illegal volumes:
image:e05874d2-fb8a-4fd2-94ff-2f4bc6438d47
[...]
- 887f486b-15cf-4083-9b35-8b7821a7841a
status: ILLEGAL, voltype: LEAF, format: COW, legality:
ILLEGAL, type: SPARSE
So I tracked
Hi Benny,
El 2018-07-12 08:50, Benny Zlotnik escribió:
Perhaps you can query the status of job using the correlation id
(taking the examples from ovirt-system-tests):
dead_snap1_params = types.Snapshot(
description=SNAPSHOT_DESC_1,
persist_memorystate=False,
Hi Alex,
We had a bigger problem recently which involved the error you mention. I
sent it to the mail list and you can find the final solution we chose at
[1]. Not the cleanest solution of course, but we managed to recover all
VMs... I think in your case the relevant part is the one that
Hi,
We're using ovirt-engine-sdk-python 4.1.6 on oVirt 4.1.9, currently
we're trying to delete some snapshots via a script like this:
sys_serv = conn.system_service()
vms_service = sys_serv.vms_service()
vm_service = vms_service.vm_service(vmid)
snaps_service =
Hi Ondra,
El 2018-07-12 08:02, Ondra Machacek escribió:
On 07/11/2018 10:10 AM, nico...@devels.es wrote:
Hi,
We're using ovirt-engine-sdk-python 4.1.6 on oVirt 4.1.9, currently
we're trying to delete some snapshots via a script like this:
sys_serv = conn.system_service()
Hi,
I'm running ovirt-engine-sdk-python 4.2.4 and I'm performing some
snapshot-related tasks. I'd like to somehow control the status of the
snapshot in order to know when I'll be able to run the next
snapshot-related operation.
For example, I'd like to create a new snapshot and then delete
El 2018-04-19 08:53, Francesco Romani escribió:
On 04/19/2018 09:44 AM, nico...@devels.es wrote:
Hi,
We're running oVirt 4.1.9 and recently we've experienced a corruption
of a lot of VMs... I tried to investigate the reasons but I simply
can't find an explaination of why this happens.
I'd
Also noticed this.
As per the CHANGELOG of the package, the maintainer is a member of
RedHat at least until Aug 2014. Not sure if he's subscribed to this
list, though. Maybe sending him an e-mail directly? You can find it in
the /usr/share/doc/ovirt-guest-agent/changelog.Debian.gz file.
Hi,
We're running oVirt 4.1.9, today I put a host on maintenance, I saw one
of the VMs was taking too long to migrate so I shut it down. It seems
that just in that moment the machine ended migrating, but the shutdown
did happen as well.
Now, when I try to start the VM I'm getting the
Guys, any hints to this?
El 2018-03-21 12:37, nico...@devels.es escribió:
Hi,
We're running oVirt 4.1.9, today I put a host on maintenance, I saw
one of the VMs was taking too long to migrate so I shut it down. It
seems that just in that moment the machine ended migrating, but the
shutdown did
El 2018-03-23 15:38, Yaniv Kaul escribió:
On Fri, Mar 23, 2018 at 3:20 PM, wrote:
El 2018-03-23 12:16, Sandro Bonazzola escribió:
2018-03-21 13:37 GMT+01:00 :
Hi,
We're running oVirt 4.1.9, today I put a host on maintenance, I saw
one of the VMs was
El 2018-03-23 12:16, Sandro Bonazzola escribió:
2018-03-21 13:37 GMT+01:00 :
Hi,
We're running oVirt 4.1.9, today I put a host on maintenance, I saw
one of the VMs was taking too long to migrate so I shut it down. It
seems that just in that moment the machine ended
El 2018-03-02 15:34, Milan Zamazal escribió:
nico...@devels.es writes:
El 2018-03-02 14:10, Milan Zamazal escribió:
nico...@devels.es writes:
We're running 4.1.9 and during the weekend we had a storage issue
that
seemed
to leave some hosts in an strange state. One of the hosts has almost
Hi,
In oVirt 4.1 we used this command to set a volume as LEGAL:
vdsClient -s setVolumeLegality sdUUID spUUID imgUUID leafUUID
LEGAL
What would be the equivalent to this command using vdsm-client in oVirt
4.3?
Thanks.
___
Users mailing list
Thanks Liran, it worked perfectly.
Regards.
El 2019-04-03 11:33, Liran Rotenberg escribió:
I think the similar way to do it as you used to is:
$ vdsm-client Volume setLegality storagedomainID=sdUUID
storagepoolID=spUUID imageID=imgUUID legality=LEGAL volumeID=volUUID
Where the values you set
Hi Benny,
Thanks for the help.
Could you please tell me what job_uuid and vol_gen should be replaced
by? Should I just put any UUID for the job?
Thanks.
El 2019-04-03 09:52, Benny Zlotnik escribió:
it should be something like this:
$ cat update.json
{
"job_id":"",
Hi,
We're running oVirt 4.3.2. When we click on the "Migrate" button over a
VM, an error popup shows up and in the ovirt-engine log we see:
2019-04-03 12:37:40,897+01 ERROR
[org.ovirt.engine.core.bll.GetValidHostsForVmsQuery] (default task-6)
[478381f0-18e3-4c96-bcb5-aafd116d7b7a] Query
Hi Andrej,
I missed to point a fact that is probably determining. Prior to noticing
the error, we upgraded the Cluster & Data Center compatibility version
from 4.1 to 4.3, which caused ovirt-engine to automatically edit all VMs
and modify their compatibility versions as well (with changes
ate %s" % self.state)
TaskStateError: Operation is not allowed in this task state: ("can't
clean in state running",)
I migrated all VMs to a different host, forcibly rebooted the SPM host
and now the event stopped showing.
Thanks.
Regards.
El 2019-01-25 16:19, Nicholas Vaugha
Hi,
We're running oVirt 4.1.9 (I know there's a new version, we can't
upgrade until [1] is implemented). The thing is that since some days
we're having an event that floods our event list:
Clearing asynchronous task Unknown that started at Tue Jan 22 14:33:17
WET 2019
The event shows up
Are the VMs from the pool 'up'? If so, no assignation can be done unless
they are powered off.
El 2019-04-12 14:31, Florian Rädler escribió:
I am getting the following Error after a Pool was generated and
migrated to another host.
START_POOL fehlgeschlagen [Cannot allocate and run VM from
El 2019-05-24 15:22, Simone Tiraboschi escribió:
On Fri, May 24, 2019 at 3:48 PM wrote:
El 2019-05-24 14:42, Simone Tiraboschi escribió:
On Fri, May 24, 2019 at 3:39 PM wrote:
El 2019-05-24 14:30, Simone Tiraboschi escribió:
On Fri, May 24, 2019 at 2:56 PM wrote:
El 2019-05-24 13:39,
Hi Shirly,
Thanks for the answer.
El 2019-06-06 16:22, Shirly Radco escribió:
Hi Nicolas,
Please open a bug in bugzilla and attach the ovirt-engine-dwh.log,
engine.log,
https://bugzilla.redhat.com/show_bug.cgi?id=1718165
Feel free to change anything that is not correctly set
Hi,
We're running oVirt 4.1.9 (cannot upgrade yet until [1] is released).
Since a few days ago our event list if full of lines like this:
ETL service sampling has encountered an error. Please consult the
service log for more details.
Having a look at the log I see events like:
Please, any ideas about this?
Thanks.
El 2019-05-10 09:18, nico...@devels.es escribió:
Hi,
We're running oVirt version 4.3.3, and trying to configure one of the
hosts to support Nested Virtualization, but when installing the nested
host it claims it doesn't support hardware virtualization.
El 2019-05-14 08:19, Yedidyah Bar David escribió:
On Tue, May 14, 2019 at 10:02 AM wrote:
Please, any ideas about this?
Thanks.
El 2019-05-10 09:18, nico...@devels.es escribió:
> Hi,
>
> We're running oVirt version 4.3.3, and trying to configure one of the
> hosts to support Nested
El 2019-05-24 13:39, Simone Tiraboschi escribió:
On Fri, May 24, 2019 at 2:32 PM wrote:
El 2019-05-24 13:22, Simone Tiraboschi escribió:
On Fri, May 24, 2019 at 1:51 PM wrote:
El 2019-05-24 12:41, nico...@devels.es escribió:
El 2019-05-14 08:19, Yedidyah Bar David escribió:
On Tue, May
El 2019-05-24 12:41, nico...@devels.es escribió:
El 2019-05-14 08:19, Yedidyah Bar David escribió:
On Tue, May 14, 2019 at 10:02 AM wrote:
Please, any ideas about this?
Thanks.
El 2019-05-10 09:18, nico...@devels.es escribió:
> Hi,
>
> We're running oVirt version 4.3.3, and trying to
El 2019-05-24 13:22, Simone Tiraboschi escribió:
On Fri, May 24, 2019 at 1:51 PM wrote:
El 2019-05-24 12:41, nico...@devels.es escribió:
El 2019-05-14 08:19, Yedidyah Bar David escribió:
On Tue, May 14, 2019 at 10:02 AM wrote:
Please, any ideas about this?
Thanks.
El 2019-05-10 09:18,
El 2019-05-24 14:30, Simone Tiraboschi escribió:
On Fri, May 24, 2019 at 2:56 PM wrote:
El 2019-05-24 13:39, Simone Tiraboschi escribió:
On Fri, May 24, 2019 at 2:32 PM wrote:
El 2019-05-24 13:22, Simone Tiraboschi escribió:
On Fri, May 24, 2019 at 1:51 PM wrote:
El 2019-05-24 12:41,
El 2019-05-24 14:42, Simone Tiraboschi escribió:
On Fri, May 24, 2019 at 3:39 PM wrote:
El 2019-05-24 14:30, Simone Tiraboschi escribió:
On Fri, May 24, 2019 at 2:56 PM wrote:
El 2019-05-24 13:39, Simone Tiraboschi escribió:
On Fri, May 24, 2019 at 2:32 PM wrote:
El 2019-05-24 13:22,
Hi,
We're running oVirt version 4.3.3, and trying to configure one of the
hosts to support Nested Virtualization, but when installing the nested
host it claims it doesn't support hardware virtualization.
On the physical host, we've enabled nested virtualization:
# cat
Guys, this is starting to be annoying. Can anything be done to
unsubscribe users with these security issues?
El 2019-05-03 07:50, deannawillia...@gmail.com escribió:
We are famous in the leather industry with our best quality of leather
and its stuff we are providing service from all over the
Hi Jason,
El 2019-08-06 22:43, Jason M. Stallings escribió:
Nicolas:
Thank you very much for this! Looks like exactly what I was looking
for... The first burst was somewhat frightening but it ended well and
now no storage domain is overused :)
Glad to hear that!
One quick question
Hi Jason,
A time ago I wrote a "Storage Balancer" exactly for that, move disks
between storage domains to keep them below a maximum threshold of
occupation. You can find the project at [1].
It's not perfect but has been working for us for the last 3 years with
no issues.
That won't avoid
Hi,
We're running oVirt 4.3.2. Currently, we have one storage backend
(cabinet) with two controllers, each of them with 2 network interfaces
(4 network interfaces in total). When we added the Storage Domain, we
discovered the target for each of the 4 IPs and marked the LUN so it
would be
Hi,
We're testing version 4.3.8, we're planning to upgrade to this version
in production as currently we're still using 4.1.9.
In 4.1.9, users could grant permissions on their created VMs to other
users from within the VM portal, however I can't find this option on
version 4.3.8.
El 2020-02-05 13:57, Gianluca Cecchi escribió:
On Wed, Feb 5, 2020 at 2:50 PM wrote:
A little bit more info on it. I debugged the requests with Chrome
and
seems that the webservice call is made with https://engine:6100 [1]
(literally), instead of https://:6100.
A snapshot is included in
Hi,
We recently upgraded to 4.3.8 and everything is working fine but the VNC
Console (Browser).
Once I click on "VNC Console (Browser)" on any machine from the VM
Portal, I get a message like this:
Disconnected from Console
Cannot connect to websocket proxy server. Please check your
Hi,
We recently upgraded to 4.3.8 from 4.1.9. In the update process we set
Cluster and DataCenter compatibility versions to 4.3, but now we're
facing a problem with VmPools. They cannot be edited and 4.1 as
compatibility level is still forcibly set.
That means that when new machines are
Hi,
We're running oVirt 4.3.8 and we recently had a oVirt crash after moving
too much disks between storage domains.
Concretely, one of the Storage Domains reports status "Unknown",
"Total/Free/Guaranteed free spaces" are "[N/A]".
After trying to activate it in the Domain Center we see
Nicolas,
You can try to recover VG metadata from a backup or archive which lvm
automatically creates by default.
1) To list all available backups for given VG:
#vgcfgrestore --list Usi3y8-S4eq-EXtl-FA58-MA3K-b4vE-4d9SCp
Select the latest one which sounds right, something with a description
along
Hi Roman and Nir,
El 2021-09-16 13:42, Roman Bednar escribió:
Hi Nicolas,
You can try to recover VG metadata from a backup or archive which lvm
automatically creates by default.
1) To list all available backups for given VG:
#vgcfgrestore --list Usi3y8-S4eq-EXtl-FA58-MA3K-b4vE-4d9SCp
Select
I can also see...
kvmr03:~# lvs | grep 927f423a-6689-4ddb-8fda-b3375c3bbca3
/dev/mapper/36001405063455cf7cd74c20bc06e9304: Checksum error at
offset 2198927383040
Couldn't read volume group metadata from
/dev/mapper/36001405063455cf7cd74c20bc06e9304.
Metadata location on
The most relevant log snippet I have found is the following. I assume it
cannot scan the Storage Domain, but I'm unsure why, as the storage
domain backend is up and running.
021-09-16 11:16:58,884+0100 WARN (monitor/219fa16) [storage.LVM]
Command ['/usr/sbin/lvm', 'vgs', '--config', 'devices
2021-09-20 09:21, nico...@devels.es escribió:
Hi Roman and Nir,
El 2021-09-16 13:42, Roman Bednar escribió:
Hi Nicolas,
You can try to recover VG metadata from a backup or archive which lvm
automatically creates by default.
1) To list all available backups for given VG:
#vgcfgrestore --l
Hi,
We upgraded from oVirt 4.3.8 to 4.4.8 and sometimes we're finding events
like these in the event log (3-4 times/day):
Failed to update OVF disks 77818843-f72e-4d40-9354-4e1231da341f, OVF
data isn't updated on those OVF stores (Data Center KVMRojo, Storage
Domain pv04-003).
Hi,
I'm making a bare metal oVirt installation, version 4.4.8.
'ovirt-engine' command ends well, however, we're using a third-party
certificate (from LetsEncrypt) both for the apache server and the
ovirt-websocket-proxy. So we changed configuration files regarding httpd
and
Thanks, this put me in the correct track.
In my case, I just needed to run step 2, as the rest of the
configuration is being handled in a different way and works well. I also
tried to restart the host and it still works.
Thanks for the help!
El 2021-10-01 00:13, Edward Berger escribió:
I
ió:
Hi Roman and Nir,
El 2021-09-16 13:42, Roman Bednar escribió:
Hi Nicolas,
You can try to recover VG metadata from a backup or archive which
lvm
automatically creates by default.
1) To list all available backups for given VG:
#vgcfgrestore --list Usi3y8-S4eq-EXtl-FA58-MA3K-b4vE-4d9SCp
S
Hi,
We're using oVirt 4.4.8.6. We make an intensive use of the VM portal
because we've hundreds of students creating their own VMs. Recently, one
of the professors reported that they are encountering an error when
adding a disk to a newly created VM.
They are creating ISO based VMs
Hi,
We're running oVirt 4.4.8.6. We have uploaded a qcow2 image (metasploit
v.3, FWIW) using the GUI (Storage -> Disks -> Upload -> Start). The
image is in qcow2 format. No options on the right side were checked. The
upload went smoothly, so we now tried to attach the disk to a VM.
To do
Hi _isi_,
I already tried with all chipset/firmwares available. Still I get the
same result, it cannot boot with that disk. Not sure what the problem
actually is, as I said, I'm pretty sure the disk is bootable under
VirtualBox.
Thanks.
El 2022-03-23 14:50, uli.i...@elkb.de escribió:
Hi,
Hi Abe,
Yes, it was set as bootable. I tried your approach, however I get the
same results; converted the disk with qemu-img from vmdk to qcow2, tried
any disk driver (SATA, VirtIO, VirtIO-SCSI) and also tried all
chipset/firmwares available. Still I get the same result, it cannot boot
with
Hi,
We have a Python-SDK script to find MAC dupes in our infrastructure.
I'm attaching the script, you just need to set the URI, USERNAME,
PASSWORD, CERTPATH and MACPOOLS variables.
Hope this helps.
Regards,
Nicolás
El 2022-03-25 14:35, Gianluca Cecchi escribió:
Sorry, incomplete message
Hi,
The checkbox is already checked, when you mark a disk as "OS" it's
marked automatically. Still it won't boot.
Thanks.
El 2022-03-23 15:23, Angus Clarke escribió:
Hi Nicolas
In oVirt 4.3:
Compute -> Virtual Machines -> Select VM
On the VM screen:
Disks -> Hig
Hi Nir,
El 2022-03-27 10:23, Nir Soffer escribió:
On Wed, Mar 23, 2022 at 3:09 PM wrote:
We're running oVirt 4.4.8.6. We have uploaded a qcow2 image
(metasploit
v.3, FWIW)
Is it Metasploitable3-0.1.4.ova from the github releases page?
https://github.com/brimstone/metasploitable3/releases
El 2022-03-28 13:12, Nir Soffer escribió:
On Mon, Mar 28, 2022 at 11:01 AM wrote:
Hi Nir,
El 2022-03-27 10:23, Nir Soffer escribió:
> On Wed, Mar 23, 2022 at 3:09 PM wrote:
>> We're running oVirt 4.4.8.6. We have uploaded a qcow2 image
>> (metasploit
>> v.3, FWIW)
>
> Is it
Hi,
We're running oVirt 4.5.4, recently we had a problem due to /var
partition being full, and we realized the
/var/log/ovirt-engine/engine.log was pretty huge, approximately 16GB in
size, despite it's configured to rotate daily.
Checking the log, we have a lot (about 53000 at the time of
Hi,
We're running oVirt 4.5. We have a template which we'd like to get rid
of, there are no VMs based on it. However, trying to remove it oVirt
states that:
Cannot remove Template. The following Disk(s) are based on it:
(b54ee1cb-ed64-4db4-bd3d-eac8b22ea095) .
When opening the 'Disks'
Hi Arik,
El 2023-10-01 07:41, Arik Hadas escribió:
On Fri, Sep 29, 2023 at 1:36 PM wrote:
Hi,
We're running oVirt 4.5. We have a template which we'd like to get
rid
of, there are no VMs based on it. However, trying to remove it oVirt
states that:
Cannot remove Template. The following
El 2023-10-03 16:35, Arik Hadas escribió:
On Mon, Oct 2, 2023 at 11:26 AM wrote:
Hi Arik,
El 2023-10-01 07:41, Arik Hadas escribió:
On Fri, Sep 29, 2023 at 1:36 PM wrote:
Hi,
We're running oVirt 4.5. We have a template which we'd like to
get
rid
of, there are no VMs based on it.
101 - 200 of 544 matches
Mail list logo