Bug 239959
Summary: | starting xend makes wake on lan not work | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jeff Layton <jlayton> |
Component: | xen | Assignee: | Xen Maintainance List <xen-maint> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | katzj, steved |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-02-27 00:11:42 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jeff Layton
2007-05-13 12:34:27 UTC
I haven't specifically reproduced this yet, but since Xen does some funny stuff with the MAC address that most-likely interferes with WoL on nvidia hardware. I'd be curious to see how well it worked with some of the other WoL methods: wol p|u|m|b|a|g|s|d... Set Wake-on-LAN options. Not all devices support this. The argument to this option is a string of characters specifying which options to enable. p Wake on phy activity u Wake on unicast messages m Wake on multicast messages b Wake on broadcast messages a Wake on ARP g Wake on MagicPacket(tm) s Enable SecureOn(tm) password for MagicPacket(tm) d Disable (wake on nothing). This option clears all previous options. like specifically ARP or broadcast. Unfortunately: # ethtool peth0 | grep Wake-on Supports Wake-on: g Wake-on: g ...I *did*, however, verify that switching the networking to network/vif-nat works around the issue. So the changing MAC addrs does seem likely to be the problem. When xend starts, it changes the name of the physical interface to "peth0" and changes its MAC address to "FE:FF:FF:FF:FF:FF". Going to see if I can wake it up using that addr... That didn't work either -- but then again, I'm not terribly suprised :-) Another data point... If I shut down xend and then run: /etc/xen/scripts/network-bridge stop and then shut down the machine, I can wake the machine up as well. network-bridge stop seems change the MAC address back on the physical interface. It looks like xend does not run this when it shuts down. I'm not sure if this is by design or not... I guess you can shutdown (or restart) xend with domains still running, so I'm not sure if we want to tear down the networking stuff when it shuts down. Maybe the best solution is to just add a new shutdown script that tears down the networking just before the "real" networking is torn down. I'll hack something together as an example, but we may want to write a python prog that just calls Vifctl.network("stop") when run. This report targets FC6, which is now end-of-life. Please re-test against Fedora 7 or later, and if the issue persists, open a new bug. Thanks |