I was searching through bugs, and found this one un-updated.
I am no longer seeing these errors under Hardy 8.04.1 and its xen
kernel. Is the right thing to do in this case to do an SRU for Gutsy?
The kernel team needs to do this one, correct?
- alvinc
--
Gutsy xen-3.1/kernel-2.6.22 dom0
I had very similar problems with when trying to write to a new LVM
logical volume using the xen kernel 2.6.22-14 (iirc). My hardware is a
Dell PowerEdge 6950 with their PERC 5 RAID controller. It turns out
that the IO scheduler changed and the megaraid_sas driver broke under
heavy use (I've been
I am getting the exakt same thing with 2.6.22-14-xen. DomU kraches when
compiling kernel. A lot of crashes when hypervisor and Dom0 are 32-bit.
A bit better with 64-bit hypervisor and Dom0. DomU works better with 64-bit.
Very disturbing, Xen does not feel stable at all.
Custom build 2.6.18 from
I' ve installed gutsy server and xen 3.10 as described here :
http://www.howtoforge.com/ubuntu-7.10-server-install-xen-from-ubuntu-repositories
But when I try to create domU image, kernel panics and this is the log:
[ 116.420322] BUG: unable to handle kernel paging request at virtual address
More bad news. Problem is persisting, even with a different NIC
(although also a Realtek, this one a PCI card instead of the onboard):
syslog:Nov 11 23:22:17 xen1 kernel: [ 8113.207809] PCI-DMA: Out of SW-IOMMU
space for 7222 bytes at device :03:05.0
syslog:Nov 11 23:22:40 xen1 kernel: [
I'm afraid I'm still seeing this bug. Or something similar.
I did not get a kernel panic, but my network died and stayed dead. I
was, however, able to reboot.
Nov 4 16:44:43 xen1 -- MARK --
Nov 4 17:04:36 xen1 kernel: [19235.154900] PCI-DMA: Out of SW-IOMMU space for
7222 bytes at device
Ok it really seems stable now.
I think the bug can be closed
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) = Géza Gémes (geza-kzsdabas)
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: In Progress = Fix Released
--
Gutsy xen-3.1/kernel-2.6.22 dom0 kernel
I've had 50 guests running stress continuously for about 2 or 3 days
with no problems like this.
This is with linux-image-2.6.22-12-xen, with Xen 3.1 backported from
Gutsy to Feisty.
I've also run a kernel compile in a loop for a number of hours, again
with no problems like this.
Sounds like
At least it boots, however I couldn't stress test it because it has
intermittent problems with the ext3 filesystems I have on the box (they are
going to get remounted read only after a few successful writes) in the syslog
there is:
PCI-DMA: Out of SW-IOMMU space for 8192 bytes at device
Please try this kernel:
http://kernel.ubuntu.com/~zul/linux-
image-2.6.22-10-xen_2.6.22-10.30_i386.deb
thanks
chuck
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Confirmed = In Progress
--
Gutsy xen-3.1/kernel-2.6.22 dom0 kernel panic
https://bugs.launchpad.net/bugs/135818
You
There is a newer kernel coming soon can you try that when it comes out.
Thanks
chuck
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New = Confirmed
--
Gutsy xen-3.1/kernel-2.6.22 dom0 kernel panic
https://bugs.launchpad.net/bugs/135818
You received this bug notification because you
Is the new kernel accessible (downloadable) somewhere?
I would be happy to test it.
Thanks
Geza
--
Gutsy xen-3.1/kernel-2.6.22 dom0 kernel panic
https://bugs.launchpad.net/bugs/135818
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
12 matches
Mail list logo
