Brandon's Blog

Hello I have followed the walk through flawlessly as far as I know everything to the letter, however I ended up with my initrd.img-2.6.33.1-xen0-amd64 in the root folder and it was named as bootinitrd.img-2.6.33.1-xen0-amd64?

well I have a proble or issue with the booing of the multiboot&&kernel&&initrd

during the boot process the whole system just halts with a

No filesystem could mount root, tried:
Kernel panic -not syncing:VFS: Unable to mount root fs on unknown-block (1,0)

then thats that?? any help would be appreciated.
Im on a internal drive on my pc partition is /dev/sda9 so in grub its marked to boot, root and look for all files at that point (hd0,9)

example:
multiboot (hd0,9)/boot/xen.gz
module (hd0,9)/boot/vmlinuz-2.6.33.1-xen0-amd64 root=/dev/sda9 root=/dev/disk/by-uuid/xxxxx-xxxxxx-xxxxxx
module (hd0,9)/boot/initrd.img-xen0-amd64

well thats my grub pretty much.. any suggestions are welcomed!

Thanks in advance

hitoshi :
I met same problem with 2.6.33.1.
I avoided this problem with changing source at line 460 in arch/x86/kernel/acpi/boot.c.
original: #ifdef(CONFIG_X86_IO_APIC)/p>
changed to: #if defined(CONFIG_X86_IO_APIC) && !defined(CONFIG_XEN)

hey, I was getting the same thing, I {{solved}} that by using a completely experimental version of the xen source {{(unstable version) 4.0.0-r6}} first compiling that asper this web post.

http://recluze.wordpress.com/2010/02/09/building-xen-from-source-on-ubuntu-8-04/

Then downloading the updated patches for a updated kernel linux kernel-2.6.33.1
then downloading updated patches for the updated latest kernel version patch-2.6.33.1

then patched, and did standard installs.

1. Compiled the xen-4.0.0-r6 $sudo make world.
2. Compiled the linux-2.6.33.1 kernel
make menuconfig-edited it accordingly plus added ect4 filesystem support.
make
sudo make install
sudo make modules_install

then made the initrd.img

then updated the /etc/grub.d/40_custom
/etc/default/grub
ran sudo update-grub

then thats where im stuck I did compile it correctly however I ran into booting problems later with my filesystem not mounting root..

Like I said in the other post any and all help is greatly appreciated

hey Brandon and friends….im newbie on ubuntu and im trying to install XEN on ubuntu KARMIC, can you tell me how do i modify the MAKEFILE please??…please tell wich instruction do i use to do that.

ill appreciatte your help!

THXS!

@Brandon
hey brandon, i need your help…how can i modify the MAKEFILE, can you tell me how to do that, wich instruction do i use??…

THXS for your help!

@jason
You probably ended up with the file bootinitrd.img-2.6.33.1-xen0-amd64 because you mistyped (forgot a slash between boot and initrd) the mkinitramfs command. The command in my post is:
sudo mkinitramfs -o /boot/initrd.img-2.6.31-8-xen0-amd64 2.6.31.8-xen0-amd64
You need to modify this (obviously) since you are using a newer kernel.

Fix that and make sure you have a correct /boot/initrd.img-2.6.xx-x-xen0-amd64 file. Also make sure this filename matches the filename on the last module line in your grub configuration (the example you provided did not match).

If you did all of this and are still having problems mounting root, you have probably have a driver issue (wrong drivers for your SATA controller) or a bad disk (not likely).

@Douglas Servellon
As I said in my post, use your favorite text editor. For example vim, emacs, nano.

I’m not trying to be rude, but I would proceed with extreme caution. My post calls for compiling the kernel from scratch, not an easy task in itself. If you’re still learning the ropes in linux and don’t know how to edit text files, I would strongly advise you not try to install Xen from scratch, you could completely hose your box. Try VirtualBox or wait for Ubuntu to package Xen.

@jason
According to the Xen wiki websource website

“Xen 4.0 switched to using Linux pv_ops based dom0 kernel as a default. This is the kernel all users should be using and testing, and all the development should be made against this kernel tree.”

@jason
I agree, and in fact in my post I say:

You have two main choices when it comes to a dom0 kernel. The Xen kernel or a dom0 pv-ops kernel. Normally I would recommend using a pv-ops kernel. The same pv-ops kernel can run on bare-metal or under the Xen hypervisor. The pv-ops kernel is going to be the default in future versions of Xen and will most likely be included in the mainline Linux kernel soon.

