Re: [Users] Problem running virtual machines
On 07/27/2012 09:36 AM, Itamar Heim wrote: On 07/26/2012 07:38 PM, jose garcia wrote: Apologies, version is 3.1.0-0.1.20120620git6ef9f8.fc17 On 07/26/2012 05:18 PM, jose garcia wrote: Good evening, I am running oVirt 3. I am not sure if the source of the problem is oVirt or KVM/qemu but the machines run really slow since some days ago. There are some warnings regarding iscsi storage latency in the oVirt portal but the behaviour is also present with NFS storage. There are no visible errors either in engine.log or vdsm.log. Var/log/messages in the node shows over and over: /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing what type of storage? what networking from host to storage? Good morning, I have got two nodes for an iSCSI datacenter and another for a NFS datacenter. The machines run slow whatever the datacenter or node is used (all run fedora 17, recently updated). Networking is basic. Only ovirtmgmt bridge and one network interface is used per node. What is strange is that the VMs seem to run without any problem, only they take more time to perform any activity. That, of course, causes problems to ovirt-engine and the delays tend to set a node in a non-operational state, specially when installing. and, after a while, waits in the node rise over 50%. It finally leads to a disconnection of the SPM node and a non-operational state. Has anyone any ideas why this happens? Regards, Jose Garcia ___ 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] Problem running virtual machines
Good evening, I am running oVirt 3. I am not sure if the source of the problem is oVirt or KVM/qemu but the machines run really slow since some days ago. There are some warnings regarding iscsi storage latency in the oVirt portal but the behaviour is also present with NFS storage. There are no visible errors either in engine.log or vdsm.log. Var/log/messages in the node shows over and over: /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing and, after a while, waits in the node rise over 50%. It finally leads to a disconnection of the SPM node and a non-operational state. Has anyone any ideas why this happens? Regards, Jose Garcia ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Problem running virtual machines
Apologies, version is 3.1.0-0.1.20120620git6ef9f8.fc17 On 07/26/2012 05:18 PM, jose garcia wrote: Good evening, I am running oVirt 3. I am not sure if the source of the problem is oVirt or KVM/qemu but the machines run really slow since some days ago. There are some warnings regarding iscsi storage latency in the oVirt portal but the behaviour is also present with NFS storage. There are no visible errors either in engine.log or vdsm.log. Var/log/messages in the node shows over and over: /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing and, after a while, waits in the node rise over 50%. It finally leads to a disconnection of the SPM node and a non-operational state. Has anyone any ideas why this happens? Regards, Jose Garcia ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Update of oVirt 3.1
.\deployment.engine.ear\.main: Failed to load module: deployment.engine.ear:main,jboss.module.service.\deployment.engine.ear.engine-genericapi.jar\.main = org.jboss.msc.service.StartException in service jboss.module.service.\deployment.engine.ear.engine-genericapi.jar\.main: Failed to load module: deployment.engine.ear.engine-genericapi.jar:main,jboss.module.service.\deployment.engine.ear.ovirtengineweb.war\.main = org.jboss.msc.service.StartException in service jboss.module.service.\deployment.engine.ear.ovirtengineweb.war\.main: Failed to load module: deployment.engine.ear.ovirtengineweb.war:main,jboss.module.service.\deployment.engine.ear.restapi.war\.main = org.jboss.msc.service.StartException in service jboss.module.service.\deployment.engine.ear.restapi.war\.main: Failed to load module: deployment.engine.ear.restapi.war:main,jboss.module.service.\deployment.engine.ear.root.war\.main = org.jboss.msc.service.StartException in service jboss.module.service.\deployment.engine.ear.root.war\.main: Failed to load module: deployment.engine.ear.root.war:main,jboss.module.service.\deployment.engine.ear.engine-scheduler.jar\.main = org.jboss.msc.service.StartException in service jboss.module.service.\deployment.engine.ear.engine-scheduler.jar\.main: Failed to load module: deployment.engine.ear.engine-scheduler.jar:main The ovirt-engine and jboss-as services are up and running. The last information logged in engine.log, however, is from before the update. I have excluded java from the update. /# java -version/ shows: java version 1.7.0_03-icedtea OpenJDK Runtime Environment (fedora-2.2.1.fc17.8-x86_64) OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode) Regards, Jose Garcia ___ 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] Update of oVirt 3.1
On 07/25/2012 09:45 AM, Juan Hernandez wrote:
On 07/25/2012 10:37 AM, Juan Hernandez wrote:
On 07/25/2012 10:22 AM, jose garcia wrote:
On 07/25/2012 09:05 AM, Ofer Schreiber wrote:
- Original Message -
Good evening,
I had installed the 3.1 beta version. After an update of Fedora
17,
the portal does not show any links. I reckon that ovirt-engine
version
has been upgraded to 3.1.0-1.fc17.
Have I lost all the information in the database? Is there a way
to
bring back the datacenters and the nodes info?
I'm pretty sure the DB is still there.
you should take a look into the log files under /var/log/ovirt-engine
(server.log and engine.log) and look for exceptions.
also, you might want to make sure that postgrsql, httpd and ovirt-engine
services are up and running.
Good morning,
Yes, there are a bunch of errors recorded in server.log, regarding
jboss-as modules:
2012-07-25 09:03:59,386 ERROR [org.jboss.msc.service.fail] (MSC
service thread 1-4) MSC01: Failed to start service
jboss.module.service.deployment.engine.ear.userportal.war.main:
org.jboss.msc.service.StartException in service
jboss.module.service.deployment.engine.ear.userportal.war.main:
Failed to load module: deployment.engine.ear.userportal.war:main
//at
org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91)
[jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc.jar:1.0.2.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[jboss-msc.jar:1.0.2.GA]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[rt.jar:1.7.0_03-icedtea]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[rt.jar:1.7.0_03-icedtea]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03-icedtea]
Caused by: org.jboss.modules.ModuleLoadException: Error loading
module from
/usr/share/jboss-as/modules/javax/xml/registry/api/main/module.xml
at
org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:292)
at
org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:242)
at
org.jboss.modules.LocalModuleLoader.parseModuleInfoFile(LocalModuleLoader.java:138)
at
org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:122)
at
org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)
at
org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)
at
org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)
at org.jboss.modules.Module.addExportedPaths(Module.java:977)
at org.jboss.modules.Module.addPaths(Module.java:883)
at org.jboss.modules.Module.link(Module.java:1196)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1225)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208)
at
org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70)
[jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at
[row,col]:[31,55]
Message: Failed to add resource root 'jboss-jaxr-1.0-api.jar' at
path 'jboss-jaxr-1.0-api.jar'
at
org.jboss.modules.ModuleXmlParser.parseResourceRoot(ModuleXmlParser.java:898)
at
org.jboss.modules.ModuleXmlParser.parseResources(ModuleXmlParser.java:854)
at
org.jboss.modules.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:676)
at
org.jboss.modules.ModuleXmlParser.parseDocument(ModuleXmlParser.java:548)
at
org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:287)
2012-07-25 09:03:59,864 ERROR
[org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads
- 1) {JBAS014653: Composite operation failed and was rolled back.
Steps that failed: = {Operation step-2 = {JBAS014671: Failed
services =
{jboss.module.service.\deployment.engine.ear.engine-bll.jar\.main =
org.jboss.msc.service.StartException in service
jboss.module.service.\deployment.engine.ear.engine-bll.jar\.main:
Failed to load module:
deployment.engine.ear.engine-bll.jar:main,jboss.module.service.\deployment.engine.ear.webadmin.war\.main
= org.jboss.msc.service.StartException in service
jboss.module.service.\deployment.engine.ear.webadmin.war\.main:
Failed to load module:
deployment.engine.ear.webadmin.war:main,jboss.module.service.\deployment.engine.ear.userportal.war\.main
= org.jboss.msc.service.StartException
[Users] Update of oVirt 3.1
Good evening, I had installed the 3.1 beta version. After an update of Fedora 17, the portal does not show any links. I reckon that ovirt-engine version has been upgraded to 3.1.0-1.fc17. Have I lost all the information in the database? Is there a way to bring back the datacenters and the nodes info? Regards, Jose Garcia ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Users Digest, Vol 10, Issue 29
On 07/09/2012 05:18 PM, users-requ...@ovirt.org wrote: Send Users mailing list submissions to users@ovirt.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.ovirt.org/mailman/listinfo/users or, via email, send a message with subject or body 'help' to users-requ...@ovirt.org You can reach the person managing the list at users-ow...@ovirt.org When replying, please edit your Subject line so it is more specific than Re: Contents of Users digest... Today's Topics: 1. Re: VM Tools (Andres Gonzalez) 2. Re: VM Tools (Robert Middleswarth) -- Message: 1 Date: Mon, 9 Jul 2012 13:10:43 -0300 From: Andres Gonzalez tuc...@gmail.com To: Robert Middleswarth rob...@middleswarth.net Cc: users@ovirt.org Subject: Re: [Users] VM Tools Message-ID: CAM-PzLfwkoCs1aGsKh1GaU5OF8=cj85nwhkadu63ragfs_y...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Thanks ! Looks that there's a problem with the CentOS repo: *[root@localhost ~]# yum install rhev-agent-pam-rhev-cred rhev-agent* *Failed to set locale, defaulting to C* *Loaded plugins: fastestmirror* *Loading mirror speeds from cached hostfile* * * base: mirror.netglobalis.net* * * commercial-addons: 66.128.53.13* * * elastix-base: 66.128.53.13* * * elastix-extras: 66.128.53.13* * * elastix-updates: 66.128.53.13* * * epel: epel.mirror.mendoza-conicet.gob.ar* * * extras: mirror.netglobalis.net* * * updates: mirror.netglobalis.net* *ovirt-dre/primary | 7.0 kB 00:00 * *http://www.dreyou.org/ovirt/ovirt-engine/repodata/primary.xml.gz: [Errno -3] Error performing checksum* *Trying other mirror.* *Error: failure: repodata/primary.xml.gz from ovirt-dre: [Errno 256] No more mirrors to try.* Regards. On Mon, Jul 9, 2012 at 12:37 PM, Robert Middleswarth rob...@middleswarth.net wrote: On 07/09/2012 10:40 AM, Andres Gonzalez wrote: Hi !! Reading the oVirt installation guide says that when a local ISO storage domain is configured during installation the virtio-win ISO and Virtual Floppy Drive (VFD) images, containing the VirtIO drivers for Windows virtual machines, are automatically copied to the new storage domain. The rhev-tools-setup ISO, containing the oVirt Guest Tools for Windows virtual machines are also copied to the domain. I'm running oVirt under FC 16, and I don't have those packages installed, what could it be ? I downloaded from http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/ the iso file but it doesn't have the floppy file (useful for the Windows setup installation) and also drivers for Windows 2008. Under RHEV when having a Windows VM at the admin GUI you can see what applications are installed, IP address, who's logged in, etc., on the VM. This is possible on oVirt too ? Is there any guest tool for Linux VMs ? (RHEL or CentOS) Thanks! Regards.- -- AGD ___ Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users This is a known limit of ovirt. You can use the Same ISO / floppy disk for windows that is used for RHEV. For whatever reason the floppy isn't available from Red Hat any-more. You can get the last known release of it using the way back machine. http://web.archive.org/web/20110501124422/http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-1.1.16.vfd I have no access to RHEL to confirm but I have been told that RHEV drivers work fine under ovirt. CentOS you can download those from http://wiki.dreyou.org/dokuwiki/doku.php/ovirt_rpm_start . You need to add the repo listed at the top and then if you look at the bottom there is the install for the guest. Thanks Robert ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users tested this morning in a scientific linux: http://www.dreyou.org/ovirt/ adding file ovirt-dre.repo http://www.dreyou.org/ovirt/ovirt-dre.repo to /etc/yum.repos.d/ Good evening. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Is it possible to attach an ISCSI export to an NFS based Data Center?
Good evening, In 3.0 there was the option to add an ISCSI export to a Data Center using NFS. I could not test the feature, however, as my LUN did not appear in the UI. When I look for this option in the interface of oVirt 3.1 I only find Data/NFS and Export/NFS (I have already an ISO Domain defined, also NFS). Is it this option available in the new version? If so, what are the requirements? Regards, Jose Garcia ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Addition of nodes to oVirt-engine
On 06/28/2012 08:06 PM, Itamar Heim wrote: On 06/28/2012 07:55 AM, jose garcia wrote: On 06/28/2012 11:33 AM, Itamar Heim wrote: On 06/28/2012 04:55 AM, jose garcia wrote: On 06/28/2012 02:43 AM, Itamar Heim wrote: On 06/27/2012 09:15 AM, jose garcia wrote: Good evening to all, I have added two nodes of Fedora 17 with vdsm 4.10 installed to oVirt 3.1 engine. I was having problems with SSL, so I have disabled it. When I added the nodes there was no attempt of installation as it was the case with oVirt 3.0, but the nodes get activated, provided that ovirtmgmt bridge is present. I have been told that there is a configuration in the database that make this happen. I just recreated the database via the script /dbscripts/create_db_devel.sh and run engine-setup, after removing all packages from oVirt 3.0 and jboss and installing ovirt 3.1 basic packages. My question is: What would be the 'standard' procedure to get oVirt 3.1 running? the standard procedure would be to install the rpm and engine-setup and add the host from UI so they will be configured with certificates and ssl Good morning, I wanted to know if there will be an installation process from scratch with a reboot for the hosts as there was in 3.0. yes. I have an issue that may also be related to authentication. I am unable to start my newly created VM. The engine seems to connect to libvirt in read-only mode, and boot of the virtual Machine fails. There is something quaint in virsh (Fedora 17 in the hosts): when trying to connect without specifying the uri (qemu:///system) it gives segmentation fault. If it is given it asks for user and password. Tried to disable sasl in libvirtd.conf and now I can connect with virsh to the default uri without providing a password, but booting of the vm keeps failing. It is required to use sasl or to add a sasl user in the engine, in the hosts or in both? everything should work out of the box without tweaking config files. however, i'm not sure we will work correctly if they were tweaked manually. please try a clean install of your node, then add it from the UI (assuming you did a clean rpm install of the engine and didn't tweak any of its configuration parameters affecting installation process) thanks I apologize for mixing up things, but had the clean install of the node worked I would never have tweaked anything. SSL was not working for me so I had to disable it. If in the first connection to the node there is an error related to SSL it is not probable that the engine can configure certificates or anything. Meanwhile I have found the problem with the VM don't booting, which is a bug in the sanlock libvirt feature reported in https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=828633. To attach an iso there is a workaround updating libvirt with the version in updates-testing and, maybe, tweaking /etc/libvirt/qemu-sanlock.conf. This does not sound as the out-of-the-box kind of thing to me. Anyway, the tweak worked but the installed machine won't first-time boot and I am at the moment wondering why//the log is showing: /managed non plugable/(sic)/device was removed unexpetedly/(sic)/from libvirt/. I can imagine how difficult is the development process. What I know is that testing software is not an easy thing either and you can't sit and wait for a solution to come out of some box. What I am trying is to test the basic features of the new version, no more. I am not trying to tune it in any way. i didn't mean to imply you did something wrong, and i appreciate you are trying to make it work. however, it will be easier to try and identify your issue if you can try to run the installation on a cleanly installed fedora 17 host. thanks, Itamar Good morning, It's all right. I will try to retake the easy way whenever i can. At the moment, I have the engine working with two nodes and without any security authentication. The general performance seems to have been improved. I think the user portal has new features. I would like to know if it's fully operative in order to take the time to have a look at it. I am having some trouble installing VMs but I don't think they are directly related to oVirt and if one of my servers refrained from rebooting randomly everything would be easier. My feeling is that the project is advancing. Cheers, Jose Garcia Regards vdsm.log reads: Thread-72::DEBUG::2012-06-27 18:57:25,511::task::978::TaskManager.Task::(_decref) Task=`e92b65bc-b9fe-492f-b77c-397321dbb105`::ref 0 aborting False Thread-70::DEBUG::2012-06-27 18:57:25,531::vm::580::vm.Vm::(_startUnderlyingVm) vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::_ongoingCreations released Thread-70::ERROR::2012-06-27 18:57:25,532::vm::604::vm.Vm::(_startUnderlyingVm) vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::The vm start process failed Traceback (most recent call last): File /usr/share/vdsm/vm.py, line 570, in _startUnderlyingVm self._run() File /usr/share/vdsm
Re: [Users] Addition of nodes to oVirt-engine
On 06/28/2012 02:43 AM, Itamar Heim wrote:
On 06/27/2012 09:15 AM, jose garcia wrote:
Good evening to all,
I have added two nodes of Fedora 17 with vdsm 4.10 installed to oVirt
3.1 engine. I was having problems
with SSL, so I have disabled it. When I added the nodes there was no
attempt of installation as it was
the case with oVirt 3.0, but the nodes get activated, provided that
ovirtmgmt bridge is present.
I have been told that there is a configuration in the database that make
this happen. I just recreated the
database via the script /dbscripts/create_db_devel.sh and run
engine-setup, after removing all packages from oVirt 3.0 and jboss and
installing ovirt 3.1 basic packages.
My question is: What would be the 'standard' procedure to get oVirt 3.1
running?
the standard procedure would be to install the rpm and engine-setup
and add the host from UI so they will be configured with certificates
and ssl
Good morning,
I wanted to know if there will be an installation process from scratch
with a reboot for the hosts as there was in 3.0.
I have an issue that may also be related to authentication. I am unable
to start my newly created VM. The engine seems to connect to libvirt in
read-only mode, and boot of the virtual Machine fails. There is
something quaint in virsh (Fedora 17 in the hosts):
when trying to connect without specifying the uri (qemu:///system) it
gives segmentation fault. If it is given it asks for user and password.
Tried to disable sasl in libvirtd.conf and now I can connect with virsh
to the default uri without providing a password, but booting of the vm
keeps failing.
It is required to use sasl or to add a sasl user in the engine, in the
hosts or in both?
vdsm.log reads:
Thread-72::DEBUG::2012-06-27
18:57:25,511::task::978::TaskManager.Task::(_decref)
Task=`e92b65bc-b9fe-492f-b77c-397321dbb105`::ref 0 aborting False
Thread-70::DEBUG::2012-06-27
18:57:25,531::vm::580::vm.Vm::(_startUnderlyingVm)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::_ongoingCreations released
Thread-70::ERROR::2012-06-27
18:57:25,532::vm::604::vm.Vm::(_startUnderlyingVm)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::The vm start process failed
Traceback (most recent call last):
File /usr/share/vdsm/vm.py, line 570, in _startUnderlyingVm
self._run()
File /usr/share/vdsm/libvirtvm.py, line 1364, in _run
self._connection.createXML(domxml, flags),
File /usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py,
line 82, in wrapper
ret = f(*args, **kwargs)
File /usr/lib64/python2.7/site-packages/libvirt.py, line 2420, in
createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed',
conn=self)
*libvirtError: internal error unsupported configuration: Readonly leases
are not supported*
Thread-70::DEBUG::2012-06-27
18:57:25,542::vm::920::vm.Vm::(setDownStatus)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::Changed state to Down:
internal error unsupported configuration: Readonly leases are not supported
Thread-75::DEBUG::2012-06-27
18:57:27,588::BindingXMLRPC::859::vds::(wrapper) client
[10.10.30.101]::call vmGetStats with
('32339151-23ed-4cc3-ada4-0f540ab81a97',) {}
Thread-75::DEBUG::2012-06-27
18:57:27,588::BindingXMLRPC::865::vds::(wrapper) return vmGetStats with
{'status': {'message': 'Done', 'code': 0}, 'statsList': [{'status':
'Down', 'hash': '0', 'exitMessage': 'internal error unsupported
configuration: Readonly leases are not supported', 'vmId':
'32339151-23ed-4cc3-ada4-0f540ab81a97', 'timeOffset': '0', 'exitCode': 1}]}
Thread-76::DEBUG::2012-06-27
18:57:27,594::BindingXMLRPC::859::vds::(wrapper) client
[10.10.30.101]::call vmDestroy with
('32339151-23ed-4cc3-ada4-0f540ab81a97',) {}
Thread-76::INFO::2012-06-27 18:57:27,595::API::317::vds::(destroy)
vmContainerLock acquired by vm 32339151-23ed-4cc3-ada4-0f540ab81a97
Thread-76::DEBUG::2012-06-27
18:57:27,595::libvirtvm::2085::vm.Vm::(destroy)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::destroy Called
Thread-76::INFO::2012-06-27
18:57:27,595::libvirtvm::2040::vm.Vm::(releaseVm)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::Release VM resources
Thread-76::WARNING::2012-06-27
18:57:27,596::vm::328::vm.Vm::(_set_lastStatus)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::trying to set state to
Powering down when already Down
Thread-76::DEBUG::2012-06-27
18:57:27,596::__init__::1249::Storage.Misc.excCmd::(_log) '/usr/bin/sudo
-n /usr/sbin/service ksmtuned retune'
And there is a log in /var/log/libvirt/qemu for the VM that says:
starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -S -M pc-0.14 -cpu
kvm64,+lahf_lm,+ssse3,-cx16 -enable-kvm -m 1024 -smp
1,sockets=1,cores=1,threads=1 -name fedora-test -uuid
32339151-23ed-4cc3-ada4-0f540ab81a97 -smbios type=1,manufacturer=Red
Hat,product=RHEV
Hypervisor,version=17-1,serial=03000200-0400-0500-0006-000700080009_00:30:18:a8:a8:42,uuid=32339151-23ed-4cc3-ada4
Re: [Users] Addition of nodes to oVirt-engine
On 06/28/2012 09:55 AM, jose garcia wrote:
On 06/28/2012 02:43 AM, Itamar Heim wrote:
On 06/27/2012 09:15 AM, jose garcia wrote:
Good evening to all,
I have added two nodes of Fedora 17 with vdsm 4.10 installed to oVirt
3.1 engine. I was having problems
with SSL, so I have disabled it. When I added the nodes there was no
attempt of installation as it was
the case with oVirt 3.0, but the nodes get activated, provided that
ovirtmgmt bridge is present.
I have been told that there is a configuration in the database that
make
this happen. I just recreated the
database via the script /dbscripts/create_db_devel.sh and run
engine-setup, after removing all packages from oVirt 3.0 and jboss and
installing ovirt 3.1 basic packages.
My question is: What would be the 'standard' procedure to get oVirt 3.1
running?
the standard procedure would be to install the rpm and engine-setup
and add the host from UI so they will be configured with certificates
and ssl
Good morning,
I wanted to know if there will be an installation process from scratch
with a reboot for the hosts as there was in 3.0.
I have an issue that may also be related to authentication. I am
unable to start my newly created VM. The engine seems to connect to
libvirt in read-only mode, and boot of the virtual Machine fails.
There is something quaint in virsh (Fedora 17 in the hosts):
when trying to connect without specifying the uri (qemu:///system) it
gives segmentation fault. If it is given it asks for user and password.
Tried to disable sasl in libvirtd.conf and now I can connect with
virsh to the default uri without providing a password, but booting of
the vm keeps failing.
It is required to use sasl or to add a sasl user in the engine, in the
hosts or in both?
vdsm.log reads:
Thread-72::DEBUG::2012-06-27
18:57:25,511::task::978::TaskManager.Task::(_decref)
Task=`e92b65bc-b9fe-492f-b77c-397321dbb105`::ref 0 aborting False
Thread-70::DEBUG::2012-06-27
18:57:25,531::vm::580::vm.Vm::(_startUnderlyingVm)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::_ongoingCreations released
Thread-70::ERROR::2012-06-27
18:57:25,532::vm::604::vm.Vm::(_startUnderlyingVm)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::The vm start process failed
Traceback (most recent call last):
File /usr/share/vdsm/vm.py, line 570, in _startUnderlyingVm
self._run()
File /usr/share/vdsm/libvirtvm.py, line 1364, in _run
self._connection.createXML(domxml, flags),
File /usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py,
line 82, in wrapper
ret = f(*args, **kwargs)
File /usr/lib64/python2.7/site-packages/libvirt.py, line 2420, in
createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed',
conn=self)
*libvirtError: internal error unsupported configuration: Readonly
leases are not supported*
Thread-70::DEBUG::2012-06-27
18:57:25,542::vm::920::vm.Vm::(setDownStatus)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::Changed state to Down:
internal error unsupported configuration: Readonly leases are not
supported
Thread-75::DEBUG::2012-06-27
18:57:27,588::BindingXMLRPC::859::vds::(wrapper) client
[10.10.30.101]::call vmGetStats with
('32339151-23ed-4cc3-ada4-0f540ab81a97',) {}
Thread-75::DEBUG::2012-06-27
18:57:27,588::BindingXMLRPC::865::vds::(wrapper) return vmGetStats
with {'status': {'message': 'Done', 'code': 0}, 'statsList':
[{'status': 'Down', 'hash': '0', 'exitMessage': 'internal error
unsupported configuration: Readonly leases are not supported', 'vmId':
'32339151-23ed-4cc3-ada4-0f540ab81a97', 'timeOffset': '0', 'exitCode':
1}]}
Thread-76::DEBUG::2012-06-27
18:57:27,594::BindingXMLRPC::859::vds::(wrapper) client
[10.10.30.101]::call vmDestroy with
('32339151-23ed-4cc3-ada4-0f540ab81a97',) {}
Thread-76::INFO::2012-06-27 18:57:27,595::API::317::vds::(destroy)
vmContainerLock acquired by vm 32339151-23ed-4cc3-ada4-0f540ab81a97
Thread-76::DEBUG::2012-06-27
18:57:27,595::libvirtvm::2085::vm.Vm::(destroy)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::destroy Called
Thread-76::INFO::2012-06-27
18:57:27,595::libvirtvm::2040::vm.Vm::(releaseVm)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::Release VM resources
Thread-76::WARNING::2012-06-27
18:57:27,596::vm::328::vm.Vm::(_set_lastStatus)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::trying to set state to
Powering down when already Down
Thread-76::DEBUG::2012-06-27
18:57:27,596::__init__::1249::Storage.Misc.excCmd::(_log)
'/usr/bin/sudo -n /usr/sbin/service ksmtuned retune'
And there is a log in /var/log/libvirt/qemu for the VM that says:
starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -S -M pc-0.14 -cpu
kvm64,+lahf_lm,+ssse3,-cx16 -enable-kvm -m 1024 -smp
1,sockets=1,cores=1,threads=1 -name fedora-test -uuid
32339151-23ed-4cc3-ada4-0f540ab81a97 -smbios type=1,manufacturer=Red
Hat,product=RHEV
Hypervisor,version=17-1,serial=03000200-0400-0500-0006-000700080009_00:30:18
Re: [Users] Addition of nodes to oVirt-engine
On 06/28/2012 11:33 AM, Itamar Heim wrote:
On 06/28/2012 04:55 AM, jose garcia wrote:
On 06/28/2012 02:43 AM, Itamar Heim wrote:
On 06/27/2012 09:15 AM, jose garcia wrote:
Good evening to all,
I have added two nodes of Fedora 17 with vdsm 4.10 installed to oVirt
3.1 engine. I was having problems
with SSL, so I have disabled it. When I added the nodes there was no
attempt of installation as it was
the case with oVirt 3.0, but the nodes get activated, provided that
ovirtmgmt bridge is present.
I have been told that there is a configuration in the database that
make
this happen. I just recreated the
database via the script /dbscripts/create_db_devel.sh and run
engine-setup, after removing all packages from oVirt 3.0 and jboss and
installing ovirt 3.1 basic packages.
My question is: What would be the 'standard' procedure to get oVirt
3.1
running?
the standard procedure would be to install the rpm and engine-setup
and add the host from UI so they will be configured with certificates
and ssl
Good morning,
I wanted to know if there will be an installation process from scratch
with a reboot for the hosts as there was in 3.0.
yes.
I have an issue that may also be related to authentication. I am unable
to start my newly created VM. The engine seems to connect to libvirt in
read-only mode, and boot of the virtual Machine fails. There is
something quaint in virsh (Fedora 17 in the hosts):
when trying to connect without specifying the uri (qemu:///system) it
gives segmentation fault. If it is given it asks for user and password.
Tried to disable sasl in libvirtd.conf and now I can connect with virsh
to the default uri without providing a password, but booting of the vm
keeps failing.
It is required to use sasl or to add a sasl user in the engine, in the
hosts or in both?
everything should work out of the box without tweaking config files.
however, i'm not sure we will work correctly if they were tweaked
manually.
please try a clean install of your node, then add it from the UI
(assuming you did a clean rpm install of the engine and didn't tweak
any of its configuration parameters affecting installation process)
thanks
I apologize for mixing up things, but had the clean install of the node
worked I would never have tweaked anything. SSL was not working for me
so I had to disable it. If in the first connection to the node there is
an error related to SSL it is not probable that the engine can configure
certificates or anything. Meanwhile I have found the problem with the VM
don't booting, which is a bug in the sanlock libvirt feature reported in
https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=828633. To
attach an iso there is a workaround updating libvirt with the version in
updates-testing and, maybe, tweaking /etc/libvirt/qemu-sanlock.conf.
This does not sound as the out-of-the-box kind of thing to me. Anyway,
the tweak worked but the installed machine won't first-time boot and I
am at the moment wondering why//the log is showing: /managed non
plugable/(sic)/device was removed unexpetedly/(sic)/from libvirt/.
I can imagine how difficult is the development process. What I know is
that testing software is not an easy thing either and you can't sit and
wait for a solution to come out of some box. What I am trying is to test
the basic features of the new version, no more. I am not trying to tune
it in any way.
Regards
vdsm.log reads:
Thread-72::DEBUG::2012-06-27
18:57:25,511::task::978::TaskManager.Task::(_decref)
Task=`e92b65bc-b9fe-492f-b77c-397321dbb105`::ref 0 aborting False
Thread-70::DEBUG::2012-06-27
18:57:25,531::vm::580::vm.Vm::(_startUnderlyingVm)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::_ongoingCreations released
Thread-70::ERROR::2012-06-27
18:57:25,532::vm::604::vm.Vm::(_startUnderlyingVm)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::The vm start process failed
Traceback (most recent call last):
File /usr/share/vdsm/vm.py, line 570, in _startUnderlyingVm
self._run()
File /usr/share/vdsm/libvirtvm.py, line 1364, in _run
self._connection.createXML(domxml, flags),
File /usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py, line
82, in wrapper
ret = f(*args, **kwargs)
File /usr/lib64/python2.7/site-packages/libvirt.py, line 2420, in
createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed',
conn=self)
*libvirtError: internal error unsupported configuration: Readonly leases
are not supported*
Thread-70::DEBUG::2012-06-27
18:57:25,542::vm::920::vm.Vm::(setDownStatus)
vmId=`32339151-23ed-4cc3-ada4-0f540ab81a97`::Changed state to Down:
internal error unsupported configuration: Readonly leases are not
supported
Thread-75::DEBUG::2012-06-27
18:57:27,588::BindingXMLRPC::859::vds::(wrapper) client
[10.10.30.101]::call vmGetStats with
('32339151-23ed-4cc3-ada4-0f540ab81a97',) {}
Thread-75::DEBUG::2012-06-27
18:57:27,588::BindingXMLRPC::865::vds::(wrapper) return vmGetStats with
{'status': {'message': 'Done', 'code': 0
[Users] Addition of nodes to oVirt-engine
Good evening to all, I have added two nodes of Fedora 17 with vdsm 4.10 installed to oVirt 3.1 engine. I was having problems with SSL, so I have disabled it. When I added the nodes there was no attempt of installation as it was the case with oVirt 3.0, but the nodes get activated, provided that ovirtmgmt bridge is present. I have been told that there is a configuration in the database that make this happen. I just recreated the database via the script /dbscripts/create_db_devel.sh and run engine-setup, after removing all packages from oVirt 3.0 and jboss and installing ovirt 3.1 basic packages. My question is: What would be the 'standard' procedure to get oVirt 3.1 running? Regards, Jose Garcia ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Vdsmd is respawning trying to sample NICs
Good monday morning, Installed Fedora 17 and tried to install the node to a 3.1 engine. I'm getting an VDS Network exception in the engine side: in /var/log/ovirt-engine/engine: 2012-06-25 10:15:34,132 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (QuartzScheduler_Worker-96) ResourceManager::refreshVdsRunTimeInfo::Failed to refresh VDS , vds = 2e9929c6-bea6-11e1-bfdd-ff11f39c80eb : ovirt-node2.smb.eurotux.local, VDS Network Error, continuing. VDSNetworkException: 2012-06-25 10:15:36,143 ERROR [org.ovirt.engine.core.vdsbroker.VdsManager] (QuartzScheduler_Worker-20) VDS::handleNetworkException Server failed to respond, vds_id = 2e9929c6-bea6-11e1-bfdd-ff11f39c80eb, vds_name = ovirt-node2.smb.eurotux.local, error = VDSNetworkException: 2012-06-25 10:15:36,181 INFO [org.ovirt.engine.core.bll.VdsEventListener] (pool-3-thread-49) ResourceManager::vdsNotResponding entered for Host 2e9929c6-bea6-11e1-bfdd-ff11f39c80eb, 10.10.30.177 2012-06-25 10:15:36,214 ERROR [org.ovirt.engine.core.bll.VdsNotRespondingTreatmentCommand] (pool-3-thread-49) [1afd4b89] Failed to run Fence script on vds:ovirt-node2.smb.eurotux.local, VMs moved to UnKnown instead. While in the node, vdsmd does fail to sample nics: in /var/log/vdsm/vdsm.log: nf = netinfo.NetInfo() File /usr/share/vdsm/netinfo.py, line 268, in __init__ _netinfo = get() File /usr/share/vdsm/netinfo.py, line 220, in get for nic in nics() ]) KeyError: 'p36p1' MainThread::INFO::2012-06-25 10:45:09,110::vdsm::76::vds::(run) VDSM main thread ended. Waiting for 1 other threads... MainThread::INFO::2012-06-25 10:45:09,111::vdsm::79::vds::(run) _MainThread(MainThread, started 140567823243072) MainThread::INFO::2012-06-25 10:45:09,111::vdsm::79::vds::(run) Thread(libvirtEventLoop, started daemon 140567752681216) in /etc/var/log/messages there is a lot of vdsmd died too quickly: Jun 25 10:45:08 ovirt-node2 respawn: slave '/usr/share/vdsm/vdsm' died too quickly, respawning slave Jun 25 10:45:08 ovirt-node2 respawn: slave '/usr/share/vdsm/vdsm' died too quickly, respawning slave Jun 25 10:45:09 ovirt-node2 respawn: slave '/usr/share/vdsm/vdsm' died too quickly for more than 30 seconds, master sleeping for 900 seconds I don't know why Fedora 17 calls p36p1 to what was eth0 in Fedora 16, but tried to configure a bridge ovirtmgmt and the only difference is that KeyError becomes 'ovirtmgmt'. Regards, Jose Garcia ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Vdsmd is respawning trying to sample NICs
On 06/25/2012 11:37 AM, Dan Kenigsberg wrote:
On Mon, Jun 25, 2012 at 10:57:47AM +0100, jose garcia wrote:
Good monday morning,
Installed Fedora 17 and tried to install the node to a 3.1 engine.
I'm getting an VDS Network exception in the engine side:
in /var/log/ovirt-engine/engine:
2012-06-25 10:15:34,132 WARN
[org.ovirt.engine.core.vdsbroker.VdsManager]
(QuartzScheduler_Worker-96)
ResourceManager::refreshVdsRunTimeInfo::Failed to refresh VDS , vds
= 2e9929c6-bea6-11e1-bfdd-ff11f39c80eb :
ovirt-node2.smb.eurotux.local, VDS Network Error, continuing.
VDSNetworkException:
2012-06-25 10:15:36,143 ERROR
[org.ovirt.engine.core.vdsbroker.VdsManager]
(QuartzScheduler_Worker-20) VDS::handleNetworkException Server
failed to respond, vds_id = 2e9929c6-bea6-11e1-bfdd-ff11f39c80eb,
vds_name = ovirt-node2.smb.eurotux.local, error =
VDSNetworkException:
2012-06-25 10:15:36,181 INFO
[org.ovirt.engine.core.bll.VdsEventListener] (pool-3-thread-49)
ResourceManager::vdsNotResponding entered for Host
2e9929c6-bea6-11e1-bfdd-ff11f39c80eb, 10.10.30.177
2012-06-25 10:15:36,214 ERROR
[org.ovirt.engine.core.bll.VdsNotRespondingTreatmentCommand]
(pool-3-thread-49) [1afd4b89] Failed to run Fence script on
vds:ovirt-node2.smb.eurotux.local, VMs moved to UnKnown instead.
While in the node, vdsmd does fail to sample nics:
in /var/log/vdsm/vdsm.log:
nf = netinfo.NetInfo()
File /usr/share/vdsm/netinfo.py, line 268, in __init__
_netinfo = get()
File /usr/share/vdsm/netinfo.py, line 220, in get
for nic in nics() ])
KeyError: 'p36p1'
MainThread::INFO::2012-06-25 10:45:09,110::vdsm::76::vds::(run) VDSM
main thread ended. Waiting for 1 other threads...
MainThread::INFO::2012-06-25 10:45:09,111::vdsm::79::vds::(run)
_MainThread(MainThread, started 140567823243072)
MainThread::INFO::2012-06-25 10:45:09,111::vdsm::79::vds::(run)
Thread(libvirtEventLoop, started daemon 140567752681216)
in /etc/var/log/messages there is a lot of vdsmd died too quickly:
Jun 25 10:45:08 ovirt-node2 respawn: slave '/usr/share/vdsm/vdsm'
died too quickly, respawning slave
Jun 25 10:45:08 ovirt-node2 respawn: slave '/usr/share/vdsm/vdsm'
died too quickly, respawning slave
Jun 25 10:45:09 ovirt-node2 respawn: slave '/usr/share/vdsm/vdsm'
died too quickly for more than 30 seconds, master sleeping for 900
seconds
I don't know why Fedora 17 calls p36p1 to what was eth0 in Fedora
16, but tried to configure a bridge ovirtmgmt and the only
difference is that KeyError becomes 'ovirtmgmt'.
The nic renaming may have happened due to biosdevname. Do you have it
installed? Does any of the /etc/sysconfig/network-scripts/ifcfg-* refer
to an old nic name?
Which version of vdsm are you running? It seems that it is
pre-v4.9.4-61-g24f8627 which is too old for f17 to run - the output of
ifconfig has changed. Please retry with latest beta version
https://koji.fedoraproject.org/koji/buildinfo?buildID=327015
If the problem persists, could you run vdsm manually, with
# su - vdsm -s /bin/bash
# cd /usr/share/vdsm
# ./vdsm
maybe it would give a hint about the crash.
regards,
Dan.
Well, thank you. I have updated Vdsm to version 4.10. Now the problem is
with SSL and XMLRPC.
This is the error in the side of the engine:
/var/log/ovirt-engine/engine.log
ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand]
(QuartzScheduler_Worker-52) XML RPC error in command GetCapabilitiesVDS
( Vds: ovirt-node2.smb.eurotux.local ), the error was:
java.util.concurrent.ExecutionException:
java.lang.reflect.InvocationTargetException, NoHttpResponseException:
The server 10.10.30.177 failed to respond.
In the side of the node, there seems to be an authentication problem:
/var/log/vdsm/vdsm.log
SSLError: [Errno 1] _ssl.c:504: error:1407609C:SSL
routines:SSL23_GET_CLIENT_HELLO:http request
Thread-810::ERROR::2012-06-25
12:02:46,351::SecureXMLRPCServer::73::root::(handle_error) client
('10.10.30.101', 58605)
Traceback (most recent call last):
File /usr/lib64/python2.7/SocketServer.py, line 582, in
process_request_thread
self.finish_request(request, client_address)
File /usr/lib/python2.7/site-packages/vdsm/SecureXMLRPCServer.py,
line 66, in finish_request
request.do_handshake()
File /usr/lib64/python2.7/ssl.py, line 305, in do_handshake
self._sslobj.do_handshake()
SSLError: [Errno 1] _ssl.c:504: error:1407609C:SSL
routines:SSL23_GET_CLIENT_HELLO:http request
In /var/log/messages there is an:
vdsm [5834]: vdsm root ERROR client ()
with the ip address of the engine.
Kind regards.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Vdsmd is respawning trying to sample NICs
On 06/25/2012 01:24 PM, Dan Kenigsberg wrote:
On Mon, Jun 25, 2012 at 01:15:08PM +0100, jose garcia wrote:
On 06/25/2012 12:30 PM, Dan Kenigsberg wrote:
On Mon, Jun 25, 2012 at 12:11:37PM +0100, jose garcia wrote:
On 06/25/2012 11:37 AM, Dan Kenigsberg wrote:
On Mon, Jun 25, 2012 at 10:57:47AM +0100, jose garcia wrote:
Good monday morning,
Installed Fedora 17 and tried to install the node to a 3.1 engine.
I'm getting an VDS Network exception in the engine side:
in /var/log/ovirt-engine/engine:
2012-06-25 10:15:34,132 WARN
[org.ovirt.engine.core.vdsbroker.VdsManager]
(QuartzScheduler_Worker-96)
ResourceManager::refreshVdsRunTimeInfo::Failed to refresh VDS , vds
= 2e9929c6-bea6-11e1-bfdd-ff11f39c80eb :
ovirt-node2.smb.eurotux.local, VDS Network Error, continuing.
VDSNetworkException:
2012-06-25 10:15:36,143 ERROR
[org.ovirt.engine.core.vdsbroker.VdsManager]
(QuartzScheduler_Worker-20) VDS::handleNetworkException Server
failed to respond, vds_id = 2e9929c6-bea6-11e1-bfdd-ff11f39c80eb,
vds_name = ovirt-node2.smb.eurotux.local, error =
VDSNetworkException:
2012-06-25 10:15:36,181 INFO
[org.ovirt.engine.core.bll.VdsEventListener] (pool-3-thread-49)
ResourceManager::vdsNotResponding entered for Host
2e9929c6-bea6-11e1-bfdd-ff11f39c80eb, 10.10.30.177
2012-06-25 10:15:36,214 ERROR
[org.ovirt.engine.core.bll.VdsNotRespondingTreatmentCommand]
(pool-3-thread-49) [1afd4b89] Failed to run Fence script on
vds:ovirt-node2.smb.eurotux.local, VMs moved to UnKnown instead.
While in the node, vdsmd does fail to sample nics:
in /var/log/vdsm/vdsm.log:
nf = netinfo.NetInfo()
File /usr/share/vdsm/netinfo.py, line 268, in __init__
_netinfo = get()
File /usr/share/vdsm/netinfo.py, line 220, in get
for nic in nics() ])
KeyError: 'p36p1'
MainThread::INFO::2012-06-25 10:45:09,110::vdsm::76::vds::(run) VDSM
main thread ended. Waiting for 1 other threads...
MainThread::INFO::2012-06-25 10:45:09,111::vdsm::79::vds::(run)
_MainThread(MainThread, started 140567823243072)
MainThread::INFO::2012-06-25 10:45:09,111::vdsm::79::vds::(run)
Thread(libvirtEventLoop, started daemon 140567752681216)
in /etc/var/log/messages there is a lot of vdsmd died too quickly:
Jun 25 10:45:08 ovirt-node2 respawn: slave '/usr/share/vdsm/vdsm'
died too quickly, respawning slave
Jun 25 10:45:08 ovirt-node2 respawn: slave '/usr/share/vdsm/vdsm'
died too quickly, respawning slave
Jun 25 10:45:09 ovirt-node2 respawn: slave '/usr/share/vdsm/vdsm'
died too quickly for more than 30 seconds, master sleeping for 900
seconds
I don't know why Fedora 17 calls p36p1 to what was eth0 in Fedora
16, but tried to configure a bridge ovirtmgmt and the only
difference is that KeyError becomes 'ovirtmgmt'.
The nic renaming may have happened due to biosdevname. Do you have it
installed? Does any of the /etc/sysconfig/network-scripts/ifcfg-* refer
to an old nic name?
Which version of vdsm are you running? It seems that it is
pre-v4.9.4-61-g24f8627 which is too old for f17 to run - the output of
ifconfig has changed. Please retry with latest beta version
https://koji.fedoraproject.org/koji/buildinfo?buildID=327015
If the problem persists, could you run vdsm manually, with
# su - vdsm -s /bin/bash
# cd /usr/share/vdsm
# ./vdsm
maybe it would give a hint about the crash.
regards,
Dan.
Well, thank you. I have updated Vdsm to version 4.10. Now the
problem is with SSL and XMLRPC.
This is the error in the side of the engine:
/var/log/ovirt-engine/engine.log
ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand]
(QuartzScheduler_Worker-52) XML RPC error in command
GetCapabilitiesVDS ( Vds: ovirt-node2.smb.eurotux.local ), the error
was: java.util.concurrent.ExecutionException:
java.lang.reflect.InvocationTargetException,
NoHttpResponseException: The server 10.10.30.177 failed to respond.
In the side of the node, there seems to be an authentication problem:
/var/log/vdsm/vdsm.log
SSLError: [Errno 1] _ssl.c:504: error:1407609C:SSL
routines:SSL23_GET_CLIENT_HELLO:http request
Thread-810::ERROR::2012-06-25
12:02:46,351::SecureXMLRPCServer::73::root::(handle_error) client
('10.10.30.101', 58605)
Traceback (most recent call last):
File /usr/lib64/python2.7/SocketServer.py, line 582, in
process_request_thread
self.finish_request(request, client_address)
File
/usr/lib/python2.7/site-packages/vdsm/SecureXMLRPCServer.py, line
66, in finish_request
request.do_handshake()
File /usr/lib64/python2.7/ssl.py, line 305, in do_handshake
self._sslobj.do_handshake()
SSLError: [Errno 1] _ssl.c:504: error:1407609C:SSL
routines:SSL23_GET_CLIENT_HELLO:http request
In /var/log/messages there is an:
vdsm [5834]: vdsm root ERROR client ()
with the ip address of the engine.
Hmm... Do you have ssl=true in your /etc/vdsm/vdsm.conf ?
Does vdsm respond locally to
vdsClient -s 0 getVdsCaps
(Maybe your local certificates and key were corrupted, and you will have
to re-install the host form Engine in order to create a new set)
I
Re: [Users] Vdsmd is respawning trying to sample NICs
On 06/25/2012 04:17 PM, Dan Kenigsberg wrote:
On Mon, Jun 25, 2012 at 03:15:47PM +0100, jose garcia wrote:
On 06/25/2012 01:24 PM, Dan Kenigsberg wrote:
On Mon, Jun 25, 2012 at 01:15:08PM +0100, jose garcia wrote:
On 06/25/2012 12:30 PM, Dan Kenigsberg wrote:
On Mon, Jun 25, 2012 at 12:11:37PM +0100, jose garcia wrote:
On 06/25/2012 11:37 AM, Dan Kenigsberg wrote:
On Mon, Jun 25, 2012 at 10:57:47AM +0100, jose garcia wrote:
Good monday morning,
Installed Fedora 17 and tried to install the node to a 3.1 engine.
I'm getting an VDS Network exception in the engine side:
in /var/log/ovirt-engine/engine:
2012-06-25 10:15:34,132 WARN
[org.ovirt.engine.core.vdsbroker.VdsManager]
(QuartzScheduler_Worker-96)
ResourceManager::refreshVdsRunTimeInfo::Failed to refresh VDS , vds
= 2e9929c6-bea6-11e1-bfdd-ff11f39c80eb :
ovirt-node2.smb.eurotux.local, VDS Network Error, continuing.
VDSNetworkException:
2012-06-25 10:15:36,143 ERROR
[org.ovirt.engine.core.vdsbroker.VdsManager]
(QuartzScheduler_Worker-20) VDS::handleNetworkException Server
failed to respond, vds_id = 2e9929c6-bea6-11e1-bfdd-ff11f39c80eb,
vds_name = ovirt-node2.smb.eurotux.local, error =
VDSNetworkException:
2012-06-25 10:15:36,181 INFO
[org.ovirt.engine.core.bll.VdsEventListener] (pool-3-thread-49)
ResourceManager::vdsNotResponding entered for Host
2e9929c6-bea6-11e1-bfdd-ff11f39c80eb, 10.10.30.177
2012-06-25 10:15:36,214 ERROR
[org.ovirt.engine.core.bll.VdsNotRespondingTreatmentCommand]
(pool-3-thread-49) [1afd4b89] Failed to run Fence script on
vds:ovirt-node2.smb.eurotux.local, VMs moved to UnKnown instead.
While in the node, vdsmd does fail to sample nics:
in /var/log/vdsm/vdsm.log:
nf = netinfo.NetInfo()
File /usr/share/vdsm/netinfo.py, line 268, in __init__
_netinfo = get()
File /usr/share/vdsm/netinfo.py, line 220, in get
for nic in nics() ])
KeyError: 'p36p1'
MainThread::INFO::2012-06-25 10:45:09,110::vdsm::76::vds::(run) VDSM
main thread ended. Waiting for 1 other threads...
MainThread::INFO::2012-06-25 10:45:09,111::vdsm::79::vds::(run)
_MainThread(MainThread, started 140567823243072)
MainThread::INFO::2012-06-25 10:45:09,111::vdsm::79::vds::(run)
Thread(libvirtEventLoop, started daemon 140567752681216)
in /etc/var/log/messages there is a lot of vdsmd died too quickly:
Jun 25 10:45:08 ovirt-node2 respawn: slave '/usr/share/vdsm/vdsm'
died too quickly, respawning slave
Jun 25 10:45:08 ovirt-node2 respawn: slave '/usr/share/vdsm/vdsm'
died too quickly, respawning slave
Jun 25 10:45:09 ovirt-node2 respawn: slave '/usr/share/vdsm/vdsm'
died too quickly for more than 30 seconds, master sleeping for 900
seconds
I don't know why Fedora 17 calls p36p1 to what was eth0 in Fedora
16, but tried to configure a bridge ovirtmgmt and the only
difference is that KeyError becomes 'ovirtmgmt'.
The nic renaming may have happened due to biosdevname. Do you have it
installed? Does any of the /etc/sysconfig/network-scripts/ifcfg-* refer
to an old nic name?
Which version of vdsm are you running? It seems that it is
pre-v4.9.4-61-g24f8627 which is too old for f17 to run - the output of
ifconfig has changed. Please retry with latest beta version
https://koji.fedoraproject.org/koji/buildinfo?buildID=327015
If the problem persists, could you run vdsm manually, with
# su - vdsm -s /bin/bash
# cd /usr/share/vdsm
# ./vdsm
maybe it would give a hint about the crash.
regards,
Dan.
Well, thank you. I have updated Vdsm to version 4.10. Now the
problem is with SSL and XMLRPC.
This is the error in the side of the engine:
/var/log/ovirt-engine/engine.log
ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand]
(QuartzScheduler_Worker-52) XML RPC error in command
GetCapabilitiesVDS ( Vds: ovirt-node2.smb.eurotux.local ), the error
was: java.util.concurrent.ExecutionException:
java.lang.reflect.InvocationTargetException,
NoHttpResponseException: The server 10.10.30.177 failed to respond.
In the side of the node, there seems to be an authentication problem:
/var/log/vdsm/vdsm.log
SSLError: [Errno 1] _ssl.c:504: error:1407609C:SSL
routines:SSL23_GET_CLIENT_HELLO:http request
Thread-810::ERROR::2012-06-25
12:02:46,351::SecureXMLRPCServer::73::root::(handle_error) client
('10.10.30.101', 58605)
Traceback (most recent call last):
File /usr/lib64/python2.7/SocketServer.py, line 582, in
process_request_thread
self.finish_request(request, client_address)
File
/usr/lib/python2.7/site-packages/vdsm/SecureXMLRPCServer.py, line
66, in finish_request
request.do_handshake()
File /usr/lib64/python2.7/ssl.py, line 305, in do_handshake
self._sslobj.do_handshake()
SSLError: [Errno 1] _ssl.c:504: error:1407609C:SSL
routines:SSL23_GET_CLIENT_HELLO:http request
In /var/log/messages there is an:
vdsm [5834]: vdsm root ERROR client ()
with the ip address of the engine.
Hmm... Do you have ssl=true in your /etc/vdsm/vdsm.conf ?
Does vdsm respond locally to
vdsClient -s 0 getVdsCaps
(Maybe your local certificates
Re: [Users] Not able to add node 2.3 to ovirt-engine 3.1
On 06/22/2012 06:21 PM, Douglas Landgraf wrote: Hi Jose, On 06/22/2012 05:18 AM, jose garcia wrote: Good morning, I have installed oVirt 3.1 over Fedora 17. When approving oVirt node it is added install fails. There is no output to engine.log or vdsm.log in the node whatsoever. It just fails. Is there a particular ovirt-node-iso version to be used with version 3.1 of the manager? Only problem I see in the system is that sometimes service libvirtd complains about not finding /etc/libvirt/krb5.tab and virsh is not accesible. A few logs should be generated in /tmp/vds_* in the node side. Can you please check or attach these logs? Hi, I am afraid there are only an ovirt.log and an ovirt-setup.tty2, both empty. I have resolved my problem with libvirt, though. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Not able to add node 2.3 to ovirt-engine 3.1
On 06/22/2012 06:51 PM, Douglas Landgraf wrote: On 06/22/2012 12:43 PM, jose garcia wrote: On 06/22/2012 06:21 PM, Douglas Landgraf wrote: Hi Jose, On 06/22/2012 05:18 AM, jose garcia wrote: Good morning, I have installed oVirt 3.1 over Fedora 17. When approving oVirt node it is added install fails. There is no output to engine.log or vdsm.log in the node whatsoever. It just fails. Is there a particular ovirt-node-iso version to be used with version 3.1 of the manager? Only problem I see in the system is that sometimes service libvirtd complains about not finding /etc/libvirt/krb5.tab and virsh is not accesible. A few logs should be generated in /tmp/vds_* in the node side. Can you please check or attach these logs? Hi, I am afraid there are only an ovirt.log and an ovirt-setup.tty2, both empty. I have resolved my problem with libvirt, though. ah, I misunderstood. I thought you were using Fedora17 as Node, sorry. Glad that you have resolved your problem. Cheers Douglas I have to use a fedora 17 for the node side too, then. Well, let's try again. At least I won't have to use that curious ovirt-node installer. Thank you. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Not able to add ISCSI storage to the Datacenter
Good morning,
I followed the procedure in
/https://fedorahosted.org/ovirt/wiki/ISCSISetup/, with
LV://dev/vg_iscsitest/iscsi1/ as backing storage.
When trying to import Export/ISCSI my volume discovery works, oVirt
makes login without problem but the lun defined does not show up. Iptables
and selinux are disabled.
/
# tgtadm --mode target --op show /
Target 1: host:storage
System information:
Driver: iscsi
State: ready
I_T nexus information:
LUN information:
LUN: 0
Type: controller
SCSI ID: IET 0001
SCSI SN: beaf10
Size: 0 MB, Block size: 1
Online: Yes
Removable media: No
Readonly: No
Backing store type: null
Backing store path: None
Backing store flags:
LUN: 1
Type: disk
SCSI ID: IET 00010001
SCSI SN: beaf11
Size: 21475 MB, Block size: 512
Online: Yes
Removable media: No
Readonly: No
Backing store type: rdwr
Backing store path: /dev/vg_iscsitest/iscsi1
Backing store flags:
Account information:
ACL information:
ALL
output of //var/log/vdsm/vdsm.log/ is:
Thread-301::DEBUG::2012-06-08
10:24:34,756::clientIF::261::Storage.Dispatcher.Protect::(wrapper)
[10.10.30.101]
Thread-301::DEBUG::2012-06-08
10:24:34,757::task::588::TaskManager.Task::(_updateState)
Task=`81890ebc-37db-4771-978b-dd2089de33bd`::moving from state init -
state preparing
Thread-301::INFO::2012-06-08
10:24:34,757::logUtils::37::dispatcher::(wrapper) Run and protect:
validateStorageServerConnection(domType=3,
spUUID='----', conList=[{'connection':
'10.10.30.101', 'iqn': 'host:storage', 'portal': '0', 'user': '',
'password': '**', 'id': '----',
'port': '3260'}], options=None)
Thread-301::INFO::2012-06-08
10:24:34,758::storage_connection::188::Storage.ServerConnection::(validate)
Request to validate ISCSI storage server
Thread-301::INFO::2012-06-08
10:24:34,759::logUtils::39::dispatcher::(wrapper) Run and protect:
validateStorageServerConnection, Return response: {'statuslist':
[{'status': 0, 'id': '----'}]}
Thread-301::DEBUG::2012-06-08
10:24:34,759::task::1174::TaskManager.Task::(prepare)
Task=`81890ebc-37db-4771-978b-dd2089de33bd`::finished: {'statuslist':
[{'status': 0, 'id': '----'}]}
Thread-301::DEBUG::2012-06-08
10:24:34,760::task::588::TaskManager.Task::(_updateState)
Task=`81890ebc-37db-4771-978b-dd2089de33bd`::moving from state preparing
- state finished
Thread-301::DEBUG::2012-06-08
10:24:34,761::resourceManager::806::ResourceManager.Owner::(releaseAll)
Owner.releaseAll requests {} resources {}
Thread-301::DEBUG::2012-06-08
10:24:34,761::resourceManager::841::ResourceManager.Owner::(cancelAll)
Owner.cancelAll requests {}
Thread-301::DEBUG::2012-06-08
10:24:34,762::task::980::TaskManager.Task::(_decref)
Task=`81890ebc-37db-4771-978b-dd2089de33bd`::ref 0 aborting False
Thread-302::DEBUG::2012-06-08
10:24:34,793::clientIF::261::Storage.Dispatcher.Protect::(wrapper)
[10.10.30.101]
Thread-302::DEBUG::2012-06-08
10:24:34,794::task::588::TaskManager.Task::(_updateState)
Task=`55fed2df-3434-4bba-a47c-a400d0c568a8`::moving from state init -
state preparing
Thread-302::INFO::2012-06-08
10:24:34,795::logUtils::37::dispatcher::(wrapper) Run and protect:
connectStorageServer(domType=3,
spUUID='----', conList=[{'connection':
'10.10.30.101', 'iqn': 'host:storage', 'portal': '0', 'user': '',
'password': '**', 'id': '----',
'port': '3260'}], options=None)
Thread-302::INFO::2012-06-08
10:24:34,795::storage_connection::146::Storage.ServerConnection::(connect)
Request to connect ISCSI storage server
Thread-302::DEBUG::2012-06-08
10:24:34,796::iscsi::148::Storage.Misc.excCmd::(addiSCSIPortal)
'/usr/bin/sudo -n /sbin/iscsiadm -m discoverydb -t sendtargets -p
10.10.30.101:3260 --discover' (cwd None)
Thread-302::DEBUG::2012-06-08
10:24:34,821::iscsi::148::Storage.Misc.excCmd::(addiSCSIPortal) SUCCESS:
err = ''; rc = 0
Thread-302::DEBUG::2012-06-08
10:24:34,822::iscsi::149::Storage.Misc.excCmd::(addiSCSIPortal)
'/usr/bin/sudo -n /sbin/iscsiadm -m node -p 10.10.30.101:3260 -o update
-n node.startup -v manual' (cwd None)
Thread-302::DEBUG::2012-06-08
10:24:34,840::iscsi::149::Storage.Misc.excCmd::(addiSCSIPortal) SUCCESS:
err = ''; rc = 0
Thread-302::DEBUG::2012-06-08
10:24:34,841::iscsi::254::Storage.Misc.excCmd::(addiSCSINode)
'/usr/bin/sudo -n /sbin/iscsiadm -m node -T host:storage -l -p
10.10.30.101:3260' (cwd None)
Thread-302::DEBUG::2012-06-08
10:24:35,379::iscsi::254::Storage.Misc.excCmd::(addiSCSINode) SUCCESS:
err = ''; rc = 0
Thread-302::DEBUG::2012-06-08
