[ovirt-users] Re: VM causes CPU blocks and forces reboot of host

[Jeff Bailey]

Sounds exactly like some trouble I was having.  I downgraded the kernel 
to 4.18.0-448 and everything is fine.  There have been a couple of 
kernel releases since I had problems but I haven't had a chance to try 
them yet.  I believe it was in 4.18.0-485 that I noticed it but that's 
just from memory.



On 5/11/2023 2:26 PM, dominik.dra...@blackrack.pl wrote:

Hello,
I have recently migrated our customer's cluster to newer hardware (CentOS 8 
Stream, 4 hypervisor nodes, 3 hosts with GlusterFS 5x 6TB SSD as JBOD with 
replica 3). After 1 month from the switch we encounter frequent vm locks that 
need host reboot in order to unlock the VM. Affected vms cannot be powered down 
from ovirt UI. Even if ovirt is successful in powering down affected vms, they 
cannot be booted again with information that OS disk is used. Once I reboot the 
host, vms can be turned on and everything works fine.

In vdsm logs I can note the following error:
  2023-05-11 19:33:12,339+0200 ERROR (qgapoller/1) [virt.periodic.Operation] 
> 
operation failed (periodic:187)
Traceback (most recent call last):
   File "/usr/lib/python3.6/site-packages/vdsm/virt/periodic.py", line 185, in 
__call__
 self._func()
   File "/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py", line 
476, in _poller
 vm_id, self._qga_call_get_vcpus(vm_obj))
   File "/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py", line 
797, in _qga_call_get_vcpus
 if 'online' in vcpus:
TypeError: argument of type 'NoneType' is not iterable

/var/log/messages reports:
May 11 19:35:15 kernel: task:CPU 7/KVM   state:D stack:0 pid: 7065 
ppid: 1 flags: 0x8182
May 11 19:35:15 kernel: Call Trace:
May 11 19:35:15 kernel: __schedule+0x2d1/0x870
May 11 19:35:15 kernel: schedule+0x55/0xf0
May 11 19:35:15 kernel: schedule_preempt_disabled+0xa/0x10
May 11 19:35:15 kernel: rwsem_down_read_slowpath+0x26e/0x3f0
May 11 19:35:15 kernel: down_read+0x95/0xa0
May 11 19:35:15 kernel: get_user_pages_unlocked+0x66/0x2a0
May 11 19:35:15 kernel: hva_to_pfn+0xf5/0x430 [kvm]
May 11 19:35:15 kernel: kvm_faultin_pfn+0x95/0x2e0 [kvm]
May 11 19:35:15 kernel: ? select_task_rq_fair+0x355/0x990
May 11 19:35:15 kernel: ? sched_clock+0x5/0x10
May 11 19:35:15 kernel: ? sched_clock_cpu+0xc/0xb0
May 11 19:35:15 kernel: direct_page_fault+0x3b4/0x860 [kvm]
May 11 19:35:15 kernel: kvm_mmu_page_fault+0x114/0x680 [kvm]
May 11 19:35:15 kernel: ? vmx_vmexit+0x9f/0x70d [kvm_intel]
May 11 19:35:15 kernel: ? vmx_vmexit+0xae/0x70d [kvm_intel]
May 11 19:35:15 kernel: ? gfn_to_pfn_cache_invalidate_start+0x190/0x190 [kvm]
May 11 19:35:15 kernel: vmx_handle_exit+0x177/0x770 [kvm_intel]
May 11 19:35:15 kernel: ? gfn_to_pfn_cache_invalidate_start+0x190/0x190 [kvm]
May 11 19:35:15 kernel: vcpu_enter_guest+0xafd/0x18e0 [kvm]
May 11 19:35:15 kernel: ? hrtimer_try_to_cancel+0x7b/0x100
May 11 19:35:15 kernel: kvm_arch_vcpu_ioctl_run+0x112/0x600 [kvm]
May 11 19:35:15 kernel: kvm_vcpu_ioctl+0x2c9/0x640 [kvm]
May 11 19:35:15 kernel: ? pollwake+0x74/0xa0
May 11 19:35:15 kernel: ? wake_up_q+0x70/0x70
May 11 19:35:15 kernel: ? __wake_up_common+0x7a/0x190
May 11 19:35:15 kernel: do_vfs_ioctl+0xa4/0x690
May 11 19:35:15 kernel: ksys_ioctl+0x64/0xa0
May 11 19:35:15 kernel: __x64_sys_ioctl+0x16/0x20
May 11 19:35:15 kernel: do_syscall_64+0x5b/0x1b0
May 11 19:35:15 kernel: entry_SYSCALL_64_after_hwframe+0x61/0xc6
May 11 19:35:15 kernel: RIP: 0033:0x7faf1a1387cb
May 11 19:35:15 kernel: Code: Unable to access opcode bytes at RIP 
0x7faf1a1387a1.
May 11 19:35:15 kernel: RSP: 002b:7fa6f5ffa6e8 EFLAGS: 0246 ORIG_RAX: 
0010
May 11 19:35:15 kernel: RAX: ffda RBX: 55be52e7bcf0 RCX: 
7faf1a1387cb
May 11 19:35:15 kernel: RDX:  RSI: ae80 RDI: 
0027
May 11 19:35:15 kernel: RBP:  R08: 55be5158c6a8 R09: 
0007d9e95a00
May 11 19:35:15 kernel: R10: 0002 R11: 0246 R12: 

May 11 19:35:15 kernel: R13: 55be515bcfc0 R14: 7fffec958800 R15: 
7faf1d6c6000
May 11 19:35:15 kernel: INFO: task worker:714626 blocked for more than 120 
seconds.
May 11 19:35:15 kernel:  Not tainted 4.18.0-489.el8.x86_64 #1
May 11 19:35:15 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.

May 11 19:35:15 kernel: task:worker  state:D stack:0 pid:714626 
ppid: 1 flags:0x0180
May 11 19:35:15 kernel: Call Trace:
May 11 19:35:15 kernel: __schedule+0x2d1/0x870
May 11 19:35:15 kernel: schedule+0x55/0xf0
May 11 19:35:15 kernel: schedule_preempt_disabled+0xa/0x10
May 11 19:35:15 kernel: rwsem_down_read_slowpath+0x26e/0x3f0
May 11 19:35:15 kernel: down_read+0x95/0xa0
May 11 19:35:15 kernel: do_madvise.part.30+0x2c3/0xa40
May 11 19:35:15 kernel: ? syscall_trace_enter+0x1ff/0x2d0
May 11 19:35:15 kernel: ? __x64_sys_madvise+0x26/0x30
May 11 19:35:15 kernel: __x64_sys_madvise+0x26/0x30
May 11 19:35:15 kernel: do_syscall_64+0x5b/0x1b0
May 11 19:35:15 

[ovirt-users] Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host

[Jeff Bailey]

Yes, downgrading edk2-ovmf will fix it.  Ultimately, there should be a 
new version of libvirt that works with the new edk2-ovmf but for now 
they're incompatible.



On 5/26/2021 12:28 PM, k.gunasekhar--- via Users wrote:

Thank you for your update .

is yum downgrade  edk2-ovmf worked? of any other changes to be made.
___
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: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/QTECUZO5WYA3AZKXNBJ25TM7KVQ25AUM/

___
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: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/IQ6NSYCCNTXU2NPYEUUH5ZC45QI356KQ/

[ovirt-users] Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host

[Jeff Bailey]