However, the pv-ops kernel will not work with Nvidia’s binary driver and since I was installing Xen for use on a desktop box with an Nvidia graphics card, I wanted to be able to use the Nvidia binary drivers (at least until KMS and the Nouveau driver mature a little). As of today, the Nvidia binary drivers require the “xenified” kernel. If you don’t need these drivers, pv-ops is the way to go. In fact, pv-ops dom0 support will probably be included in the mainline kernel very soon (2.6.34 or 2.6.35) – which will hopefully cause Ubuntu to start packaging Xen again and render this post obsolete!

@Brandon
hello Brandon, I did rename the Initrd.img file I figured I typed it wrong I must have hit the button on the post too quick, or was thinking out loud with my key board.

It indeed is a correct initrd image file and yes I renamed it correctly to match the gentoo linux kernel.

It is erroring out on me again. It keeps giving me the same error yes. and sorry I was not clear on the first post.

Incidentaly I am thinking of debugging using kexec-tools as seen in the grub entry im setting up a dump kernel (as the xen-4.0.gz) however I am unsure how to properly set up this scenario, and using a gz image? I believe I am meant to use a uncompresses image. Any suggestions will be greatly rewarded, well Ill buy you a beer )

im reading this site on root mounting problems:
http://www.howtoforge.com/forums/showthread.php?p=112023

and was thinking about the whole dump scenario

grub was updated and now reads:

menuentry “Ubuntu, Xen 4.0.0-rc6 dom0 2.6.33.1-xen0-amd64″ {
set quiet=1
insmod ext2
insmod ext4
set root=(hd0,9)
search –no-floppy –fs-uuid –set b0d66caf-41fc-437a-bf92-fe2424de9017
multiboot (hd0,9)/boot/xen-4.0.gz quiet
module (hd0,9)/boot/vmlinuz-2.6.33.1-xen0-amd64 root=UUID=b0d66caf-41fc-437a-bf92-fe2424de9017 root=/dev/sda9 ro quiet splash all_generic_ide
module (hd0,9)/boot/initrd.img-2.6.31.12-xen0-amd64
}

menuentry “Ubuntu-DUMP! DUMP!, Xen 4.0.0-rc6 dom0 2.6.33.1-xen0-amd64″ {
set quiet=1
insmod ext2
insmod ext4
set root=(hd0,9)
search –no-floppy –fs-uuid –set b0d66caf-41fc-437a-bf92-fe2424de9017
multiboot (hd0,9)/boot/xen-4.0.gz quiet crashkernel=128M@16M
module (hd0,9)/boot/vmlinuz-2.6.33.1-xen0-amd64 root=UUID=b0d66caf-41fc-437a-bf92-fe2424de9017 root=/dev/sda9 ro quiet
module (hd0,9)/boot/initrd.img-2.6.31.12-xen0-amd64
}

@jason
Are you copying and pasting your grub configuration into my blog, because some things still look strange. For example I’d expect the version numbers on the initrd.img file to match the kernel version. Your latest post shows 2.6.33.1 as the kernel and 2.6.31.12 as the initrd.img. Perhaps you renamed these, but you want to make sure you are generating the initrd image for the correct kernel (with the mkinitramfs command). Simply renaming the file to match the kernel version won’t work.

If you copied Ubuntu’s original .config file, you really shouldn’t have any driver problems – but it’d be worth a few minutes to run through your menuconfig and check that you’ve enabled the correct filesystem types and SATA drivers for your system. I tend to compile my SATA driver and filesystem into the kernel rather than as a module (eliminates the dependence on an initramfs).

One quick question: What filesystem are you using? You may need an appropriate insmod line in your grub configuration (hint: look at the Ubuntu generated sections in /boot/grub/grub.cfg)

@Brandon
Thank you for your help. I change dash to two dash.It’s OK.
But there is a new problem.

“error:file not found.”appears when booting “Ubuntu, Linux 2.6.31.8-xen0-amd64″

menuentry “Ubuntu, Linux 2.6.31.8-xen0-amd64″ {
insmod ext4
set root=(hd0)
search –fs-uuid –set d4d38180-6c21-4eb1-b675-d82328b09771
multiboot (hd0)/boot/xen-3.4.2.gz vga=gfx-1440*900*32 quiet
module (hd0)/boot/vmlinuz-2.6.31.8-xen0-amd64 root=/dev/mapper/VolGroup01-LogVo100 root=/dev/mapper/VolGroup01-LogVo100 ro quiet splash
module /boot/initrd.img-2.6.31.8-xen0-amd64
}

