Xen dom0 support

[Loranga]

http://www.ubuntu.com/products/whati...virtualization says "Running a Xen host (Dom0) on Ubuntu still requires a community maintained kernel in universe."

Which kernel package is this, and is this kernel "in phase" with the normal kernel in Intrepid 8.10?

[wamcvey]

I've tried used the -server kernel from Intrepid as well as from Hardy, and both give me the error

(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_init: not an ELF binary
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Could not set up DOM0 guest OS
(XEN) ****************************************

Eagerly awaiting feedback on how to get dom0 support working with an Intrepid install.

[bedge]

I was expecting a recent dom0 kernel with intrepid. This is quite disappointing.

What is everyone else using for their dom0 OS?

[klauskiwi]

I am suffering from the same problem.. Tried using the -server version hoping that it would be 'xen-enabled', but got the message reported by wamcvey above.

[albertcz]

Hi

I'm see in the ubuntu 8.10 doesn't existing kernel support xen dom0, kernel from hardy which support xen dom0 and domU 2.6.24 is broken,but if you have using xen could you get a kernel from lenny packages http://packages.debian.org/lenny/xen...6.26-1-xen-686
I using this kernel with dom0 and it's is ok.

it's a pity that cannonical don't support xen dom0 in ubuntu 8.10

[geraldbrandt]

So, what is everyone using for dom0? I'd use KVM, but I need to pass through PCI cards.

[randallb]

I hope the Debian/Ubuntu developers will reconsider their decision to remove dom0 support, as I find Xen to be the best virtualization solution for non-VT-capable servers. It's not fair to all the users of non-VT systems, especially considering that VT is still only couple years old.


In the meantime, I was able to get Ubuntu Intrepid 8.10 to run as a dom0 by manually downloading a Linux image package from Hardy and installing it manually with dpkg -i.

http://packages.ubuntu.com/hardy-upd...-2.6.24-19-xen

(2.6.24-21-xen will probably work too, and is probably safer, but I haven't yet tried it.)

I have Xen 3.3 running with one domU. The only issue I ran into so far was that the domU wouldn't boot if I configured it to use /boot/vmlinuz-2.6.27-7-server and /boot/initrd.img-2.6.27-7-server. Instead, I am using the 2.6.24-19-xen kernel/initrd in the domU.

[dePOLL]

I am very annoyed by the dropped dom0 support as well. Is anybody aware of community efforts to bring xen dom0 to Ubuntu's 2.6.27 kernel line?

kvm is not an option for me and I am having big trouble with the hardy kernel (the dreaded "Out of SW-IOMMU space" issue)..

[randallb]

I am very annoyed by the dropped dom0 support as well. Is anybody aware of community efforts to bring xen dom0 to Ubuntu's 2.6.27 kernel line?

kvm is not an option for me and I am having big trouble with the hardy kernel (the dreaded "Out of SW-IOMMU space" issue)..

I'm also seeing those errors. Occasionally, lots of these appear in the kern.log:

PCI-DMA: Out of SW-IOMMU space for 65536 bytes at device 0000:04:01.0

lspci shows that the related device is the server's SCSI controller:

04:01.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 08)

[dePOLL]

For me it's SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA. From what I understand the bug is prominent with RAID controllers but might also occur with SATA controllers or NICs. According to #247148 it has been fixed upstream a few months ago.

Why this is ignored by the kernel team I do not know. It really seems like they are leaving dom0 support out to die slowly and painfully..

I will hopefully find some time to look further into the upstream patches and maybe even patch the .27 kernel to xen bliss but was hoping there might already be a community effort underway. Because my kernel knowledge is really quite embarassing..