Re: [ovirt-users] IO errors when adding new disk on iSCSI storage

2014-05-15 Thread Morten A. Middelthon

On 13. mai 2014 10:09, Morten A. Middelthon wrote:

Hi,

I have a new oVirt setup which is giving me some headache. I have one
administration server running on CentOS 6.5, and two hosts also running
CentOS 6.5. Storage is running on both NFS and iSCSI, but iSCSI is the
preferred storage, running on a HP LeftHand server.




Anyone with suggestions or ideas on this problems?


with regards,
Morten
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] IO errors when adding new disk on iSCSI storage

2014-05-15 Thread Morten A. Middelthon

On 13. mai 2014 10:09, Morten A. Middelthon wrote:

Hi,

I have a new oVirt setup which is giving me some headache. I have one
administration server running on CentOS 6.5, and two hosts also running
CentOS 6.5. Storage is running on both NFS and iSCSI, but iSCSI is the
preferred storage, running on a HP LeftHand server.




Anyone with any suggestions or input on this problem?

with regards,
Morten
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] IO errors when adding new disk on iSCSI storage

2014-05-15 Thread Morten A. Middelthon

On 16. mai 2014 04:45, Trey Dockendorf wrote:

A colleague of mine has run into issues doing Linux (EL6.5) iSCSI over
bonded interfaces.  The solution he found was to abandon bonding and
instead use multiple interfaces and multipath on the iscsi initiators.
I can't provide details yet as this is all second hand knowledge.  The
errors you posted are almost identical to what he faced.


Thanks for your input. The strange thing is that the existing iSCSI 
disks on the very same LUN works without any issues. The problem only 
seems to appear when I add a new disk to a running VM.


To properly test this I probably have to add another hypervisor host 
without bonding, as my current hypervisor hosts are in a production 
environment


with regards,

--
Morten A. Middelthon
Email: mor...@flipp.net
Phone: +47 907 83 708
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] IO errors when adding new disk on iSCSI storage

2014-05-15 Thread Morten A. Middelthon

On 15. mai 2014 11:58, Dafna Ron wrote:

ovirt does not pause the vm for ENOSpace, if a vm is pause for this
reason it would be done by qemu.

The logs you attached show no issues.
can you please attach the vm log and libvirt logs?
Also, can you please try the same test on a prealloacted disk?


Thanks, I will first try to add a preallocated disk.

Syslog on the vm did not show anything related, but I included the dmesg 
output in my original post


with regards,

--
Morten A. Middelthon
Email: mor...@flipp.net
Phone: +47 907 83 708
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] IO errors when adding new disk on iSCSI storage

2014-05-15 Thread Morten A. Middelthon

Hi,

I just re-ran the test with adding a preallocated disk, and the problem 
did _not_ appear. I tried a few times to write large files with dd, but 
the vm continued to run without problems


with regards,

--
Morten A. Middelthon
Email: mor...@flipp.net
Phone: +47 907 83 708
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] IO errors when adding new disk on iSCSI storage

2014-05-16 Thread Morten A. Middelthon

On 16. mai 2014 15:04, Dafna Ron wrote:

adding federico since I think he can probably add more info here.

