** Changed in: linux (Ubuntu)
Assignee: Tim Gardner (timg-tpi) = (unassigned)
Status: In Progress = Fix Released
** Changed in: linux (Ubuntu Hardy)
Assignee: Tim Gardner (timg-tpi) = (unassigned)
--
xen guest kernel bug: 'kernel BUG at
So I tried Hirano's -19~33 kernel, and I was able to boot, but crashed
on update:
[EMAIL PROTECTED]:/home/matt# apt-get update
Get:1 http://archive.ubuntu.com hardy Release.gpg [191B]
Get:2 http://archive.ubuntu.com hardy Release [65.9kB]
Get:3 http://archive.ubuntu.com hardy/main Packages
I've just upgraded the kernel in my Xen hardy guest to
linux-image-2.6.24-19-xen_2.6.24-19.33_i386.deb
I don't currently appear to have the network issues, although I haven't
put a high network load on the image yet.
It booted cleanly with none of the usual issues.
--
xen guest kernel bug:
Hello all,
I found this thread and attempted to follow. I am quite new to Ubuntu
and XEN.
I have: dom0 - Centos 5.1
I would like to install Ubuntu hardy as a domU. The only Ubuntu version I can
install properly with no problem is dapper (6.06).
What I have done so far:
1. Install dapper
Hirano's kernels were good but still unstable with 3-4 oops a day on my
dell sc1425. My own experience was that I had to use the stock xen
kernel from xen.org (compiled most easily using the instructions from
gentoo's wiki) before I saw any stability or decent performance on my
hardy system.
I'm still showing symptoms similar to Chris Lea's.
Basically, if I do a large rsync between a domU (running gutsy) and an
outside server, both my domU and dom0 network connections will fail. If
I go to sit at the terminal, everything works correctly (minus
networking, of course).
My Dom0 is
Just tried with the updated kernel 2.6.24-18-xen and still have the same
issues with a crash at netfront.c:855.
Centos 5.1 Dom0 running xen-3.0.3-41.el5_1.5
Full boot and crash output below
[0.00] Linux version 2.6.24-18-xen ([EMAIL PROTECTED]) (gcc version
4.2.3 (Ubuntu
I've just booted the same guest with the 2.6.24-19-xen kernel from
http://www.il.is.s.u-tokyo.ac.jp/~hiranotaka/ without issue or crash.
I need to stress test the Xen guest a bit but it appears to have
resolved the netfront:855 issue
Can anyone provide detail on what has been patched in this
Ok not looking that good with the xen kernel from
http://www.il.is.s.u-tokyo.ac.jp/~hiranotaka/
[ 322.044307] logwatch[3122] general protection eip:b7ebd13c esp:bfb9a774
error:0
[ 542.537078] apache2[3167] general protection eip:b7ea08ab esp:bfeadaa4
error:0
[ 580.412190] logwatch[3175]
Hello,
Running:
dom0 - 2.6.18-92.el5xen
domU (Ubuntu 8.04- 32 bits) - 2.6.24-17-xen
I still have this error:
[0.616642] EIP: [c0269cc3] network_alloc_rx_buffers+0x503/0x510 SS:ESP
e021:de817edc
[0.616650] Kernel panic - not syncing: Fatal exception in interrupt
domU is up-to-date
Sorry,
this bug call it at line 855 in netfront.c, not at 785 (as said in title).
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
https://bugs.launchpad.net/bugs/218126
You received this bug notification
The commit has restored. Thanks, Tim.
https://lists.ubuntu.com/archives/kernel-team/2008-May/002483.html
** Changed in: linux (Ubuntu Hardy)
Status: In Progress = Fix Committed
--
xen guest kernel bug: 'kernel BUG at
Great news.
I shall give it a try.
Thanks guys, and thanks Hirano.
B
On 20 May 2008, at 10:55 PM, whs wrote:
I am running Hardy dom0 and domU's on i386 with Hiranos kernel without
any trouble at all for my mail-, web- and nameservers .
Hardware: HP ML110 (7 domU's), ML115 (4 domU's) and Tyan
My patch seems to be rejected for 17.32.
I'm asking the reason of that...
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
https://bugs.launchpad.net/bugs/218126
You received this bug notification because
Not 17.32, but it will be 18.32. Sorry.
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
https://bugs.launchpad.net/bugs/218126
You received this bug notification because you are a member of Ubuntu
Bugs,
Just a 'me too'. Trying to boot the kernel from proposed updates works
for a few seconds and results in an invalid opcode (). Dom0 is
Debian Etch with Xen 3.1, domU is Hardy.
--
xen guest kernel bug: 'kernel BUG at
Reopening the bug, since the commit was reverted. See:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commit;h=272e9bd390693017174eb6dd3e03e955e4d5df81
** Changed in: linux (Ubuntu Hardy)
Status: Fix Committed = In Progress
--
xen guest kernel bug: 'kernel BUG at
I am running Hardy dom0 and domU's on i386 with the proposed kernel
without any troubles at all.
This was just for the record.
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
Hi Wido,
Good news.
Are you using LVM or loop-back devices for your DomU's?
B
On 20 May 2008, at 5:55 PM, Wido den Hollander wrote:
I am running Hardy dom0 and domU's on i386 with the proposed kernel
without any troubles at all.
This was just for the record.
--
xen guest kernel bug:
I am using iSCSI as storage for my domU's.
The iSCSI Target server is also a Ubuntu Hardy machine (i386).
For the iSCSI initiator i use Open-iSCSI.
My domU's run Hardy of Debian Etch (i just found out) and are running
with the new kernel for about a week now, no troubles found yet.
This is
I am running Hardy dom0 and domU's on i386 with Hiranos kernel without any
trouble at all for my mail-, web- and nameservers .
Hardware: HP ML110 (7 domU's), ML115 (4 domU's) and Tyan GS21 (4 domU's)
I'm using domU's in TAP:AIO uand LVM configurations without any problems.
Thank You Hirano for
Jiří,
It is not accurate to say that this bug is not considered serious; this
bug is marked to be fixed before the first point release, and an attempt
at fixing it has been included in the first stable release update of the
kernel in 8.04.
However, the patch included in 2.6.24-17 is evidently
Thank you, Ubuntu developers!
At THURSDAY, I've upgraded to Hardy. And Xen networking between domU and
dom0 stopped working immediately. I've tried everything until today
evening, when I've found this bug description. After I installed Linux
2.6.24-17-xen #1 SMP x86_64 GNU/Linux from
Jiři nemas dovod takto skaredo penit a utri si penu z ust. :)
Nasraty je kazdy. Aj ja, co som to reportoval, pozri vyssie.
I understand now the policy of Canonical is against the best interests of
community.
The kernel freeze should not be applicable to such grevious bugs.
I suspect the
I tried turning off checksumming, first just in domU, then in both dom0
and domU, but the network still stopped.
However I have figured out what the problem is. The domU's network is
becoming unresponsive immediately after 4GB of data has been transmitted
by the eth0 device, as reported by
@Tim, Hirano,
I believe that Hiranos last comment (comment 19) is that 17.31 only contains a
partial fix.
Any idea when 17.32 with the correct fix is coming?
(BTW, Hirano is right about the line with BUG being incorrect. Original
has [i] and fix has [j]. This BUG is producing the traces at
Chris, Wolfgang, Roger,
I'm not entirely sure about this, but it might be necessary to turn off
checksum offload in all doms on the same machine. If I remember
correctly, it is required to turn off the offload in dom0 as well. I
know I have it off in all domUs and dom0.
--
xen guest kernel
@janevert
For the record, yes, I had to turn off checksumming on all the domU to
get them to be able to transfer files reliably between themselves. I did
not have to turn off checksumming on dom0 for this.
But, having said this, it doesn't really help me. With checksumming off,
other things stop
@janevert:
You are right, checksumming was turned on by default and my ethtool was
broken, so turning of tx-offloading when bringing up the interface
hasn`t worked.
So I can confirm too, that this problem was not related to the kernel
itself.
Regards
Wolfgang
--
xen guest kernel bug:
I have similar issues with a Centos 5.1 Dom0 and a Hardy DomU.
I am fine if I use the gutsy Xen kernel (2.6.22-14.46), but get the same
kernel panic with the vanilla Hardy Xen kernel.
I've just tried the kernel from proposed and whilst the VM boots a lot
quicker, I still get the following error
Chris has a point there, about checksumming.
I have no problems with the 17.31 kernel on an amd64 domU. And dom0 is running
the hardy kernel (-16.xx), also amd64. I'm using debians hypervisor
(3.2.0-3~bpo4+2).
And I DO have checksumming offload off (as described using
/etc/network/interfaces).
Yeah, unfortunately for me, I'm planning on just wiping the box and
trying to redo things using KVM at this point. Which I don't like for
performance reasons. But the reason I found this issue is that I was
trying to set up a mini-cluster for mogilefs to do development against.
And if I can't
HIRANO Takahito's x86 kernel worked for me and was extremely low hassle.
dpkg -i kernel and reboot, magically works. Hope this can be figured
out soon though.
--
xen guest kernel bug: 'kernel BUG at
D'oh! I should have read more closely.
What I'm seeing is exactly what Wolfgang notes in comment 48, and what
Roger notes in comment 51.
Not that it makes it any more usable. But I'm a me too for this
problem.
--
xen guest kernel bug: 'kernel BUG at
I am experiencing the same problem as Wolfgang two posts above. Unsure
if it is related to bug 218126.
Running stock feisty dom0, upgraded domU to hardy and now having this
problem. Tried Hirano Takahito's kernel on the domU yet the problem
subsists.
The server is quite heavily loaded as a web
I'm seeing another effect. Not sure if this is the correct bug for it or
not, and my apologies if it's not.
I'm running Xen on 32 bit hardy, on an HP Proliant DL 140 machine. Using
Hirano's kernel or the 2.6.24-17-xen from hardy-upcoming, networking
works. But only sort of. If I try and transfer
Hello,
I posted allready in a duplicate bug, haven`t seen, that this is the
main thread.
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 my network up and running, however the
Still crashing with linux-image-2.6.24-17-xen 2.6.24-17.31 on i386
[0.468544] kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:855!
[0.468551] invalid opcode: [#1] SMP
(full domU dmesg output attached)
on dom0 (centos 5.1):
The kernel linux-image-2.6.24-16-xen_2.6.24-16.30zng1_i386.deb made by
HIRANO Takahito boots successfully and networking seems to work ok.
This is with a Centos 5.1 dom0 on the same i386 box as was used in my
last report (for 2.6.24-17.31)
http://www.il.is.s.u-tokyo.ac.jp/~hiranotaka/
So
Hi,
the Kernel from the proposed-repo (linux-
image-2.6.24-17-xen_2.6.24-17.31_i386.deb) is'nt fixing the problem for
us.
We got a CentOS 5.1 (x64) with self-compiled XEN3.2 on it as dom0. When I start
the domU with 32bit-hardy an the kernel (s.a.)
the following is printed to stdo:
---
I too can confirm that the hardy-proposed kernel for 32bit systems isn't
fixing the issue here also. I can see RX/TX packets on the vif1.0
interface in Dom0, however, still no reply to pings / traffic from
inside or outside DomU.
--
xen guest kernel bug: 'kernel BUG at
Russell,
what kernel are you currently using? I.e. does that domU work with a
different kernel?
Thanks.
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
https://bugs.launchpad.net/bugs/218126
You received
kibe,
it would be really useful to have the full trace. I suspect that it is present
in 'dmesg'.
Because it is now cut-off by the prompt.
Thanks.
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
For me the image from proposed (17.31) works for and amd64 domU. I can
ssh into the domU.
(note that this debian etch/testing domU previously worked ok using
2.6.18 and I only replaced the kernel)
--
xen guest kernel bug: 'kernel BUG at
Unfortunately, the fix on 17.31 was incomplete.
Try my kernel at http://www.il.is.s.u-tokyo.ac.jp/~hiranotaka/ , or wait for
17.32.
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
janevert,
sorry that was everything i got from xen.. the machine wasn't started at all
and the bootprocess was cut off as well at that point.
I changed back a test-setting in the hwclock-scripts in the VM-root, so now
there is a little more:
now xen states that the machine is already present,
Thanks for the responses, Hirano janevirt.
I tried Hirano's 32bit kernel and had no luck, now I'm on the hardy-
proposed kernel and still have no luck.
To answer your question, janevirt, I'm using 2.6.24-17-xen. I'm
installing via xen-tools, which seems (to my surprise) to be booting
using
rehi,
the domain already present-thing was a configuration fault of mine... I had a
on_crash=reboot in the configuration of that domain.
so the server tried to start it repeatedly...
@russel:
I already tried a 32bit-hardy-system with gutsy-xen-kernel as domU with no luck.
the bootprocess stucks
I tried Hirano's 32bit kernel and had no luck, now I'm on the hardy-
proposed kernel and still have no luck.
Can you tell me the log message of my kernel?
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
Ok,
The good news here is that I'm an idiot!!! :)
I'm very, very new to xen and had accepted pretty much the defaults for
the xend configuration.
I was setting up my DomU to use routed traffic, however, my xend config
was configured to use bridging.
I switched from:
(network-script
So is the conclusion here that the 32-bit 2.6.24-17.31 does work, or is
there still a required fix missing?
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
https://bugs.launchpad.net/bugs/218126
You
So is the conclusion here that the 32-bit 2.6.24-17.31 does work, or
is there still a required fix missing?
If you are using Hardy as Dom0, I think you don't have any problems with
2.6.24-17.31.
If you are using older Xen hypervisors, you have to wait for a new release.
--
xen guest kernel
Steve,
yes there is still a Problem with 32-bit 2.6.24-17.31. See my log
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/218126/comments/40)...
This is with XEN 3.2 selfcompiled on 64bit CentOS 5.1
Benjamin
--
xen guest kernel bug: 'kernel BUG at
As far as I can tell from the activity log Colin scheduled the fix for
for 8.04.1.
I think waiting for a fix for a such a major bug which isn't even
mentioned in the release notes for another two months is too long. This
prevents production environments from being upgraded or installed and
gives
Colin Watson wrote:
Accepted into hardy-proposed
does this mean that the fixed kernel is now in the hard-proposed
repository and that I can safely upgrade Hirano's custom made kernel
with the proposed one?
--
xen guest kernel bug: 'kernel BUG at
On Tue, 2008-05-06 at 19:34 +, Bart Heinsius wrote:
Colin Watson wrote:
Accepted into hardy-proposed
does this mean that the fixed kernel is now in the hard-proposed
repository and that I can safely upgrade Hirano's custom made kernel
with the proposed one?
Seems like this, I
I can confirm that the new kernel 2.6.24-17-xen from hardy-proposed
fixes this problem on my AMD64 machine (hardy Dom0, hardy DomU).
Karsten
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
Has anyone tried upgrading Dom0 from Gutsy to Hardy?
And DomU?
Experiences?
On Wed, May 7, 2008 at 12:17 AM, kbe [EMAIL PROTECTED] wrote:
I can confirm that the new kernel 2.6.24-17-xen from hardy-proposed
fixes this problem on my AMD64 machine (hardy Dom0, hardy DomU).
Karsten
--
xen
Do we know yet if this fix is to be released in 8.04.1 or will it
(hopefully!) be seen earlier?
Thanks for the fix, Hirano!
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
+1 for Hirano kernel
linux-image-2.6.24-16-xen_2.6.24-16.30zng1_amd64.deb runs great (so
far).
Thanks Hirano!
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
https://bugs.launchpad.net/bugs/218126
You
Accepted into hardy-proposed.
** Changed in: linux (Ubuntu Hardy)
Importance: Undecided = Medium
Assignee: (unassigned) = Tim Gardner (timg-tpi)
Status: New = Fix Committed
Target: None = ubuntu-8.04.1
** Changed in: linux (Ubuntu)
Target: ubuntu-8.04.1 = None
--
** Description changed:
-
[EMAIL PROTECTED] ~]# xm create -c /etc/xen/pps-x12
Using config file /etc/xen/pps-x12.
Started domain pps-x12
[0.00] Linux version 2.6.24-16-xen ([EMAIL PROTECTED]) (gcc version
4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Thu Apr 10 14:35:03 UTC 2008 (Ubuntu
I confirmed the correct fix is NOT committed yet.
My patch and the applied patch differs at the BUG_ON() line.
Compare them carefully.
http://launchpadlibrarian.net/13564638/004-xen-netfront-fix.patch
Hirano, since you've already built the packages could you create a PPA
and host them from there in order to have a temporary fix until there is
a new official release of the packages?
Thanks,
Alessandro
--
xen guest kernel bug: 'kernel BUG at
SRU Justification:
Impact: Xen network traffic between Dom0 and another domain causes
kernel oops.
Fix Description: Use NAPI enable/disable when virtual network interface
is enabled/disabled.
Patch: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
Tim, the current fix in the hardy git tree by Chuck is not complete.
This still causes the kernel BUG() in some environments.
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
The patch against the current hardy tree.
** Attachment added:
0001-UBUNTU-Fix-incomplete-commit-294d61f7b574d2909aec60.patch
http://launchpadlibrarian.net/14048582/0001-UBUNTU-Fix-incomplete-commit-294d61f7b574d2909aec60.patch
--
xen guest kernel bug: 'kernel BUG at
Drat. I'll pick this up on the next upload cycle, probably next week.
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
https://bugs.launchpad.net/bugs/218126
You received this bug notification because you
Hirano,
Thank you very much for this fix.
I was running into the exact same problem trying to run a PVM
Ubuntu-8.04 within a CentOS-5.1 Dom0. I was able to install the fixed
package in the DomU (running in HVM mode), copy the kernel and initrd to
the Dom0 host, fix the guest configuration to
Ooops, actually this should be released much sooner than in 8.04.1.
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
https://bugs.launchpad.net/bugs/218126
You received this bug notification because you are
I am also quite outraged that Ubuntu 8.04LTS was released with such a
major bug. This basically disqualifies 8.04LTS for a very large number
of server deployments and puts Ubuntu's reuputation as a well tested,
stable server distribution on stake.
Can someone from Canonical (or whoever has some
Many thanks to Hirano, I hope that new xen karnel will hit the tree
soon. Now it looks like We support KVM, so Xen is going to randomly
break from now.
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
I cannot believe it.
The ubuntu is released and the bug is still there.
This bug is critical for xen users. That is also what hirano said in his first
response.
It is not even in the release notes.
Shame on Canonical.
--
xen guest kernel bug: 'kernel BUG at
I am running Hardy RC 64bit with 2.6.24-16-xen Dom0 and DomU, can
confirm this bug is still present. Thanks Hirano for your compiled
packages, they fix the problem.
--
xen guest kernel bug: 'kernel BUG at
Yep,
Been running Hardy Xen Dom0 here, solid as a rock, on top of gutsy
gibbon. I downloaded source and backported Xen. Just added patch
here, and recompiled, now DomU is running sweetly too!
I have been running Debian Etch 2.6.18 DomU (maintained source tree),
and also have a 2.6.25
Just ran into this bug and eagerly awaiting the release of the fix :)
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
https://bugs.launchpad.net/bugs/218126
You received this bug notification because you
Attached patch is what was committed.
** Attachment added:
0001-UBUNTU-Xen-Fix-networking-between-dom0-and-domU.patch
http://launchpadlibrarian.net/13613697/0001-UBUNTU-Xen-Fix-networking-between-dom0-and-domU.patch
--
xen guest kernel bug: 'kernel BUG at
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
hardy.git;a=commit;h=294d61f7b574d2909aec6017ab2333b26d6314c5
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Tim Gardner (timg-tpi)
Status: In Progress = Fix Committed
Target: None =
I can confirm that this fix does work for me. Thanks Hirano!
Could this please be released in time for Hardy, since this makes the
difference between an essentially useless DomU and a working DomU. See
Bug 204010 for the types and numbers of people that have been affected.
--
xen guest kernel
I can now confirm that your packages helped me to get the domU network working.
It is interesting to know, that testing ubuntu domU with other DISTRO (SL5.1)
as host OS can reveal the problem more precisely
and fix the problem more quickly then testing with ubuntu.
** Changed in: linux (Ubuntu)
The fix is not committed yet, and I have no privilege to commit it.
** Changed in: linux (Ubuntu)
Assignee: HIRANO Takahito (hiranotaka) = (unassigned)
Status: Fix Committed = In Progress
--
xen guest kernel bug: 'kernel BUG at
This is a ciritical problem for Xen users.
The attachment is the patch for hardy's broken Xen netfront driver.
This fixes the duplicated memory allocation on the older Xen hypervisors,
and enables NAPI for correct message receiving.
Put this under debian/binary-custom.d/xen/patchset in the source
** Changed in: linux (Ubuntu)
Sourcepackagename: None = linux
--
xen guest kernel bug: 'kernel BUG at
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/netfront/netfront.c:785'
https://bugs.launchpad.net/bugs/218126
You received this bug notification because you are a
Sorry, the previous patch sucks.
Please use this one.
** Attachment added: patch for the netfront driver
http://launchpadlibrarian.net/13563531/004-xen-netfront-fix.patch
--
xen guest kernel bug: 'kernel BUG at
Sorry, again.
Please use THIS one.
The compiled package is at:
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
** Attachment added: patch for the
Unfortunately I don't have the opportunity to test the fixed packages
in the same scenario , because I removed my SL5.1 host and installed
ubuntu as the host OS as well.
2008/4/18, HIRANO Takahito [EMAIL PROTECTED]:
Sorry, again.
Please use THIS one.
The compiled package is at:
Will be the fix also in the upstream kernel www.kernel.org and in
debian?
2008/4/18, HIRANO Takahito [EMAIL PROTECTED]:
Sorry, again.
Please use THIS one.
The compiled package is at:
http://www.il.is.s.u-tokyo.ac.jp/~hiranotaka/linux-image-2.6.24-16-xen_2.6.24-16.30zng1_amd64.deb
As long as I read the source code, The netfront driver available from
kernel.org has already fixed this problem.
However, the current source code in Ubuntu (and perhaps in Debian) differs
greatly from the one in kernel.org.
--
xen guest kernel bug: 'kernel BUG at
88 matches
Mail list logo
