Ran into a strange issue with XEN on CentOS that I think is specific
to CentOS, which is why I'm starting by posting to this list first,
I'll post on the XEN list depending on responses. My sense is this
issue has something to do with how CentOS handles network setup on
first boot of the XEN
Am Dienstag, den 04.08.2009, 14:43 +0200 schrieb Brett Serkez:
Ran into a strange issue with XEN on CentOS that I think is specific
to CentOS, which is why I'm starting by posting to this list first,
I'll post on the XEN list depending on responses. My sense is this
issue has something to do
Hi,
This commonly happens when you using Xen in the bridged mode (when you
reboot your system the first time, this is default Xen configuration).
You have to change your configuration to routed mode if you want to
prevent that in future.
You can get more info about network in Xen going by links
Brett Serkez wrote on Tue, 4 Aug 2009 08:43:28 -0400:
My understanding of the HWaddr is that the first portion is
manufacturer assigned for uniqueness, I cannot image this NIC
originally had this HWaddr, but I don't know what it originally was.
Indeed, AFAIK all hardware adapters start with
Sergey Smirnov wrote on Tue, 4 Aug 2009 17:14:48 +0400:
This commonly happens when you using Xen in the bridged mode (when you
reboot your system the first time, this is default Xen configuration).
You have to change your configuration to routed mode if you want to
prevent that in future.
On Tue, Aug 4, 2009 at 9:09 AM, Christoph Maserc...@financial.com wrote:
snip
When Xen starts does some trickery with your interfaces. You should see
FE:FF:FF:FF:FF:FF on device peth0 and the real MAC-address on device
eth0.
All Xen vif devices will show also MAC FE:FF:FF:FF:FF:FF. That is
On Tue, Aug 4, 2009 at 12:30 PM, Brett Serkezbser...@gmail.com wrote:
On Tue, Aug 4, 2009 at 9:09 AM, Christoph Maserc...@financial.com wrote:
snip
When Xen starts does some trickery with your interfaces. You should see
FE:FF:FF:FF:FF:FF on device peth0 and the real MAC-address on device
On Aug 4, 2009, at 12:50 PM, Ross Walker rswwal...@gmail.com wrote:
On Tue, Aug 4, 2009 at 12:30 PM, Brett Serkezbser...@gmail.com
wrote:
On Tue, Aug 4, 2009 at 9:09 AM, Christoph Maserc...@financial.com
wrote:
snip
When Xen starts does some trickery with your interfaces. You
should
Maybe because you are looking at the bridge's mac and not the
ethernet's which would be peth0.
No I am not. dmesg shows the kernel messages at boot and it is
looking at the physical device, let's not get distracted, the issue is
clear in this regard. As I previously stated, this happens even
Brett,
I think the following link answers your question about the MAC changes. You
may find more useful links on the resources page of the Running Xen site
http://runningxen.com/resources/.
http://lists.xensource.com/archives/html/xen-users/2006-02/msg00030.html
If you performed a fresh
Brett Serkez wrote:
Maybe because you are looking at the bridge's mac and not the
ethernet's which would be peth0.
No I am not. dmesg shows the kernel messages at boot and it is
looking at the physical device, let's not get distracted, the issue is
clear in this regard. As I
Brett Serkez wrote:
- Investigation concluded the issue was that the HWaddr address of the
physical NIC matched the fabricated HWaddr that XEN uses for most of
its adapters: FE:FF:FF:FF:FF:FF.
I had the same problem after (IIRC) a kernel panic. After a few rounds
of research and ineffective
On Tue, Aug 4, 2009 at 12:30 PM, Brett Serkezbser...@gmail.com wrote:
snip
# Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet
DEVICE=eth1
BOOTPROTO=none
HWADDR=00:40:F4:CE:E6:7B
So now I know what the original MAC address was.
Is it possible for the MAC address to be changed
13 matches
Mail list logo