You  might also want to watch out for hostname-3.20-7.el8.x86_64.  It's 
causing loops in systemd's service start ordering which get broken by 
randomly not starting a service.  Often this service turns out to be 
NetworkManager :(



On 5/25/2021 1:38 PM, nsu...@provmed.net wrote:

Thanks Jeff Bailey,

The issue was with edk2-ovmf, rolling that package back and it started 
recognizing the CPU correctly.
___
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: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6J2WGNN3XPPH6ALLNPEE72J5JLUVESSH/

___
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: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LZ2Q5HDZQTD6NQWPLGAJEE7BEKY5SPBW/

[ovirt-users] Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host

[Jeff Bailey]

If it's the same problem that I ran into then it's the latest version of 
edk2-ovmf.  I'm not sure why it was pushed into the repos without a 
fixed libvirt to go with it.



On 5/25/2021 7:20 AM, Nur Imam Febrianto wrote:


Hi,

This morning I have a problem that suddenly my Host (Using Centos 8 
Stream, not oVirt Node) showing error with Cpu Compatibility. It says 
my CPU doesn’t have Haswell-noTSX and spec_ctrl flag. After 
downgrading the kernel back from 4.18.0 – 305 to 4.18.0 – 301.1 and 
rollback yum update, it working again. Do anybody having same issue ?


I’m using Xeon E5-2695v4 with cluster compatibility Secure Intel 
Haswell. Using oVirt 4.4.6 on CentOS Stream host.


Thanks before.

Sent from Mail  for 
Windows 10



___
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: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7R7SFBOPQL5S6WRT7RLZMIXOIOYBUGIF/
___
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: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/D47YYGMGJZIOM3QTDRVNBMRDEPK4ZMCQ/

[ovirt-users] Re: "POSIX storage based vm live migration failed"

[Jeff Bailey]

Yes, it used to work for me too.  I didn't investigate much further than 
tracking it down to selinux.  The cephfs client in the new kernel 
supports selinux security labels.  Since there were no labels before it 
probably didn't matter.  Now the problem has been revealed.  It might be 
possible to mount the filesystem with the labels disabled but I haven't 
tried.



On 12/28/2020 1:12 PM, Kushwaha, Tarun Kumar wrote:

thanks Jeff
it's working after disable SELinux but before 4.4.4 i was running 
everything perfectly with SELinux


On Mon, Dec 28, 2020 at 11:03 PM Kushwaha, Tarun Kumar 
mailto:ta...@synergysystemsindia.com>> 
wrote:


i am using CEPHFS

On Mon, Dec 28, 2020 at 10:18 PM Jeff Bailey mailto:bai...@cs.kent.edu>> wrote:

Try setting selinux to permissive (setenforce 0) on the hosts
and try to migrate again. What kind of filesystem are you
using for the posix mount?

 Original message 
From: Tarun Kushwaha mailto:ta...@synergysystemsindia.com>>
Date: 12/28/20 7:55 AM (GMT-05:00)
To: users@ovirt.org <mailto:users@ovirt.org>
Subject: [ovirt-users] "POSIX storage based vm live migration
failed"

After upgrading cluster version to 4.5  VM live migration
failed showing error due to storage I/O error and VM status is
being changed running to Pause , lower cluster version same is
working
___
Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
To unsubscribe send an email to users-le...@ovirt.org
<mailto:users-le...@ovirt.org>
Privacy Statement: https://www.ovirt.org/privacy-policy.html
<https://www.ovirt.org/privacy-policy.html>
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
<https://www.ovirt.org/community/about/community-guidelines/>
List Archives:

https://lists.ovirt.org/archives/list/users@ovirt.org/message/6NUNN54G25UKH6GOFDX3OYDZK2SJECXK/

<https://lists.ovirt.org/archives/list/users@ovirt.org/message/6NUNN54G25UKH6GOFDX3OYDZK2SJECXK/>
___
Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
To unsubscribe send an email to users-le...@ovirt.org
<mailto:users-le...@ovirt.org>
Privacy Statement: https://www.ovirt.org/privacy-policy.html
<https://www.ovirt.org/privacy-policy.html>
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
<https://www.ovirt.org/community/about/community-guidelines/>
List Archives:

https://lists.ovirt.org/archives/list/users@ovirt.org/message/BW5R2UUYWTEVY6GBAXOI45UGZXXPD5L2/

<https://lists.ovirt.org/archives/list/users@ovirt.org/message/BW5R2UUYWTEVY6GBAXOI45UGZXXPD5L2/>

___
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: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UUVIWCGW6NI7UT2O7QNA4TXYJO3DPNA7/

[ovirt-users] Re: "POSIX storage based vm live migration failed"

[Jeff Bailey]

Try setting selinux to permissive (setenforce 0) on the hosts and try to 
migrate again.  What kind of filesystem are you using for the posix mount?
 Original message From: Tarun Kushwaha 
 Date: 12/28/20  7:55 AM  (GMT-05:00) To: 
users@ovirt.org Subject: [ovirt-users] "POSIX storage based vm live migration 
failed" After upgrading cluster version to 4.5  VM live migration failed 
showing error due to storage I/O error  and VM status is being changed running 
to Pause , lower cluster version same is 
working___Users mailing list -- 
users@ovirt.orgTo unsubscribe send an email to users-leave@ovirt.orgPrivacy 
Statement: https://www.ovirt.org/privacy-policy.htmloVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6NUNN54G25UKH6GOFDX3OYDZK2SJECXK/___
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: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BW5R2UUYWTEVY6GBAXOI45UGZXXPD5L2/

[ovirt-users] Re: Latest ManagedBlockDevice documentation

[Jeff Bailey]

On 10/15/2020 12:07 PM, Michael Thomas wrote:

On 10/15/20 10:19 AM, Jeff Bailey wrote:


On 10/15/2020 10:01 AM, Michael Thomas wrote:

Getting closer...

I recreated the storage domain and added rbd_default_features=3 to 
ceph.conf.  Now I see the new disk being created with (what I think 
is) the correct set of features:


# rbd info rbd.ovirt.data/volume-f4ac68c6-e5f7-4b01-aed0-36a55b901
fbf
rbd image 'volume-f4ac68c6-e5f7-4b01-aed0-36a55b901fbf':
    size 100 GiB in 25600 objects
    order 22 (4 MiB objects)
    snapshot_count: 0
    id: 70aab541cb331
    block_name_prefix: rbd_data.70aab541cb331
    format: 2
    features: layering
    op_features:
    flags:
    create_timestamp: Thu Oct 15 06:53:23 2020
    access_timestamp: Thu Oct 15 06:53:23 2020
    modify_timestamp: Thu Oct 15 06:53:23 2020

However, I'm still unable to attach the disk to a VM.  This time 
it's a permissions issue on the ovirt node where the VM is running.  
It looks like it can't read the temporary ceph config file that is 
sent over from the engine:



Are you using octopus?  If so, the config file that's generated is 
missing the "[global]" at the top and octopus doesn't like that.  
It's been patched upstream.


Yes, I am using Octopus (15.2.4).  Do you have a pointer to the 
upstream patch or issue so that I can watch for a release with the fix?



https://bugs.launchpad.net/cinder/+bug/1865754


It's a simple fix.  I just changed line 100 of 
/usr/lib/python3.6/site-packages/os_brick/initiator/connectors/rbd.py to:


conf_file.writelines(["[global]", "\n", mon_hosts, "\n", keyring, "\n"])




--Mike
___
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: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KUO5OQWJDAHC25YLYVATQ6U2LLT6PH5Z/

[ovirt-users] Re: Latest ManagedBlockDevice documentation

[Jeff Bailey]

On 10/15/2020 10:01 AM, Michael Thomas wrote:

Getting closer...

I recreated the storage domain and added rbd_default_features=3 to 
ceph.conf.  Now I see the new disk being created with (what I think 
is) the correct set of features:


# rbd info rbd.ovirt.data/volume-f4ac68c6-e5f7-4b01-aed0-36a55b901
fbf
rbd image 'volume-f4ac68c6-e5f7-4b01-aed0-36a55b901fbf':
    size 100 GiB in 25600 objects
    order 22 (4 MiB objects)
    snapshot_count: 0
    id: 70aab541cb331
    block_name_prefix: rbd_data.70aab541cb331
    format: 2
    features: layering
    op_features:
    flags:
    create_timestamp: Thu Oct 15 06:53:23 2020
    access_timestamp: Thu Oct 15 06:53:23 2020
    modify_timestamp: Thu Oct 15 06:53:23 2020

However, I'm still unable to attach the disk to a VM.  This time it's 
a permissions issue on the ovirt node where the VM is running.  It 
looks like it can't read the temporary ceph config file that is sent 
over from the engine:



Are you using octopus?  If so, the config file that's generated is 
missing the "[global]" at the top and octopus doesn't like that.  It's 
been patched upstream.





https://pastebin.com/pGjMTvcn

The file '/tmp/brickrbd_nwc3kywk' on the ovirt node is only accessible 
by root:


[root@ovirt4 ~]# ls -l /tmp/brickrbd_nwc3kywk
-rw---. 1 root root 146 Oct 15 07:25 /tmp/brickrbd_nwc3kywk

...and I'm guessing that it's being accessed by the vdsm user?

--Mike

On 10/14/20 10:59 AM, Michael Thomas wrote:

Hi Benny,

You are correct, I tried attaching to a running VM (which failed), then
tried booting a new VM using this disk (which also failed). I'll use
the workaround in the bug report going forward.

I'll just recreate the storage domain, since at this point I have
nothing in it to lose.

Regards,

--Mike

On 10/14/20 9:32 AM, Benny Zlotnik wrote:

Did you attempt to start a VM with this disk and it failed, or you
didn't try at all? If it's the latter then the error is strange...
If it's the former there is a known issue with multipath at the
moment, see[1] for a workaround, since you might have issues with
detaching volumes which later, because multipath grabs the rbd devices
which would fail `rbd unmap`, it will be fixed soon by automatically
blacklisting rbd in multipath configuration.

Regarding editing, you can submit an RFE for this, but it is currently
not possible. The options are indeed to either recreate the storage
domain or edit the database table


[1] https://bugzilla.redhat.com/show_bug.cgi?id=1881832#c8




On Wed, Oct 14, 2020 at 3:40 PM Michael Thomas  
wrote:


On 10/14/20 3:30 AM, Benny Zlotnik wrote:

Jeff is right, it's a limitation of kernel rbd, the recommendation is
to add `rbd default features = 3` to the configuration. I think there
are plans to support rbd-nbd in cinderlib which would allow using
additional features, but I'm not aware of anything concrete.

Additionally, the path for the cinderlib log is
/var/log/ovirt-engine/cinderlib/cinderlib.log, the error in this case
would appear in the vdsm.log on the relevant host, and would look
something like "RBD image feature set mismatch. You can disable
features unsupported by the kernel with 'rbd feature disable'"


Thanks for the pointer!  Indeed,
/var/log/ovirt-engine/cinderlib/cinderlib.log has the errors that I 
was

looking for.  In this case, it was a user error entering the RBDDriver
options:


2020-10-13 15:15:25,640 - cinderlib.cinderlib - WARNING - Unknown 
config

option use_multipath_for_xfer

...it should have been 'use_multipath_for_image_xfer'.

Now my attempts to fix it are failing...  If I go to 'Storage -> 
Storage
Domains -> Manage Domain', all driver options are unedittable 
except for

'Name'.

Then I thought that maybe I can't edit the driver options while a disk
still exists, so I tried removing the one disk in this domain.  But 
even

after multiple attempts, it still fails with:

2020-10-14 07:26:31,340 - cinder.volume.drivers.rbd - INFO - volume
volume-5419640e-445f-4b3f-a29d-b316ad031b7a no longer exists in 
backend

2020-10-14 07:26:31,353 - cinderlib-client - ERROR - Failure occurred
when trying to run command 'delete_volume': (psycopg2.IntegrityError)
update or delete on table "volumes" violates foreign key constraint
"volume_attachment_volume_id_fkey" on table "volume_attachment"
DETAIL:  Key (id)=(5419640e-445f-4b3f-a29d-b316ad031b7a) is still
referenced from table "volume_attachment".

See https://pastebin.com/KwN1Vzsp for the full log entries related to
this removal.

It's not lying, the volume no longer exists in the rbd pool, but the
cinder database still thinks it's attached, even though I was never 
able

to get it to attach to a VM.

What are my options for cleaning up this stale disk in the cinder 
database?


How can I update the driver options in my storage domain (deleting and
recreating the domain is acceptable, if possible)?

--Mike




___
Users 

[ovirt-users] Re: Latest ManagedBlockDevice documentation

[Jeff Bailey]

On 10/13/2020 5:01 PM, Michael Thomas wrote:
After getting past the proxy issue, I was finally able to run the 
engine-setup --reconfigure-optional-components.  The new 
ManagedBlockStorage storage domain exists, and I was able to create a 
disk.  However, I am unable to attach the disk to a running VM.


The engine.log shows the following, with a reference to a possible 
cinderlib error ("cinderlib execution failed"):


2020-10-13 15:15:23,508-05 INFO 
[org.ovirt.engine.core.bll.UpdateVmCommand] (default task-13) 
[c73386d0-a713-4c37-bc9b-e7c4f9083f78] Lock Acquired to object 
'EngineLock:{exclusiveLocks='[grafana=VM_NAME]', 
sharedLocks='[5676d441-660e-4d9f-a586-e53ff0ea054b=VM]'}'
2020-10-13 15:15:23,522-05 INFO 
[org.ovirt.engine.core.bll.UpdateVmCommand] (default task-13) 
[c73386d0-a713-4c37-bc9b-e7c4f9083f78] Running command: 
UpdateVmCommand internal: false. Entities affected :  ID: 
5676d441-660e-4d9f-a586-e53ff0ea054b Type: VMAction group 
EDIT_VM_PROPERTIES with role type USER
2020-10-13 15:15:23,536-05 INFO 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(default task-13) [c73386d0-a713-4c37-bc9b-e7c4f9083f78] EVENT_ID: 
USER_UPDATE_VM(35), VM grafana configuration was updated by 
michael.thomas@internal-authz.
2020-10-13 15:15:23,539-05 INFO 
[org.ovirt.engine.core.bll.UpdateVmCommand] (default task-13) 
[c73386d0-a713-4c37-bc9b-e7c4f9083f78] Lock freed to object 
'EngineLock:{exclusiveLocks='[grafana=VM_NAME]', 
sharedLocks='[5676d441-660e-4d9f-a586-e53ff0ea054b=VM]'}'
2020-10-13 15:15:24,129-05 INFO 
[org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand] 
(default task-13) [f8829338-b040-46d0-a838-3cf28869637c] Lock Acquired 
to object 
'EngineLock:{exclusiveLocks='[5419640e-445f-4b3f-a29d-b316ad031b7a=DISK]', 
sharedLocks=''}'
2020-10-13 15:15:24,147-05 INFO 
[org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand] 
(default task-13) [f8829338-b040-46d0-a838-3cf28869637c] Running 
command: AttachDiskToVmCommand internal: false. Entities affected :  
ID: 5676d441-660e-4d9f-a586-e53ff0ea054b Type: VMAction group 
CONFIGURE_VM_STORAGE with role type USER,  ID: 
5419640e-445f-4b3f-a29d-b316ad031b7a Type: DiskAction group 
ATTACH_DISK with role type USER
2020-10-13 15:15:24,152-05 INFO 
[org.ovirt.engine.core.bll.storage.disk.managedblock.ConnectManagedBlockStorageDeviceCommand] 
(default task-13) [7cb262cc] Running command: 
ConnectManagedBlockStorageDeviceCommand internal: true.
2020-10-13 15:15:26,006-05 ERROR 
[org.ovirt.engine.core.common.utils.cinderlib.CinderlibExecutor] 
(default task-13) [7cb262cc] cinderlib execution failed:
2020-10-13 15:15:26,011-05 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] 
(default task-13) [7cb262cc] START, HotPlugDiskVDSCommand(HostName = 
ovirt4-mgmt.ldas.ligo-la.caltech.edu, 
HotPlugDiskVDSParameters:{hostId='61da4cdf-638b-4cbd-9921-5be820998d31', 
vmId='5676d441-660e-4d9f-a586-e53ff0ea054b', 
diskId='5419640e-445f-4b3f-a29d-b316ad031b7a'}), log id: 660ebc9e
2020-10-13 15:15:26,012-05 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] 
(default task-13) [7cb262cc] Failed in 'HotPlugDiskVDS' method, for 
vds: 'ovirt4-mgmt.ldas.ligo-la.caltech.edu'; host: 
'ovirt4-mgmt.ldas.ligo-la.caltech.edu': null
2020-10-13 15:15:26,012-05 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] 
(default task-13) [7cb262cc] Command 'HotPlugDiskVDSCommand(HostName = 
ovirt4-mgmt.ldas.ligo-la.caltech.edu, 
HotPlugDiskVDSParameters:{hostId='61da4cdf-638b-4cbd-9921-5be820998d31', 
vmId='5676d441-660e-4d9f-a586-e53ff0ea054b', 
diskId='5419640e-445f-4b3f-a29d-b316ad031b7a'})' execution failed: null
2020-10-13 15:15:26,012-05 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand] 
(default task-13) [7cb262cc] FINISH, HotPlugDiskVDSCommand, return: , 
log id: 660ebc9e
2020-10-13 15:15:26,012-05 ERROR 
[org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand] 
(default task-13) [7cb262cc] Command 
'org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand' failed: 
EngineException: java.lang.NullPointerException (Failed with error 
ENGINE and code 5001)
2020-10-13 15:15:26,013-05 ERROR 
[org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand] 
(default task-13) [7cb262cc] Transaction rolled-back for command 
'org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand'.
2020-10-13 15:15:26,021-05 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(default task-13) [7cb262cc] EVENT_ID: 
USER_FAILED_ATTACH_DISK_TO_VM(2,017), Failed to attach Disk 
testvm_disk to VM grafana (User: michael.thomas@internal-authz).
2020-10-13 15:15:26,021-05 INFO 
[org.ovirt.engine.core.bll.storage.disk.AttachDiskToVmCommand] 
(default task-13) [7cb262cc] Lock freed to object 
'EngineLock:{exclusiveLocks='[5419640e-445f-4b3f-a29d-b316ad031b7a=DISK]', 
sharedLocks=''}'


The /var/log/cinder/ directory on the ovirt node is empty, and doesn't 

[ovirt-users] Re: Support for Shared SAS storage

[Jeff Bailey]

I haven't tried with 4.4 but shared SAS works just fine with 4.3 (and 
has for many, many years).  You simply treat it as Fibre Channel.  If 
your LUNs aren't showing up I'd make sure they're being claimed as 
multipath devices.  You want them to be.  After that, just make sure 
they're sufficiently wiped so they don't look like they're in use.



On 8/7/2020 10:49 PM, Lao Dh via Users wrote:
Wow. That's sound bad. Then what storage type you choose at last (with 
your SAS connected storage)? VMware vSphere support DAS. Red Hat 
should do something.


2020年8月8日土曜日 4:06:34 GMT+8、Vinícius Ferrão via Users 
が書いたメール:



No, there’s no support for direct attached shared SAS storage on 
oVirt/RHV.


Fibre Channel is a different thing that oVirt/RHV supports.

> On 7 Aug 2020, at 08:52, hkexdong--- via Users > wrote:

>
> Hello Vinícius,
> Do you able to connect the SAS external storage?
> Now I've the problem during host engine setup. Select Fibre Channel 
and end up show "No LUNS found".

> ___
> 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: 
https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RDPLKGIRN5ZGIEPWGOKMGNFZNMCEN5RC/ 




___
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: 
https://www.ovirt.org/community/about/community-guidelines/

List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2CLI3YSYU7BPI62YANJXZV7RIQFOXXED/ 




___
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: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WOBHQDCBZZK5WKRAUNHP5CGFYY3HQYYU/
___
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: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UY52JRY5EMQJTMKG3POE2YXSFGL7P55S/

[ovirt-users] Re: remote-viewer Spice Problem on MacOS

[Jeff Bailey]

