Displaying 20 results from an estimated 300 matches similar to: "kernel-4.9.37-29.el7 (and el6)"
2017 Jul 19
2
kernel-4.9.37-29.el7 (and el6)
On 07/19/2017 04:27 AM, Piotr Gackiewicz wrote:
> On Mon, 17 Jul 2017, Johnny Hughes wrote:
>
>> Are the testing kernels (kernel-4.9.37-29.el7 and kernel-4.9.37-29.el6,
>> with the one config file change) working for everyone:
>>
>> (turn off: CONFIG_IO_STRICT_DEVMEM)
>
> Hello.
> Maybe it's not the most appropriate thread or time, but I have been
>
2017 Jul 19
1
kernel-4.9.37-29.el7 (and el6)
On Mon, 17 Jul 2017, Johnny Hughes wrote:
> Are the testing kernels (kernel-4.9.37-29.el7 and kernel-4.9.37-29.el6,
> with the one config file change) working for everyone:
>
> (turn off: CONFIG_IO_STRICT_DEVMEM)
Hello.
Maybe it's not the most appropriate thread or time, but I have been
signalling it before:
4.9.* kernels do not work well for me any more (and for other people
2017 Jul 19
0
kernel-4.9.37-29.el7 (and el6)
On 07/19/2017 09:23 AM, Johnny Hughes wrote:
> On 07/19/2017 04:27 AM, Piotr Gackiewicz wrote:
>> On Mon, 17 Jul 2017, Johnny Hughes wrote:
>>
>>> Are the testing kernels (kernel-4.9.37-29.el7 and kernel-4.9.37-29.el6,
>>> with the one config file change) working for everyone:
>>>
>>> (turn off: CONFIG_IO_STRICT_DEVMEM)
>>
>> Hello.
2017 Jul 20
2
kernel-4.9.37-29.el7 (and el6)
On Wed, 19 Jul 2017, Johnny Hughes wrote:
> On 07/19/2017 09:23 AM, Johnny Hughes wrote:
>> On 07/19/2017 04:27 AM, Piotr Gackiewicz wrote:
>>> On Mon, 17 Jul 2017, Johnny Hughes wrote:
>>>
>>>> Are the testing kernels (kernel-4.9.37-29.el7 and kernel-4.9.37-29.el6,
>>>> with the one config file change) working for everyone:
>>>>
2017 Jul 20
4
kernel-4.9.37-29.el7 (and el6)
On Thu, 20 Jul 2017, Kevin Stange wrote:
> On 07/20/2017 05:31 AM, Piotr Gackiewicz wrote:
>> On Wed, 19 Jul 2017, Johnny Hughes wrote:
>>
>>> On 07/19/2017 09:23 AM, Johnny Hughes wrote:
>>>> On 07/19/2017 04:27 AM, Piotr Gackiewicz wrote:
>>>>> On Mon, 17 Jul 2017, Johnny Hughes wrote:
>>>>>
>>>>>> Are the
2017 Jul 17
0
kernel-4.9.37-29.el7 (and el6)
Hello, is this kernel usable also for KVM or is only for XEN?
S pozdravem Kristi?n Feldsam
Tel.: +420 773 303 353, +421 944 137 535
E-mail.: support at feldhost.cz
www.feldhost.cz - FeldHost? ? profesion?ln? hostingov? a serverov? slu?by za adekv?tn? ceny.
FELDSAM s.r.o.
V rohu 434/3
Praha 4 ? Libu?, PS? 142 00
I?: 290 60 958, DI?: CZ290 60 958
C 200350 veden? u M?stsk?ho soudu v Praze
Banka:
2017 Jul 20
0
kernel-4.9.37-29.el7 (and el6)
On 07/20/2017 05:31 AM, Piotr Gackiewicz wrote:
> On Wed, 19 Jul 2017, Johnny Hughes wrote:
>
>> On 07/19/2017 09:23 AM, Johnny Hughes wrote:
>>> On 07/19/2017 04:27 AM, Piotr Gackiewicz wrote:
>>>> On Mon, 17 Jul 2017, Johnny Hughes wrote:
>>>>
>>>>> Are the testing kernels (kernel-4.9.37-29.el7 and
>>>>>
2017 Jul 24
0
kernel-4.9.37-29.el7 (and el6)
On 07/20/2017 03:14 PM, Piotr Gackiewicz wrote:
> On Thu, 20 Jul 2017, Kevin Stange wrote:
>
>> On 07/20/2017 05:31 AM, Piotr Gackiewicz wrote:
>>> On Wed, 19 Jul 2017, Johnny Hughes wrote:
>>>
>>>> On 07/19/2017 09:23 AM, Johnny Hughes wrote:
>>>>> On 07/19/2017 04:27 AM, Piotr Gackiewicz wrote:
>>>>>> On Mon, 17 Jul
2017 Jun 27
2
4.9.34-29 EL6 and EL7 kernels
OK Guys and Gals,
We have just kicked off a build of the 4.9.34-29 xen kernel on the
Community Build Service for both EL6 and EL7.
This kernel has some important things in it.
1. It has a patch for the stack guard issue (CVE-2017-1000364). Also
the patch for Xen Security fix XSA-216.
See these upstream changelogs for ALL kernel commits from 4.9.31 to 4.9.34:
2016 Aug 29
2
No network using qemu-kvm-ev-2.3.0-31.el7.16.1
Hello, this could be issue with firewall or netfilter on bridge
S pozdravem Kristi?n Feldsam
Tel.: +420 773 303 353
E-mail.: admin at feldhost.cz
www.feldhost.cz - FeldHost poskytuje kvalitn? hostingov? a serverov? slu?by za p??znivou cenu.
FELDSAM s.r.o.
V rohu 434/3
Praha 4 ? Libu?, PS? 142 00
I?: 290 60 958, DI?: CZ290 60 958
C 200350 veden? u M?stsk?ho soudu v Praze
Banka: Fio banka a.s.
2017 Jul 21
0
kernel-4.9.37-29.el7 (and el6)
On 07/20/2017 03:14 PM, Piotr Gackiewicz wrote:
> On Thu, 20 Jul 2017, Kevin Stange wrote:
>
>> On 07/20/2017 05:31 AM, Piotr Gackiewicz wrote:
>>> On Wed, 19 Jul 2017, Johnny Hughes wrote:
>>>
>>>> On 07/19/2017 09:23 AM, Johnny Hughes wrote:
>>>>> On 07/19/2017 04:27 AM, Piotr Gackiewicz wrote:
>>>>>> On Mon, 17 Jul
2016 Aug 28
2
No network using qemu-kvm-ev-2.3.0-31.el7.16.1
Hi all,
To do some tests, I have installed a new CentOS7 host (fully patched) using qemu-kvm-ev-2.3.0-31.el7.16.1 instead of qemu-kvm's default package. And I have problems with network inside my guests.
All guests can ping to CentOS host but nothing more: can't resolv dns names, can access via tcp to other hosts, etc ... Using same config on other CentOS7 host, but using default
2017 Mar 30
3
Network isolation for KVM guests
Hi all,
What options exists under CentOS hosts to work with isolated networks?. For example, on BSD systems it is really trivial. In FreeBSD you can use setfib tools and on OpenBSD it is possible to use rdomain options. In 30 secs it is possible to work with isolated networks and assign process, ip address and routes (hidden from the main route table and ip addresses), etc.
But I can't
2017 May 17
2
4.9 kernel fails to boot because it didn't have the mpt3sas module
Howdy,
I hit a snag trying to install Xen4CentOS on a Supermicro based system
(X9DRD-7LN4F with the Broadcom/LSI 2308 chipset). I spent a few hours on
this today, I'm posting this here in case it helps anyone else and saves
them the frustration I dealt with.
On this system I did a fresh install of CentOS 7, updated it, rebooted it,
then installed Xen.
The system was booting fine using the
2017 Jul 21
0
kernel-4.9.37-29.el7 (and el6)
On 07/21/2017 06:06 AM, Piotr Gackiewicz wrote:
> On Fri, 21 Jul 2017, Johnny Hughes wrote:
>
>>>
>>
>> I will happily create a test kernel with SLAB .. what is your config
>> file diff?
>
> I have just choosed SLAB allocator in menuconfig.
> It has implied several other internal configurations changes.
>
> Overall differencess (config file patch)
2016 Aug 30
0
No network using qemu-kvm-ev-2.3.0-31.el7.16.1
Nop. Problem was with systemd-networkd. Using openvswitch of ifcfg-XXX config files, all works ok without problems.
On Mon 29.Aug'16 at 17:02:03 +0200, Kristi?n Feldsam wrote:
> Hello, this could be issue with firewall or netfilter on bridge
>
> S pozdravem Kristi?n Feldsam
> Tel.: +420 773 303 353
> E-mail.: admin at feldhost.cz
>
> www.feldhost.cz - FeldHost poskytuje
2017 Jun 12
3
xen4centos kernel version / debuginfo
Is there any problem moving to 4.9.31? This contains upstream commits f2e767bb5d6ee0d9 for mpt3sas and
69861e0a52f87333 for dom0 memory mappings.
I am also trying to build a debuginfo package but it's not correct. Specifically I'm able to get vmlinux but the .debug files for modules are
stripped, which isn't right. Does anyone know how to fix this?
I'm also not sure how
2017 Jul 21
3
kernel-4.9.37-29.el7 (and el6)
On Fri, 21 Jul 2017, Johnny Hughes wrote:
>>
>
> I will happily create a test kernel with SLAB .. what is your config
> file diff?
I have just choosed SLAB allocator in menuconfig.
It has implied several other internal configurations changes.
Overall differencess (config file patch) is in attachment.
But my considerations about compiled in PATA etc., instead of modules,
remain
2019 Sep 04
3
Ubuntu Bionic Samba 4.9.13 and 4.10.8 packages online now (amd64/i386)
Hai,
?
If uploaded the Ubuntu Bionic Samba 4.9.13 and 4.10.8 packages.
The Build and Changes logs : http://downloads.van-belle.nl/samba4/Buildlogs/ubuntu/
?
1) Choose http or https for you apt, both work, for https you need to :
apt-get install apt-transport-https
?
2) Import my public key
wget -O - http://apt.van-belle.nl/louis-van-belle.gpg-key.asc | apt-key add -
?
3) (optional) setup a
2017 Apr 14
4
Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.
List moderator: feel free to delete my previous large message with attachments that's in the moderation queue...it's now obsolete anyway.
I have found a fix/workaround for my reboot issues with Xen 4.6.3-12 + Kernel 4.9.13:
Once I finally got serial output all the way through the boot process (xen+dom0) I discovered the stack trace:
[Firmware Bug]: CPU7: APIC id mismatch. Firmware: 0