On 2 Jan 2014, at 20:12, Dan Ferris wrote:
Hi,
Has anyone run across this error:
Cannot run VM. Invalid time zone for given OS type.
The OS type for these VMs is set to Linux Other.
What was the original TZ in 3.2?
They were all exported
from an Ovirt 3.2 cluster and are being
On 02.01.2014 20:12, Dan Ferris wrote: Hi,
Has anyone run across this error:
Cannot run VM. Invalid time zone for given OS type.
The OS type for these VMs is set to Linux Other. They were all exported
from an Ovirt 3.2 cluster and are being reimported into an Ovirt 3.3
cluster. None of
Hi,
I'm a little surprised by this development technique.
In my world, when you change data formats in a not compatible way
you should also write some sort of transition code to
convert the old data to the new data format for all possible
cases.
And if this is not possible for some reason, at
Hi,
I am starting with oVirt 3.3.2 and I have an issue adding a host to a cluster.
I am using oVirt Engine Version 3.3.2-1.el6
There is a cluster with one host (installed with oVirt Node - 3.0.3 - 1.1.fc19
ISO image) up and running.
I installed a second host using the same ISO image.
I
yes, please attach the vdsm log
also, can you run vdsClient 0 getStorageDomainsList and vdsClient 0
getDeviceList on both hosts?
It might be a cache issue, so can you please restart the host and if it
helps attach output before and after the reboot?
Thanks,
Dafna
On 01/03/2014 01:12 PM,
Hello,
I used qemu-img-rhev-0.12.1.2-2.355.el6 successfully with -s parameter,
but now qemu-img-rhev-0.12.1.2-2.415.el6 (latest atm) errors out with:
convert: invalid option -- 's'
What am I missing? Do I need any special rpmbuild switches or
something? I see the spec already says rhev 1
yes, there are bugs reported in openstack for the same issue on qemu-kvm:
https://bugzilla.redhat.com/show_bug.cgi?id=1027074
https://bugzilla.redhat.com/show_bug.cgi?id=1016896
On 01/03/2014 01:34 PM, Nux! wrote:
Hello,
I used qemu-img-rhev-0.12.1.2-2.355.el6 successfully with -s
Dafna,
you were right, it seems to be a caching issue. Rebooting the host did the
job:
Before Reboot:
[root@host01 log]# vdsClient -s 0 getStorageDomainsList
52cf84ce-6eda-4337-8c94-491d94f5a18d
f404398a-97f9-474c-af2c-e8887f53f688
7841a1c0-181a-4d43-9a25-b707accb5c4b
[root@host02 log]#
Thanks for reporting the issue :)
As for the vm, can you please find the error in vdsm.log and in engine
and paste it?
Thanks,
Dafna
On 01/03/2014 01:49 PM, Albl, Oliver wrote:
Dafna,
you were right, it seems to be a caching issue. Rebooting the host did the
job:
Before Reboot:
Dafna,
please find the logs below:
ERRORs in vdsm.log on host02:
Thread-61::ERROR::2014-01-03
13:51:48,956::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for
unfetched domain f404398a-97f9-474c-af2c-e8887f53f688
Thread-61::ERROR::2014-01-03
Can you please try this?
http://forums.opensuse.org/english/get-technical-help-here/virtualization/492483-cannot-start-libvert-kvm-guests-after-update-tumbleweed.html
On 01/03/2014 02:00 PM, Albl, Oliver wrote:
Dafna,
please find the logs below:
ERRORs in vdsm.log on host02:
On 01/03/2014 12:22 PM, Sven Kieske wrote:
Hi,
I'm a little surprised by this development technique.
its not a development technique. its a bug in upgrade or export/import
of the change to the much more powerful config file based OsInfo
implementation in 3.3.
though i thought we already
actually, looking at this again, it's a libvirt error and it can be
related to selinux or sasl.
can you also, look at libvirt log and the vm log under /var/log/libvirt?
On 01/03/2014 02:00 PM, Albl, Oliver wrote:
Dafna,
please find the logs below:
ERRORs in vdsm.log on host02:
Dafna,
Libvirtd.log shows no errors, but VM log shows the following:
2014-01-03 13:52:11.296+: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name OATEST2 -S -machine
pc-1.0,accel=kvm,usb=off -cpu SandyBridge -m 1024
On 3 Jan 2014, at 15:04, Itamar Heim wrote:
On 01/03/2014 12:22 PM, Sven Kieske wrote:
Hi,
I'm a little surprised by this development technique.
its not a development technique. its a bug in upgrade or export/import of the
change to the much more powerful config file based OsInfo
ignore the link :)
so searching for this error I hit an old bug and it seemed to be an
issue between libvirt/sanlock.
https://bugzilla.redhat.com/show_bug.cgi?id=828633
are you using latest packages?
On 01/03/2014 02:15 PM, Albl, Oliver wrote:
Dafna,
Libvirtd.log shows no errors,
I installed both hosts using the oVirt Node ISO image:
OS Version: oVirt Node - 3.0.3 - 1.1.fc19
Kernel Version: 3.11.9 - 200.fc19.x86_64
KVM Version: 1.6.1 - 2.fc19
LIBVIRT Version: libvirt-1.1.3.1-2.fc19
VDSM Version: vdsm-4.13.0-11.fc19
Thanks,
Oliver
-Ursprüngliche Nachricht-
Von:
Hi,
I got some questions regarding the MAC-Range in the engine
and how to utilize the set custom mac feature via API:
We want to set a custom MAC per VM via REST-API (JSON)
The RSDL tells me, that this should be possible in general.
However, I have two questions:
Must the specified custom MAC
ok, let's try to zoom in on the issue...
can you run vm's on the first host or do you have issues only on the
second host you added?
can you run on both hosts?
# egrep -v ^# /etc/libvirt/qemu-sanlock.conf
can you run yum update on one of the hosts and see if there are newer
packages?
Dafna,
yes, the VM starts on the first node, the issues are on the second node only.
/etc/libvirt/qemu-sanlock.conf is identical on on both nodes:
auto_disk_leases=0
require_lease_for_disks=0
yum updates reports Using yum is not supported...
Thanks,
Oliver
-Ursprüngliche Nachricht-
On 03.01.2014 13:45, Dafna Ron wrote:
yes, there are bugs reported in openstack for the same issue on
qemu-kvm:
https://bugzilla.redhat.com/show_bug.cgi?id=1027074
https://bugzilla.redhat.com/show_bug.cgi?id=1016896
Hi and thanks,
I cannot access
Redirecting to /bin/systemctl reconfigure vdsmd.service
Unknown operation 'reconfigure'.
... seems to me, I should get rid of the ovirt-node iso installation and move
to a rpm based install?
Thanks,
Oliver
-Ursprüngliche Nachricht-
Von: Dafna Ron [mailto:d...@redhat.com]
Gesendet:
:) no, there are just different ways of dealing with things... don't
give up now.
lets try to re-install the host, perhaps the original issue cased a
configuration problem and a re-install will solve it...
On 01/03/2014 02:56 PM, Albl, Oliver wrote:
Redirecting to /bin/systemctl reconfigure
can you run:
service vdsmd reconfigure on the second host?
On 01/03/2014 02:43 PM, Albl, Oliver wrote:
Dafna,
yes, the VM starts on the first node, the issues are on the second node only.
/etc/libvirt/qemu-sanlock.conf is identical on on both nodes:
auto_disk_leases=0
- Original Message -
From: Oliver Albl oliver.a...@fabasoft.com
To: d...@redhat.com
Cc: users@ovirt.org
Sent: Friday, January 3, 2014 4:56:33 PM
Subject: Re: [Users] Host cannot access storage domains
Redirecting to /bin/systemctl reconfigure vdsmd.service
Unknown operation
On 01/03/2014 02:43 PM, Nux! wrote:
On 03.01.2014 13:45, Dafna Ron wrote:
yes, there are bugs reported in openstack for the same issue on
qemu-kvm:
https://bugzilla.redhat.com/show_bug.cgi?id=1027074
https://bugzilla.redhat.com/show_bug.cgi?id=1016896
Hi and thanks,
I cannot access
On 03.01.2014 15:17, Dafna Ron wrote:
On 01/03/2014 02:43 PM, Nux! wrote:
On 03.01.2014 13:45, Dafna Ron wrote:
yes, there are bugs reported in openstack for the same issue on
qemu-kvm:
https://bugzilla.redhat.com/show_bug.cgi?id=1027074
https://bugzilla.redhat.com/show_bug.cgi?id=1016896
On Fri, Jan 03, 2014 at 01:34:39PM +, Nux! wrote:
Hello,
I used qemu-img-rhev-0.12.1.2-2.355.el6 successfully with -s
parameter, but now qemu-img-rhev-0.12.1.2-2.415.el6 (latest atm)
errors out with:
convert: invalid option -- 's'
Could you provide more context, preferably with the
On 03.01.2014 16:29, Dan Kenigsberg wrote:
On Fri, Jan 03, 2014 at 01:34:39PM +, Nux! wrote:
Hello,
I used qemu-img-rhev-0.12.1.2-2.355.el6 successfully with -s
parameter, but now qemu-img-rhev-0.12.1.2-2.415.el6 (latest atm)
errors out with:
convert: invalid option -- 's'
Could you
Do you happen to notice what is consuming CPU?
When I check with top, glusterfs and glusterfsd are the only process who
use a significant amount of CPU. Load average is between 5 and 6, and I
don't have any started VM.
Since the same cluster
does both virtualization and storage, a GigE
When I try to activate a host to the engine I get the error non responsive.
I can ping the hosts but I cant connect with ssh.
oVirt Engine Version: 3.3.2-1.el6
ovirt-node-iso-3.0.3-1.1.vdsm.fc19
--
Zach Underwood (RHCE,RHCSA,RHCT,UACA)
My website http://zachunderwood.me
My photos
check iptables.
in any case, you have a communication problem between the engine and the
hosts.
when engine cannot get status on the vdsm, hosts will move to
non-responsive.
On 01/03/2014 06:32 PM, Zach Underwood wrote:
When I try to activate a host to the engine I get the error non
I ran iptables -F on the engine and host no luck. The engine and the two
hosts are on the same /24 layer 2 network. I can ping both ways.
On Fri, Jan 3, 2014 at 1:33 PM, Dafna Ron d...@redhat.com wrote:
check iptables.
in any case, you have a communication problem between the engine and the
Here are the two errors from engine.log
2014-01-03 13:40:19,348 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
(DefaultQuartzScheduler_Worker-78) Command GetCapabilitiesVDS execution
failed. Exception: VDSNetworkException: java.net.ConnectException:
Connection refused
Zach,
I had a similar problem. I temporarily disabled SELinux on the hosts using
setenforce 0. Let me know if this helps.
All the best,
Oliver
Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von
Zach Underwood
Gesendet: Freitag, 03. Jänner 2014 19:32
An:
disable slinux=no change
On Fri, Jan 3, 2014 at 1:51 PM, Albl, Oliver oliver.a...@fabasoft.comwrote:
Zach,
I had a similar problem. I temporarily disabled SELinux on the hosts
using “setenforce 0”. Let me know if this helps.
All the best,
Oliver
*Von:* users-boun...@ovirt.org
what do you mean you don't have vdsm service?
did your host installation succeed?
On 01/03/2014 06:44 PM, Zach Underwood wrote:
Here are the two errors from engine.log
2014-01-03 13:40:19,348 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
after reading logs on the node I found this
vdsm vds error xml-rpc handler exception
I installed the node from ISO named ovirt-node-iso-3.0.3-1.1.vdsm.fc19
On Fri, Jan 3, 2014 at 1:55 PM, Zach Underwood zunder1...@gmail.com wrote:
disable slinux=no change
On Fri, Jan 3, 2014 at 1:51 PM,
is the service up?
if vdsm is down or not installed than the engine will set host status as
non-responsive.
it seems as if there might have been an error during the host
installation? please look at the engine log and you should also have
deployment logs and see if everything was successful.
oh! and Oliver had issues before which were solved by a reboot of the
host - so were they rebooted after the installation?
On 01/03/2014 07:03 PM, Dafna Ron wrote:
is the service up?
if vdsm is down or not installed than the engine will set host status
as non-responsive.
it seems as if there
I restarted the node and the engine and no change. Here is a list on the
services on the node(sorry for the screenshot I am using idrac)
[image: Inline image 1]
On Fri, Jan 3, 2014 at 2:04 PM, Dafna Ron d...@redhat.com wrote:
oh! and Oliver had issues before which were solved by a reboot of
please re-install the hosts - I think your installation must have failed.
On 01/03/2014 07:18 PM, Zach Underwood wrote:
I restarted the node and the engine and no change. Here is a list on
the services on the node(sorry for the screenshot I am using idrac)
Inline image 1
On Fri, Jan 3,
Hi. I need some help to troubleshoot this. I can't find a log showing any hint
for me to go forward with it.
Any help is appreciated.
Will
Hi,
Running oVirt 3.3.2-1.el6 on CentOS 6.5
I have oVirt installed on a test host (ovirt1) and two test visualization
hosts (onode1,
On Wed, Dec 25, 2013 at 1:00 AM, Yaniv Dary wrote:
Hi,
We have found a few blockers on the setup of dwh and reports.
We hope to resolve the issues in the next few days. If you restore your
environment using the backups, you will be able to upgrade.
I've put a note to let you know when new
I've run into another issue with Ovirt 3.3.2.
We have a 2 node VM cluster with Fibre Channel storage. After upgrade
everything to FC 19 and installing Ovirt 3.3 from scratch one of the
nodes has network issues.
The issue is that when we start a VM on the node, the VM cannot access
the network.
Hello All,
A little bit ago I wrote an email about network issues I was having.
I found the problem...
On the VM host, I had a bond set up between two network interfaces. The
bond mode was set to mode 1 (active/passive).
However when I look at the bond on the box, I get this:
[root@node02
46 matches
Mail list logo