I've been seeing similar behavior but when running virt-viewer on 
windows.  I only noticed it after updating to 4.2 but for me it seems to 
only happen with guests running CentOS 7.5 and then only after a while 
like it's related to the console going blank from being idle.  Using 
aspice from movirt has no problem and using vnc also works fine. 
Connecting with either of those, hitting a key and then disconnecting 
and switching to the windows spice client fixes it for a while. 
Updating to remote-viewer 6.0-256 made no difference.


On 6/18/2018 5:09 AM, hpey...@plusline.net wrote:

Hi all,

we are currently experiencing a weird problem with oVirt and the spice console 
on MacOS:
Occasionally when our Mac Users are connecting to a Spice Console of any oVirt VM it 
opens the usual window but just displays the message: "Connected to graphic 
server". When a Linux user now connects to it and closes the connection the Mac user 
can also connect again normally.

I have tried https://www.spice-space.org/osx-client.html and 
https://rizvir.com/articles/ovirt-mac-console/ with exactly the same behaviour. 
The Issue appears on several different MacOS Versions and we believe it started 
after our upgrade to oVirt 4.2.

MacOS Version: 10.13.5
oVirt Version: 4.2.3.8-1.el7

Any help or suggestion is greatly appreciated.

Best regards,
Hendrik
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZQS676FGIRSLSXKSMIUEJAKY4RAVVA6F/


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MWFTUGIDZ74ZS2U7ZVR45MXAD5YSWIIZ/

[ovirt-users] Re: External ceph storage

[Jeff Bailey]

While it's certainly not ideal, of the available options I prefer 
cephfs.  You get full functionality unlike going through cinder and I 
wouldn't trust the new iscsi gateway functionality for any kind of 
redundant gateway usage yet.  Direct native rbd access would certainly 
be preferred but unfortunately I just don't see it coming.  Once upon a 
time there was hope but then the cinder bandaid arrived and that pretty 
much killed it.


On 5/27/2018 11:13 AM, Luca 'remix_tj' Lorenzetto wrote:

No,

The only way you have is to configure cinder to manage ceph pool or in 
alternative you have to deploy an iscsi gateway, no other ways are 
available at the moment.


So you can't use rbd directly.

Luca

Il dom 27 mag 2018, 16:54 Leo David > ha scritto:


Thank you Luca,
At the moment i would try the cinder storage provider, since we
already have a proxmox cluster directly connecting to ceph. The
problem is that I just could not find a straight way to do this.
ie: Specify the ceph monitors and ceph pool to connect to. Can oVirt
directly connect to ceph monitors ? How the configuration should be
done if so ?
Thank you very much !


On Sun, May 27, 2018, 17:20 Luca 'remix_tj' Lorenzetto
mailto:lorenzetto.l...@gmail.com>> wrote:

Hello,

Yes, using cinder or through iscsi gateway.

For a simpler setup i suggest the second option.

Luca

Il dom 27 mag 2018, 16:08 Leo David mailto:leoa...@gmail.com>> ha scritto:

Hello everyone,
I am new to ovirt and very impressed of its features. I
would like to levereage on our existing ceph cluster to
provide rbd images for vm hdds, is this possible to achieve ?
Thank you very much !
Regards,
Leo
___
Users mailing list -- users@ovirt.org 
To unsubscribe send an email to users-le...@ovirt.org




___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/SVQ7XSEXPHZXUJB3XX6TAUU7QGF6Q54D/

Re: [ovirt-users] oVirt 4.2 with cheph

[Jeff Bailey]

Yes, it works fine.  Just configure it as a posix fs.  I'm pretty sure 
you still need a different storage domain to hold the hosted engine 
(haven't tried 4.2) but other than that it works just like NFS.



On 2/15/2018 6:18 AM, Christoph Köhler wrote:

Hello,

does someone have experience with cephfs as a vm-storage domain? I think
about that but without any hints...

Thanks for pointing me...




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Anyone running Shared SAS hosted engine ?

[Jeff Bailey]

On 5/9/2017 6:06 AM, Gary Lloyd wrote:

Hi

I was just wondering if anyone is running Ovirt using a shared SAS array
with the ability to live migrate between hosts ?
If so has anyone been able to get hosted engine working with it ?


Yes, it works fine.  Just claim it's FC storage and use a dedicated LUN
for the hosted engine domain.



Thanks

/Gary Lloyd/

I.T. Systems:Keele University
Finance & IT Directorate
Keele:Staffs:IC1 Building:ST5 5NB:UK
+44 1782 733063 



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] More 4.1 Networking Questions

[Jeff Bailey]

On 4/10/2017 6:59 AM, Charles Tassell wrote:

Ah, spoke to soon.  30 seconds later the network went down with IPv6 
disabled.  So it does appear to be a host forwarding problem, not a VM 
problem.  I have an oVirt 4.0 cluster on the same network that doesn't 
have these issues, so it must be a configuration issue somewhere.  
Here is a dump of my ip config on the host:



The same L2 network?  Using the same range of MAC addresses?


[07:57:26]root@ovirt730-01 ~ # ip addr show
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: em1:  mtu 1500 qdisc mq master 
vmNet state UP qlen 1000

link/ether 18:66:da:eb:8f:c0 brd ff:ff:ff:ff:ff:ff
3: em2:  mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 18:66:da:eb:8f:c1 brd ff:ff:ff:ff:ff:ff
4: em3:  mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 18:66:da:eb:8f:c2 brd ff:ff:ff:ff:ff:ff
5: em4:  mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 18:66:da:eb:8f:c3 brd ff:ff:ff:ff:ff:ff
6: p5p1:  mtu 1500 qdisc mq master 
ovirtmgmt state UP qlen 1000

link/ether f4:e9:d4:a9:7a:f0 brd ff:ff:ff:ff:ff:ff
7: p5p2:  mtu 1500 qdisc noop state DOWN qlen 1000
link/ether f4:e9:d4:a9:7a:f2 brd ff:ff:ff:ff:ff:ff
8: vmNet:  mtu 1500 qdisc noqueue 
state UP qlen 1000

link/ether 18:66:da:eb:8f:c0 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.180/24 brd 192.168.1.255 scope global vmNet
   valid_lft forever preferred_lft forever
10: ovirtmgmt:  mtu 1500 qdisc 
noqueue state UP qlen 1000

link/ether f4:e9:d4:a9:7a:f0 brd ff:ff:ff:ff:ff:ff
inet 192.168.130.180/24 brd 192.168.130.255 scope global ovirtmgmt
   valid_lft forever preferred_lft forever
11: ;vdsmdummy;:  mtu 1500 qdisc noop state DOWN 
qlen 1000

link/ether fa:f3:48:35:76:8d brd ff:ff:ff:ff:ff:ff
14: vnet0:  mtu 1500 qdisc pfifo_fast 
master ovirtmgmt state UNKNOWN qlen 1000

link/ether fe:16:3e:3f:fb:ec brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc16:3eff:fe3f:fbec/64 scope link
   valid_lft forever preferred_lft forever
15: vnet1:  mtu 1500 qdisc pfifo_fast 
master vmNet state UNKNOWN qlen 1000

link/ether fe:1a:4a:16:01:51 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc1a:4aff:fe16:151/64 scope link
   valid_lft forever preferred_lft forever
16: vnet2:  mtu 1500 qdisc pfifo_fast 
master vmNet state UNKNOWN qlen 1000

link/ether fe:1a:4a:16:01:52 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc1a:4aff:fe16:152/64 scope link
   valid_lft forever preferred_lft forever

[07:57:50]root@ovirt730-01 ~ # ip route show
default via 192.168.1.254 dev vmNet
192.168.1.0/24 dev vmNet  proto kernel  scope link  src 192.168.1.180
169.254.0.0/16 dev vmNet  scope link  metric 1008
169.254.0.0/16 dev ovirtmgmt  scope link  metric 1010
192.168.130.0/24 dev ovirtmgmt  proto kernel  scope link  src 
192.168.130.180


[07:57:53]root@ovirt730-01 ~ # ip rule show
0:from all lookup local
32760:from all to 192.168.130.0/24 iif ovirtmgmt lookup 3232268980
32761:from 192.168.130.0/24 lookup 3232268980
32762:from all to 192.168.1.0/24 iif vmNet lookup 2308294836
32763:from 192.168.1.0/24 lookup 2308294836
32766:from all lookup main
32767:from all lookup default
[07:57:58]root@ovirt730-01 ~ #


On 2017-04-10 07:54 AM, Charles Tassell wrote:


Hi Everyone,

  Just an update, I installed a new Ubuntu guest VM and it was doing 
the same thing regarding the network going down, then I disabled IPv6 
and it's been fine for the past 10-15 minutes.  So the issue seems to 
be IPv6 related, and I don't need IPv6 so I can just turn it off.  
The eth1 NIC disappearing is still worrisome though.



On 2017-04-10 07:13 AM, Charles Tassell wrote:

Hi Everyone,

  Thanks for the help, answers below.

On 2017-04-10 05:27 AM, Sandro Bonazzola wrote:

Adding Simone and Martin, replying inline.

On Mon, Apr 10, 2017 at 10:16 AM, Ondrej Svoboda 
> wrote:


Hello Charles,

First, can you give us more information regarding the
duplicated IPv6 addresses? Since you are going to reinstall the
hosted engine, could you make sure that NetworkManager is
disabled before adding the second vNIC (and perhaps even
disable IPv6 and reboot as well, so we have a solid base and
see what makes the difference)?

I disabled NetworkManager on the hosts (systemctl disable 
NetworkManager ; service NetworkManager stop) before doing the oVirt 
setup and rebooted to make 

Re: [ovirt-users] Shared storage

[Jeff Bailey]

An MD1400 should be a JBOD and probably not what you want.  An MD3400 
should work fine though.  We use MD3200s with SAS switches and treat 
them as FC storage with no trouble.


On 3/21/2016 5:50 AM, Maton, Brett wrote:

Hello list,

   I was wondering if any one could tell me if a Dell MD1400 Direct
Attached Storage unit is suitable for shared storage between ovirt hosts?

   I really don't want to buy something that isn't going to work :)

Regards,
Brett


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Can´t use a VM Network VLAN, because the Virtual Machines inside can't reach the Gateway

[Jeff Bailey]

I see the tap interface on the ovirtmgmt bridge which is in the 
192.168.0.0/24 subnet but your vm has a 192.168.50.0/27 address.  I 
don't know why it's attached to that bridge though since it looks like 
you've placed it on the dmz network.  What happens if you change the IP 
address in your test vm to something in 192.168.0.0/24 and then ping 
your 192.168.0.1 gateway?


On 7/6/2015 1:06 PM, Julián Tete wrote:

Hi Friends of oVirt

This the data required:

I have a HP Enclosure with a HP SAN.
I can't change the net settings in the switch because we have VMware 
Virtual Machines in production in the same enclosure.
The switch is in Trunk Mode and all the traffic are in Tagged VLAN's 
with ID's: 1,50,90,91 and 100.

I can play with 6 blades.
I in the first Blade I installed oVirt in hosted engine mode.
The only S.O is CentOS 7.1

I used inxi to brig the data for you:

My First Host is the only host until now (SPM) is the first data 
domain (NFS) and contains the hosted engine machine.
I installed oVirt with ovirtmgmt in VLAN 1, over the interface eno1, 
without any VLAN Tagged configuration.


This the data for my first host:

http://pastebin.com/dfC0XTQM

This the data for the Engine:

http://pastebin.com/JdrMSbj0

This the data for the Virtual Machine created in VLAN 50:

S.O : CentOS 7.1
SELinux: Permissive
IP ADDRESS: 192.168.50.8
PREFIX: 27
GATEWAY: 192.168.50.1
Interface: eth0

The Virtual Machine hasn´t any VLAN configuration.

In the 3 S.O, Network Manager is stopped and disabled, connectivity is 
managed by the network daemon.


This is the data for the Networking in the admin interface:

http://postimg.org/image/lbypejxrh/

http://postimg.org/image/jtkyhqs8f/

http://postimg.org/image/7dwf1nb9f/

http://postimg.org/image/6i9t75g33/

http://postimg.org/image/sm8e6lecv/

http://postimg.org/image/cvig7rjuv/

http://postimg.org/image/fxcthsrtl/

http://postimg.org/image/o6xjwwvyz/

http://postimg.org/image/pv5ar5v3j/

http://postimg.org/image/dx8br0gq7/

http://postimg.org/image/baixp4b0j/

This the case

With No IP in the VLAN, and IP in the Virtual Machine, From the 
Virtual Machine can ping myself (192.168.50.8) but I can't reach the 
gateway, can't reach the host, can't reach Internet.


Any help is appreciated

Thanks Friends of oVirt








2015-07-06 7:51 GMT-05:00 Soeren Malchow soeren.malc...@mcon.net 
mailto:soeren.malc...@mcon.net:


Hi,

To make it easier to understand what the situation is, it would
help to
see your bridging configuration and your interface configration.

Something like:

# ip addr

And

# brctl show

Regards
Soeren

On 06/07/15 13:30, users-boun...@ovirt.org
mailto:users-boun...@ovirt.org on behalf of Dan Kenigsberg
users-boun...@ovirt.org mailto:users-boun...@ovirt.org on
behalf of dan...@redhat.com mailto:dan...@redhat.com wrote:

On Tue, Jun 30, 2015 at 03:48:49PM -0500, Julián Tete wrote:
 Hi Friends of oVirt

 I'm trying to migrate my company from VMware to oVirt.

We'd like to help you do this!

 In my final tests, I set up 2 more VLANs in oVirt, (VM VLANs)
 The Virtual Machines in these VLANs, can be reached from the
external
IPs
 from the net range,
 but from the Virtual machines only can ping the Host with the
Bridge and
 itself, can't reach the gateway. ¿?

 I configured a IP Forwarding in the Host with the virtual
machine, and
 nothing changes...

 Any idea ? This is the last duty before embrace oVirt in the
company.

 Look to the VLAN 100 configuration (My desired VM Network):

 http://postimg.org/image/7hrog0a2n/

 http://postimg.org/image/68b40i1vr/

 http://postimg.org/image/lu6mlshgp/

