lucas castro writes:
> Who is working on ovirt debian porting,
I'm working on inclusion of Vdsm into Debian. ovirt-guest-agent is
already included in Debian (packaged by another Debian maintainer). I'm
not aware about any plans to package Engine for Debian nor I
Rafael Martins <rmart...@redhat.com> writes:
> Milan Zamazal (CC'd) is working on packaging VDSM for Debian. You may
> want to talk to him about what is missing.
I just sent a complete report (and added devel@). It's probably better
to keep the Debian packaging discussion on (one o
Nir Soffer writes:
> If you must avoid /rhev/data-center, move it to /run/vdsm/data-center,
> but note that future version of vdsm may move it to /run/vdsm/storage,
> or another location, so old debain code will not be compatible with
> new debian code :-)
>
> It would be
We've found out that if libvirtd got restarted then VMs with disabled
memory balloon device are wrongly reported as being in the paused state.
It's a bug and we're working on a fix.
___
Users mailing list
Users@ovirt.org
Bill James writes:
> .recovery setting before removing:
> p298
> sS'status'
> p299
> S'Paused'
> p300
>
> After removing .recovery file and shutdown and restart:
> V0
> sS'status'
> p51
> S'Up'
> p52
Thank you for the information. I was able to reproduce the problem with
Nathanaël Blanchet writes:
> * how to get out of a selectionned vm where we are on the login prompt
> (why not backing up to the vm menu) rather than killing the ssh
> process or closing the terminal? Usual "^] " doesn't work there.
You must use ssh escape sequences with ssh,
Alexis HAUSER writes:
> I would like to change the video memory size (vram_size parameter), how can I
> proceed ?
Look for vramMultiplier in osinfo-defaults.properties file.
The following formula applies: vram_size = vramMultiplier * vgamem
You must restart
Alexis HAUSER writes:
>> Look for vramMultiplier in osinfo-defaults.properties file.
>> The following formula applies: vram_size = vramMultiplier * vgamem
>> You must restart Engine to apply the new setting.
>
> The only thin I found about it in that file is :
Logan Kuhn writes:
> Am I correct in the assumption that importing a previously master data domain
> into a fresh engine without a current master domain is supported?
It's supported only in case the master domain was previously correctly
detached from the data center.
In
Johan Kooijman writes:
> Situation as follows: mixed cluster with 3.5 and 3.6 nodes. Now in the
> process of reinstalling the 3.5 nodes with 3.6 on CentOS 7.2. I can't live
> migrate VM's while they're running on different versions.
Live migration should always work
Alexis HAUSER writes:
> This doesn't looks really good, right ? Should I report that somewhere ?
>
> I actually had this bug when using RHEL7 profile for a Fedora 24 (to provide
> enough vram, because the default with other profiles is really lower).
I don't
Mark Gagnon writes:
> even if it's a storage problem, if it's to happen, how can I force it
> to restart the engine?
Hi Mark, it indeed looks like a storage problem. Unfortunately, there's
very little what can be done when storage is broken. I don't think
there is any
"Federico Sayd" writes:
> I'm trying to upgrade ovirt 3.6.3 to 4.0, but engine-setup complaints about
> upgrading from incompatible version 3.3
>
> I see in the engine-setup log that vds_groups table is checked to determine
> the compatibility version. The logs shows that
If anybody uses Vdsm connectivity log (/var/log/vdsm/connectivity.log),
please tell me. We work on logging cleanup in Vdsm and we are thinking
whether that log is still useful. We consider removing it in case
nobody needs it.
Thanks,
Milan
___
Users
Michal Skrivanek writes:
>> > I'm afraid that we are not yet ready to backport it to 4.0 - we found
>> > out that as it is, it break migration for vmfex and external network
>> > providers; it also breaks when a buggy Engine db does not send a
>> > displayNetwork.
Wolfgang Bucher writes:
> After reboot i cannot start some vms, and i get the following warnings in
> vdsm.log:
>
> periodic/6::WARNING::2016-08-18
> 19:26:10,244::periodic::261::virt.periodic.VmDispatcher::(__call__) could not
> run on
>
Sandro Bonazzola writes:
> On Fri, Oct 21, 2016 at 1:22 AM, Jon Forrest
> wrote:
>>
>> On 10/20/16 4:11 PM, Charles Kozler wrote:
>>
>>> oVirt is the upstream source project for RedHat Enterprise
>>> Virtualization (RHEV). As expected, its only
"Luca 'remix_tj' Lorenzetto" <lorenzetto.l...@gmail.com> writes:
> On Fri, Jun 23, 2017 at 11:16 AM, Milan Zamazal <mzama...@redhat.com> wrote:
>> "Luca 'remix_tj' Lorenzetto" <lorenzetto.l...@gmail.com> writes:
>>
>>> i just
"Luca 'remix_tj' Lorenzetto" writes:
> i just tested the memory hot add to a vm. This vm had 2048 MB. I set
> the new memory to 2662 MB.
> I logged into the vm and i've seen that hasn't been any memory change,
> even if i said to the manager to apply memory expansion
Алексей Максимов writes:
> # wget
> http://ftp.us.debian.org/debian/pool/main/o/ovirt-guest-agent/ovirt-guest-agent_1.0.13.dfsg-2_all.deb
> # apt-get install gir1.2-glib-2.0 libdbus-glib-1-2 libgirepository-1.0-1
> libpango1.0-0 libuser1 python-dbus
Maor Lipchuk writes:
> I encountered a bug (see [1]) which contains the same error mentioned in
> your VDSM logs (see [2]), but I doubt it is related.
Indeed, it's not related.
The error in vdsm_victor.log just means that the info gathering call
tries to access libvirt
our VMs from
Engine of course. Once the management network is back, things should
return to normal state sooner or later.
Regards,
Milan
> Regards
> Terry Hung
>
> 2018-02-28 22:29 GMT+08:00 Milan Zamazal <mzama...@redhat.com>:
>
>> Terry hey <recreati...@gmail.com&
our VMs from
Engine of course. Once the management network is back, things should
return to normal state sooner or later.
Regards,
Milan
> Regards
> Terry Hung
>
> 2018-02-28 22:29 GMT+08:00 Milan Zamazal <mzama...@redhat.com>:
>
>> Terry hey <recreati...@gmail.com&
og. It will be huge, so I suggest to enable it only for the time
of reproducing the problem.
> --
>
> Cordialement,
>
> Frank Soyer
>
>
>
> Le Vendredi, Février 23, 2018 09:56 CET, Milan Zamazal <mzama...@redhat.com>
> a écrit:
> Maor Lipchuk <mlipc..
Terry hey writes:
> I am testing iSCSI bonding failover test on oVirt, but i observed that VM
> were paused and did not migrate to another host. Please see the details as
> follows.
>
> I have two hypervisors. Since they are running iLO 5 and oVirt 4.2 cannot
> support iLO
was also
> experiencing this issue prior to upgrading my environment to 4.2.
If you experienced it also in 4.1 then it must be another problem, which
may or may not be fixed in 4.2 or it can be related to your template or
setup. Let's see what happens once you upgrade to 4.2.2.
> From: &quo
"Bryan Sockel" writes:
> I am having an issue migrating all vm's based on a specific template. The
> template was created in a previous ovirt environment (4.1), and all VM's
> deployed from this template experience the same issue.
>
> I would like to find a
"fsoyer" writes:
> I tried to activate the debug mode, but the restart of libvirt crashed
> something on the host : it was no more possible to start any vm on it, and
> migration to it just never started. So I decided to restart it, and to be
> sure,
> I've restarted all the
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 all VMs
> migrating (although it seems to not actually being migrating them) and the
> migration state cannot be
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
Arild Ringøy writes:
> Then I'll just keep calm and wait.
I'm afraid that won't help. I'll see if I can prepare a non-maintainer
upload of the package with fixes.
Regards,
Milan
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email
Sandro Bonazzola writes:
> Il giorno gio 20 set 2018 alle ore 13:44 Arild Ringøy
> ha scritto:
>
>> Hi Jon!
>>
>> Thanks for your reply!
>> This did help me last time I had problems like this. The problem then was,
>> like yours, that the agent wasn't running. But now it is. At least as far
>>
Josep Manel Andrés Moscardó writes:
> Hi all,
> I have a host with 2 M60 with the latest supported driver installed,
> and working as you can see:
Hi, all looks fine and the same as on my setup, which is working.
How about kernel command line (cat /proc/cmdline)? It's important to
have
Greg Sheremeta writes:
>> Exit message: internal error: qemu unexpectedly closed the monitor:
> 2019-02-08T14:01:11.287955Z qemu-kvm: warning: All CPU(s) up to maxcpus
> should be described in NUMA config, ability to start up with partial NUMA
> mappings is obsoleted and will be removed in
zoda...@gmail.com writes:
> Hi,
>
> I'd like to try the memory hot unplug, refer to:
> https://www.ovirt.org/documentation/vmm-guide/chap-Editing_Virtual_Machines.html:
>
> "All blocks of the hot-plugged memory must be set to
> **online_movable** in the virtual machine’s device management
>
nard...@gmail.com writes:
> Wonder if this issue is related to our problem and if there is a way
> around it. We upgraded from 4.2.8. to 4.3.2. Now when we start some of
> the VM's fail to start. You need to deattach the disks, create new VM,
> reattach the disks to the new VM and then the new VM
ere anything special about your network interfaces or is there
anything suspicious about them in Engine when the VM fails to start?
> On Wed, 10 Apr 2019 at 10:39, Milan Zamazal wrote:
>
>> nard...@gmail.com writes:
>>
>> > Wonder if this issue is related to our problem a
10:37, Milan Zamazal wrote:
>> Shani Leviim writes:
>>
>>> Hi,
>>> It seems that you hit this bug:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1666795
>>>
>>> Adding +Milan Zamazal , Can you please confirm?
>>
>> There may sti
"Vrgotic, Marko" writes:
> What I am aiming for is following:
> We have a nauseate hook which deletes dns records from DNS server, for of a
> VM “destroyed”.
> That is just as we wanted it, except in a case of Migration, which is
> also a “destructive” action, looking from perspective of a
Milan Zamazal writes:
> "Vrgotic, Marko" writes:
>
>> What I am aiming for is following:
>> We have a nauseate hook which deletes dns records from DNS server, for of a
>> VM “destroyed”.
>> That is just as we wanted it, except in a case of Migration,
"Vrgotic, Marko" writes:
> Would you be so kind to help me/tell me or point me how to find which
> Hooks, and in which order, are triggered when VM is being migrated?
See "VDSM and Hooks" appendix of oVirt Admin Guide:
https://ovirt.org/documentation/admin-guide/appe-VDSM_and_Hooks.html
Shani Leviim writes:
> Hi,
> It seems that you hit this bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1666795
>
> Adding +Milan Zamazal , Can you please confirm?
There may still be problems when using GlusterFS with libgfapi:
https://bugzilla.redhat.com/1719789.
What's yo
Strahil writes:
> Why do you use 'all_squash' ?
>
> all_squashMap all uids and gids to the anonymous user. Useful for
> NFS-exported public FTP directories, news spool directories, etc. The
> opposite option is no_all_squash, which is the default setting.
AFAIK all_squash,anonuid=36,anongid=36
Strahil writes:
> Hi ,
>
> You can try with:
> 1. Set the host in maintenance
> 2. From Install dropdown , select 'reinstall' and then configure the
> necessary info + whether you would like to use the host as Host for
> the HostedEngine VM.
Rather than full reinstall, Enroll Certificate action
"JoseMa(G-Mail)" writes:
> Hi folks,
> When trying to start a VM in a nested env with Ryzen it complains with:
>
> 2019-09-28 14:29:53,940-0400 ERROR (vm/0391a661) [virt.vm]
> (vmId='0391a661-20fd-490a-9653-dd217147224d') The vm start process failed
> (vm:933)
> Traceback (most recent call
Ben writes:
> Hi, I'm pretty stuck at the moment so I hope someone can help me.
>
> I have an oVirt 4.3 data center with two hosts. Recently, I attempted to
> segregate migration traffic from the the standard ovirtmgmt network, where
> the VM traffic and all other traffic resides.
>
> I set up
:
> source-ports:
> icmp-blocks:
> rich rules:
>
> On Mon, Jan 20, 2020 at 6:29 AM Milan Zamazal wrote:
>
>> Ben writes:
>>
>> > Hi, I'm pretty stuck at the moment so I hope someone can help me.
>> >
>> > I have an oVirt 4.3 data cen
David David writes:
> solved using this link https://bugzilla.redhat.com/show_bug.cgi?id=1672587
Great, good to know.
> чт, 2 апр. 2020 г. в 16:11, Milan Zamazal :
>
>> David David writes:
>>
>> > can connect to a vm which has spice console protocol by remote-vi
gt;
>>>> >пт, 27 мар. 2020 г. в 21:56, Strahil Nikolov :
>>>> >
>>>> >> On March 27, 2020 12:23:10 PM GMT+02:00, David David
>>>> >
>>>> >> wrote:
>>>> >> >here is debug from opening console.vv by remote-viewer
&
David David writes:
> copied from qemu server all certs except "cacrl" to my desktop-station
> into /etc/pki/
This is not needed, the CA certificate is included in console.vv and no
other certificate should be needed.
> but remote-viewer is still didn't work
The log looks like remote-viewer
> 2020-03-26 21:38 GMT+04:00, Milan Zamazal :
>> David David writes:
>>
>>> copied from qemu server all certs except "cacrl" to my desktop-station
>>> into /etc/pki/
>>
>> This is not needed, the CA certificate is included in console.vv and no
&g
Gianluca Cecchi writes:
> On Wed, Dec 16, 2020 at 8:59 PM Milan Zamazal wrote:
>
>>
>> If the checkbox is unchecked, the migration shouldn't be prevented.
>> I think the TSC frequency shouldn't be written to the VM domain XML in
>> such a case and then t
Gianluca Cecchi writes:
> On Thu, Dec 17, 2020 at 5:30 PM Milan Zamazal wrote:
>
>> Gianluca Cecchi writes:
>>
>> > On Wed, Dec 16, 2020 at 8:59 PM Milan Zamazal
>> wrote:
>> >
>> >>
>> >> If the checkbox is unchecked, the
Gianluca Cecchi writes:
> Hello,
> I'm in 4.4.3 and CentOS 8.3 with 3 hosts.
>
> I have a high performance VM that is running on ov300 and is configured to
> be run on any host.
>
> It seems that both if I set or not the option
>
> Migrate only to hosts with the same TSC frequency
>
> I always
Gianluca Cecchi writes:
> On Fri, Dec 11, 2020 at 5:39 PM Milan Zamazal wrote:
>
>>
>>
>> TSC frequency is the frequency with which Time Stamp Counter register is
>> updated, typically a nominal CPU frequency (see
>> https://en.wikipedia.org/wiki/Time_Stamp_
Sandro Bonazzola writes:
> Il giorno gio 8 lug 2021 alle ore 13:38 Sandro Bonazzola <
> sbona...@redhat.com> ha scritto:
>
>> +Milan Zamazal , +Arik Hadas ,
>> +Michal
>> Skrivanek any hint?
>>
>
> I found https://metacpan.org/pod/Ovirt::Displa
Nir Soffer writes:
> On Fri, Jul 9, 2021 at 5:57 PM nroach44--- via Users wrote:
>>
>> Hi All,
>
>>
>> After upgrading some of my hosts to 4.4.7, and after fixing the
>> policy issue, I'm no longer able to migrate VMs to or from 4.4.7
>> hosts. Starting them works fine regardless of the host
Nathaniel Roach via Users writes:
> On 10/7/21 9:07 pm, Nathaniel Roach wrote:
>> On 10/7/21 3:31 am, Nir Soffer wrote:
>>> On Fri, Jul 9, 2021 at 5:57 PM nroach44--- via Users
>>> wrote:
>
Hi All,
After upgrading some of my hosts to 4.4.7, and after fixing the
policy
ohibited. If you have
> received this message in error, please immediately notify the sender
> and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and
> delete or destroy any copy of this message.
>
>
>
> From: Sandro Bonazzola
> Date: Friday, 9 July 2021 at 15:3
nelson.lamei...@lyra-network.com writes:
> Hello,
>
> We are currently running oVirt 4.3.10
> Our oVirt hypervisors (HV) have 2 cpu sockets * 6 cores * HT = 24 vcpu
> Our VMs (centos7) range globally from 2vcpu to 8vcpu
> oVirt allows to configure - per VM - the following 3 advanced
> parameters
n it from anywhere where Engine REST API
is reachable from.
Regards,
Milan
> Could someone explain it to me?
>
> Best regarda
>
> Am 8. Juli 2021 16:05:42 MESZ schrieb Milan Zamazal :
>>Sandro Bonazzola writes:
>>
>>> Il giorno gio 8 lug 2021 alle ore
e example in Synopis section of
https://metacpan.org/pod/Ovirt::Display
> Am 30.07.2021 14:04 schrieb Milan Zamazal:
>> Merlin Timm writes:
>>
>>> Hey,
>>> Thanks for the answers!
>>> I want to try the perl solution. One, maybe stupid, question: how
>>
"mediocre.slacker--- via Users" writes:
> To add, it was pretty clear the VM never came up just by looking at
> top/htop. qemu-kvm was using negligible (0.7% of a core) CPU. I'm 99%
> certain this is the cause of my woes. Using Q35 with UEFI should be
> fine, as most systems are fine booting
Arik Hadas writes:
> On Wed, Jul 14, 2021 at 10:36 AM Milan Zamazal wrote:
>
>> Marko Vrgotic writes:
>>
>> > Dear Arik and Milan,
>> >
>> > In the meantime, I was asked to check if in current 4.4 version or
>> > coming 4.5, are/will there
francesco--- via Users writes:
> Hi all,
>
> I'm using websockify + noVNC for expose the vm console via browser getting
> the graphicsconsoles ticket via API. Everything works fine for every other
> host that I have (more than 200), the console works either via oVirt engine
> and via
e significant for
>> # VNC passwords. This parameter is only used if the per-domain
>> # XML config does not already provide a password.
>
> Francesco
>
> Il 14/02/2022 12:41, Milan Zamazal ha scritto:
>> francesco--- via Users writes:
>>
>>> Hi all,
&
Nathanaël Blanchet writes:
> Hi,
>
> Some of my hosts came into a non responsive state since there
> certicate had expired:
>
> VDSM palomo command Get Host Capabilities failed: PKIX path validation
> failed: java.security.cert.CertPathValidatorException: validity check
> failed
>
> |openssl
Patrick Hibbs writes:
> Second problem: After having renewed the engine certificate, the engine
> can no longer update a host certificate nor (re-)install a host. Giving
> me the following error in the Admin WebUI: "Error while executing
> action InstallVds: Internal Engine Error"
>
> I've
Don Dupuis writes:
> Hello
> Anyone have any ideas?
>
> Don
>
> On Fri, Jun 10, 2022 at 11:45 AM Don Dupuis wrote:
>
>> THis is for version oVirt 4.5.0.8-1. Sorry left out the exact release.
>>
>> Don
>>
>> On Fri, Jun 10, 2022 at 11:41 AM Don Dupuis wrote:
>>
>>> Hello
>>> I have a RHEL 8.6
Don Dupuis writes:
> Hello
> Anyone have any ideas?
>
> Don
>
> On Fri, Jun 10, 2022 at 11:45 AM Don Dupuis wrote:
>
>> THis is for version oVirt 4.5.0.8-1. Sorry left out the exact release.
>>
>> Don
>>
>> On Fri, Jun 10, 2022 at 11:41 AM Don Dupuis wrote:
>>
>>> Hello
>>> I have a RHEL 8.6
Don Dupuis writes:
> I am looking for an example on how to use the new VmMediatedDevices service
> to add an Nvidia vGPU in ovirt to guest vms. I had it working just fine in
> oVirt 4.4 when using the custom_properties method. Just need to understand
> the new method/way of doing it correctly
"David Sekne" writes:
> Hello,
>
> Not sure about the feature part. I additionally tested this on oVirt
> 4.4.10.7-1.el8 and it works fine even if cluster compatibility there
> is set to 4.6.
Before oVirt 4.5, MaxNumOfCpusCoefficient was applied only if the
maximum number of the VM vCPU sockets
"KSNull Zero" writes:
> Is it safe to restart libvirtd on hosts with workloads without entering
> Maintenance mode ?
Generally no, often yes. Restarting libvirtd shouldn't cause harm to
the VMs themselves but it can disrupt running jobs managed by libvirt or
confuse oVirt if some actions are
Patrick Hibbs writes:
> That error is saying the enrollment script cannot access the serial.txt
> file to generate the new certificate's serial number. That file should
> be located at /etc/pki/ovirt-engine/serial.txt Owned by the ovirt user
> / group. (Oddly enough on my system that file is
"KSNull Zero" writes:
> Running oVirt 4.4.5
> VM cannot migrate between hosts.
>
> vdsm.log contains the following error:
> libvirt.libvirtError: operation failed: Failed to connect to remote
> libvirt URI qemu+tls://ovhost01.local/system: authentication failed:
> Failed to verify peer's
"David Sekne" writes:
> Hello,
>
> I recently upgraded our cluster from 4.3 to 4.5 (4.5.1.3-1.el8), I
> raised the cluster compatibility afterwards to 4.7 as well. I noticed
> that the CPU hot plugging does not work above 16 CPU's if cluster
> compatibility is set to 4.6 or 4.7.
>
> Error I get
David Johnson writes:
> Good afternoon all,
>
> We are trying to update our cluster from 4.5.2 to see if we can
> resolve some issues with the VM Web console not functioning on VM's that
> run on one of the hosts. So there's two problems here, if we can resolve
> the one (dependency resolution)
parallax writes:
> ovirt 4.4.4.7
>
> not able to migrate VMs between hosts with following vdsm error:
>
> operation failed: Failed to connect to remote libvirt URI
> qemu+tls://kvm4.imp.loc/system: authentication failed: Failed to verify
> peer's certificate
You should be able to see a more
Christopher Law writes:
> Anyone explain why I can't export a Virtual Machine with a TPM? Is
> this something to do with the TPM data? I'm exporting the VM to some
> cold storage. What's the deal here how can I export it and keep the
> TPM data or do I have to disable TPM on it first?
>
> oVirt
David Johnson writes:
> My current environment is ovirt 4.5.2.4-1.el8, running on centos 7.9.
>
> I'm looking for advice on resolving two issues that have just come to light:
>
> *Issue #1*: When I attempt to create a template from the oVirt GUI, I click
> the "Make Template" button, enter the
Andrea Chierici writes:
> The strange thing is that now every time I log on the engine I get
> warnings about host certificates about to expire, even if the expiry
> date is in 2023. This looks weird to me and I wonder if there is
> somewhere a setting to specify how in advance the warning
Christopher Law writes:
> I've got a couple of VMs giving me this error message, "the latest
> guest agent needs to be installed and running". These VMs have the
> latest guest agent installed and it is running (virtio-win-1.9.24.iso)
You're probably hitting https://bugzilla.redhat.com/2120381.
82 matches
Mail list logo