Nightly builds of vdsm in jenkins need NVR bump
by mburns@redhat.com
Hi Dan, Federico,
I noticed that the current jenkins builds of vdsm have an NVR like
vdsm-4.10.3-0.xxxxxx while the current stable version is
4.10.3-10.xxxxx. This means that someone testing nightly builds for
oVirt 3.3 will always get the stable version from either ovirt.org or
Fedora repos, and not the nightly build.
I would submit a patch to increase the NVR, but I don't know which
change is the right one (vdsm-4.10.4 or vdsm-4.11.0 or vdsm-5.0.0).
Mike
11 years, 1 month
How to figure out the transport type of Gluster volume from VDSM host (which is not a gluster peer) ?
by deepakcs@linux.vnet.ibm.com
Hi Lists,
I am looking at options to figure the transport type of a gluster
volume (given the volfileserver:volname) from a host that is *not* part
of gluster volume (aka not a gluster peer).
The context here is GlusterFS as a storage domain in oVirt/VDSM, which
is currently available in upstream oVirt.
This features exploits the QEMU-GlusterFS native integration, where the
VM disk is specified using gluster+<transport>://... protocol.
For eg. if transport is TCP.. the URI looks liek gluster+tcp://...,
otherwise gluster+rdma://...
Thus, to generate the gluster QEMU URI in VDSM, i need to know the
Gluster volume's transport type and the only inputs that oVirt gets for
GlusterFS storage domain are...
a) volfileserver (the host running glusterd)
b) volname (the name of the volume)
Currently i use VDSM's gluster plugin to do the eq. of "gluster volume
info <volname>" to determine Gluster volume's transport type, but this
won't work if the VDSM host is not a gluster peer, which is a
constraint! ... and I would like to fix/remove this constraint.
So i discussed a bit on #glsuter-dev IRC and want to put down the
options here for the community to help provide inputs on whats the best
way to approach this...
1) Use gluster --remote-host=<host_running_glusterd> volume info <volname>
This is not a supported way and there is no guarantee on how long the
--remote-host option be supported in gluster, since it has some security
issues
2) Use gluster ::system getspec <volname>
I tried this but it never worked for me... whats the right way of using
this ?
For me.. it just returned back to shell w/o dumping the volfile at all!
3) Have oVirt user provide the transport type as well (while creating
Gluster storgae domain) in addition to volfileserver:volname options
This would be easiest, since VDSM can form the gluster QEMU URI by
directly using the transport type specified by the user, and this won't
have a need to use the vdsm-gluster plugin, hence no need for VDSM host
to be part of gluster peer...but this would mean addnl input for user to
provide during Gluster domain creation and oVirt UI changes to take the
transport type as input in addition to volfileserver:volname
Comments/Opinions/Inputs appreciated
thanx,
deepak
(P.S. cross-posting this to VDSM and Gluster devel lists, as it relates
to both)
11 years, 1 month
libvirt domain xml has no leases specified in vdsm-4.10.3-10
by Mars gu
hi all,
my Engine version is 3.1.2. and my Vdsm version is 4.10.3-10.
I created a VM and tried to run it, then some error occoured, the error log is below:
Exit message: internal error unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified
The libvirt domain XML did not have <lease> elements which created by vdsm. Must I enable auto_disk_leases in /etc/libvirt/qemu-sanlock.conf and manually set host id in qemu-sanlock.conf ?
11 years, 1 month
'cannot acquire state change lock' reappear again
by bigclouds
i encounter an error of libvirt, which is reported in 2011. i intended to update the ticket(spice password) of vm.
https://bugzilla.redhat.com/show_bug.cgi?id=676205
libvirt-0.10.2-18.el6_4.4.x86_64
libvirt-client-0.10.2-18.el6_4.4.x86_64
libvirt-python-0.10.2-18.el6_4.4.x86_64
libvirt-lock-sanlock-0.10.2-18.el6_4.4.x86_64
---------log------------------
Thread-162::ERROR::2013-05-08 13:50:46,000::BindingXMLRPC::909::vdsm::(wrapper) libvirt error
Traceback (most recent call last):
File "/usr/share/vdsm/BindingXMLRPC.py", line 904, in wrapper
res = f(*args, **kwargs)
File "/usr/share/vdsm/BindingXMLRPC.py", line 213, in vmSetTicket
return vm.setTicket(password, ttl, existingConnAction, params)
File "/usr/share/vdsm/API.py", line 550, in setTicket
return v.setTicket(password, ttl, existingConnAction, params)
File "/usr/share/vdsm/libvirtvm.py", line 2245, in setTicket
self._dom.updateDeviceFlags(graphics.toxml(), 0)
File "/usr/share/vdsm/libvirtvm.py", line 524, in f
raise toe
TimeoutError: Timed out during operation: cannot acquire state change lock
11 years, 1 month
Too many open files
by bigclouds
Thread-19::DEBUG::2013-05-09 09:02:15,701::domainMonitor::170::Storage.DomainMonitorThread::(_monitorDomain) Refreshing domain 3a570ac5-8814-4255-9834-e45d14939007
Thread-19::DEBUG::2013-05-09 09:02:15,701::misc::83::Storage.Misc.excCmd::(<lambda>) '/usr/bin/sudo -n /sbin/lvm vgs --config " devices { preferred_names = [\\"^/dev/mapper/\\"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter = [ \\"r%.*%\\" ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 } backup { retain_min = 50 retain_days = 0 } " --noheadings --units b --nosuffix --separator | -o uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free 3a570ac5-8814-4255-9834-e45d14939007' (cwd None)
Thread-19::ERROR::2013-05-09 09:02:15,701::sdc::150::Storage.StorageDomainCache::(_findDomain) Error while looking for domain `3a570ac5-8814-4255-9834-e45d14939007`
Traceback (most recent call last):
File "/usr/share/mcvda/storage/sdc.py", line 145, in _findDomain
File "/usr/share/mcvda/storage/blockSD.py", line 1221, in findDomain
File "/usr/share/mcvda/storage/blockSD.py", line 1191, in findDomainPath
File "/usr/share/mcvda/storage/lvm.py", line 810, in getVG
File "/usr/share/vdsm/storage/lvm.py", line 542, in getVg
File "/usr/share/vdsm/storage/lvm.py", line 397, in _reloadvgs
File "/usr/lib64/python2.6/contextlib.py", line 34, in __exit__
File "/usr/share/vdsm/storage/misc.py", line 1204, in acquireContext
File "/usr/share/vdsm/storage/lvm.py", line 369, in _reloadvgs
File "/usr/share/vdsm/storage/lvm.py", line 305, in cmd
File "/usr/share/vdsm/storage/misc.py", line 198, in execCmd
File "/usr/lib64/python2.6/site-packages/vdsm/betterPopen/__init__.py", line 46, in __init__
File "/usr/lib64/python2.6/subprocess.py", line 632, in __init__
File "/usr/lib64/python2.6/subprocess.py", line 1055, in _get_handles
OSError: [Errno 24] Too many open files
Thread-19::ERROR::2013-05-09 09:02:15,702::domainMonitor::208::Storage.DomainMonitorThread::(_monitorDomain) Error while collecting domain 3a570ac5-8814-4255-9834-e45d14939007 monitoring information
Traceback (most recent call last):
File "/usr/share/vdsm/storage/domainMonitor.py", line 186, in _monitorDomain
File "/usr/share/vdsm/storage/sdc.py", line 49, in __getattr__
File "/usr/share/vdsm/storage/sdc.py", line 52, in getRealDomain
File "/usr/share/vdsm/storage/sdc.py", line 121, in _realProduce
File "/usr/share/vdsm/storage/sdc.py", line 152, in _findDomain
StorageDomainDoesNotExist: Storage domain does not exist: ('3a570ac5-8814-4255-9834-e45d14939007',)
11 years, 1 month
sync meeting minutes
by asegurap@redhat.com
VDSM sync meeting May 6th 13:30 UTC
Federico says that he can't see anything pending for 3.2. Tomorrow 3.2.2 will
be released. If anybody has anything pending push and ping Federico today.
Storage is working on completing the feature pages, after that they will link
them in the oVirt release management page.
http://wiki.ovirt.org/OVirt_3.3_release-management
Dan suggests to link the feature pages in their incomplete state to get more
feedback.
Yaniv states features for oVirt-3.3 to be reported. Splitting supervdsm is
going to be one of them. Needs reviews.
Yaniv discussed the libvirt connection getting wrapper. We are still looking
for a better solution that doesn't involve a special cif instance.
Vinzenz hints Yaniv that for his cpopen that he needs to talk in fedora-devel
for the package to be reviewed there.
Infra has been working on improving vdsm utils for out of process execution.
The git master breakage from Mark Wu's patch was reverted and Giuseppe
Vallarelli has made a unit test for preventing future patches from breaking
master by importing vdsm/ modules from lib/vdsm.
Vinzenz to ask on the list about the jsonrpc model.
Libvirtvm.py and vm.py to be verified by Vinzenz and QE to be thoroughly tested
this week.
Vinzenz points out that vdsClient is completely out of sync with the schema.
Dan mentions that Zhou Zheng Sheng has probably had some success with that. To
be presented in the Shangai workshop.
Adam has automatically generated bindings that need review and should be given
a push. Also vdsm schema verification has some work already done that should be
resumed.
We should put effort in bringing up possible changes/inconsistencies in the
schema relative to the way the api is evolving.
Toni to copy the agenda of the workshop in the mailing list. (DONE)
11 years, 1 month
vm down for client reset
by bigclouds
hi,all
1.it seems that there are many racing condition between channels.
for example all channels of a vm connect to just only one client, if the client down, a variable shared between channels should be set.
let see my problem.
1.server is aware of client is down (reset),
2.snd_receive still compare the numbers of data , why? why assert?
each thread do not communicate with each other.
---log-------------
handle_dev_display_connect: connect
handle_new_display_channel: add display channel client
handle_new_display_channel: add display channel client
handle_new_display_channel: New display (client 0x7fe2408720f0) dcc 0x7fe1d899bc20 stream 0x7fe240cebbe0
handle_new_display_channel: jpeg disabled
handle_new_display_channel: zlib-over-glz disabled
listen_to_new_client_channel: NEW ID = 0
handle_new_display_channel: zlib-over-glz disabled
listen_to_new_client_channel: NEW ID = 0
reds_show_new_channel: channel 9:2, connected successfully, over Secure link
reds_handle_auth_mechanism: Auth method: 1
reds_show_new_channel: channel 9:3, connected successfully, over Secure link
reds_handle_auth_mechanism: Auth method: 1
reds_show_new_channel: channel 9:1, connected successfully, over Secure link
display_channel_client_wait_for_init: creating encoder with id == 0
red_channel_client_disconnect: 0x7fe240e09030 (channel 0x7fe2407cd2f0 type 3 id 0)
red_peer_receive: Connection reset by peer
red_channel_client_disconnect: 0x7fe1d899bc20 (channel 0x7fe1d80458d0 type 2 id 0)
display_channel_client_on_disconnect:
red_channel_client_disconnect: 0x7fe1d80c8890 (channel 0x7fe1d8045e90 type 4 id 0)
snd_channel_put: sound channel freed
snd_receive: ASSERT n failed
/usr/lib64/libspice-server.so.1(+0xbf465)[0x7fe23d176465]
/usr/lib64/libspice-server.so.1(+0x45d2a)[0x7fe23d0fcd2a]
/usr/lib64/libspice-server.so.1(+0x45d80)[0x7fe23d0fcd80]
/usr/libexec/qemu-kvm(+0x625df)[0x7fe23ef315df]
/usr/libexec/qemu-kvm(+0x8428a)[0x7fe23ef5328a]
/usr/libexec/qemu-kvm(main+0x154c)[0x7fe23ef3412c]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7fe23c8a8cdd]
/usr/libexec/qemu-kvm(+0x5f149)[0x7fe23ef2e149]
2013-05-10 05:55:38.945+0000: shutting down
11 years, 1 month