Hi,
with xfs Wolfgang -----Ursprüngliche Nachricht----- Von: Yaniv Kaul <[email protected]> Gesendet: Don 25 August 2016 13:01 An: Wolfgang Bucher <[email protected]> Betreff: Re: [ovirt-users] Problem starting VMs On Wed, Aug 24, 2016 at 7:37 PM, Wolfgang Bucher <[email protected] <mailto:[email protected]> > wrote: Hello using the kernel-lt from elrepo solves all problems!! With XFS, or EXT4? Maybe it is a problem with the current kernel from centos ?? It's an XFS issue, I think it'll be fixed for 7.3. Y. Thanks Wolfgang -----Ursprüngliche Nachricht----- Von: Wolfgang Bucher <[email protected] <mailto:[email protected]> > Gesendet: Die 23 August 2016 20:14 An: Yaniv Kaul <[email protected] <mailto:[email protected]> > CC: [email protected] <mailto:[email protected]> ([email protected] <mailto:[email protected]> ) <[email protected] <mailto:[email protected]> > Betreff: Re: [ovirt-users] Problem starting VMs Hello i just changed xfs to ext4 and defragmantion is much better then before, i will also try kernel lts from elrepo and test it again. Thanks Wolfgang -----Ursprüngliche Nachricht----- Von: Yaniv Kaul <[email protected] <mailto:[email protected]> > Gesendet: Die 23 August 2016 19:46 An: Wolfgang Bucher <[email protected] <mailto:[email protected]> > CC: Charles Gruener <[email protected] <mailto:[email protected]> > Betreff: Re: AW: [ovirt-users] Problem starting VMs On Aug 23, 2016 7:33 PM, "Wolfgang Bucher" <[email protected] <mailto:[email protected]> > wrote: > > Hello > > > I am using local storage with adaptec raid controller, disk format is raw Raw is always raw-sparse, so that may explain this somehow, yet still odd that Windows installation would cause so much fragmentation. I wonder if using the discard hook (and IDE or virtio-scsi) would help - or perhaps using a qcow2 makes more sense (create a snapshot right after disk creation for example). > > > image: e4d797d1-5719-48d0-891e-a36cd4a79c33 > file format: raw > virtual size: 50G (53687091200 bytes) > disk size: 8.5G > > > this is a fresh installation of W2012 after installation i got with xfs_db > -c frag -r /dev/sdb1: > > aktuell 407974, ideal 35, Unterteilungsfaktor 99,99% And the XFS formatted with default parameters? Y. > > > Thanks > > > Wolfgang > > >> -----Ursprüngliche Nachricht----- >> Von: Yaniv Kaul <[email protected] <mailto:[email protected]> > >> Gesendet: Die 23 August 2016 17:56 >> An: Wolfgang Bucher <[email protected] >> <mailto:[email protected]> > >> CC: Michal Skrivanek <[email protected] >> <mailto:[email protected]> >; [email protected] >> <mailto:[email protected]> ([email protected] <mailto:[email protected]> ) >> <[email protected] <mailto:[email protected]> > >> >> Betreff: Re: [ovirt-users] Problem starting VMs >> >> >> >> On Tue, Aug 23, 2016 at 6:40 PM, Wolfgang Bucher >> <[email protected] <mailto:[email protected]> > >> wrote: >>> >>> Hello >>> >>> >>> in var log messages i get following : >>> >>> >>> kernel: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250) >>> >>> >>> I have this problem on 4 different hosts. >>> >>> >>> This happens during copying files from network to a thin provisioned disk, >>> no problems with preallocated disks. >> >> >> What kind of storage are you using? local storage? Even though, it makes >> little sense to me - the disk is a qcow2 disk, which shouldn't be very >> fragmented as you might think (qcow2 grows in 64K chunks). >> It may grow and grow and grow (until you sparsify it), but that's not going >> to cause fragmentation. What causes it to be fragmented? Perhaps the >> internal qcow2 mapping is quite fragmented? >> Y. >> >>> >>> >>> Thanks >>> >>> Wolfgang >>> >>> >>>> -----Ursprüngliche Nachricht----- >>>> Von: Michal Skrivanek <[email protected] >>>> <mailto:[email protected]> > >>>> Gesendet: Die 23 August 2016 17:11 >>>> An: Wolfgang Bucher <[email protected] >>>> <mailto:[email protected]> > >>>> CC: Milan Zamazal <[email protected] <mailto:[email protected]> >; >>>> [email protected] <mailto:[email protected]> ([email protected] >>>> <mailto:[email protected]> ) <[email protected] <mailto:[email protected]> > >>>> Betreff: Re: [ovirt-users] Problem starting VMs >>>> >>>> >>>>> On 23 Aug 2016, at 11:06, Wolfgang Bucher <[email protected] >>>>> <mailto:[email protected]> > wrote: >>>>> >>>>> Thank's >>>>> >>>>> but what do you mean with "initialization is finished” >>>> >>>> >>>> until it gets from WaitForLaunch to PoweringUp state, effectively until >>>> the qemu process properly starts up >>>> >>>>> >>>>> sometimes the vm crashes while copying files! >>>> >>>> >>>> when exactly? Can you describe exactly what you are doing and what is >>>> reported as a reason for crash. When exactly does it crash and how? >>>> >>>> Thanks, >>>> michal >>>> >>>>> >>>>> >>>>> >>>>> Wolfgang >>>>> >>>>> >>>>>> -----Ursprüngliche Nachricht----- >>>>>> Von: Milan Zamazal <[email protected] <mailto:[email protected]> > >>>>>> Gesendet: Die 23 August 2016 16:59 >>>>>> An: Wolfgang Bucher <[email protected] >>>>>> <mailto:[email protected]> > >>>>>> CC: [email protected] <mailto:[email protected]> ([email protected] >>>>>> <mailto:[email protected]> ) <[email protected] <mailto:[email protected]> > >>>>>> Betreff: Re: AW: Problem starting VMs >>>>>> >>>>>> Wolfgang Bucher <[email protected] >>>>>> <mailto:[email protected]> > writes: >>>>>> >>>>>> > the problem is "waiting for launch" takes up to 20 min. >>>>>> > >>>>>> > >>>>>> > I did a lot of tests with some vm's and th problem is: >>>>>> > >>>>>> > >>>>>> > 1. create a win2012 server >>>>>> > >>>>>> > 2. attache a new disk (thin provision) >>>>>> > >>>>>> > 3. fill the disk from network share with about 100G >>>>>> > >>>>>> > 4. shutdown the vm >>>>>> > >>>>>> > 5. reboot host and try starting the vm (takes a lot of time until >>>>>> > launch) >>>>>> > >>>>>> > >>>>>> > >>>>>> > It's because of a high fragmented filessystem >>>>>> >>>>>> I see, thank you for the explanation. In such a case, it may take a lot >>>>>> of time before all the initialization is finished. >>>>>> >>>>>> Regards, >>>>>> Milan >>>>> >>>>> _______________________________________________ >>>>> Users mailing list >>>>> [email protected] <mailto:[email protected]> >>>>> http://lists.ovirt.org/mailman/listinfo/users >>>>> <http://lists.ovirt.org/mailman/listinfo/users> >>>> >>>> >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] <mailto:[email protected]> >>> http://lists.ovirt.org/mailman/listinfo/users >>> <http://lists.ovirt.org/mailman/listinfo/users> >>> >> _______________________________________________ Users mailing list [email protected] <mailto:[email protected]> http://lists.ovirt.org/mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users> _______________________________________________ Users mailing list [email protected] <mailto:[email protected]> http://lists.ovirt.org/mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
