Re: [ovirt-users] Two Problems On New Install

Hi, yeah both snippets are actually telling you that there was something really unexpected. The first one comes from a call by MOM who is trying to get some IO limiting information about the VM. VDSM responded with "I know about the VM, but I can't find it in libvirt". The second part is

[ovirt-users] Recognize HE iSCSI volume size change

I'm testing upgrading an oVirt 3.5 setup, and I have run into a problem when going from 3.5 to 3.6 on a physical machine configured for the hosted engine. I upgraded the engine itself okay, but when I upgraded the first physical machine, it cannot be re-activated; it gets an error connecting to

Re: [ovirt-users] Recognize HE iSCSI volume size change

Chris, Sorry to chime in late, but this might help you (or someone with a similar upgrade situation) in the future. The "rescan-scsi-bus.sh" script from the sg3-utils package can handle the update for the size increase without the reboot. Just need to run with the "-s" param to look for

Re: [ovirt-users] Recognize HE iSCSI volume size change

I did see that page, but... I can't get there from here. I can't get upgraded from 3.5 until I get past this problem, and on 3.5, the hosted engine storage domain isn't included in the normal UI at all. I think I did get this working though; both servers had kernel messages that they saw the LUN

Re: [ovirt-users] log out event but not log in?

On Thu, Feb 23, 2017 at 8:51 AM, Yura Poltoratskiy wrote: > I have the same issue since oVirt 4.0.x. > > 21.02.2017 10:28, Gianluca Cecchi пишет: > >> Hello, >> In oVirt 4.1 web admin gui I see events about users logging out (they >> have been created on internal domain

Re: [ovirt-users] Disable guest agent not installed warning

On Thu, Feb 23, 2017 at 7:48 PM, Karli Sjöberg wrote: > > Den 23 feb. 2017 6:10 em skrev Nir Soffer : > > > > On Thu, Feb 23, 2017 at 6:47 PM, Karli Sjöberg > wrote: > > > > > > Den 23 feb. 2017 4:09 em skrev Nir Soffer

Re: [ovirt-users] Recognize HE iSCSI volume size change

Once upon a time, Nir Soffer said: > I think the complete flow on 3.5 can work like this: > > 1. stop ovirt-engine, so it will not try to restart vdsm on any host > 2. stop vdsm on all hosts > 3. rescan scsi bus, resizing luns on all hosts > 4. pvresize the pv from one on the

[ovirt-users] 3.5->3.6 did not import hosted engine storage domain

So, on to my next upgrade issue (sorry for all the questions and thanks for everybody's help)... I upgraded my test cluster from 3.5 to 3.6 (latest version of each, all on CentOS 7 except the engine on CentOS 6). Now I'm working on the next step, upgrading to 4.0 and migrating the HE to the

[ovirt-users] Can't virtualize CentOS 7.x on oVirt 3.6

Hello Friends of oVirt Suddenly I have a super creepy bug: I can't boot a CentOS-7-x86_64-Minimal-1611.iso I check the sha256sum and everything is OK The Virtual Machine Stuck in: "EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)" or "systemd-journal[88]: Received

Re: [ovirt-users] Recognize HE iSCSI volume size change

On Fri, Feb 24, 2017 at 7:36 PM, Jeff Burns wrote: > Chris, > > Sorry to chime in late, but this might help you (or someone with a similar > upgrade situation) in the future. The "rescan-scsi-bus.sh" script from the > sg3-utils package can handle the update for the size

Re: [ovirt-users] Recognize HE iSCSI volume size change

On Fri, Feb 24, 2017 at 8:33 PM, Chris Adams wrote: > Once upon a time, Nir Soffer said: >> This is not enough, you need to resize the multiapth mapping on all hosts, >> resize the pv using the LUN (must be done by the SPM), and invalidate >> vdsm lvm cache

[ovirt-users] upgrading from 3.6 -> 4.1, vm restarts at 4.0 mandatory?

I’m upgrading my main cluster from 3.6 to 4.1, and I’m currently at 4.0. I’ve upgraded the cluster and datacenter compatibility versions to 4.0, and now all my VMs are pending restart to update their configs to 4.0. My question is “Do I need to do this here, or can I go ahead and update the

Re: [ovirt-users] Recognize HE iSCSI volume size change

Hi Chris. We added this feature to newer versions of oVirt (see the feature page[1]). The easiest way to work around this problem might be to add an additional LUN to this domain if you are able to do it. If not, it looks like you would need to manually reconnect the host to the domain, to a

Re: [ovirt-users] Troubleshoot failed storage migration

Hi Christian, I'd start by checking the vdsm log of the SPM host when you are failing to retry the migration. This should give more detail about the failure. It's possible that you will need to manually remove some LVs on the destination VG. On Thu, Feb 23, 2017 at 4:11 PM, Christian Grenier

Re: [ovirt-users] Can't virtualize CentOS 7.x on oVirt 3.6

Hi I see this also and I've logged a bug with Red Hat support on it. I have found though that sometimes, if you wait long enough (i.e. approx 22 minutes) it will eventually boot. The other thing I've found is that if you change from SPICE to VNC, the problem goes away completely. Thanks On