I must admit that I don't understand your problem yet. When you ping
from inside your guest, where are your packets dropped?

I'd like to point that your Hosting network, as most VM
networks, is
better off left without an IP address. The benefit of this is better
security (host TCP stack is not accessible from VMs) and less
chances of
routing collisions from the host.

So unless you need to use the same network for something other
than VM
communication, try to clear its address.

Regards,
Dan.
___
Users mailing list
Users@ovirt.org mailto:Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ceph

[Jeff Bailey]

On 5/1/2014 2:58 PM, Dave Neary wrote:

Hi all,

For my education, how would you like to use Ceph with oVirt?


Personally, I'd like to see a simple consumer of RBDs.  I don't want to 
manage/monitor/configure/etc my ceph cluster through ovirt.  I wouldn't 
mix storage and virtualization nodes either.  I also wouldn't make any 
assumptions that the ceph cluster is being used exclusively by ovirt.  
It could be a very large cluster supporting many other things.  I've 
wanted ceph support for quite some time and hopefully with this extra 
attention we'll get it a bit sooner :)



Thanks,
Dave.


On 05/01/2014 06:17 PM, Nicolas Ecarnot wrote:

Le 01/05/2014 16:27, Jeremiah Jahn a écrit :

Personally, I'd love to use it. I haven't used it because it hasn't
been part of RedHat's enterprise platform, and didn't want to have to
track updates separately, so we went with gluster for all of our
storage needs as opposed to a mix of both gluster and ceph where
appropriate.

For the exact same reasons, we did not yet choose which way to go
between Ceph and Gluster, wondering which one will lead the market in
the next future.
But we are strongly willing to use their features, whatever the future
mixed enhanced product or name.


/2cents

On Thu, May 1, 2014 at 2:07 AM, Jiri Moskovcak jmosk...@redhat.com
wrote:

Hello oVirt users!

When I read [1] I got curious how much demand for supporting Ceph we can
expect in the near future. So if use it or plan to use it please let us
know.

Have a nice day,
Jirka

[1]
http://www.redhat.com/about/news/press-archive/2014/4/red-hat-to-acquire-inktank-provider-of-ceph

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users





___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] oVirt and SAS shared storage??

[Jeff Bailey]

On 11/16/2013 9:22 AM, Ryan Barry wrote:

 unfortunally, I didn't got a reply for my question. So.. let's try
 again.

 Does oVirt supports SAS shared storages (p. e. MSA2000sa) as
 storage domain?
 If yes.. what kind of storage domain I've to choose at setup time?

 SAS is a bus which implements the SCSI protocol in a point-to-point
 fashion. The array you have is the effective equivalent of attaching
 additional hard drives directly to your computer.

 It is not necessarily faster than iSCSI or Fiber Channel; almost any
 nearline storage these days will be SAS, almost all the SANs in
 production, and most of the tiered storage as well (because SAS
 supports SATA drives). I'm not even sure if NetApp uses FC-AL drives
 in their arrays anymore. I think they're all SAS, but don't quote me
 on that.

 What differentiates a SAN (iSCSI or Fiber Channel) from a NAS is that
 a SAN presents raw devices over a fabric or switched medium rather
 than point-to-point (point-to-point Fiber Channel still happens, but
 it's easier to assume that it doesn't for the sake of argument). A NAS
 presents network file systems (CIFS, GlusterFS, Lustre, NFS, Ceph,
 whatever), though this also gets complicated when you start talking
 about distributed clustered network file systems.

 Anyway, what you have is neither of these. It's directly-attached
 storage. It may work, but it's an unsupported configuration, and is
 only shared storage in the sense that it has multiple controllers. If
 I were going to configure it for oVirt, I would:


It's shared storage in every sense of the word.  I would simply use an
FC domain and choose the LUNs as usual.

 Attach it to a 3rd server and export iSCSI LUNs from it
 Attach it to a 3rd server and export NFS from it
 Attach it to multiple CentOS/Fedora servers, configure clustering (so
 you get fencing, a DLM, and the other requisites of a clustered
 filesystem), and use raw cLVM block devices or GFS2/OCFS filesystems
 as POSIXFS storage for oVirt.


These would be terrible choices for both performance and reliability. 
It's exactly the same as fronting an FC LUN would be with all of that
crud when you could simply access the LUN directly.  If the array port
count is a problem then just toss an SAS switch in between and you have
an all SAS equivalent of a Fibre Channel SAN.  This is exactly what we
do in production vSphere environments and there are no technical reasons
it shouldn't work fine with oVirt.

 Thank you for your help

 Hans-Joachim


 Hans
  
 -- 
 while (!asleep) { sheep++; }


 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Fault tolerant storage

[Jeff Bailey]

On 5/2/2013 5:18 AM, Jakub Bittner wrote:

Dne 1.5.2013 17:25, Sven Knohsalla napsal(a):

Hi Jakub,

I assume the solution you are searching for is something GlusterFS 
can serve for example:

http://www.gluster.org/about/

Best, Sven.




-Ursprüngliche Nachricht-
Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im 
Auftrag von Jonathan Horne

Gesendet: Mittwoch, 1. Mai 2013 17:16
An: Jakub Bittner; users@ovirt.org
Betreff: Re: [Users] Fault tolerant storage

I would be surprised if you could do that without your users noticing.

It seems like you would be better served to have each storage domain 
on a RAID array and rely on the hardware tools of the RAID to handle 
disk failure tolerance.


Cheers,
jonathan

-Original Message-
From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On 
Behalf Of Jakub Bittner

Sent: Tuesday, April 30, 2013 9:19 AM
To: users@ovirt.org
Subject: [Users] Fault tolerant storage

Hi,

would it be possible in near future to use for example 2 attached 
DATA storage (iSCSi, or so) as fault tolerant storage?


I mean I have two data storage connected to data center and they 
include exactly same data and my VMs runs from one and all changes 
are mirrored to second like RAID 1 and if one storage fails 
everything switch to second storage without user notice?

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


This is a PRIVATE message. If you are not the intended recipient, 
please delete without copying and kindly advise us by e-mail of the 
mistake in delivery. NOTE: Regardless of content, this e-mail shall 
not operate to bind SKOPOS to any order or other contract unless 
pursuant to explicit written agreement or government initiative 
expressly permitting the use of e-mail for such purpose.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Hi,

thank you for replies.
Sven:
I know Gluster. I am using it since 2009 in production but the problem 
is that many organisations and users already have Storage arrays 
(SAN,NAS,..) and migrating to Gluster is not possible or reliable.




It seems to me that the easiest way to get mirrored storage would be to 
use mirrored LVM logical volumes.  That would require modifications to 
vdsm at least (probably the engine too for management) but certainly 
seems like it would be the easiest/most reliable way.


While I have 2 storage arrays I would like to use them like network 
raid 1.  Also the combination of more storage types would be super 
cool (NFS + ISCSI) or so.


Jonathan:
Yes, I can rely on disk arrays for hdd fault tolerance, but there are 
more points of failure than disks (network, ram, cpu, water in rack 
and so).


To be clear, I know, I can manage fault tolerance by hardware, but it 
is more expensive

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] [Spice-devel] 3.2 final and status of spice console in ie

[Jeff Bailey]

On 3/20/2013 5:20 AM, Christophe Fergeau wrote:

On Tue, Mar 19, 2013 at 05:11:56PM -0400, Jeff Bailey wrote:

On 3/19/2013 11:05 AM, Christophe Fergeau wrote:

As far as I know, there haven't been public spicex releases, so I'm not
sure where this spicex used with oVirt comes from.

I was referring to the log file named spicex related to the
activex plugin.

Yes, I got that part, but same answer, as far as I know there hasn't been
any public releases of the activex plugin ;)


Heh, heh, maybe it's a secret. :)

Actually, I believe I got it from 
http://elmarco.fedorapeople.org/spice.cab and it seems to be version 
5.0.2.2.



Christophe


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] [Spice-devel] 3.2 final and status of spice console in ie

[Jeff Bailey]

On 3/19/2013 11:05 AM, Christophe Fergeau wrote:

Hey,

On Tue, Mar 19, 2013 at 12:08:13AM +0200, Itamar Heim wrote:

On 03/19/2013 12:05 AM, Jeff Bailey wrote:

On 3/18/2013 7:56 AM, Juan Jose wrote:

Hello Itamar and everybody,

I have tested this Howto with a Windows 7 Enterprise edition client
and IE 9 and when you click over console button in User portal
virt-viewer is launched but after one second it close windows and
don't connect to virtual machine. I have oVirt 3.1 and I'm thinking in
migrate my system to oVirt 3.2 but it will be nice to know which it is
the reason because it doesn't work. Some indications about what would
be the problem will be wellcome.


This is exactly the same thing I get.  3.2 doesn't help.  The spicex log
says that it can't connect to the spice client pipe.  This is with both
the admin portal and the user portal.

adding spice-devel for their input

As far as I know, there haven't been public spicex releases, so I'm not
sure where this spicex used with oVirt comes from.


I was referring to the log file named spicex related to the activex 
plugin.  Adding the engine url to the IE trusted zone fixed my problem 
though.



Christophe


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] 3.2 final and status of spice console in ie

[Jeff Bailey]

On 3/18/2013 2:43 PM, Dead Horse wrote:
I have seen this one before.Try adding the your ovirt manager to the 
Internet Explorer trusted sites.

-DHC



Hmm, that does indeed seem to fix it.  I added the engine URL to the 
trusted sites zone and unchecked the Require server verification box 
and now I get a connected spice client.  Thanks !




On Mon, Mar 18, 2013 at 7:01 AM, Itamar Heim ih...@redhat.com 
mailto:ih...@redhat.com wrote:


On 03/18/2013 01:56 PM, Juan Jose wrote:

Hello Itamar and everybody,

I have tested this Howto with a Windows 7 Enterprise edition
client and
IE 9 and when you click over console button in User portal
virt-viewer
is launched but after one second it close windows and don't
connect to
virtual machine. I have oVirt 3.1 and I'm thinking in migrate
my system
to oVirt 3.2 but it will be nice to know which it is the
reason because
it doesn't work. Some indications about what would be the
problem will
be wellcome.

If it is necessary some log I can provide it.


hard to help without logs (spice client to begin with).
will be easier helping/patching you on 3.2 of course.


Many thanks,

Juanjo.

On Fri, Mar 15, 2013 at 10:37 AM, Itamar Heim
ih...@redhat.com mailto:ih...@redhat.com
mailto:ih...@redhat.com mailto:ih...@redhat.com wrote:

On 02/28/2013 01:34 PM, Karli Sjöberg wrote:

But to me one question arise, with a Windows
clients, XP or
7, any
version, it's possible to use the User Portal to
be able
users lauch
the VM console?, or it's mandatory to have Fedora
clients with
spice-xpi for firefox.

It would seem impossible with oVirt-3.1, which is the
biggest
reason why
we cannot take into any real production at the
moment:( What
good does
it do that it works with Fedora when the total of
people using
it counts
to 1(me)?


1. there are wiki's on how to add spice windows support to
ovirt:
http://wiki.ovirt.org/wiki/How_to_Connect_to_SPICE_Console_With_Portal

2. there are patches for various solutions to this coming
(mime
based launched, spice.html5, novnc, maybe spice-xpi for
firefox windows)

HTH,
Itamar



___
Users mailing list
Users@ovirt.org mailto:Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] 3.2 final and status of spice console in ie

[Jeff Bailey]

On 2/27/2013 11:01 AM, Gianluca Cecchi wrote:

On Wed, Feb 27, 2013 at 4:48 PM, Juan Jose  wrote:

Hello Karli,

I'm working with a oVirt version 3.1, but I have read that Gianluca have
been able to do this console works. Anybody can help us providing some
guidance?

Many thanks in avanced,

Juanjo.

keep in mind that I have only used spice console with oVirt version
3.2 final and ie 9 32 bit in the client


I've never gotten it to work in IE (3.1 or 3.2) but haven't put lots of 
effort into finding out why.  I get the exact same results (client for a 
couple of seconds).  I believe it's always been with IE 9 and Windows 7/64.



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] engine 3.2 installation issue

[Jeff Bailey]

On 2/28/2013 2:23 AM, Sven Knohsalla wrote:

 Hi Moran,

 seems so, did override the config and set it manually after the
 engine-setup was done, did work fine.

 Specifying iptables won’t work, as firewalld replaced iptables in F18.


Firewalld is simply the default in F18. You can disable it and enable
iptables like the good ol' days :) Just make sure to install
iptables-services.

 Thanks for the notice J

 Best, Sven.

 *Von:*Moran Goldboim [mailto:mgold...@redhat.com]
 *Gesendet:* Donnerstag, 28. Februar 2013 00:37
 *An:* Gianluca Cecchi
 *Cc:* Sven Knohsalla; users
 *Betreff:* Re: [Users] engine 3.2 installation issue

 On 02/27/2013 09:56 AM, Gianluca Cecchi wrote:

 I found problems too with firewalld in fedora 18.
 I got an error if I remember correctly, so I ran again specifying
 iptables




 ___

 Users mailing list

 Users@ovirt.org mailto:Users@ovirt.org

 http://lists.ovirt.org/mailman/listinfo/users


 any chance you are hitting [Bug 904153] engine-setup hangs on
 Firewalld config ?



 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] vlan interface failed : Bridged network Internet is attached to multiple interfaces: UNKNOWN on Host node1.

[Jeff Bailey]

On 2/20/2013 4:56 AM, Antoni Segura Puimedon wrote:
 There's a systemd hackfest this week on occasion of the developers
 conference in Brno. I'll try to see what can be done about this.

 @Kevin. Did you try the 60-net.rules that Lukas Nykryn proposed?
 ACTION==add, SUBSYSTEM==net, ATTRS{type}==1, 
 PROGRAM=/lib/udev/rename_device, RESULT==?*, NAME=$result

