[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: [Xen-users] After migration: network-device of dom0 lost?!
- To: <Xen-users@xxxxxxxxxxxxxxxxxxx>
- From: "Rustedt, Florian" <Florian.Rustedt@xxxxxxxxxxx>
- Date: Fri, 27 Feb 2009 11:08:18 +0100
- Cc:
- Delivery-date: Fri, 27 Feb 2009 02:09:04 -0800
- List-id: Xen user discussion <xen-users.lists.xensource.com>
- Thread-index: AcmYN6c8zZbS3h0yRliMvQWEQgkd0gAhghyw
- Thread-topic: [Xen-users] After migration: network-device of dom0 lost?!
ï
xen1 ~ # ls /sys/class/net/
eth0 eth1 lo peth0
veth0 veth1 veth2 veth3 vif0.0 vif0.1
vif0.2 vif0.3
After
migration:
xen1 ~ # ls
/sys/class/net/
eth0 eth1 lo peth0 veth0
veth1 veth2 veth3 vif0.0 vif0.1 vif0.2
vif0.3 vif1.0
The iface eth0 exists in /sys/class/net/eth0 (in
Xen1)?
Also exists: vteh0 and peth0 (in XEN1)?
On Thu, Feb 26, 2009 at 12:36 PM, Rustedt, Florian
<Florian.Rustedt@xxxxxxxxxxx>
wrote:
Hello
list,
I am migrating a domU from dom0: XEN0 to Ddom0: XEN1. Both are
connected via eth1, both are connected to the net via (p)eth0.
While
doing this, my ssh-connection to the domU keeps running well.
After
about a minute, i get a "remote host closed the connection".
If i try to
log into host domU or XEN1 then via ssh, i get a "connection timed
out".
If i then check the logs locally on XEN1, there's nothing
special in them.
On XEN1 i have no network any more except the eth1
connection to XEN0. I even can't ping the gateway in the same
subnet!!
Checking ifconfig, route and resolv.conf doesn't help
either, they are all the same as before the error, pretending all is ok.
Dmesg is clean. The logs are clean, as told before.
If i try to
restart networking, i get an error telling me, that network device eth0 does
not exist?!? After that, dmesg hasn't got any additionally
entries...
What could that be? What could have destroyed my (p)eth0
shortly after migrating?
Cheers,
Florian
**********************************************************************************************
IMPORTANT:
The contents of this email and any attachments are confidential. They are
intended for the
named recipient(s) only.
If you have received this
email in error, please notify the system manager or the sender immediately
and do
not disclose the contents to anyone or make copies thereof.
***
eSafe scanned this email for viruses, vandals, and malicious content.
***
**********************************************************************************************
_______________________________________________
Xen-users
mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
--
ITIL: âAn industry accepted way of doing something, that
worksâ (Aidan Lawes)
IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the
named recipient(s) only.
If you have received this email in error, please notify the system manager or the sender immediately and do
not disclose the contents to anyone or make copies thereof.
*** eSafe scanned this email for viruses, vandals, and malicious content. ***
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
