*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
jist anidiot wrote:
> This bug is still in 8.04.
This particular bug is fixed, but many bugs remain including one I
submitted months ago where if you have >4GB of memory the Ubuntu Xen
kernel will crash reg
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
This bug is still in 8.04.
The URLS in
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010/comments/47
no longer seem to be valid.
Is there somewhere else I can get the patches to make Xen work?
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
Hirano, thanks a million for putting your kernels out there. Using your
-19 kernel fixed a major instability problem that was plaguing one of my
systems. You've really helped me a lot!
--
networking not wo
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
I've been testing my amd64 kernels with several vcpus, but have not encountered
such problem.
It may be i386 specific.
According to the log, the crash happened at the PageForeignDestructor macro.
The index
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
Hirano- Using the older[1] image you provided I have networking
operating again (thank you!), however the guest created with this kernel
often crashes when it's assigned more than one vcpu. The program
trigg
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
Hmm, I cannot figure out the reason by your description of your environment...
As long as I tested it, there were no problems around Xen networking.
--
networking not working
https://bugs.launchpad.net/bugs/
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
Takahito:
I tried your latest kernel
(linux-image-2.6.24-19-xen_2.6.24-19.33~zng1_amd64.deb) but it did not solve
the domU networking problem. Like the stock Hardy kernel, the guest OS does not
receive any
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
These *untested* packages are built from Hardy's latest development source tree.
In addition to this Xen bug, some other issues have been fixed.
See changelog in the package for details.
--
networking not wo
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
http://www.il.is.s.u-tokyo.ac.jp/~hiranotaka/
I see Hirano have new PKGs uploaded today...
Hirano, what's the fix?
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug not
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
Hello,
I was fighting with the same error described here. I installed Hiranos kernel
(32-bit version) on my AMD Athlon X2 5600+ server.
With that kernel I am now able to get up my network, however the networ
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
+1 for Hirano's kernel
Works great... Hope he didn't install some kind of backdoor... ;)
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
Forgot to say that i run both Dom0 and DomU with the hardy version.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
Hirano, thank you for the patch i just tested the i386 version that you
compiled, and it works for me.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification beca
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
Marking as a duplicate of bug 218126, since that bug is the same as
this, and has had a fix committed. I am not sure if this means that a
fix will make it for Hardy, but I am hopeful.
** This bug has been mar
*** This bug is a duplicate of bug 218126 ***
https://bugs.launchpad.net/bugs/218126
forall wrote:
> deti could you put somewhere this kernel , and I can dowload it?
See posting above:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010/comments/47
--
networking not working
https:
"Declined for Hardy by Steve Langasek "
That's what the report says!
Like what!? A serious bug like this won't be fixed in Hardy? Like how
can they do this, so many servers will do down when people upgrade their
servers from Gutsy to Hardy, not knowing this bug exists.
And how could this ever
deti could you put somewhere this kernel , and I can dowload it?
Albert
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
> Someone have kernel 2.6.24-16-xen with Hirano's patch?
Yes and it's working fine. Now we hope his patch will be included in the
8.04 release...
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi
Someone have kernel 2.6.24-16-xen with Hirano's patch?
Albert
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Since Hirano's patch fix this bug, would it be a duplicate for #218126 ?
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
James posted the suggestion on this bug to the mailing list. Thanks.
https://lists.ubuntu.com/archives/kernel-team/2008-April/002309.html
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Hirano, I can confirm that your images fix the problem for me. I hope
that this fix can be implemented for Hardy, since it is a kernel change
that only affects the XEN kernel, and turns the xen kernel from having
non-working networking to having a working networking stack.
Thanks for chasing this
Hirano,
Thanks much for chasing down the fix to this bug. You rock. :)
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
I tried to cross-compile the i386 version:
http://www.il.is.s.u-tokyo.ac.jp/~hiranotaka/linux-image-2.6.24-16-xen_2.6.24-16.30zng1_i386.deb
Note I haven't tested this at all.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a mem
[EMAIL PROTECTED]:~# uname -a
Linux ldap-master 2.6.24-16-xen #1 SMP Sat Apr 19 05:03:28 JST 2008 x86_64
GNU/Linux
[EMAIL PROTECTED]:~# ping www.google.de
PING www.l.google.com (209.85.137.99) 56(84) bytes of data.
64 bytes from mg-in-f99.google.com (209.85.137.99): icmp_seq=1 ttl=245
time=23.1 m
At the moment i only have a i386 system to test on, so i won't be able
to test HIRANO's kernel. Could somebody please test it so this hopefully
can be fixed before hardy comes out?
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are
I just meant that the patch does not affect Dom0 at all.
It fixes bugs on DomU.
> HIRANO: are you saying that this won't work with a hardy dom0?
>
> If so, why?
>
> I will try to do some testing this weekend.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug
whs (and others): did you try the packages as listed in HIRANO's comment
number 47 above?
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010/comments/47
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubun
Today I installed the 8.04rc with kernel 2.6.24-16-xen on one of my
servers (HP ML110) and the networking problem in domU still exists.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
HIRANO: are you saying that this won't work with a hardy dom0?
If so, why?
I will try to do some testing this weekend.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
If you are using Ubuntu hardy in DomU, and not in Dom0,
try these packages:
http://www.il.is.s.u-tokyo.ac.jp/~hiranotaka/linux-image-2.6.24-16-xen_2.6.24-16.30zng1_amd64.deb
http://www.il.is.s.u-tokyo.ac.jp/~hiranotaka/linux-headers-2.6.24-16-xen_2.6.24-16.30zng1_amd64.deb
This fixes the problem a
I agree with the affirmation that this isn't a Hypervisor or xen-3.2
bug. I have tested Hardy Kernel linux-2.6.24 with "Hypervisor" and
"Tools" from original xen-3.2.0.tar.gz and I got the same network
problem with hypervisor/tools compiled from source, so, this isn't a
xen-3.2 bug. Ah, and I have
Can somebody send in a kernel patch to the xennet driver that fixes the
problem and that can make it past the kernel freeze?
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried the Gutsy kernel for my domU.
But now the guest gets stuck at "Setting up the system clock"
Adding HWCLOCK=no to /etc/default/rcS in the domU solves this, but then
the guest gets stuck a little bit further while booting.
So this really should be fixed in Hardy, asap! The release is just
Given that there are two reports that there's a setup where other kernel
versions work but this one does not, I'd say it is confirmed that
there's a bug in this kernel.
** Also affects: linux-source-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Sourcepa
Nothing really new to add... but another cry of yes, this bug is hitting
me too. 2.6.22-14-xen works perfectly, but the 2.6.24-16 do not work for
me, with exactly the same problem as described above.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notificati
I just realized that this bug is on xen-3.2. But I guess this is wrong.
I have a etch(64) domU with 2.6.18-5 on it.
I have another domU with eth(64) userspace which I use for playing and testing.
I've used this with the eth kernel (2.6.18), the feisty or gutsy 2.6.22 and now
the hardy 2.6.24.
Th
So I tried it myself. It took actually a lot less effort than I
expected!
I downloaded the current xen kernel from (1), search for kernel-xen, and used
alien to extract it (alien -g).
The package also contains xen itself, I think, so don't convert and install!
I manually copied part of /boot from
using gutsy kernel it works! (following
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010/comments/35)
waiting for a fix of hardy kernel...
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Perhaps someboby should try a redhat kernel. Their status page
(http://fedoraproject.org/wiki/Features/XenPvops) says it works...
After that it just the same game: spot the difference.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you
Another "me too".
Deti, in -16 they finally decided to make the front- and backends into the
kernel instead of modules.
So the /etc/initramfs/modules workaround is no longer needed.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you a
linux-image-2.6.24-16-xen does not seem to contain any XEN modules which
makes this kernel unusable for XEN operation. I did not find any other
package that provides the missing modules. Any clues?
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification
The same here,
with hardy 64 host and etch 64 guests, running 2.6.24-14-xen.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
I can also confirm the same symptoms.
I am running the 2.6.24-15-xen kernel with a 64-Bit host and a 32-Bit
guest (Hardy also).
Traffic gets out of the domU, but it doesn't get back into it.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification beca
I have exactly the same as Elie.
Every ping to the DomU results in a drop.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Also encountering the same problem on 2.6.24-15-xen
The bridges are created, a win2k3/xp virtual host works perfectly (after fixing
the qemu-ifup script (see bug 201765 )). However when I run a centos 4.6
virtual host I see the same symptoms discussed in this thread. The bridges get
created, t
Same problem still exists with new kernel package 2.6.24-15
vv-etch64:~# uname -a
Linux vv-etch64 2.6.24-15-xen #1 SMP Fri Apr 4 05:04:49 UTC 2008 x86_64
GNU/Linux
vv-etch64:~# ping -c 1 192.168.3.100
PING 192.168.3.100 (192.168.3.100) 56(84) bytes of data.
>From 192.168.3.174 icmp_seq=1 Destina
I tried the ethtool command on domU. didn't work for me.
also tried to put the card in promisc with ifconfig eth0 promisc on the
guest.
I am in #xen in oftc trying to get some ideas, i will hang out in both
##xen and #xen like i said before.
I was told that it is the frontend driver in domU, whi
Todd Deshane wrote:
> can you give the following command a shot:
>
> ethtool -K eth0 tx off
>
> I plan to spend as much time as I can in ##xen on freenode and also
> #xen on irc.oftc.net to try to get some advice.
>
> I would like to see a working system before hardy releases...
I'm yet to have a r
can you give the following command a shot:
ethtool -K eth0 tx off
I plan to spend as much time as I can in ##xen on freenode and also
#xen on irc.oftc.net to try to get some advice.
I would like to see a working system before hardy releases...
--
networking not working
https://bugs.launchpad.n
Same problem still exists with new kernel package 2.6.24-14.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
> Same problem still exists with new kernel package 2.6.24-14.
confirmed.
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Mark, i can confirm that the problem ist present on amd64 AND i386... Tested
both of them a few days ago.
Both (amd64 and i386) are working with 2.6.22-14-xen from gutsy on domU
and 2.6.24-12-xen from hardy-beta on dom0 with xen3.2 following the
steps described in the initial bug report
An
Mark: Interesting point you bring up, I hadn't thought of that. DomU
support should be in mainline Linux, although dom0 support is still
lacking until Red Hat finishes their port.
Would you be willing to bring some of the key points and information to
the xen-users list [1] for a broader audience
Perhaps I might be stating something obvious here, but Xen was merged in
upstream in 2.6.23, doesn't it strike someone as odd that kernels since
then appear to have problems with their networking?
In main-line kernel Xen support 64-bit support is currently missing, so
perhaps we have a conflict be
Todd: Attached the complete diff.
[EMAIL PROTECTED]:~$ more config.diff | grep -i "xen"
--- config-2.6.22-14-xen2008-02-12 05:41:08.0 +0100
+++ config-2.6.24-12-xen2008-03-13 01:35:22.0 +0100
-# Linux kernel version: 2.6.22-14-xen
+# Linux kernel version: 2.6.24-12-
Dirk: could you post the config (differences) for those two kernels.
Maybe we are missing a module or like suggested above, maybe an iptable
or similar configuration is broken with either the kernel or a xen
setting that relies on something in the kernel.
--
networking not working
https://bugs.la
Todd: Tried this suggestion, no joy - this seems to be for adding a
separate bridge on a different vlan, so perhaps not surprising it's
doing nothing for us.
Packets are getting out from the domU OK, and replies are getting as far
as the bridge interface, but not the domU itself, for example:
(o
I don't think this has something todo with the network bridge. Tcpdump
shows the packets on vifx.0 in dom0. But the packets don't reach the
domU.
Using a 2.6.22-12-xen kernel for domU and the stock 2.6.24-12 for dom0
without changing the configuration, networking works out of the box.
--
network
i recognized, that the virtual interface (vifx.0) is dropping pakets:
- eth0 (domU) to vifx.0 (dom0) is working
- vifx.0 (dom0) to destination (i.e. ping to router) over bridge is working
- reply from router to vifx.0 (dom0) over bridge is working
- vifx.0 (dom0) to eth0 (domU) is not working -> v
Same problem here - I was wondering, why network packets from dom-u can
be seen in dom0 but not the other direction. It seems that no packet can
be received by domU instances. This behaviour is independent of any
bridging enabled in dom0.
Deti
--
networking not working
https://bugs.launchpad.net
>From this post:
http://xen.markmail.org/search/?q=creating%20xenbr0%20manually#query:creating%20xenbr0%20manually+page:1+mid:y3gyxx3kh25eogdz+state:results
I found the following suggestion:
auto xen-br1
iface xen-br1 inet manual
pre-up /sbin/ip link set vif0.1 arp off multicast off
pre-up /sbi
> Did anyone try making a manual bridge. For example adding something
like the following to /etc/network/interfaces
Yes, I did. And it didn't change anything. (But I didn's set bridge_fd,
_hello or _maxage)
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug no
Did anyone try making a manual bridge. For example adding something like
the following to /etc/network/interfaces
auto br0
iface br0 inet static
address 192.168.133.7
netmask 255.255.255.0
broadcast 192.168.133.0
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_
> 2.6.24-12-xen Dom0 + 2.6.22-14-xen DomU -> network is working
I can confirm this. Base install on amd64 (FSC Primergy RX220) was
Ubuntu dapper, dist-upgraded to hardy. With the hardy xen kernel running
in domU, I could see outgoing network traffic on eth0 in domU and on vif
in dom0. I could also
Quoting Todd Deshane ([EMAIL PROTECTED]):
> what happens when you do
> ifdown eth0
> ifup eth0
[EMAIL PROTECTED]:~# ifdown eth0; sleep 1; ifup eth0
ifdown: interface eth0 not configured
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reser
what happens when you do
ifdown eth0
ifup eth0
Do you get errors like:
SIOCSIFFLAGS: Invalid argument
AND/OR
send_packet: Network is down
receive_packet failed on eth0: Network is down
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because
brctl show on dom0
bridge namebridge id STP enabled interfaces
eth0 8000.001617a97350 nopeth0
vif1.0
--
networking not working
https://bugs.laun
** Changed in: xen-3.2 (Ubuntu)
Status: New => Confirmed
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
could you include the output of brctl show?
Also take a look here:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/199533
a manual bridge (i.e. br0, that KVM sometimes uses) has sometimes worked
better than the default ethX bridge.
I will try to confirm if that is true tomorrow.
--
net
Another "me too" - I'm running into the same bugs trying to deploy a server here
- xen modules are not included in the initramfs
- xen networking cannot receive packets in domU
The first bug is annoying but easily fixed; it's the second bug that's
got me stuck. I've tried rx_copy and rx_flip with
One more ;)
2.6.24-12-xen Dom0 + 2.6.22-14-xen DomU -> network is working
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
Did some more research today...
Not even the latest Hypervisor Xen version 3.3-unstable (Debian
3.3-unstable+hg17192-1)
(Debian Version installs without any problem) works so it must be something
with the Ubuntu-Xen Kernel?
--
networking not working
https://bugs.launchpad.net/bugs/204010
You re
Hi All
I have the same problem here,
I have done everything and nothing
Tanks
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
Same problem here. Can you ran ifconfig in dom0 and domu?
I have:
domu:
~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:3E:5D:DC:2A
inet addr:192.168.200.240 Bcast:192.168.200.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packe
** Attachment added: "startup_etch.txt"
http://launchpadlibrarian.net/12740635/startup_etch.txt
--
networking not working
https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Exactly the same problem here!
Thought I am am the only one :)
See
http://groups.google.com/group/de.comp.os.unix.linux.misc/browse_thread/thread/3f51434a0f02b269/6a64d635d9e45691?lnk=st&q=Chris+Cohen+xen#6a64d635d9e45691
(german)
--
networking not working
https://bugs.launchpad.net/bugs/204010
77 matches
Mail list logo