I had tried this and it didn't help.  It seems that the vlan interface
has type 1 (/sys/class/net/em1_1.538/type contains 1) and the rename
still happens.

 Best,

 Toni

 - Original Message -
 From: Jeff Bailey bai...@cs.kent.edu
 To: users@ovirt.org
 Sent: Wednesday, February 20, 2013 3:38:28 AM
 Subject: Re: [Users] vlan interface failed : Bridged network Internet is 
 attached to multiple interfaces: UNKNOWN
 on Host node1.

 On 2/19/2013 8:04 PM, Jeff Bailey wrote:
 On 2/19/2013 5:34 PM, Dan Kenigsberg wrote:
 On Tue, Feb 19, 2013 at 11:12:42PM +0100, Kevin Maziere Aubry
 wrote:
 Hi

 I've just found a workaround ... rm
 /usr/lib/udev/rules.d/60-net.rules and
 reboot
 Then I can add vlan to physical interface.



 2013/2/19 Kevin Maziere Aubry kevin.mazi...@alterway.fr

 Hi

 Today on IRC we worked on this issue and I will try to
 summarized the
 results of our troubleshooting :

 Current stable systemd rpm has a bug with device mapper which
 cause
 all
 device created on a fibrechannel to have wrong access right.
 So the workaround is to replace systemd with the one on the
 testing
 repo.

 But the testing release as also a bug with udev which rename
 network
 interface so that each new network interface is named
 renameX@interface.

 We test some udev workaround unsucessfully. (
 https://bugzilla.redhat.com/show_bug.cgi?id=907365 )
 Now I think a patch on systemd testing rpm should fix the issue,
 waiting
 for it

 Reference:

 https://bugzilla.redhat.com/show_bug.cgi?id=912323
 Last word that I've heard about this bug ^^^ (Bug 912323 - Adding
 a
 VLAN Device does not Work ) is that Muli can no longer reproduce
 it on
 his host.

 If this does reproduce on your system, would you provide more data
 as
 requested on https://bugzilla.redhat.com/show_bug.cgi?id=912323#c2
 ?
 Note that I've just called the systemd cavalry to our assistance.
 I thought I had a simple (if inconvenient) work around but it looks
 like something (either the deploy or syncing the management
 network)
 puts the HWADDR line back in ifcfg-em1_1.  I'm going to do some
 more
 testing...  Yep, it's the network sync that adds HWADDR back which
 then triggers udev to rename em1_1.538 to em1_1 which doesn't work
 and
 I end up with rename??@em1_1.  I can live without the sync I
 suppose.  I'll try leaving the manual config of the management
 network
 alone and then config the other networks and see what happens.

 Well, that didn't work.  I can't seem to find any combination that
 plays
 nicely together.  Looks like Kevin's solution of ripping out udev's
 ability to rename interfaces may be the only quick fix.  It does get
 us
 the ability to change ownership of LVs back which is more important.
  So
 far, I've seen no ill effects and everything (networking and storage)
 seems to be working as it should.

 Dan.
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Permission issues

[Jeff Bailey]

On 2/20/2013 5:50 AM, Jakub Bittner wrote:
 Hi,
 I have permission issues with ovirt node and iSCSi.


What version of systemd is on your node?


 2013-02-20 11:20:47.854+: 15899: error :
 virNetClientProgramDispatchError:174 : internal error process exited
 while connecting to monitor: qemu-kvm: -drive
 file=/rhev/data-center/20ca8725-0221-4227-b87a-5e6d71ab6fe3/ce0168c1-e69f-479e-a591-daca0a8ee7db/images/ebb3b49c-717d-4ae5-8ddb-4d25a367126c/60ddc3a1-7855-4c0a-a5a6-7169bc29db3a,if=none,id=drive-virtio-disk0,format=qcow2,serial=ebb3b49c-717d-4ae5-8ddb-4d25a367126c,cache=none,werror=stop,rerror=stop,aio=native:
 could not open disk image
 /rhev/data-center/20ca8725-0221-4227-b87a-5e6d71ab6fe3/ce0168c1-e69f-479e-a591-daca0a8ee7db/images/ebb3b49c-717d-4ae5-8ddb-4d25a367126c/60ddc3a1-7855-4c0a-a5a6-7169bc29db3a:
 Permission denied

 I tried chown 36:36
 /rhev/data-center/20ca8725-0221-4227-b87a-5e6d71ab6fe3/ce0168c1-e69f-479e-a591-daca0a8ee7db/images/ebb3b49c-717d-4ae5-8ddb-4d25a367126c/60ddc3a1-7855-4c0a-a5a6-7169bc29db3a


 which leads to
 /dev/ce0168c1-e69f-479e-a591-daca0a8ee7db/60ddc3a1-7855-4c0a-a5a6-7169bc29db3a
 which leads to /dev/dm-13

 I tried all of them to chmod 36:36, but this does not help. But if I
 change to vdsm user (su - vdsm -s /bin/bash I can read from it)

 After chmoding this file it started to work (VM started)

 /rhev/data-center/20ca8725-0221-4227-b87a-5e6d71ab6fe3/ce0168c1-e69f-479e-a591-daca0a8ee7db/images/ebb3b49c-717d-4ae5-8ddb-4d25a367126c/2ea15f6b-8029-474f-90c9-e693e4c10a67



 Creating new hard drives still doesn work. I have node version
 2.6.0-20130212.fc18.
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Fwd: Re: Permission issues

[Jeff Bailey]

On 2/20/2013 2:55 PM, supo...@logicworks.pt wrote:
 How can I update systemd in the node?

You would need to install from a newer node iso.  If you don't want to
wait, you could install a minimal F18, configure your networking, add
the ovirt repo and then just add that host using the engine GUI.  At
this stage, you will still have the same problem you currently have. 
You then need to:

yum --enablerepo=updates-testing update systemd

After that, remove /usr/lib/udev/rules.d/60-net.rules-  typing from
memory but should be close

Reboot and everything *should* work :)

There are other little things like disabling firewalld, tweeking
multipath.conf, etc that I do but the steps above basically cover it.

 Thanks

 - Mensagem original -
 De: Kevin Maziere Aubry kevin.mazi...@alterway.fr
 Para: Jakub Bittner j.bitt...@nbu.cz
 Cc: users users@ovirt.org
 Enviadas: Quarta-feira, 20 Fevereiro, 2013 17:48:29
 Assunto: Re: [Users] Fwd: Re: Permission issues



 Sur. 
 I update systemd and remove udev network conf file. 
 I also stop network manager and add gateway to /etc/sysconfig/network. 

 Also I set dns manager name to /etc/hosts file to avoid dns issue. 

 It works ;) 
 Le 20 févr. 2013 18:42, Jakub Bittner  j.bitt...@nbu.cz  a écrit : 


 I wonder if is there any way to create ovirt-node from running Fedora 18 
 netinstalled server. Do anybody know what packages should I install? 

 Thanks 
 __ _ 
 Users mailing list 
 Users@ovirt.org 
 http://lists.ovirt.org/ mailman/listinfo/users 

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] vlan interface failed : Bridged network Internet is attached to multiple interfaces: UNKNOWN on Host node1.

[Jeff Bailey]

On 2/19/2013 5:34 PM, Dan Kenigsberg wrote:

On Tue, Feb 19, 2013 at 11:12:42PM +0100, Kevin Maziere Aubry wrote:

Hi

I've just found a workaround ... rm  /usr/lib/udev/rules.d/60-net.rules and
reboot
Then I can add vlan to physical interface.



2013/2/19 Kevin Maziere Aubry kevin.mazi...@alterway.fr


Hi

Today on IRC we worked on this issue and I will try to summarized the
results of our troubleshooting :

Current stable systemd rpm has a bug with device mapper which cause all
device created on a fibrechannel to have wrong access right.
So the workaround is to replace systemd with the one on the testing repo.

But the testing release as also a bug with udev which rename network
interface so that each new network interface is named renameX@interface.

We test some udev workaround unsucessfully. (
https://bugzilla.redhat.com/show_bug.cgi?id=907365 )
Now I think a patch on systemd testing rpm should fix the issue, waiting
for it

Reference:

https://bugzilla.redhat.com/show_bug.cgi?id=912323

Last word that I've heard about this bug ^^^ (Bug 912323 - Adding a
VLAN Device does not Work ) is that Muli can no longer reproduce it on
his host.

If this does reproduce on your system, would you provide more data as
requested on https://bugzilla.redhat.com/show_bug.cgi?id=912323#c2 ?
Note that I've just called the systemd cavalry to our assistance.


I thought I had a simple (if inconvenient) work around but it looks like 
something (either the deploy or syncing the management network) puts the 
HWADDR line back in ifcfg-em1_1.  I'm going to do some more testing...  
Yep, it's the network sync that adds HWADDR back which then triggers 
udev to rename em1_1.538 to em1_1 which doesn't work and I end up with 
rename??@em1_1.  I can live without the sync I suppose.  I'll try 
leaving the manual config of the management network alone and then 
config the other networks and see what happens.



Dan.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] compatibility issue

[Jeff Bailey]

Did you add the ovirt repo to the node before deploying it?  If not then 
you may have the older vdsm from the fedora repo.


---
Jeff

On 2/18/2013 5:06 PM, Jonathan Horne wrote:

Both the manager and the node are fresh installs of fedora 18, and the node 
ovirt install was initiated from the web console (so I don’t see how its 
possible I have a downlevel version on the node).

-Original Message-
From: Gianluca Cecchi [mailto:gianluca.cec...@gmail.com]
Sent: Monday, February 18, 2013 1:12 PM
To: Jonathan Horne
Cc: users@ovirt.org
Subject: Re: [Users] compatibility issue

On Mon, Feb 18, 2013 at 7:27 PM, Jonathan Horne jho...@skopos.us wrote:

Just got 3.2 installed as ovirt node on a fedora 18 install.  After
the reboot, the console now complains with this:





2013-Feb-18, 12:20 Host rnd8 is compatible with versions (3.0,3.1) and
cannot join Cluster Default which is set to version 3.2.

2013-Feb-18, 12:20 Bridged network ovirtmgmt is attached to multiple
interfaces: UNKNOWN on Host rnd8.



The server (rnd8)  is a dell 2950 with dual X5460 processors. I never
had to mess with this type of thing in the past on 3.1, is there
something I did not configure on 3.2 that is causing this?  Is a dell
2950 not supported on 3.2?



Thanks,

jonathan


At a certain point during 3.2 development the default became 3.2.
What version is your engine? Did you install ex-novo the engine and the node?
Did you perhaps reuse an ip that for some reason is already allocated in db as 
3.1 host?

Probably not me, but others can help you if you give full details of 
environment and logs...

Gianluca


This is a PRIVATE message. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to 
any order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Host deployment on 3.2

[Jeff Bailey]

On 2/16/2013 2:00 AM, Alon Bar-Lev wrote:

Can you please send the content of /proc/net/vlan?


Here's a cat /proc/net/vlan/em1_1.538.  I attached it instead of 
pasting so you can get an exact copy with all the white space etc.




- Original Message -

From: Jeff Bailey bai...@cs.kent.edu
To: Alon Bar-Lev alo...@redhat.com
Cc: users@ovirt.org
Sent: Saturday, February 16, 2013 2:01:44 AM
Subject: Re: [Users] Host deployment on 3.2

On 2/15/2013 6:42 PM, Alon Bar-Lev wrote:

Can you please provide the relevant log from
/var/log/ovirt-engine/host-deploy?

Sure.  Here's the error and some bits around it.


- Original Message -

From: Jeff Bailey bai...@cs.kent.edu
To: users@ovirt.org
Sent: Saturday, February 16, 2013 1:29:44 AM
Subject: [Users] Host deployment on 3.2

I've hit a couple of small problems deploying an F18 minimal host
with
3.2.  The first problem was missing tar.  Second, I had manually
set
up
a vlan on the host for initial communication and the regular
expression
in bridge.py of the otopi plugin couldn't determine the vlan id.
   After
tweeking it a bit to make it similar to _RE_VLAN_DEVICE it was
fine.

---
 Jeff

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users





em1_1.538  VID: 538  REORDER_HDR: 1  dev-priv_flags: 1
 total frames received   469445
  total bytes received   6044333168
  Broadcast/Multicast Rcvd12437

  total frames transmitted   418744
   total bytes transmitted197589374
Device: em1_1
INGRESS priority mappings: 0:0  1:0  2:0  3:0  4:0  5:0  6:0 7:0
 EGRESS priority mappings: 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Host deployment on 3.2

[Jeff Bailey]

On 2/16/2013 3:53 AM, Alon Bar-Lev wrote:

Thanks!
Can you please check if the following fixes the problem?


Looks like that fixed it.  Thanks.


I can provide rpms if you like.

- Original Message -

From: Jeff Bailey bai...@cs.kent.edu
To: users@ovirt.org
Sent: Saturday, February 16, 2013 10:29:43 AM
Subject: Re: [Users] Host deployment on 3.2


On 2/16/2013 2:00 AM, Alon Bar-Lev wrote:

Can you please send the content of /proc/net/vlan?

Here's a cat /proc/net/vlan/em1_1.538.  I attached it instead of
pasting so you can get an exact copy with all the white space etc.


- Original Message -

From: Jeff Bailey bai...@cs.kent.edu
To: Alon Bar-Lev alo...@redhat.com
Cc: users@ovirt.org
Sent: Saturday, February 16, 2013 2:01:44 AM
Subject: Re: [Users] Host deployment on 3.2

On 2/15/2013 6:42 PM, Alon Bar-Lev wrote:

Can you please provide the relevant log from
/var/log/ovirt-engine/host-deploy?

Sure.  Here's the error and some bits around it.


- Original Message -

From: Jeff Bailey bai...@cs.kent.edu
To: users@ovirt.org
Sent: Saturday, February 16, 2013 1:29:44 AM
Subject: [Users] Host deployment on 3.2