These are the files under boot.
ls /boot
abi-2.6.31-14-server
grub
System.map-2.6.31-14-server
vmlinuz-2.6.31-14-server
config-2.6.31-14-server
initrd.img-2.6.31-14-server
xen-3.gz xen.gz xen-3.4.gz xen-3.4.2.gz
System.map-2.6.31.8-xen0-amd64
vmlinuz-2.6.31.8-xen0-amd64
config-2.6.31.8-xen0-amd64
initrd.img-2.6.31.8-xen0-amd64
System.map-2.6.31.8-xen0-amd64.old
vmlinuz-2.6.31.8-xen0-amd64.old
xen-syms-3.4.2
vmcoreinfo-2.6.31-14-server
config-2.6.31.8-xen0-amd64.old
memtest86+.bin

cat /proc/mounts
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev tmpfs rw,relatime,mode=755 0 0
/dev/mapper/VolGroup01-LogVo100 / ext4 rw,relatime,errors=remount-ro,barrir=1,data=ordered 0 0
none /sys/kernel/security securityfs rw,relatime 0 0
none /sys/fs/fuse/connections fusectl rw,relatime 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxode=000 0 0
none /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
none /var/run tmpfs rw,nosuid,relatime,mode=755 0 0
none /var/lock tmpfs rw,nosuid,nodev,noexec,relatime 0 0
none /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0

How can I do now? How to change the menuentry? Please help me. Thank you very much.

You may have been right.

Okey, I apologize for not checking my posts the grub config it is set at:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the ‘exec tail’ line above.

menuentry “Ubuntu, Xen 4.0.0-rc6 2.6.31.12-xenU-64bit-Hypervisor” {
set quiet=1
insmod ext2
insmod ext4
set root=(hd0,9)
search –no-floppy –fs-uuid –set b0d66caf-41fc-437a-bf92-fe2424de9017
multiboot (hd0,9)/boot/xen-4.0.gz quiet
module (hd0,9)/boot/vmlinuz-2.6.31.12-xenU-64bit-Hypervisor root=UUID=b0d66caf-41fc-437a-bf92-fe2424de9017 root=/dev/sda9 ro quiet splash all_generic_ide
module (hd0,9)/boot/initrd.img-2.6.31.12-xenU-64bit-Hypervisor
}

menuentry “Ubuntu, Xen 4.0.0-rc6 dom0 2.6.33.1-xen1-amd64″ {
set quiet=1
insmod ext2
insmod ext4
set root=(hd0,9)
search –no-floppy –fs-uuid –set b0d66caf-41fc-437a-bf92-fe2424de9017
multiboot (hd0,9)/boot/xen-4.0.gz quiet
module (hd0,9)/boot/vmlinuz-2.6.32.10-xen1-amd64 root=UUID=b0d66caf-41fc-437a-bf92-fe2424de9017 root=/dev/sda9 ro quiet splash all_generic_ide
module (hd0,9)/boot/initrd.img-2.6.32.10-xen1-amd64
}

menuentry “Ubuntu, Xen 4.0.0-rc6 dom0 2.6.33.1-xen0-amd64″ {
set quiet=1
insmod ext2
insmod ext4
set root=(hd0,9)
search –no-floppy –fs-uuid –set b0d66caf-41fc-437a-bf92-fe2424de9017
multiboot (hd0,9)/boot/xen-4.0.gz quiet
module (hd0,9)/boot/vmlinuz-2.6.33.1-xen0-amd64 root=UUID=b0d66caf-41fc-437a-bf92-fe2424de9017 root=/dev/sda9 ro quiet splash all_generic_ide
module (hd0,9)/boot/initrd.img-2.6.33.1-xen0-amd64
}

menuentry “Ubuntu-DUMP! DUMP!, Xen 4.0.0-rc6 dom0 2.6.32.10-xen1-amd64″ {
set quiet=1
insmod ext2
insmod ext4
set root=(hd0,9)
search –no-floppy –fs-uuid –set b0d66caf-41fc-437a-bf92-fe2424de9017
multiboot (hd0,9)/boot/xen-4.0.gz quiet crashkernel=128M@16M
module (hd0,9)/boot/vmlinuz-2.6.32.10-xen1-amd64 root=UUID=b0d66caf-41fc-437a-bf92-fe2424de9017 root=/dev/sda9 ro quiet
module (hd0,9)/boot/initrd.img-2.6.32.1-xen1-amd64
}

