Comments on: Setup Fedora 11 PV DomU at Xen 3.4.1 Dom0 (kernel 2.6.31-rc3) on top of Fedora 11

By: Nishikant

Nishikant — Fri, 06 Nov 2009 20:43:18 +0000

[root@nishikant nishikant]# xm info
host : nishikant
release : 2.6.31
version : #4 SMP Mon Nov 2 15:51:44 EST 2009
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 1995
hw_caps : bfebfbff:20100800:00000000:00000140:040ce33d:00000000:00000001:00000000
virt_caps : hvm
total_memory : 8189
free_memory : 8
node_to_cpu : node0:0-7
node_to_memory : node0:8
xen_major : 3
xen_minor : 4
xen_extra : .0
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC)
cc_compile_by : nishikant
cc_compile_domain : (none)
cc_compile_date : Mon Nov 2 10:15:55 EST 2009
xend_config_format : 4

[root@nishikant nishikant]# brctl show
bridge name bridge id STP enabled interfaces
eth0 8000.0023ae95d38d no peth0
vif13.0
pan0 8000.000000000000 no
virbr0 8000.000000000000 yes

By: dbaxps

dbaxps — Fri, 06 Nov 2009 08:24:05 +0000

>FC 11 wasn’t able to configure my network,
>so I removed the bridge = eth0 from vif and made it -
>vif = ['']
Please, post
# xm info
# brctl show.
Something is wrong with your xen-bridge.

By: Nishikant

Nishikant — Fri, 06 Nov 2009 06:42:55 +0000

It was

http://dom0IP/f11

FC 11 wasn’t able to configure my network,

so I removed the bridge = eth0 from vif and made it -

vif = ['']

and it worked

My other issue is with ‘Xenoprof’, my domU’s report processor type as not supported when I do

opcontrol –init
ophelp -r

do u have any experience with Xenoprof on domU?

By: Boris

Boris — Wed, 04 Nov 2009 06:10:35 +0000

Submit your URL.

By: Nishikant

Nishikant — Wed, 04 Nov 2009 01:34:46 +0000

Excellent post!
But when I choose URL to install domU, it says “there was an error configuring your network interface”
can u help please!

By: Nishikant

Nishikant — Sun, 01 Nov 2009 04:51:58 +0000

I followed your steps, everything compiles, but I get following error while booting at grub loader

Error 11: Unrecognized device string

My grub entries

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/mapper/lvmvolume-fedora–root
# initrd /initrd-version.img
#boot=/dev/sda
default=1
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu

title Xen 3.4 / Fedora kernel 2.6.31
root (hd0, 0)
kernel /boot/xen-3.4.gz
module /boot/vmlinuz-2.6.31 root=/dev/mapper/lvmvolume-fedora–root ro
module /boot/initrd-2.6.31.img

title Fedora (2.6.31)
root (hd0,0)
kernel /vmlinuz-2.6.31 ro root=/dev/mapper/lvmvolume-fedora–root rhgb quiet
initrd /initrd-2.6.31.img

title Fedora (2.6.30.9-90.fc11.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.30.9-90.fc11.x86_64 ro root=/dev/mapper/lvmvolume-fedora–root rhgb quiet
initrd /initrd-2.6.30.9-90.fc11.x86_64.img

By: dbaxps

dbaxps — Tue, 01 Sep 2009 02:26:20 +0000

Sorry, i never was concerned about PAE, working on 64-bit
hardware (Core2Duo, Core2Quad boxes)

By: Madhu

Madhu — Tue, 01 Sep 2009 00:44:43 +0000

Thanks for the writeup.
But booting up XEN following your steps results in the kernel
seeing only 4Gig memory. My system has 28Gigs & the CPU has PAE support :

[XEN ~]$ grep pae /proc/cpuinfo
flags : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush acpi mmx fxsr sse sse2 ss ht nx constant_tsc up xtopology tsc_reliable nonstop_tsc pni est ssse3 sse4_1 sse4_2 hypervisor ida

I was hoping to see all the 28 gigs… Is it because of the kernel limitation ?

After following all the steps, the final Grub looks as follows. Though i see a grub entry for the kernel with pae support, the XEN grub entry (last one)’s kernel module do
not seem to have the PAE support. Any suggestions ?

Grub entries :

title Fedora (2.6.29-xen-r4)
root (hd0,0)
kernel /vmlinuz-2.6.29-xen-r4 ro root=/dev/mapper/vg_trifecta-lv_root nomodeset rhgb quiet
initrd /initrd-2.6.29-xen-r4.img

title Fedora (2.6.30-rc3-tip)
root (hd0,0)
kernel /vmlinuz-2.6.30-rc3-tip ro root=/dev/mapper/vg_trifecta-lv_root nomodeset rhgb quiet
initrd /initrd-2.6.30-rc3-tip.img

title Fedora (2.6.29.4-167.fc11.i686.PAE)
root (hd0,0)
kernel /vmlinuz-2.6.29.4-167.fc11.i686.PAE ro root=/dev/mapper/vg_trifecta-lv_root nomodeset rhgb quiet
initrd /initrd-2.6.29.4-167.fc11.i686.PAE.img

title Xen 3.4 / Fedora kernel 2.6.30-rc3-tip
root (hd0,0)
kernel /xen-3.4.gz vtd=1 iommu=1
module /vmlinuz-2.6.30-rc3-tip root=/dev/mapper/vg_trifecta-lv_root ro console=tty0
module /initrd-2.6.30-rc3-tip.img

By: dbaxps

dbaxps — Wed, 26 Aug 2009 10:08:59 +0000

The best board i have is ASUS P5Q-E, so i never had concern
like yours. I even cannot work on this issue due to no VT-d support by BIOS.Post it to xen-users@list.xensouce.com.

By: Dipak Dudhabhate

Dipak Dudhabhate — Wed, 26 Aug 2009 09:33:55 +0000

I have installed xen as per above procedure, i am getting
“(XEN) I/O virtualisation disabled” when i do “xm dmesg”

I have VT-d in BIOS, which is detected by xen kernel as follows

(XEN) VMX: Supported advanced features:
(XEN) – APIC TPR shadow
(XEN) – MSR direct-access bitmap
(XEN) HVM: VMX enabled

then why pnly I/O Virtulization is disabled?

thanks

-Dipak

.
.
.