I've hit a couple of small problems deploying an F18 minimal
host
with
3.2.  The first problem was missing tar.  Second, I had manually
set
up
a vlan on the host for initial communication and the regular
expression
in bridge.py of the otopi plugin couldn't determine the vlan id.
After
tweeking it a bit to make it similar to _RE_VLAN_DEVICE it was
fine.

---
  Jeff

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] Host deployment on 3.2

[Jeff Bailey]

I've hit a couple of small problems deploying an F18 minimal host with 
3.2.  The first problem was missing tar.  Second, I had manually set up 
a vlan on the host for initial communication and the regular expression 
in bridge.py of the otopi plugin couldn't determine the vlan id.  After 
tweeking it a bit to make it similar to _RE_VLAN_DEVICE it was fine.


---
  Jeff

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Host deployment on 3.2

[Jeff Bailey]

On 2/15/2013 6:42 PM, Alon Bar-Lev wrote:

Can you please provide the relevant log from /var/log/ovirt-engine/host-deploy?


Sure.  Here's the error and some bits around it.



- Original Message -

From: Jeff Bailey bai...@cs.kent.edu
To: users@ovirt.org
Sent: Saturday, February 16, 2013 1:29:44 AM
Subject: [Users] Host deployment on 3.2

I've hit a couple of small problems deploying an F18 minimal host
with
3.2.  The first problem was missing tar.  Second, I had manually set
up
a vlan on the host for initial communication and the regular
expression
in bridge.py of the otopi plugin couldn't determine the vlan id.
  After
tweeking it a bit to make it similar to _RE_VLAN_DEVICE it was fine.

---
Jeff

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



2013-02-15 14:57:13 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge 
bridge._waitForRoute:248 connect established ('131.123.38.29', 80)
2013-02-15 14:57:13 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge 
bridge._getInterfaceForDestination:302 determine interface for 131.123.38.29
2013-02-15 14:57:13 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge 
plugin.executeRaw:347 execute: ('/sbin/ip', 'route', 'get', 'to', 
'131.123.38.29'), executable='None', cwd='None', env=None
2013-02-15 14:57:13 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge 
plugin.executeRaw:364 execute-result: ('/sbin/ip', 'route', 'get', 'to', 
'131.123.38.29'), rc=0
2013-02-15 14:57:13 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge 
plugin.execute:411 execute-output: ('/sbin/ip', 'route', 'get', 'to', 
'131.123.38.29') stdout:
131.123.38.29 dev em1_1.538  src 131.123.38.20 
cache 

2013-02-15 14:57:13 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge 
plugin.execute:416 execute-output: ('/sbin/ip', 'route', 'get', 'to', 
'131.123.38.29') stderr:


2013-02-15 14:57:13 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge 
bridge._getInterfaceForDestination:337 interface for 131.123.38.29 is em1_1.538
2013-02-15 14:57:13 DEBUG otopi.context context._executeMethod:130 method 
exception
Traceback (most recent call last):
  File /tmp/ovirt-DyHo6SymCE/pythonlib/otopi/context.py, line 120, in 
_executeMethod
method['method']()
  File /tmp/ovirt-DyHo6SymCE/otopi-plugins/ovirt-host-deploy/vdsm/bridge.py, 
line 733, in _validation
self._getVlanMasterDevice(name=interface)
  File /tmp/ovirt-DyHo6SymCE/otopi-plugins/ovirt-host-deploy/vdsm/bridge.py, 
line 393, in _getVlanMasterDevice
interface=name,
RuntimeError: Interface em1_1.538 is VLAN interface However its configuration 
is unexpected
2013-02-15 14:57:13 ERROR otopi.context context._executeMethod:139 Failed to 
execute stage 'Setup validation': Interface em1_1.538 is VLAN interface However 
its configuration is unexpected
2013-02-15 14:57:13 DEBUG otopi.context context.dumpEnvironment:391 ENVIRONMENT 
DUMP - BEGIN
2013-02-15 14:57:13 DEBUG otopi.context context.dumpEnvironment:401 ENV 
BASE/error=bool:'True'
2013-02-15 14:57:13 DEBUG otopi.context context.dumpEnvironment:401 ENV 
VDSM/engineAddress=str:'131.123.38.29'
2013-02-15 14:57:13 DEBUG otopi.context context.dumpEnvironment:403 ENVIRONMENT 
DUMP - END
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] F18 iSCSI/FC and latest systemd/udev

[Jeff Bailey]

While not an actual problem with oVirt, the latest systemd/udev packages 
for F18 (197-1) break permissions on LVM volumes and stop vdsm/qemu/etc 
from accessing them.  I just downgraded them and everything seems OK but 
I thought I'd let people know (easier to just avoid rather than repair 
:) ).  There's a bugzilla for it from a week or two ago but since 3.2 
came out I figured a lot more people might be installing it on new F18 
installations with all the updates and running into problems.


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] oVirt 3.2 -- Now Available

[Jeff Bailey]

There seems to be an awful lot of open bugs left in 
https://bugzilla.redhat.com/show_bug.cgi?id=881006 :)


The real reason for this message though is conflicts between the 
ovirt-engine-cli and ovirt-engine-sdk packages in the F18 repo. Plus, I 
don't see an ovirt-engine-sdk in the 3.2 stable repo.  The F18 repo 
problem could just be lag in the mirroring but shouldn't there be an sdk 
rpm in the 3.2 repo?  Oh, by F18 repo I mean the official fedora/updates 
repos not the fedora 18 portion of the ovirt repos.


On 2/14/2013 3:10 PM, Mike Burns wrote:

The oVirt Team is pleased to announce that oVirt 3.2 is now available.

There are a number of exciting new features in 3.2 [1].

Some of the highlights include:

* UI Plugins
* Port Mirroring
* Networks as a top level Configuration
* Japanese Localization
* Storage Live Migration
* Improved Gluster Integration
* oVirt Node TUI Redesign
* Node Plugins

A Quick Start is available on the Wiki [2]

Packages are currently available for Fedora 18 [3], with EL6 packages 
coming soon.


Please see our Release Notes[4] for additional information

If you run into any problems or need help, people are available on 
#ovirt on OFTC and users@ovirt.org


Thanks

The oVirt Team


[1] http://www.ovirt.org/OVirt_3.2_release-management#Features
[2] http://www.ovirt.org/Quick_Start_Guide
[3] http://resources.ovirt.org/releases/stable/rpm/Fedora/18/
[4] http://www.ovirt.org/OVirt_3.2_release_notes
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] oVirt 3.2 -- Now Available

[Jeff Bailey]

On 2/14/2013 6:00 PM, Jeff Bailey wrote:
There seems to be an awful lot of open bugs left in 
https://bugzilla.redhat.com/show_bug.cgi?id=881006 :)


The real reason for this message though is conflicts between the 
ovirt-engine-cli and ovirt-engine-sdk packages in the F18 repo. Plus, 
I don't see an ovirt-engine-sdk in the 3.2 stable repo.  The F18 repo 


Poking a bit more I see that there are new versions of the sdk and cli 
in the updates-testing repo.  Until those make it through it looks like 
a simple yum install ovirt-engine won't work.  If those rpms (or 
something newer) were included in the ovirt 3.2 repo then that should 
cover the dependencies until things get out of testing. Separately 
installing the sdk/cli from updates-testing and then installing engine 
without enabling the test repo looks OK.


problem could just be lag in the mirroring but shouldn't there be an 
sdk rpm in the 3.2 repo?  Oh, by F18 repo I mean the official 
fedora/updates repos not the fedora 18 portion of the ovirt repos.


On 2/14/2013 3:10 PM, Mike Burns wrote:

The oVirt Team is pleased to announce that oVirt 3.2 is now available.

There are a number of exciting new features in 3.2 [1].

Some of the highlights include:

* UI Plugins
* Port Mirroring
* Networks as a top level Configuration
* Japanese Localization
* Storage Live Migration
* Improved Gluster Integration
* oVirt Node TUI Redesign
* Node Plugins

A Quick Start is available on the Wiki [2]

Packages are currently available for Fedora 18 [3], with EL6 packages 
coming soon.


Please see our Release Notes[4] for additional information

If you run into any problems or need help, people are available on 
#ovirt on OFTC and users@ovirt.org


Thanks

The oVirt Team


[1] http://www.ovirt.org/OVirt_3.2_release-management#Features
[2] http://www.ovirt.org/Quick_Start_Guide
[3] http://resources.ovirt.org/releases/stable/rpm/Fedora/18/
[4] http://www.ovirt.org/OVirt_3.2_release_notes
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] oVirt 3.2 -- Now Available

[Jeff Bailey]

On 2/14/2013 6:21 PM, Mike Burns wrote:

On 02/14/2013 06:00 PM, Jeff Bailey wrote:

There seems to be an awful lot of open bugs left in
https://bugzilla.redhat.com/show_bug.cgi?id=881006 :)


Yes, we need to go through and clean that up.  I think they all got 
in, but in the effort to get it out -- well, i wasn't very diligent in 
making sure the tracker was clear.




The real reason for this message though is conflicts between the
ovirt-engine-cli and ovirt-engine-sdk packages in the F18 repo. Plus, I
don't see an ovirt-engine-sdk in the 3.2 stable repo.  The F18 repo
problem could just be lag in the mirroring but shouldn't there be an sdk
rpm in the 3.2 repo?  Oh, by F18 repo I mean the official fedora/updates
repos not the fedora 18 portion of the ovirt repos.


Hmm...I wasn't aware I missed the sdk rpms in the 3.2 repo. Thanks for 
letting me know.  I've copied what was in the beta repo for the 
ovirt-engine-sdk into the standard 3.2 repo, though I don't know if 
that will work or not since it's a different NVR than the cli there.  
I'll follow up with the maintainer to confirm the right package versions.


As for the rpms in the official Fedora repos, they're still ovirt 3.1 
rpms (and functionally crippled ovirt 3.1 rpms at that).  I hope to 
get the maintainers to solve this problem in the near future, but 
getting things through the fedora review process and koji takes time.




At least the ones in updates-testing claim to be 3.2.0.  The cli in just 
plain updates has a newer version than the cli in the ovirt 3.2 repo.  
If they're actually older then I can see some problems coming :)



Thanks

Mike


On 2/14/2013 3:10 PM, Mike Burns wrote:

The oVirt Team is pleased to announce that oVirt 3.2 is now available.

There are a number of exciting new features in 3.2 [1].

Some of the highlights include:

* UI Plugins
* Port Mirroring
* Networks as a top level Configuration
* Japanese Localization
* Storage Live Migration
* Improved Gluster Integration
* oVirt Node TUI Redesign
* Node Plugins

A Quick Start is available on the Wiki [2]

Packages are currently available for Fedora 18 [3], with EL6 packages
coming soon.

Please see our Release Notes[4] for additional information

If you run into any problems or need help, people are available on
#ovirt on OFTC and users@ovirt.org

Thanks

The oVirt Team


[1] http://www.ovirt.org/OVirt_3.2_release-management#Features
[2] http://www.ovirt.org/Quick_Start_Guide
[3] http://resources.ovirt.org/releases/stable/rpm/Fedora/18/
[4] http://www.ovirt.org/OVirt_3.2_release_notes
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] oVirt node install hanging on admin login prompt

[Jeff Bailey]

On 1/15/2013 3:31 AM, Nicolas Ecarnot wrote:

Le 14/01/2013 22:24, Jeff Bailey a écrit :

On 1/14/2013 9:08 AM, Nicolas Ecarnot wrote:

Hi,

I'm trying to install oVirt node 2.5.5-0.1.fc17 and it is node going
well. I'm trying to install it on a Dell blade M610 via a iDrac, and
I'm quit accustomed to this kind of thing.

- As I already had the issue of the label on the grub boot line, I
knew how to specify /dev/sr0 or sr1 on the linux line. Well.
- The install is ok with discovering my hard drive, and the
installation seems to be fine. After rebooting, the bott process is
leading me to the login prompt where the documentation tells me to log
as 'admin' with the correct password :

The keyboard is not responding, I can not even type the user name.


Try adding usbcore.autosuspend=-1 to the kernel command line. I've had
problems with iDRAC 7 virtual consoles with both Fedora 17 and 18 and
this fixes it.  I don't know about iDRAC 6 but trying it couldn't hurt
:)  Getting the machine to always boot with that option could be a bit
tricky with Node.  I'm not sure if you'll just be able to edit the
grub.conf and persist it or not.


Thank you very much, Jeff, this did the trick !


You're welcome!  I know that suddenly losing console access to your 
blades can be a bit distressing :)


And better than that : adding it on the first use in the kernel line 
leads it to be permanently added in the grub conf even after a reboot.




That's very nice to know.  I was afraid it would be tricky with Node but 
I guess it isn't.



Nice !



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] oVirt node install hanging on admin login prompt

[Jeff Bailey]

On 1/14/2013 9:08 AM, Nicolas Ecarnot wrote:

Hi,

I'm trying to install oVirt node 2.5.5-0.1.fc17 and it is node going 
well. I'm trying to install it on a Dell blade M610 via a iDrac, and 
I'm quit accustomed to this kind of thing.


- As I already had the issue of the label on the grub boot line, I 
knew how to specify /dev/sr0 or sr1 on the linux line. Well.
- The install is ok with discovering my hard drive, and the 
installation seems to be fine. After rebooting, the bott process is 
leading me to the login prompt where the documentation tells me to log 
as 'admin' with the correct password :


The keyboard is not responding, I can not even type the user name.


Try adding usbcore.autosuspend=-1 to the kernel command line.  I've had 
problems with iDRAC 7 virtual consoles with both Fedora 17 and 18 and 
this fixes it.  I don't know about iDRAC 6 but trying it couldn't hurt 
:)  Getting the machine to always boot with that option could be a bit 
tricky with Node.  I'm not sure if you'll just be able to edit the 
grub.conf and persist it or not.



