[Expired for xen-3.1 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xen-3.1 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/150805
[Expired for xen-3.2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xen-3.2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/150805
Can you please try to reproduce this with a supported Ubuntu version?
Thank you!
** Changed in: xen-3.1 (Ubuntu)
Status: New => Incomplete
** Changed in: xen-3.2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported should be reproducible with
the live environment of the Desktop CD development release - Maverick
Meerkat. It would help us greatly if you could test with it so we can
work on getting it
There are 2 behaviors that seem to be part of this report.
1. By default Xen will assign a random mac address and by default
Ubuntu will assign each new mac address to a new interface. I don't
expect either behavior to change and suggest that it is wise to assign a
static address to each DomU an
** Also affects: xen-3.2 (Ubuntu)
Importance: Undecided
Status: New
--
domU fails to get network connection
https://bugs.launchpad.net/bugs/150805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
I also ran into this problem, on 7.10 (desktop). I already had the mac address
set in the guest configuration file, but networking didn't work in the guest.
I finally got it to work by applying Todd Deshane's workaround of removing
network-manager and adding
auto eth0
iface eth0 inet dhcp
to
Alternatively, open up /etc/udev/rules.d/70-persistent-net.rules, and
remove the ATTRS{address} parameter entirely. That stops udev using a
different name for each MAC.
--
domU fails to get network connection
https://bugs.launchpad.net/bugs/150805
You received this bug notification because you ar
OK so, every time it increments the interface number, it stores the new
entry in /etc/udev/rules.d/70-persistent-net.rules. My 'original' eth0
had a mac address of 00:16:3e:61:a6:be.
So all I needed to do was specify the desired MAC address in my
domain.cfg:
#
# Networking
#
vif = [ 'ip=
I had an eth0 created normally the first time I started a gutsy domU,
but repeated restarts generated additional eth* devices (I am on eth13).
I am not very familiar with network-manager or the difference between
-workstation and -server, but I don't appear to be using network-manager
as I already
I experienced the same problem, Todd Deshane's workaround (add an
interface eth0 to /etc/network/interfaces) solved the problem for me.
--
domU fails to get network connection
https://bugs.launchpad.net/bugs/150805
You received this bug notification because you are a member of Ubuntu
Bugs, which
so I looked into it some more.
I have a work around that I can live with (for now). Better solutions
and working on the box are going to be for hardy hopefully.
I noticed that I got the following errors in /etc/xen/xend-debug.log:
ifdown: interface eth0 not configured
SIOCSIFNAME: Device or resou
The setting of the mac address, does fix the udev problem, but I don't
seem to have networking working yet though.
Is there any other steps that are needed?
--
domU fails to get network connection
https://bugs.launchpad.net/bugs/150805
You received this bug notification because you are a member
can anyone confirm this workaround? I've switched to debian because of
this bug but if this workaround works i'll switch back..
--
domU fails to get network connection
https://bugs.launchpad.net/bugs/150805
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
I had the same problem with Gutsy domU on Gutsy dom0. It is caused by
xend generating a new MAC address each boot, udev recognises this as a
new card and therefore creates a new entry.
Add MAC address to the domU config file like:
vif = [ 'mac=00:11:22:33:44:55' ]
See
http://www.cl.cam.a
Same story here.
After getting past the 'Mount Filesystem'-Bug and the 'HW Clock'-Bug I
was beaten by no networking. I double checked every step I made,
reinstalled everything, changed the hardware to a real machine and
finally found the missing eth0.
It isn't eth0 anymore. If I take a look at /p
I have exactly the same problem as Fred H, and it is very strange.
Using a fresh gutsy install, installed ubuntu-xen-server, and domUs work
after first creating then booting them but then networking fails trying
to boot the domU a second time with eth0: error fetching interface
information: Device
Fred: So, you can look can look closer at networking as you test this.
Run a network analyzer such as wireshark, tshark, or similar on the dom0
when you ping the dom0. See if anything is going on. You should also be
able to trace the virtual network card associated with the guest.
Other things to
214.725.5434 (V)
214.206.1957 (F)
[EMAIL PROTECTED]
http://www.bereanservices.com
-Original Message-
From: Todd Deshane <[EMAIL PROTECTED]>
Date: Fri, 16 Nov 2007 13:20:09
To:[EMAIL PROTECTED]
Subject: [Bug 150805] Re: domU fails to get network connection
Fred: So, you can look can look
I went back and followed Todd Deshane's input above, reverting to revert
to the earlier kernel (2.6.19-4-generic-amd64) for both my dom0 and
domU. However, I am still experiencing the same problems as reported
above with the latest kernel. After using "xen-create-image" to create
the image and "x
I too am experiencing precisely the same issues as reported above on my
Dell 430SC server with dual core pentium D920 processors running 64 bit
Ubuntu 7.10 gutsy server and Xen 3.1 ( 2.6.22-14-xen #1 SMP Sun Oct 14
23:20:20 GMT 2007 x86_64 GNU/Linux).
However, immediately after initially creating
Sorry, but this interface allows only one file upload
** Attachment added: "xend-config.sxp"
http://launchpadlibrarian.net/10252600/xend-config.sxp
--
domU fails to get network connection
https://bugs.launchpad.net/bugs/150805
You received this bug notification because you are a member of Ubu
Sorry, but this interface allows only one file upload
--
domU fails to get network connection
https://bugs.launchpad.net/bugs/150805
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
I too have this problem on a generic Pentium 4 system with a single Ethernet
card. Here are my specifics:
dom0 is gutsy
[EMAIL PROTECTED]:/etc/xen# dpkg -l "*xen*"|grep ii
ii libc6-xen2.6.1-1ubuntu9 GNU C Library:
Shared libraries [Xen version
ii libxen3.1
Sorry, but this interface allows only one file upload
** Attachment added: "domU config file (created by xen-tools)"
http://launchpadlibrarian.net/10252595/gutsy2.cfg
--
domU fails to get network connection
https://bugs.launchpad.net/bugs/150805
You received this bug notification because you
I have two similar ethernet cards:
00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2)
00:09.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2)
So, it doesn't rule out the possibility of hardware-specific. But, it
still could be a configuration problem.
Could you post your /etc/xen/xend
well, i don't have problems with networking on DomU, but if it can help,
i'll post some information.
Kernel AMD64
Linux Silver 2.6.22-14-xen #1 SMP Sun Oct 14 23:20:20 GMT 2007 x86_64 GNU/Linux
Ethernet
00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2)
Maybe it's a hardware specific
I can confirm this one. I have exactly the same thing you report, it happens
with gutsy for me: `uname -a` shows
Linux pcuw32 2.6.22-14-xen #1 SMP Tue Oct 9 11:22:33 GMT 2007 i686 GNU/Linux
--
domU fails to get network connection
https://bugs.launchpad.net/bugs/150805
You received this bug notif
I am on the old kernel and the network connection on the domU works
fine. I can dchp an address, ping and SSH to the domU with no problems
too.
Something is broken in the latest Xen-3.1 packages.
--
domU fails to get network connection
https://bugs.launchpad.net/bugs/150805
You received this bug
29 matches
Mail list logo
