On 01/20/2016 04:21 PM, Gordon Messmer wrote:
On 01/20/2016 09:55 AM, Steve Clark wrote:
Any ideas?
IP forwarding needs to be enabled, and you also need rules in your
FORWARD chain to allow the packets.
Thanks, but forwarding is turned on and my FW rules are empty.
Chain INPUT (policy
On Thu, Jan 21, 2016 at 12:01 PM, Peter wrote:
> On 15/01/16 05:57, George Dunlap wrote:
>> As mentioned yesterday, Xen 4.6 packages are now available for
>> testing. These also include an update to libvirt 1.3.0, in line with
>> what's available for CentOS 7. Please
Well when the last upgrade 4.2 > 4.4 went live and XM was disabled by
default it took many hosts down without warning. 4.4 > 4.6 may cause the
same issues. It's a dangerous upgrade for sure. Why can't 4.4 be LTS for
C6? as it's the last build with XM. Any XSA patches should not be hard to
Its my impression that as a general rule from RH once some software has
been released into a major release any further release of that software
does not change major version or fundamental features..
For C6 I would argue Xen 4.2 should stay packaged as xen and Xen 4.4 be
packaged as xen44 ...
On 15/01/16 05:57, George Dunlap wrote:
> As mentioned yesterday, Xen 4.6 packages are now available for
> testing. These also include an update to libvirt 1.3.0, in line with
> what's available for CentOS 7. Please test, particularly the upgrade
> if you can, and report any problems here.
Per
This is related to another earlier post regarding "realm discover"
I want to set the timezone to Melbourne/Australia which failed with:
[root@sssd-testing ~]# timedatectl set-timezone Australia/Melbourne
Error getting authority: Error initializing authority: Error calling
StartServiceByName for
On Thu, Jan 21, 2016 at 1:28 PM, Phill Bandelow wrote:
> Well when the last upgrade 4.2 > 4.4 went live and XM was disabled by
> default it took many hosts down without warning. 4.4 > 4.6 may cause the
> same issues. It's a dangerous upgrade for sure. Why can't 4.4 be LTS for
My .02 is to stay the course. As a server admin, I want to be able to type
things like:
yum upgrade php
not
yum upgrade php55-epel-rpmforge-fancy-package
Having to remember all the idiosyncrasies of a system is what causes some type
of major failure in the future whenever (1) you
I am using Xen 4.6.0-8.el7 on CentOS 7 with 3 Linux DomUs. I did have Xen 4.?
on CentOS 6.5 on my previous system. I installed using yum install
centos-release-xen.
On shutting down the Hypervisor it used to wait for the DomUs to shut down
gracefully (one can take a minute or more), then on
Try this:
systemctl start xendomains.service
systemctl enable xendomains.service
On 21 January 2016 at 08:48, Francis Greaves wrote:
> I am using Xen 4.6.0-8.el7 on CentOS 7 with 3 Linux DomUs. I did have Xen
> 4.? on CentOS 6.5 on my previous system. I installed using
Hi Francis.
Personally I would gracefully shutdown all the VM’s first, before attempting to
shutdown the xen hypervisor.
Are you getting any fsck errors when restarting those VM’s?
Kind Regards,
Keith
On 21 Jan 2016, at 08:48, Francis Greaves wrote:
> I am using Xen
On 01/21/2016 08:02 AM, George Dunlap wrote:
> On Thu, Jan 21, 2016 at 1:28 PM, Phill Bandelow wrote:
>> Well when the last upgrade 4.2 > 4.4 went live and XM was disabled by
>> default it took many hosts down without warning. 4.4 > 4.6 may cause the
>> same issues. It's a
Hi all,
I have installed a CentOS6 lxc guest under a Debian 8.x LXC host. All
it is working ok but I can't change the hostname for the centos6 lxc
container (it is using the same hostname from Debian host). I have
modifyed HOSTNAME under /etc/sysconfig/network and /etc/hosts file,
but it doesn't
On Thu, Jan 21, 2016 at 3:39 PM, Johnny Hughes wrote:
> On 01/21/2016 09:29 AM, Johnny Hughes wrote:
>> This is a community SIG .. and xenproject.org does NOT release XSAs for
>> 4.2. The goal of Xen4centOS was to use an upstream LTS kernel and
>> update those as required to
On 01/21/2016 09:29 AM, Johnny Hughes wrote:
> This is a community SIG .. and xenproject.org does NOT release XSAs for
> 4.2. The goal of Xen4centOS was to use an upstream LTS kernel and
> update those as required to stay on an LTS. Also to do every second
> point release of xen (ie, 4.2, 4.4,
This is a community SIG .. and xenproject.org does NOT release XSAs for
4.2. The goal of Xen4centOS was to use an upstream LTS kernel and
update those as required to stay on an LTS. Also to do every second
point release of xen (ie, 4.2, 4.4, 4.6). All so we are longer term
than upstream, BUT we
How does the ifenslave command relate to "normal" network slave
configuration in /etc/sysconfig/network-scripts? Does config-file-based
setup use ifenslave or is it more complicated than that? ThanksNick
___
CentOS mailing list
CentOS@centos.org
I am happy to announce the General Availability of Gluster 3.6 and 3.7
for CentOS 6 on x86_64. These packages are following the upstream
Gluster Community releases, with one minor update for each version per
month.
Users of CentOS 6 can now simply install Gluster with only these two
commands:
On 01/20/2016 01:37 AM, Alice Wonder wrote:
I'm trying to find where / how to use sha256 when I sign packages
but I
am not having much luck. Closest I have found is this :
https://fedoraproject.org/wiki/RPM_file_format_changes_to_support_SHA-256
This thread has been a whole bunch of
On 01/20/2016 01:43 PM, Chris Murphy wrote:
On Wed, Jan 20, 2016, 7:17 AM Lamar Owen wrote:
The standard Unix way of refreshing the disk contents is with
badblocks' non-destructive read-write test (badblocks -n or as the
-cc option to e2fsck, for ext2/3/4 filesystems).
On 01/21/2016 09:52 AM, George Dunlap wrote:
> On Thu, Jan 21, 2016 at 3:39 PM, Johnny Hughes wrote:
>> On 01/21/2016 09:29 AM, Johnny Hughes wrote:
>>> This is a community SIG .. and xenproject.org does NOT release XSAs for
>>> 4.2. The goal of Xen4centOS was to use an
On Thu, Jan 21, 2016 at 4:17 PM, Alvin Starr wrote:
> My comment was targeted more at naming than support.
>
> I appreciate that there are vanishingly few resources to throw at support.
>
> I am glad to see any xen support for C7 and am thankful of all those who are
> putting in
Greetings,
- Original Message -
> I have installed a CentOS6 lxc guest under a Debian 8.x LXC host.
> All it is working ok but I can't change the hostname for the centos6 lxc
> container (it is using the same hostname from Debian host). I have
> modifyed HOSTNAME under
On 01/21/2016 03:49 AM, Steve Clark wrote:
Thanks, but forwarding is turned on and my FW rules are empty.
Try specifying the physical device the packets are going out, rather
than the bridge, in your postrouting rule.
Apparently you also need an ebtables rule to prevent the return packets
On Thu, Jan 21, 2016 at 1:28 PM, Phill Bandelow wrote:
> Well when the last upgrade 4.2 > 4.4 went live and XM was disabled by
> default it took many hosts down without warning. 4.4 > 4.6 may cause the
> same issues. It's a dangerous upgrade for sure. Why can't 4.4 be LTS for
CentOS Errata and Security Advisory 2016:0049 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0049.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
CentOS Errata and Security Advisory 2016:0054 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0054.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
CentOS Errata and Security Advisory 2016:0054 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0054.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
On 01/21/2016 09:23 AM, Gordon Messmer wrote:
%_gpg_digest_algo sha256
Thank you! That worked beautifully.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Thanks a million for that.
All working fine now.
Ragards
From: "Phill Bandelow"
To: "Francis Greaves" , "centos-virt"
Sent: Thursday, 21 January, 2016 09:20:40
Subject: Re: [CentOS-virt] DomU Guests not shutting down nicely
CentOS Linux release 7.2.1511 (Core)
Hi,
Last night our CentOS 7 server rebooted. Seemingly it's a very clean reboot. I
can't find a shred of
evidence as to why it happened though.
Things I've checked:
* sa reports
* /var/log/{messages,secure,dmesg,cron}
* /var/log/audit/audit.log
* lastlog
Try use memtest this problem crash memóry on segment. Good luck
Em 21/01/2016 20:28, "Tom Robinson" escreveu:
> CentOS Linux release 7.2.1511 (Core)
>
> Hi,
>
> Last night our CentOS 7 server rebooted. Seemingly it's a very clean
> reboot. I can't find a shred of
>
Hey list,
I got a problem with a Gigabyte radeon HD 2600 pro card regarding my multi head
setup with . This card has two DVI connectors. The second monitor has the state
of being disconnected after startup (xrandr -q). When I disconnect it and
reconnect sometimes the screen comes up and the
CentOS Errata and Security Advisory 2016:0050 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0050.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
CentOS Errata and Security Advisory 2016:0053 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0053.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
On 22/01/16 01:32, George Dunlap wrote:
> 1. In the Xen 4.4 packages (first released October 2014), xend was
> disabled by default; so anyone using xend at the moment has already
> manually intervened to enable deprecated functionality
Xen4CentOS was first available in CentOS 6.4 with Xen 4.2, so
On 20/01/2016 19:55, Steve Clark wrote:
So I want traffic coming in eth5 with 10.10.0.x addresses to be source
natted to 192.168.100.3.
But my iptables nat statement never gets hit.
Chain POSTROUTING (policy ACCEPT 172 packets, 31384 bytes)
pkts bytes target prot opt in out source
Everyone,
I have a problem I have been chasing for about three weeks and only
occurred after cups was updated with cups-1.6.3-22.el7. I would be
interested as to whether any one else has had this problem, and would
entertain suggestions as to how I can debug the problem.
My Centos 5 server is a
http://unix.stackexchange.com/questions/157539/cant-load-zfs-kernel-module-on-fedora-with-secure-boot-required-key-not-avai
So, module must be signed with trusted key, or else it just fails.
Eero
22.1.2016 9.34 ap. "wk" <304702...@qq.com> kirjoitti:
> Hi,
> another question.With secure boot
On 01/21/2016 09:47 PM, wk wrote:
How to check/get UEFI information by shell/bash terminal ? example:if
UEFI is enabled? if secure boot is enabled?
Systems that boot via UEFI will have /sys/firmware/efi.
You may have access to your secure boot setting in
/sys/firmware/efi/efivars/, or
Hi,
another question.With secure boot on,
I make a kernel module test.ko
Then insmod test.ko:
[root@localhost linux]# insmod test.ko
insmod: ERROR: could not insert module test.ko: Required key not available
How can I sign my test.ko for CentOS7.1?
If I set secure
Hi,
CentOS7.1, Dell PowerEdge R730xd.
How to check/get UEFI information by shell/bash terminal ? example:if UEFI
is enabled? if secure boot is enabled?
Thanks.
___
CentOS mailing list
CentOS@centos.org
Hi,
Read this page:
https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface
2016-01-22 7:47 GMT+02:00 wk <304702...@qq.com>:
> Hi,
>
>CentOS7.1, Dell PowerEdge R730xd.
>
>How to check/get UEFI information by shell/bash terminal ? example:if
> UEFI is enabled? if
On 01/21/2016 04:32 AM, George Dunlap wrote:
> I'm a developer, not a server admin, so I can't gauge how important
> this issue is. Before making such a change, I'd like to hear opinions
> from other people in the community about how important (or not) it is
> to avoid breaking xm, given the
44 matches
Mail list logo