I can't change of console, no network activity is seen.
There does not seem to be a kernel panic, as some additional log lines 
are displayed (about the creation of bond interfaces).


I also see some more lines about systemd-readahead-collect : failed 
to open pack file: read-only file system...


When downloading the iso install file from the oVirt repo, I choosed 
the smalest one, not the live one. Did I did wrong?


Anyway, now, what are my options?



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] ovirt 3.2 migrations failing

[Jeff Bailey]

I don't know any details about the dreyou version you're running but 
look in the libvirtd log on the source host and see if there is a 
complaint about a missing CA cert.  That problem existed in the 3.2 
alpha but should have been fixed in the nightlies.  I don't know whether 
it made it to the version you're running.  It could also be something 
totally different :)


---
Jeff

On 1/9/2013 8:54 AM, Jonathan Horne wrote:

from source:

[root@d0lppn032 vdsm]# egrep 'Thread-30209|Thread-30210'
/var/log/vdsm/vdsm.log
Thread-30209::DEBUG::2013-01-09
07:49:08,543::BindingXMLRPC::908::vds::(wrapper) client [10.32.0.21]::call
vmMigrate with ({'src': 'd0lppn032.skopos.me', 'dst':
'd0lppn031.skopos.me:54321', 'vmId':
'e00adf83-78d2-4f65-a259-0e01680f57fd', 'method': 'online'},) {} flowID
[343d5f4c]
Thread-30209::DEBUG::2013-01-09 07:49:08,543::API::435::vds::(migrate)
{'src': 'd0lppn032.skopos.me', 'dst': 'd0lppn031.skopos.me:54321', 'vmId':
'e00adf83-78d2-4f65-a259-0e01680f57fd', 'method': 'online'}
Thread-30210::DEBUG::2013-01-09
07:49:08,544::vm::139::vm.Vm::(_setupVdsConnection)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::Destination server is:
d0lppn031.skopos.me:54321
Thread-30210::DEBUG::2013-01-09
07:49:08,545::vm::141::vm.Vm::(_setupVdsConnection)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::Initiating connection with
destination
Thread-30209::DEBUG::2013-01-09
07:49:08,545::BindingXMLRPC::915::vds::(wrapper) return vmMigrate with
{'status': {'message': 'Migration process starting', 'code': 0}}
Thread-30210::DEBUG::2013-01-09
07:49:08,614::libvirtvm::298::vm.Vm::(_getDiskLatency)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::Disk vda latency not available
Thread-30210::DEBUG::2013-01-09
07:49:08,659::vm::190::vm.Vm::(_prepareGuest)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::migration Process begins
Thread-30210::DEBUG::2013-01-09 07:49:08,751::vm::261::vm.Vm::(run)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::migration semaphore acquired
Thread-30210::DEBUG::2013-01-09
07:49:09,168::libvirtvm::469::vm.Vm::(_startUnderlyingMigration)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::starting migration to
qemu+tls://d0lppn031.skopos.me/system
Thread-30210::DEBUG::2013-01-09
07:49:09,230::libvirtvm::370::vm.Vm::(cancel)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::canceling migration downtime
thread
Thread-30210::DEBUG::2013-01-09
07:49:09,231::libvirtvm::429::vm.Vm::(stop)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::stopping migration monitor
thread
Thread-30210::ERROR::2013-01-09 07:49:09,232::vm::196::vm.Vm::(_recover)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::operation failed: Failed to
connect to remote libvirt URI qemu+tls://d0lppn031.skopos.me/system
Thread-30210::ERROR::2013-01-09 07:49:09,374::vm::284::vm.Vm::(run)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::Failed to migrate



and from destination:

[root@d0lppn031 vdsm]# egrep 'Thread-40128|Thread-40129'
/var/log/vdsm/vdsm.log
Thread-40128::DEBUG::2013-01-09
07:49:08,943::BindingXMLRPC::908::vds::(wrapper) client [10.32.0.32]::call
vmMigrationCreate with ({'username': 'root', 'acpiEnable': 'true',
'emulatedMachine': 'pc', 'afterMigrationStatus': 'Up', 'vmId':
'e00adf83-78d2-4f65-a259-0e01680f57fd', 'transparentHugePages': 'true',
'displaySecurePort': '5901', 'timeOffset': 1, 'cpuType': 'SandyBridge',
'custom': {}, 'migrationDest': 'libvirt', 'smp': '4', 'vmType': 'kvm',
'spiceSslCipherSuite': 'DEFAULT', '_srcDomXML': domain type='kvm'
id='2'\n  named0lpvf051/name\n
uuide00adf83-78d2-4f65-a259-0e01680f57fd/uuid\n  memory
unit='KiB'4194304/memory\n  currentMemory
unit='KiB'4194304/currentMemory\n  vcpu placement='static'4/vcpu\n
cputune\nshares1020/shares\n  /cputune\n  sysinfo
type='smbios'\nsystem\n  entry
name='manufacturer'oVirt/entry\n  entry name='product'oVirt
Node/entry\n  entry name='version'6-3.el6.centos.9/entry\n
entry name='serial'4C4C4544-004D-4E10-8036-B3C04F575731/entry\n
entry name='uuid'e00adf83-78d2-4f65-a259-0e01680f57fd/entry\n
/system\n  /sysinfo\n  os\ntype arch='x86_64'
machine='rhel6.3.0'hvm/type\nboot dev='hd'/\nsmbios
mode='sysinfo'/\n  /os\n  features\nacpi/\n  /features\n
cpu mode='custom' match='exact'\nmodel
fallback='allow'SandyBridge/model\ntopology sockets='4' cores='1'
threads='1'/\n  /cpu\n  clock offset='variable' adjustment='1'\n
timer name='rtc' tickpolicy='catchup'/\n  /clock\n
on_poweroffdestroy/on_poweroff\n  on_rebootrestart/on_reboot\n
on_crashdestroy/on_crash\n  devices\n
emulator/usr/libexec/qemu-kvm/emulator\ndisk type='file'
device='cdrom'\n  driver name='qemu' type='raw'/\n  source
startupPolicy='optional'/\n  target dev='hdc' bus='ide'/\n
readonly/\n  serial/serial\n  alias name='ide0-1-0'/\n
  address type='drive' controller='0' bus='1' target='0' unit='0'/\n
/disk\ndisk type='block' device='disk' snapshot='no'\n
driver name='qemu' type='qcow2' cache='none' error_policy='stop'
io='native'/\n  source

Re: [Users] ovirt 3.2 migrations failing

[Jeff Bailey]

On 1/9/2013 5:52 PM, Jonathan Horne wrote:

yep, sure enough:


[root@d0lppn032 ~]# cat /var/log/libvirtd.log|grep CA
2013-01-09 22:45:30.310+: 4413: error :
virNetTLSContextCheckCertFile:92 : Cannot read CA certificate
'/etc/pki/CA/cacert.pem': No such file or directory
[root@d0lppn032 ~]# locate cacert.pem
/etc/pki/vdsm/certs/cacert.pem


I just installed symbolic links for the CA cert and the client cert and 
key to the vdsm certs/key on the hosts and everything was fine then.


---
Jeff



is there a config file somewhere i can edit and hopefully get this working?




On 1/9/13 4:39 PM, Jeff Bailey bai...@cs.kent.edu wrote:


I don't know any details about the dreyou version you're running but
look in the libvirtd log on the source host and see if there is a
complaint about a missing CA cert.  That problem existed in the 3.2
alpha but should have been fixed in the nightlies.  I don't know whether
it made it to the version you're running.  It could also be something
totally different :)

---
Jeff

On 1/9/2013 8:54 AM, Jonathan Horne wrote:

from source:

[root@d0lppn032 vdsm]# egrep 'Thread-30209|Thread-30210'
/var/log/vdsm/vdsm.log
Thread-30209::DEBUG::2013-01-09
07:49:08,543::BindingXMLRPC::908::vds::(wrapper) client
[10.32.0.21]::call
vmMigrate with ({'src': 'd0lppn032.skopos.me', 'dst':
'd0lppn031.skopos.me:54321', 'vmId':
'e00adf83-78d2-4f65-a259-0e01680f57fd', 'method': 'online'},) {} flowID
[343d5f4c]
Thread-30209::DEBUG::2013-01-09 07:49:08,543::API::435::vds::(migrate)
{'src': 'd0lppn032.skopos.me', 'dst': 'd0lppn031.skopos.me:54321',
'vmId':
'e00adf83-78d2-4f65-a259-0e01680f57fd', 'method': 'online'}
Thread-30210::DEBUG::2013-01-09
07:49:08,544::vm::139::vm.Vm::(_setupVdsConnection)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::Destination server is:
d0lppn031.skopos.me:54321
Thread-30210::DEBUG::2013-01-09
07:49:08,545::vm::141::vm.Vm::(_setupVdsConnection)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::Initiating connection with
destination
Thread-30209::DEBUG::2013-01-09
07:49:08,545::BindingXMLRPC::915::vds::(wrapper) return vmMigrate with
{'status': {'message': 'Migration process starting', 'code': 0}}
Thread-30210::DEBUG::2013-01-09
07:49:08,614::libvirtvm::298::vm.Vm::(_getDiskLatency)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::Disk vda latency not
available
Thread-30210::DEBUG::2013-01-09
07:49:08,659::vm::190::vm.Vm::(_prepareGuest)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::migration Process begins
Thread-30210::DEBUG::2013-01-09 07:49:08,751::vm::261::vm.Vm::(run)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::migration semaphore
acquired
Thread-30210::DEBUG::2013-01-09
07:49:09,168::libvirtvm::469::vm.Vm::(_startUnderlyingMigration)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::starting migration to
qemu+tls://d0lppn031.skopos.me/system
Thread-30210::DEBUG::2013-01-09
07:49:09,230::libvirtvm::370::vm.Vm::(cancel)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::canceling migration
downtime
thread
Thread-30210::DEBUG::2013-01-09
07:49:09,231::libvirtvm::429::vm.Vm::(stop)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::stopping migration monitor
thread
Thread-30210::ERROR::2013-01-09 07:49:09,232::vm::196::vm.Vm::(_recover)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::operation failed: Failed to
connect to remote libvirt URI qemu+tls://d0lppn031.skopos.me/system
Thread-30210::ERROR::2013-01-09 07:49:09,374::vm::284::vm.Vm::(run)
vmId=`e00adf83-78d2-4f65-a259-0e01680f57fd`::Failed to migrate



and from destination:

[root@d0lppn031 vdsm]# egrep 'Thread-40128|Thread-40129'
/var/log/vdsm/vdsm.log
Thread-40128::DEBUG::2013-01-09
07:49:08,943::BindingXMLRPC::908::vds::(wrapper) client
[10.32.0.32]::call
vmMigrationCreate with ({'username': 'root', 'acpiEnable': 'true',
'emulatedMachine': 'pc', 'afterMigrationStatus': 'Up', 'vmId':
'e00adf83-78d2-4f65-a259-0e01680f57fd', 'transparentHugePages': 'true',
'displaySecurePort': '5901', 'timeOffset': 1, 'cpuType': 'SandyBridge',
'custom': {}, 'migrationDest': 'libvirt', 'smp': '4', 'vmType': 'kvm',
'spiceSslCipherSuite': 'DEFAULT', '_srcDomXML': domain type='kvm'
id='2'\n  named0lpvf051/name\n
uuide00adf83-78d2-4f65-a259-0e01680f57fd/uuid\n  memory
unit='KiB'4194304/memory\n  currentMemory
unit='KiB'4194304/currentMemory\n  vcpu
placement='static'4/vcpu\n
cputune\nshares1020/shares\n  /cputune\n  sysinfo
type='smbios'\nsystem\n  entry
name='manufacturer'oVirt/entry\n  entry name='product'oVirt
Node/entry\n  entry name='version'6-3.el6.centos.9/entry\n
entry name='serial'4C4C4544-004D-4E10-8036-B3C04F575731/entry\n
entry name='uuid'e00adf83-78d2-4f65-a259-0e01680f57fd/entry\n
/system\n  /sysinfo\n  os\ntype arch='x86_64'
machine='rhel6.3.0'hvm/type\nboot dev='hd'/\nsmbios
mode='sysinfo'/\n  /os\n  features\nacpi/\n  /features\n
cpu mode='custom' match='exact'\nmodel
fallback='allow'SandyBridge/model\ntopology sockets='4'
cores='1'
threads='1'/\n  /cpu\n  clock offset='variable' adjustment='1'\n
timer

Re: [Users] ovirt reporting wrong cpu family

[Jeff Bailey]

On 1/2/2013 3:33 PM, Itamar Heim wrote:

On 01/02/2013 03:37 PM, Jithin Raju wrote:

Hi,

I have installed ovirt 3.1 on fedora 17.
I added my node wtih intel E5-2620 (sandy bridge) to cluster.
Even though model is detected properly,CPU name is shown as Intel Conroe
family instead of sandy bridge.
Since my cluster is configured as sandy bridge i got this error:

Host fig moved to Non-Operational state as host does not meet the
cluster's minimum CPU level. Missing CPU features : model_SandyBridge.



I had a similar problem with 3.1 and E5-2670's.  The 3.2 alpha works 
fine though.


as per cpuinfo :model name  : Intel(R) Xeon(R) CPU E5-2620 0 @ 
2.00GHz.


i moved the cluster to conroe ,got the host up.

reference:
http://en.wikipedia.org/wiki/Sandy_Bridge_(microarchitecture)
http://ark.intel.com/products/64594

PFA for screenshot.

Thanks,
Jithin


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



please share vdsClient -s 0 getVdsCaps | grep -i flags from the host

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] tagged vs untagged and sharing the interface

[Jeff Bailey]

On 12/28/2012 3:25 PM, Jonathan Horne wrote:

ok, i started over on my ovirt cluster here.  now that i have built a new
data center and modified my ovirtmgmt network (to be tagged as vlan 3200),
if i try to edit the interface to create a bond, ovirtmgmt does not move
to the right side so i can reassign it to the new bond interface, it
disappears all together.

so then i cancel.  i go back into the edit host networks window, and this
time i just assign my iscsi vlan to the other interface, check for static
on both, and then  click ok.  but ovirt deletes the ovirtmgmt interface
off the node and i lose the node from the network.

very strange the the ovirtmgmt network disappears :(


I have not tried any bonding.  What version are you running?  I don't 
think I've ever actually tried to configure the ovirtmgmt network with 
the GUI.  I would assume that it's supposed to work but I can't confirm 
that.  I either manually configure it the way I want it on a plain 
Fedora install or use the TUI on initial Node setup. I know there have 
been fixes between 3.1 and the 3.2 alpha (3.1 just didn't work for me at 
all).  Perhaps there were bonding problems that have been corrected.  If 
you can, you might want to hang on to the logs (engine and vdsm) from 
the time you tried to change the network config.


On 12/27/12 5:42 PM, Jeff Bailey bai...@cs.kent.edu wrote:

On 12/27/2012 6:10 PM, Jonathan Horne wrote:

On 12/27/12 2:57 PM, Jeff Bailey bai...@cs.kent.edu wrote:


On 12/27/2012 3:01 PM, Jonathan Horne wrote:

if someone could help me confirm, but it appear that i cannot
co-populate tagged vlan on the same interface as ovirtmgmt?

You can but you need to edit the ovirtmgmt network to make it tagged
before adding a cluster to the datacenter.

It tells me cannot edit management network.

If there is already a cluster attached to the datacenter then you can't
edit the ovirtmgmt network.  You may be able to create another temporary
datecenter, move your cluster, edit the network and then move the
cluster back.  If you edit the network before adding a cluster and hosts
then it's easier.  I'm not sure you'll be able to move the cluster
though.  I haven't tried that.  If you can't then you'll probably have
to remove the hosts and cluster and add them back afterwards.  There has
been recent discussion about improving this situation so in the future
this may not be a problem.


for me it would really be better if i can share these 2 on same
interface, but if i can't ill just have to live with it.

can any one confirm this?

thanks,
jonathan


---
-
This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. NOTE: Regardless of content, this e-mail shall
not operate to bind SKOPOS to any order or other contract unless
pursuant to explicit written agreement or government initiative
expressly permitting the use of e-mail for such purpose.


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. NOTE: Regardless of content, this e-mail shall not
operate to bind SKOPOS to any order or other contract unless pursuant to
explicit written agreement or government initiative expressly permitting
the use of e-mail for such purpose.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



This is a PRIVATE message. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to 
any order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] tagged vs untagged and sharing the interface

[Jeff Bailey]

On 12/27/2012 6:10 PM, Jonathan Horne wrote:

On 12/27/12 2:57 PM, Jeff Bailey bai...@cs.kent.edu wrote:


On 12/27/2012 3:01 PM, Jonathan Horne wrote:

if someone could help me confirm, but it appear that i cannot
co-populate tagged vlan on the same interface as ovirtmgmt?

You can but you need to edit the ovirtmgmt network to make it tagged
before adding a cluster to the datacenter.

It tells me cannot edit management network.


If there is already a cluster attached to the datacenter then you can't 
edit the ovirtmgmt network.  You may be able to create another temporary 
datecenter, move your cluster, edit the network and then move the 
cluster back.  If you edit the network before adding a cluster and hosts 
then it's easier.  I'm not sure you'll be able to move the cluster 
though.  I haven't tried that.  If you can't then you'll probably have 
to remove the hosts and cluster and add them back afterwards.  There has 
been recent discussion about improving this situation so in the future 
this may not be a problem.



for me it would really be better if i can share these 2 on same
interface, but if i can't ill just have to live with it.

can any one confirm this?

thanks,
jonathan


This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. NOTE: Regardless of content, this e-mail shall
not operate to bind SKOPOS to any order or other contract unless
pursuant to explicit written agreement or government initiative
expressly permitting the use of e-mail for such purpose.


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



This is a PRIVATE message. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to 
any order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] Report size of thin provisioned disk

[Jeff Bailey]

With 3.2 alpha, on the disks subtab of the virtual machines tab I'm 
seeing the correct virtual size for the disk but the actual size 
remains 1GB even though the drive has grown to 11GB (according to lvs 
output).  It doesn't seem to be causing any problems.  The auto-growth 
(from my perspective) is working much smoother than it did a release ago 
:)  I just wondered if anyone else had noticed this.