when we use thin provisionining we have to extend the disk during
writing (it's set to do that every 2GB I think).
during extend the vm pauses and resumes.

However, this action should not be noticeable by the vm user.

Does the vm pause and resumes or pauses completely? is it noticeable by
the vm user?


Hi,

the vm pauses completely, and I can't resume it without 
deactivating/disconnecting the new disk


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


Re: [ovirt-users] IO errors when adding new disk on iSCSI storage

2014-05-21 Thread Morten A. Middelthon

Hi list,

I just tried this again with preallocated disk, otherwise the exact same 
procedure as described in my original post. No problems at all so far


with regards,

--
Morten A. Middelthon
Email: mor...@flipp.net
Phone: +47 907 83 708
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Strange disk behaviour within VMs

2015-09-24 Thread Morten A. Middelthon

Hi,

last Sunday I experienced a power outage with one of my two oVirt 
hypervisors. After power was restored I experienced some weirdness:


- on one of the VMs running on this hypervisor the boot disk changed, so 
it was no longer able to boot. Looking at the console the VM would hang 
on "Booting from hard disk". After I noticed that the wrong virtual disk 
was marked as OS/bootable I got it booting again after correcting it to 
the proper boot disk. This was done from the oVirt management server.


- on another VM I tried today to add another virtual disk to expand a 
LVM volume. In dmesg I can see the new device:

[17167560.005768]  vdc: unknown partition table
However, when I tried to run pvcreate I got an error message saying that 
this was already marked as an LVM disk, and then running pvs give me the 
following error:


# pvs
  Couldn't find device with uuid 7dDcyq-TZ6I-96Im-lfjL-cTUv-nff1-B11Mm7.
  PV VG  Fmt  Attr PSizePFree
  /dev/vda5  rit-kvm-ssweb02 lvm2 a--59.76g0
  /dev/vdb1  vg_syncsharelvm2 a--   500.00g0
  /dev/vdc1  VG_SYNCSHARE01  lvm2 a--   400.00g0
  unknown device VG_SYNCSHARE01  lvm2 a-m  1024.00g0

As you can see there's already a PV called /dev/vdc1, as well another 
one named "unknown device". These two PVs belong to a VG that does NOT 
belong to this VM, VG_SYNCSHARE01. The uuids for these two PVs are:


--- Physical volume ---
  PV Name   unknown device
  VG Name   VG_SYNCSHARE01
  PV Size   1024.00 GiB / not usable 3.00 MiB
  Allocatable   yes (but full)
  PE Size   4.00 MiB
  Total PE  262143
  Free PE   0
  Allocated PE  262143
  PV UUID   7dDcyq-TZ6I-96Im-lfjL-cTUv-nff1-B11Mm7

  --- Physical volume ---
  PV Name   /dev/vdc1
  VG Name   VG_SYNCSHARE01
  PV Size   400.00 GiB / not usable 3.00 MiB
  Allocatable   yes (but full)
  PE Size   4.00 MiB
  Total PE  102399
  Free PE   0
  Allocated PE  102399
  PV UUID   oKSDoo-3pxU-0uue-zQ0H-kv1N-lyPa-P2M2FY

The two PVs which doesn't belong on this VM actually belongs to a 
totally different VM.


On VM number two:

# pvdisplay
  --- Physical volume ---
  PV Name   /dev/vdb1
  VG Name   VG_SYNCSHARE01
  PV Size   1024.00 GiB / not usable 3.00 MiB
  Allocatable   yes (but full)
  PE Size   4.00 MiB
  Total PE  262143
  Free PE   0
  Allocated PE  262143
  PV UUID   7dDcyq-TZ6I-96Im-lfjL-cTUv-nff1-B11Mm7

  --- Physical volume ---
  PV Name   /dev/vdd1
  VG Name   VG_SYNCSHARE01
  PV Size   400.00 GiB / not usable 3.00 MiB
  Allocatable   yes (but full)
  PE Size   4.00 MiB
  Total PE  102399
  Free PE   0
  Allocated PE  102399
  PV UUID   oKSDoo-3pxU-0uue-zQ0H-kv1N-lyPa-P2M2FY

As you can see, same uuid and VG name, but two different VMs.

My setup:
oVirt manager: oVirt 3.5 running on CentOS 6.7
oVirt hypervisors: two oVirt 3.5 servers running on CentOS 6.7

During the time of the power outage mentioned earlier I was running 
oVirt 3.4, but I upgraded today and rebooted the manager and both 
hypervisors, but NOT the VMs.


Virtual machines:
Debian wheezy 7.9 x86_64

Storage:
HP LeftHand iSCSI

I have tried to locate error messages in the logs which can be related 
to this behaviour, but so far no luck :(


--
Morten A. Middelthon
Email: mor...@flipp.net

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


[ovirt-users] Restoring oVirt after hardware crash

2016-04-07 Thread Morten A. Middelthon

Hi,

the machine running my oVirt Engine administrator recently died on me. I 
have been able to get most of it back up and running again on a new 
virtual machine with CentOS 6.x in another virtual environment. The 
local postgresql database is running, and I can login via the web 
interface. All my VMs, storages, networks and hosts are visible, but 
marked as being offline/non responsive. Is there a way I can re-add or 
re-enable my existing hosts on this restored manager?


with regards,

--
Morten A. Middelthon
Email: mor...@flipp.net

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


Re: [ovirt-users] Restoring oVirt after hardware crash

2016-04-08 Thread Morten A. Middelthon

On 07. april 2016 19:00, Oved Ourfali wrote:

Hard to help without the logs.
Can you attach the engine log and server log?


Yep, forgot the logs... From the engine.log this seems relevant:

2016-04-08 09:30:14,140 ERROR 
[org.ovirt.engine.core.vdsbroker.HostMonitoring] 
(DefaultQuartzScheduler_Worker-23) [] Failure to refresh Vds runtime 
info: sun.security.provider.certpath.SunCertPathBuilderException: unable 
to find valid certification path to requested target


and


2016-04-08 09:30:14,139 ERROR 
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] 
(DefaultQuartzScheduler_Worker-23) [] Command 
'GetCapabilitiesVDSCommand(HostName = RIT-D2-SSM01, 
VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', 
hostId='9af028a1-35ec-4b10-96d3-6dda6e7061e5', 
vds='Host[RIT-D2-SSM01,9af028a1-35ec-4b10-96d3-6dda6e7061e5]'})' 
execution failed: 
sun.security.provider.certpath.SunCertPathBuilderException: unable to 
find valid certification path to requested target


The hosts are called RIT-D1-SSM01 and RIT-D2-SSM01

I have uploaded the logs to:

http://flipp.net/ovirt/

The engine.log is quite large, so I've put the last 1000 lines of it into:

http://flipp.net/ovirt/engine.log.tail

--
Morten A. Middelthon
Email: mor...@flipp.net

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


Re: [ovirt-users] Restoring oVirt after hardware crash

2016-04-08 Thread Morten A. Middelthon

Den 08.04.2016 19:35, skrev Adam Litke:

Looks like the client certificates need to be refreshed on your hosts.
From the UI, select a host and choose the reinstall option.  This will
reinstall the certificates and your hosts should be able to activate.


I assume this won't affect any running VMs on the hosts?

--
Morten A. Middelthon
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users