#You may have been right.

#Okey, I apologize for not checking my posts the grub config it is set at:
well you may notice the two new entries in there besides the original xen0-amd64

now I have the debug kernel and the completely new compiled 2.32.10-xen1-amd64 kernel, that works thank heavens!

so thats good news, I got the earlier 2.32.10 kernel to work with all the xen patches, so now I have tow things I can do, ether start work on debugging the 2.33.1 kernel. And I can start work compiling a DomU kernel.

well the xen developer Jeremy had some notes earlier this month about not being ready to start the bleeding edge version of the release yet, and I didnt try to download the git remote /xen/next it gave me errors when I tried.

The bad news… I cant access my wireless in the xen1-amd64, and I could swear that I gave user privileged access to hardware in the kernel! :S

I had a privileged guest account im sure.. I may need to recompile?
specific network problems include:

the wlan0 giving me grief, Its telling me that theres things that are unsupported in the device?? when Im just connecting using the normal everyday terminal commands like ifconfig wlan0 down, dhclient -r wlan0, ifconfig wlan0 up, gives some errors around the dhclient, and then if i tried to continue connecting with iwconfig wlan0 essid “linksys” I get “not supported in module errors”?? any help here.

hi brandon just read your posts quickly this morning was meaning to go over them earlyer for a reply, however as my previous two posts say Ive been trying the pvops compilations today, and with only moderate success, one of those pvops only booted up to a certain point then it “gave up on boredom or something like that trying to mount one of my filesystems.

my file systems are one ext4 for the root = /
And the rest are on separate partitions well… /home, /usr, /var, /tmp are on separate ones. and these are all ext3 fs.

thanks for the grub mod line hint.

I did get into the root shell however the bash system had some major errors with missing commands.. witch reminds me that in the linux-2.32.10-xen1-amd64 kernel that was giving me grief with the network.

I was also noticing that the /prov and the sys folders were both populated with 0bit files and folders!??

So I am guessing that it didn’t mount the fs correctly? or what..

Should I boot into my working server vanilla kernel and manually create separate partitions for the sys and prov system folders then remount them in the fstab reboot to check once then reboot the linux-2.6.32.10-xen1-amd64 kern?

hey brandon, one question…
when i was in the grub, appears the option:

Ubuntu, linux 2.6.31.8-xen0-amd64

if i try to get in this options appears a error message like this:

“error: invalid magic number”
press any key to continue…

and if i select this option in the grub:

Ubuntu, Xen 3.4.2 dom0 2.6.31.8-xen0-amd64

this error appears:

error: no such device: 31d4873b-fed1-49d9-b37d-89d9f7a46566
press any key to continue

what do i do wrong with the configuration?
what should i change to fix this problem??

i hope you can help me, cause this is something like a test in my new job and i have to make Xen Run…

ill appreciate your support..

THXS again

@jason
It sounds like you are making some progress – just need to work out the kinks. You really shouldn’t have to touch fstab, or do anything differently to your file systems. The kernel you compiled should really be a drop in replacement for the stock Ubuntu kernel, except capable of running under Xen. And if your using a pvops kernel, it should be capable of running with or without Xen.

I’d compare your new kernel .config file to the Ubuntu stock .config file. There will naturally be differences, but see if anything jumps out at you (regarding wifi, etc.) There really isn’t much you need to change on your system when using a new kernel. Go back and make sure you followed each step, maybe try the kernel I used (2.6.31.8) just to eliminate some variables (you can upgrade later). And try posting on the xen-users mailing list. There’s a much wider audience over there.

@Douglas Servellon
May I suggest trying Ubuntu 8.04 instead of 9.10. Ubuntu dropped support for Xen in 9.10, which is why this post describes how to install it manually. In 8.04 it’s as easy as using to aptitude to install any other package. There are some instructions here: https://help.ubuntu.com/community/Xen

The errors you are currently seeing are because you are copying and pasting my config files without adjusting them to match your system. 31d4873b-fed1-49d9-b37d-89d9f7a46566 is the UUID for my root device, not yours. Your UUID is different – which is why Grub2 can’t find it.

hello brandon
I have one question.
When I boot 2.6.33.1-xen0-amd64, appears the option:

Gave up waiting for root device. Common problems:
-Boot args (cat /proc/cmdline)
-Check rootdelay = (did the system wait long enough?)
-Check root = (did the system wait for the right device?)
-Missing modules (cat /proc/modules; ls /dev)
ALERT! does not exist. Dropping to a shell!

What’s wrong? How can I do now? Please help me. Thank you very much.

You may also need to install the following packages to get xen to compile.

* zlib-bin
* libcurl4-openssl-dev
* xserver-xorg-dev
* gettext

Cheers,

Duke.

I ran into a nasty bug in the grub2 bootloader that causes the first parameter to be ignored. After tearing my hair out I came across this solution: add dummy=dummy or anything=anything as the first parameter. It will be ignored and it will then process the option for root properly. Hope this helps.

Hello Brandon,

This article is very useful but I don’t know why you know to created patch file for ubuntu. Which resources or document do you research and refer to?

Please help me to show about resources and document.

Thank you.

Hi Brandon,
Thanks for your nice guide! When I run the mkinitramfs command it showed as below:

$ sudo mkinitramfs -o /boot/initrd.img-2.6.31.8-xen0-intel64 2.6.31.8-xen0-intel64
W: Possible missing firmware /lib/firmware/2.6.31.8-xen0-intel64/e100/d102e_ucode.bin for module e100
W: Possible missing firmware /lib/firmware/2.6.31.8-xen0-intel64/e100/d101s_ucode.bin for module e100
W: Possible missing firmware /lib/firmware/2.6.31.8-xen0-intel64/e100/d101m_ucode.bin for module e100

Could you please tell me what does the information mean? By the way I encountered the same problem as Akanksha & Dulcardo.

@frank
Unless you use an e100 network card, I wouldn’t worry about those messages. Did you download the vanilla kernel from kernel.org? I’m pretty sure the firmware is included.

@Brandon
Yeah I’ve downloaded the kernel from kernel.org. Before this command, everything works well on my machine. Does it matter at all?

@frank
If your internet works when you boot into the Xenfied kernel, than I wouldn’t worry about it.

Hi Brandon,
Thanks for this useful guide.
I also have a nvidia card. Could you give me some hints about how to make it work under xenified kernel?
Thanks.

Hey. All!
If have tis message
“Gave up waiting for root device. Common problems:
-Boot args (cat /proc/cmdline)
-Check rootdelay = (did the system wait long enough?)
-Check root = (did the system wait for the right device?)
-Missing modules (cat /proc/modules; ls /dev)
ALERT! does not exist. Dropping to a shell!”

Fix it through the add ‘ in grub.cfg

For example:
root=’/dev/mapper/Lv1-Vl1′

I have a question as well. When I am applying the xen patches and I type in “for i in `ls ../xenpatches-v10_2.6.31.8/`; do patch -p1 < ../xenpatches-v10_2.6.31.8/"$i"; done" (without the quotes) it then comes to a prompt where it says "File to Patch: "

Has anyone seen this and/or know what to do at this point? Any help would be beneficial.

P.S. Thanks for the tutorial Brandon! Really helps out!

@Brian
Usually this that means that the patch command cannot find the file to patch and is asking you to find it. This shouldn’t happen. I get encounter that message often when trying to patch from the wrong directory. Did you change directory into the kernel directory before running the command?

Are you using the vanilla kernel from kernel.org? Does the kernel version you are using match up with the xenpatches kernel version? If you followed my tutorial to the letter than the answer is “yes”, but sometimes people use the latest kernel. This should still work, but you want to make sure all the versions match up.

@Brandon
yup, I have done everything up to that point exactly the same as pointed out in the tutorial. The only thing I changed was that I used the newest Xen release, 4.0.0. Other then that, everything thing else is the same. Hmmm… I really dont know what could be causing this. I know i’m typing in the correct filenames, because im hitting tab for autofill, and I’ve checked the command to make sure it’s the same as yours about 20 times
Is there another way to do the for loop that will produce the same results?

@Brian
Hmm… Well all the for loop is doing is applying each patch one at a time in order. You could apply each patch by hand but that would be a pain. That may give you an indication of where it is failing however.

You might check your version of patch patch --version. Mine is 2.6. I have no idea what version you need, but it’s at least worth checking.

Try applying a single patch by itself:

cd linux-2.6.31.8-xen0-amd64
patch -p1 < ../xenpatches-v10_2.6.31.8/60000_add-console-use-vt.patch1

Did that work? If it did not, from the current directory you are in can you:

ls -l drivers/char/tty_io.c


@Brandon
Wow, that actually worked (The patch -p1 line).
The only thing I had to do was type sudo in front of it so I could carry out the process (I dont want to become root user… messed up to many things that way)
So… I really don’t want to do all of these by hand… I noticed when I was doing the for loop before.. I skipped over some of the patches… and it went on and on and on…

————————————————————————
So… hmm. Well when I type sudo in front of the entire for loop:

sudo for i in `ls ../xenpatches-v10_2.6.31.8/`; do patch -p1 < ../xenpatches-v10_2.6.31.8/"$i"; done

it says:

bash: syntax error near unexpected token `do'

So I removed the do, and I got a similar response as above, but with the `done'

So again I removed that, but now it does the exact same thing as before.. where it says:

File to Patch:
————————————————————————

BTW, I checked my patch version, and its 2.5.9

Should I upgrade my patch version? and how would I do that? I acquired the patch command from typing:

sudo apt-get install patch

I assumed that would've installed the latest release… I guess I was wrong.

Thanks again for your help.

@Brian
I’m sure 2.5.9 is fine. I’m on Ubuntu 10.04 now, I bet it was 2.5.9 in 9.10.

It sounds like your problem is related to root permissions. You should do everything as a normal user (not root) except when I prefix my command with sudo. This means you shouldn’t have used sudo to untar the files, etc. It sounds like you don’t have permission to modify the source files as an ordinary user when running patch. This would be the case if you used sudo to untar the source files.

I’d suggest starting over in a directory inside your home directory, or /tmp, or somewhere else where your user has write access. Untar the files without sudo and try the patch command again.

Hope that made sense :/

@Brandon
Oh no don’t worry that totally makes sense. I just finished a Linux class in my college, so I’m fluent with what your talking about. Ok I will try that… because you were right.. I had to use sudo in front of 90% of the commands in the tutorial. Ok well I will try over and I’ll let you know how that goes!!

@Brandon
Awesome! That did the trick! Now to keep going on the tutorial!!

Thanks!!!

@Brandon
Well, hit another snag. I’m at the point where I’m compiling and installing the kernel. I type in:
export CONCURRENCY_LEVEL=3

That works fine. But then I type:
make

And it gives me an error stating:
awk: line 2: function gensub never defined
scripts/Makefile.build:82: *** ‘Your awk program does not define gensub. Use gawk or another awk with gensub’. Stop.
make: *** [scripts_basic] Error 2

From what I read, I’m thinking I have a problem with awk. I checked the man pages for awk, but all I had was mawk.

So I typed:
sudo apt-get install awk

That displayed a page where it asked for me to specify whether I wanted original-awk, gawk, or mawk. I told it original-awk. So it installed. I checked the man page for awk… and again only mawk displayed.

So is it something else or is my awk being like… overwritten by mawk?

Hello, I had another question regarding xen, specifically on loading modules after build?

You only typed a few Is there a list currently that you know of for all the modules available and their specified names or calls in this file?

any time and help is appreciated

If you compiled the Xen net, block and usb backend drivers as modules, you will probably want to load them by default by adding them to your /etc/modules file:
view source
print?
1 # /etc/modules
2 …
3 # These modules are required for Xen DomUs to work
4 netbk
5 blkbk
6 usbbk

@Brian
I ran into your problem as well “‘Your awk program does not define gensub. Use gawk or another awk with gensub’. Stop.” I installed gawk and it seems to be working now

Everything is ok,but when i reboot the Xen,there are some problems.
usb 1-6: new low speed USB device using ehci_hcd and address 4
usb 1-6: configuration #1 chosen from 1 choice

how to slove？

Hello Brandon,

Thanks for the tutorial.
When I was compiling my kernel I hit this error when I executed the “make” command
————————-
CC [M] drivers/net/sfc/falcon.o
drivers/net/sfc/falcon.c:2928: error: redefinition of ‘falcon_dimension_resources’
drivers/net/sfc/falcon.c:2825: note: previous definition of ‘falcon_dimension_resources’ was here
make[3]: *** [drivers/net/sfc/falcon.o] Error 1
make[2]: *** [drivers/net/sfc] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
————————-

Any idea how to get rid of this error and move forward?
Any help regarding this issue would be really helpful.

Thanks,
Abhiram

did u install domU using terminal??
I mean manuall create vms using xen?

Thank you so much but I actually need xen with pae kernel so i can’t move on with the instructions.