Thanks,
  Jeff

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] Testing ovirt all in one on F18 gives error on DB creation

[Jeff Bailey]

On 12/18/2012 9:46 AM, Gianluca Cecchi wrote:

On Wed, Dec 12, 2012 at 11:29 PM, Jason Brooks wrote:


the same if I run from command line:
/sbin/tuned-adm profile virtual-host
 
 
  I was having this same issue w/ F18 w/ all updates applied and
  ovirt
  3.2 from the new 3.2-alpha repo. I did a yum downgrade tuned and
  the install completed successfully.
 
  Now I just have to figure out why my host is non-operational...
 
  Jason

 I suggest you perform host deployment again.

Thanks, that worked. The ovirtmgmt bridge wasn't created the first
time around, now I'm up.


Hello,  had again time to come back on this today.
So I updated my f18 vm with ovirt-nightly repo and then engine-cleanup 
and engine-setup again.

and I got the usual error on timeout when first deploying host.

But I'm able to connect from my host to webadmin portal on my vm (f18aio)
After downgrade of tuned-adm it worked for me too the re-deploy of the 
host from the gui.




The tuned-adm problem is selinux related.  If you set selinux to 
permissive before the host deploy it will work fine using 
tuned-2.1.1-1.fc18.noarch.



from
Dec 11 00:58:09 Updated: tuned-2.1.1-1.fc18.noarch

to
Dec 18 13:00:14 Installed: tuned-2.0.1-4.fc18.noarch

I think it was the deploy step that caused also the vm (oVirt node 
deployed from itself...) to restart.

And now I have this situation I would like to fix:

my vm is f18aio with ip 192.1681.122.160
On my f17 host I have in /etc/hosts
192.168.122.160 f18aio.localdomain.local f18aio

so that dnsmask lets me use firefox on host to connect to webadmin 
portal on vm
But after the successful deploy I'm not able anymore to connect 
correctly as before to admin portal


From host:

http://f18aio --- ok

click on webadmin portal link ---  ko
Firefox can't establish a connection to the server at f18aio.

http://192.168.122.160 -- ko
Firefox can't establish a connection to the server at 192.168.122.160

If I ssh -X f18aio from host and run firefox on vm side:

http://f18aio --- ok

click on webadmin portal link ---  ok
(see screenshot at
https://docs.google.com/open?id=0BwoPbcrMv8mvZzdsQnFMU0RuUGs
)

The same if I use 192.168.122.160


DO I have to set up anything at vm side of my host side?
At this moment on it I see I have the ip address put on ovirtmgmt 
network that the deploy step made available:


[g.cecchi@f18aio ~]$ ip addr list
1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 http://127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast 
master ovirtmgmt state UP qlen 1000

link/ether 52:54:00:b0:6c:5f brd ff:ff:ff:ff:ff:ff
inet6 fe80::5054:ff:feb0:6c5f/64 scope link
   valid_lft forever preferred_lft forever
3: ovirtmgmt: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue 
state UP

link/ether 52:54:00:b0:6c:5f brd ff:ff:ff:ff:ff:ff
inet 192.168.122.160/24 http://192.168.122.160/24 brd 
192.168.122.255 scope global ovirtmgmt

inet6 fe80::5054:ff:feb0:6c5f/64 scope link
   valid_lft forever preferred_lft forever
5: ;vdsmdummy;: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN
link/ether 06:95:56:60:84:1a brd ff:ff:ff:ff:ff:ff
6: bond0: NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP mtu 1500 qdisc 
noqueue state DOWN

link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
7: bond4: NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP mtu 1500 qdisc 
noqueue state DOWN

link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

[g.cecchi@f18aio ~]$ cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: load balancing (round-robin)
MII Status: down
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0

[g.cecchi@f18aio ~]$ cat /proc/net/bonding/bond4
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: load balancing (round-robin)
MII Status: down
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0

[root@f18aio ~]# brctl show
bridge namebridge idSTP enabledinterfaces
;vdsmdummy;8000.no
ovirtmgmt8000.525400b06c5fnoeth0


Thanks in advance,
Gianluca



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] migration missing cert - 3.2 alpha

[Jeff Bailey]

Hi,

I have an F18 Beta + oVirt 3.2 alpha setup with two hosts.  When I try 
to migrate from one host to the other I get


2012-12-15 15:18:51.381+: 1541: error : 
virNetTLSContextCheckCertFile:113 :
Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or 
directory


in libvirtd.log on the source host.  Is that actually where the cert 
should be and I should try to track down why it's not there or should it 
be somewhere else?  If it should be somewhere else where would that be 
configured?  The default location for the client certificates seems to 
be /etc/pki/libvirt which doesn't exist so even with a cacert it still 
probably wouldn't work.  Could this be related to the missing spice 
certificates (I manually made the symbolic links for those).


Thanks,
  Jeff

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] migration missing cert - 3.2 alpha

[Jeff Bailey]

On 12/15/2012 1:49 PM, Alon Bar-Lev wrote:


- Original Message -

From: Jeff Bailey bai...@cs.kent.edu
To: users@ovirt.org
Sent: Saturday, December 15, 2012 6:28:20 PM
Subject: [Users] migration  missing cert - 3.2 alpha

Hi,

I have an F18 Beta + oVirt 3.2 alpha setup with two hosts.  When I
try
to migrate from one host to the other I get

2012-12-15 15:18:51.381+: 1541: error :
virNetTLSContextCheckCertFile:113 :
Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or
directory

in libvirtd.log on the source host.  Is that actually where the cert
should be and I should try to track down why it's not there or should
it
be somewhere else?  If it should be somewhere else where would that
be
configured?  The default location for the client certificates seems
to
be /etc/pki/libvirt which doesn't exist so even with a cacert it
still
probably wouldn't work.  Could this be related to the missing spice
certificates (I manually made the symbolic links for those).

Thanks,
Jeff

This is interesting...

What do you have in both machines at /etc/libvirt/libvirtd.conf in ca_file, 
cert_file, key_file?


In /etc/libvirt/libvirtd.conf on both hosts:

ca_file=/etc/pki/vdsm/certs/cacert.pem
cert_file=/etc/pki/vdsm/certs/vdsmcert.pem
key_file=/etc/pki/vdsm/keys/vdsmkey.pem

It looks like it pulled libvirt-0.10.2.2-1.fc18.x86_64 from the F18 
updates-testing repository.  Maybe that's the problem.  I'll try to 
install a clean F18 beta with the updates-testing repo disabled.



As as far as I seen these variables set to /etc/pki/vdsm/*, I did not duplicate 
these files to libvirtd.

I would like to understand why the default libvirt setting are in effect.

Regards,
Alon


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] glusterfs and ovirt

[Jeff Bailey]

On 5/17/2012 1:35 PM, Itamar Heim wrote:

On 05/17/2012 06:55 PM, Bharata B Rao wrote:

On Wed, May 16, 2012 at 3:29 PM, Itamar Heimih...@redhat.com  wrote:

On 05/15/2012 07:35 PM, Andrei Vakhnin wrote:


Yair

Thanks for an update. Can I have KVM hypervisors also function as 
storage
nodes for glusterfs? What is a release date for glusterfs support? 
We're

looking for a production deployment in June. Thanks



current status is
1. patches for provisioning gluster clusters and volumes via ovirt 
are in

review, trying to cover this feature set [1].
I'm not sure if all of them will make the ovirt 3.1 version which is 
slated

to branch for stabilization June 1st, but i think enough is there.
so i'd start trying current upstream version to help find issues 
blocking
you, and following on them during june as we stabilize ovirt 3.1 for 
release

(planned for end of june).

2. you should be able to use same hosts for both gluster and virt, 
but there

is no special logic/handling for this yet (i.e., trying and providing
feedback would help improve this mode).
I would suggest start from separate clusters though first, and only 
later

trying the joint mode.

3. creating a storage domain on top of gluster:
- expose NFS on top of it, and consume as a normal nfs storage domain
- use posixfs storage domain with gluster mount semantics
- future: probably native gluster storage domain, up to native
  integration with qemu


I am looking at GlusterFS integration with QEMU which involves adding
GlusterFS as block backend in QEMU. This will involve QEMU talking to
gluster directly via libglusterfs bypassing FUSE. I could specify a
volume file and the VM image directly on QEMU command line to boot
from the VM image that resides on a gluster volume.

Eg: qemu -drive file=client.vol:/Fedora.img,format=gluster

In this example, Fedora.img is being served by gluster and client.vol
would have client-side translators specified.

I am not sure if this use case would be served if GlusterFS is
integrated as posixfs storage domain in VDSM. Posixfs would involve
normal FUSE mount and QEMU would be required to work with images from
FUSE mount path ?

With QEMU supporting GlusterFS backend natively, further optimizations
are possible in case of gluster volume being local to the host node.
In this case, one could provide QEMU with a simple volume file that
would not contain client or server xlators, but instead just the posix
xlator. This would lead to most optimal IO path that bypasses RPC
calls.

So do you think, this use case (QEMU supporting GlusterFS backend
natively and using volume file to specify the needed translators)
warrants a specialized storage domain type for GlusterFS in VDSM ?


I'm not sure if a special storage domain, or a PosixFS based domain 
with enhanced capabilities.

Ayal?


Direct qemu support for gluster is similar to ceph rbd/rados object 
storage which is also supported in qemu.  A domain type which can handle 
object based storage of this sort would be very nice.



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users