Okay, that's solved, but I'm hitting another issue, now. When I start VMs, the
MAC address of my dom0 is changing to some very random addresses. One of the
systems has had all of the following MAC addresses over the past three days:
b8:ac:6f:a3:e:e5
96:15:8b:65:4e:b8
82:30:42:d9:a6:79
5e:9:f3:fa:a1:7c
b6:cc:c:42:44:70
72:40:f7:66:8e:72
The first one is the real MAC address of the system, the next five are
seemingly random MAC addresses that don't correspond with either the host MAC
address or the VM MAC address. It seems to be using these MAC addresses in
dom0 for the DHCP-assigned address on my bridge. So, it isn't as if interfaces
are being added to the bridge and they're picking up new IP addresses, it's as
if the system is sending out packets of some sort with a source IP address the
same as the bridge, but with several different MAC addresses. Any hints would
be greatly appreciated.
-Nick
>>> On 2010/08/20 at 20:21, Mark Pryor <tlviewer@xxxxxxxxx> wrote:
> Hello,
>
> --- On Fri, 8/20/10, Nick Couchman <Nick.Couchman@xxxxxxxxx> wrote:
>
>> From: Nick Couchman <Nick.Couchman@xxxxxxxxx>
>> Subject: [Xen-users] Xen Hotplug Issues
>> To: xen-users@xxxxxxxxxxxxxxxxxxx
>> Date: Friday, August 20, 2010, 6:56 PM
>> I'm running Xen 4.0.0 on openSuSE
>> 11.3, and I'm having issues with hotplug scripts not working
>> correctly. If I create a domU, I can start it
>> correctly exactly once - if it shuts down or restarts, I can
>> no longer start it, and I get the error message:
>>
>> Device 0 (vif) could not be connected. Hotplug scripts not
>> working.
>>
>
> Let me guess, your kernel-xen is the stock 2.6.34-12.x?
>
> this is covered here
> https://bugzilla.novell.com/show_bug.cgi?id=623286#c12
>
> comment 12 recommends installing the KOTD - kernel of the day, but a more
> robust approach is to setup the kernel build service repo
>
> #zypper ar
> http://download.opensuse.org/repositories/Kernel:/openSUSE-11.3/openSUSE_11.
> 3/ kernel-obs
>
> the above repo is now at 2.6.34.5-x
> Bug 623286# is fixed here.
>
> BTW the factory repo has a kernel-xen 2.6.34-14.x that still has this bug.
> Good thing that you didn't try it too.
--------
This e-mail may contain confidential and privileged material for the sole use
of the intended recipient. If this email is not intended for you, or you are
not responsible for the delivery of this message to the intended recipient,
please note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly
prohibited from downloading, photocopying, distributing or otherwise using this
message, its contents or attachments in any way. If you have received this
message in error, please notify us immediately by replying to this e-mail and
delete the message from your mailbox. Information contained in this message
that does not relate to the business of SEAKR is neither endorsed by nor
attributable to SEAKR.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home