Thomas Schwinge
2007-Mar-05 17:52 UTC
[Pkg-xen-devel] domUs don't know their `eth0' anymore
Hello! I recently upgraded a number of Debian testing packages (three days ago) and just now rebooted the system, with the effect that the Xen domUs don't know their `eth0' devices anymore: #v+ # ifconfig eth0 eth0: error fetching interface information: Device not found #v- I'm using xen-hypervisor-3.0.3-1-i386-pae 3.0.3-0-2 and upgraded linux-image-2.6.18-4-xen-686 from 2.6.18.dfsg.1-10 to 2.6.18.dfsg.1-11, likewise for linux-modules-2.6.18-4-xen-686, the latter on both the dom0 and domUs. In the Xen domU configuration files I have ``vif = [ 'bridge=br0' ]''. Any idea? Regards, Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20070305/7f718ab0/attachment.pgp
On Mon, Mar 05, 2007 at 06:27:08PM +0100, Thomas Schwinge wrote:> I recently upgraded a number of Debian testing packages (three days ago) > and just now rebooted the system, with the effect that the Xen domUs > don't know their `eth0' devices anymore: > > #v+ > # ifconfig eth0 > eth0: error fetching interface information: Device not found > #v-Are you using udev now? Did you end up with eth1, eth2 and so on instead? Cheers, Andy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20070305/1c21b7ce/attachment.pgp
Possibly Parallel Threads
- Bug#413601: Xen domUs vs. udev
- NUT UPS monitor & APC Back UPS CS-350 (nut-2.2.2p1) on OpenBSD
- NUT UPS monitor & APC Back UPS CS-350 (nut-2.2.2p1) on OpenBSD
- Cannot start xen domUs anymore, domUs hang on kernel startup, happens after a long dom0 uptime
- strptime and plot(),lines()