Re: [Xen-users] Re: Xen 4.0.1 on Ubuntu Lucid 10.04 - Desktop / Server - 64 Bits - With OpenGL (Intel GEM) enabled - From Linuxcon Brazil! :-D

[listmail <listmail@xxxxxxxxxxxx>]

Yes, the direct edit should work and is a much easier approach.Â

To add to my previous suggestion perhaps, for use in other circumstances; you can run update-grub from a chroot if you prepare /dev and /proc ahead of time. Assuming dom0 root was mounted on /mnt/a, doing a mount --bind /dev /mnt/a/dev && mount -t proc none /mnt/a/proc ahead of creating the chroot would suffice. On occasion I've also used kpartx and makedev to be able to install grub from a chroot on domU's using file based images.

On 9/16/2010 6:18 PM, Bruce Edge wrote:

On Thu, Sep 16, 2010 at 3:05 PM, listmail <listmail@xxxxxxxxxxxx> wrote:

Checkout /etc/default/grub. I am pretty sure Lucid hides the grub menu by default now. Not sure if you can hit a key to make it appear so you may have to use the desktop cd and use a chroot to fix things.

You could also use partprobe on dom0 to make embedded lvm partitions visible if that's what you're using.

Just don't try run update-grub while chrooted. Better to hack /boot/grub/grub.cfg directly then re-run update-grub after you get it booted.

-Bruce

Â

On 9/16/2010 4:08 PM, Priya wrote:

Hey guys!Â

Thanks for the continued support and advice. It seems like my job is not done yet.. :(

I finished the installation using Thiago's documentation and the configuration file from Boris.

While building the kernel, I kept the default setting for all the questions that came up at the prompt.

When I set up the xend and the xendaemon services using, I still get the earlier warning:

update-rc.d xend defaults 20 21

the output was:
update-rc.d: warning: xend start runlevel arguments (2 3 4 5) do not match LSB
Default-Start values (3 4 5)
update-rc.d: warning: xend stop runlevel arguments (0 1 6) do not match LSB
Default-Stop values (0 1 2 6)

And after rebooting the machine, I don't even get the grub2 choices for boot. All I get is a Kernel Panic message saying:

kernel panic - not syncing : VFS: unable to mount root FS on unknown-block

Obviously, this is a problem with the grub file that I created, but shouldn't I at least get the option to boot up the Ubuntu 10.04 that was initially working?

Now, can anyone please tell me how to correctly assign "root" to the correct hard disk partition ("hda.?") while creating your custom grub file in the /etc/grub2.d/ directory?

Now that I don't get the options from grub about which OS operating system I want to boot up from, is there a way to change the grub file to point to the correct hd partition? State of complete collapse at this time............

On Thu, Sep 16, 2010 at 3:09 PM, Outback Dingo <outbackdingo@xxxxxxxxx> wrote:

funny, how so many of us are having trouble with this documentation, ive got a kernel and all built, but i fear same as you somethings not right with the grub config

On Thu, Sep 16, 2010 at 2:20 PM, Priya <pbhat@xxxxxxxxxxxx> wrote:

Hey Boris!

I am using your configuration file to install xen4.0.1 from scratch. Thanks! Could you please also send me the grub entry (or the file that you made for the xen boot in the /etc/grub.d/ directory). I just want to confirm that it is the same as the original tutorial.

Also, did you change anything else from the steps given below (from the original mail by Thiago) while installing your version:


-----

The procedure:


Â1- Install all the packages:

Âaptitude update
Âaptitude install bridge-utils build-essential libncurses5-dev dpkg-dev debhelper fakeroot uuid-dev iasl texinfo git-core
Âapt-get build-dep xen-3.3

Â2- Download, compile and install Xen and its tools:

Âcd /usr/src
Âwget http://bits.xensource.com/oss-xen/release/4.0.1/xen-4.0.1.tar.gz
Âtar xf xen-4.0.1.tar.gz
Âcd xen-4.0.1
Âmake xen
Âmake tools
Âmake stubdom
Âmake install-xen
# make install-tools
Âmake install-tools PYTHON_PREFIX_ARG=
Âmake install-stubdom


Â3- Download, compile and install Linux from the Jemery's tree:

Âmake prep-kernels
Âwget http://livexen01.worldweb.com.br/linux-config-2.6.23.18-xen-4.0.1-1-tcmc-10.08-1 -O build-linux-2.6-pvops_x86_64/.config
Âcd build-linux-2.6-pvops_x86_64
Âmake menuconfig # Change whatever you want, if you now what you're doing...
Âmake
Âchmod g-s /usr/src/ -R
Âmake deb-pkg
Âdpkg -i ../linux-image-2.6.32.18-tcmc-10.08-1-xen_2.6.32.18-tcmc-10.08-1-xen-*.deb
Âdepmod 2.6.32.18-tcmc-10.08-1-xen
Âupdate-initramfs -c -k 2.6.32.18-tcmc-10.08-1-xen

Â4- Enable Xen at boot:

Âupdate-rc.d xend defaults 20 21

Âupdate-rc.d xendomains defaults 21 20

Â5- Configure the Grub2:

Âvim /etc/grub.d/40_custom

---- cut here ----
#!/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 'Xen 4.0.1, Ubuntu 10.4 kernel 2.6.32.18' {
ÂÂÂÂÂÂÂ recordfail
ÂÂÂÂÂÂÂ insmod ext2
ÂÂÂÂÂÂÂ set root='(hd0,4)'
ÂÂÂÂÂÂÂ multiboot (hd0,4)/boot/xen-4.0.1.gz dummy=dummy dom0_mem=832M
ÂÂÂÂÂÂÂ module (hd0,4)/boot/vmlinuz-2.6.32.18-tcmc-10.08-1-xen dummy=dummy root=/dev/sda4 i915.modeset=0 earlyprintk=xen ro
ÂÂÂÂÂÂÂ module (hd0,4)/boot/initrd.img-2.6.32.18-tcmc-10.08-1-xen
}
---- cut here ----

ÂNOTE.: Pay attention to you root partition and also you'll need to disable the KMS (maybe the nomodeset option works for you) of your videoboard.

Âupdate-grub
Âreboot

ÂChoose the right Grub2 menu entry...

----------


Thanks!

On Thu, Sep 16, 2010 at 12:03 PM, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

Don't worry about /proc/xen. Config is attached.
Some where down here you tune wrong :-

Device Drivers

[*] Xen memory balloon driver â âÂ
 â â [*] Scrub pages before returning them to stem â âÂ
 â â <*> Xen /dev/xen/evtchn device â âÂ
 â â [*] Backend driver support â âÂ
 â â <*> Xen backend network device â âÂ
 â â <*> Block-device backend driver â âÂ
 â â <*> Block-device tap backend driver â âÂ
 â â <*> PCI-device backend driver â âÂ
 â â PCI Backend Mode (Virtual PCI) ---> â âÂ
 â â [*] PCI Backend Debugging â âÂ
 â â <*> Xen filesystem â âÂ
 â â [*] Create compatibility mount point /proc/xen â âÂ
 â â [*] Create xen entries under /sys/hypervisor â âÂ
 â â <*> userspace grant access device driver â âÂ
 â â <*> xen platform pci device driver â âÂ
 â â [*] Staging drivers ---> â âÂ
 â â [*] X86 Platform Specific Device Drivers ---> â âÂ
 â âââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ

Boris.

--- On Thu, 9/16/10, Priya <pbhat@xxxxxxxxxxxx> wrote:

From: Priya <pbhat@xxxxxxxxxxxx>

Subject: Re: [Xen-users] Re: Xen 4.0.1 on Ubuntu Lucid 10.04 - Desktop / Server - 64 Bits - With OpenGL (Intel GEM) enabled - From Linuxcon Brazil! :-D

To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: nunziaG84@xxxxxxxxx, "hurenkam" <hurenkam@xxxxxxxxx>, "Pasi KÃrkkÃinen" <pasik@xxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Date: Thursday, September 16, 2010, 11:25 AM

There is no "/proc/xen" either!

What do you all recommend? Should I use a different kernel (if so which one) or a different .config file?

Can I fix the present set up in some way?

I find it amusing that I am learning stuff about the internal setup of Xen that I wouldn't have had this install been "seamless"...ÂÂ

Cheers to that!

On Thu, Sep 16, 2010 at 11:14 AM, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

> root@XenOpen:~# ls -l /dev/xen
ls: cannot access /dev/xen: No such file or directory
root@XenOpen:~# ls /dev

That's a core issue , why xend fails to start. During pvops Dom0 load "udevd" should
create :-

# ls -l /dev/xen
total 0

crw------- 1 root root 10, 58 Sep 16 18:41 evtchn
crw------- 1 root root 10, 57 Sep 16 18:41 gntdev

On any system Ubuntu 10.04.1 Server, F13,F14,etc
Then xend will start after Dom0 gets loaded.

Boris.

--- On Thu, 9/16/10, Priya <pbhat@xxxxxxxxxxxx> wrote:

From: Priya <pbhat@xxxxxxxxxxxx>

Subject: Re: [Xen-users] Re: Xen 4.0.1 on Ubuntu Lucid 10.04 - Desktop / Server - 64 Bits - With OpenGL (Intel GEM) enabled - From Linuxcon Brazil! :-D

To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "hurenkam" <hurenkam@xxxxxxxxx>, nunziaG84@xxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx, "Pasi KÃrkkÃinen" <pasik@xxxxxx>
Date: Thursday, September 16, 2010, 11:03 AM

Thanks for the responses !

@Mark

xenfs is not mounted. Here is the output for the mount command:

-------------
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev type tmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
/dev/sdb1 on /media/08AF-8FE8 type vfat (rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,flush)

------------------------------

I did a modprobe on xenfs but I cannot mount it yet. Could you please give me the correct command line arguments for doing so. Here are my outputs:
------------------------

root@XenOpen:~# modprobe xenfs
root@XenOpen:~# mount xenfs
mount: can't find xenfs in /etc/fstab or /etc/mtab

-----------------------------------------------------------
Thanks a lot for your advice. Really appreciate it!


@Borris:

There is no "xen" directory in /dev....Here is what I have:

---------------

root@XenOpen:~# ls -l /dev/xen

ls: cannot access /dev/xen: No such file or directory
root@XenOpen:~# ls /dev
adsp null snapshot tty41 vcs1 vcs5 vcsa30
agpgartÂÂÂÂÂÂÂÂÂÂÂÂ nvramÂÂÂÂÂÂ sndÂÂÂÂÂÂ tty42ÂÂÂ vcs10Â vcs50ÂÂ vcsa31
audioÂÂÂÂÂÂÂÂÂÂÂÂÂÂ oldmemÂÂÂÂÂ sndstatÂÂ tty43ÂÂÂ vcs11Â vcs51ÂÂ vcsa32
blockÂÂÂÂÂÂÂÂÂÂÂÂÂÂ parport0ÂÂÂ sr0ÂÂÂÂÂÂ tty44ÂÂÂ vcs12Â vcs52ÂÂ vcsa33
bsgÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ portÂÂÂÂÂÂÂ stderrÂÂÂ tty45ÂÂÂ vcs13Â vcs53ÂÂ vcsa34
busÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ pppÂÂÂÂÂÂÂÂ stdinÂÂÂÂ tty46ÂÂÂ vcs14Â vcs54ÂÂ vcsa35
cdromÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ptmxÂÂÂÂÂÂÂ stdoutÂÂÂ tty47ÂÂÂ vcs15Â vcs55ÂÂ vcsa36
cdrwÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ptsÂÂÂÂÂÂÂÂ ttyÂÂÂÂÂÂ tty48ÂÂÂ vcs16Â vcs56ÂÂ vcsa37
charÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ramÂÂÂÂÂÂÂÂ tty0ÂÂÂÂÂ tty49ÂÂÂ vcs17Â vcs57ÂÂ vcsa38
consoleÂÂÂÂÂÂÂÂÂÂÂÂ ram0ÂÂÂÂÂÂÂ tty1ÂÂÂÂÂ tty5ÂÂÂÂ vcs18Â vcs58ÂÂ vcsa39
coreÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ram1ÂÂÂÂÂÂÂ tty10ÂÂÂÂ tty50ÂÂÂ vcs19Â vcs59ÂÂ vcsa4
cpuÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ram10ÂÂÂÂÂÂ tty11ÂÂÂÂ tty51ÂÂÂ vcs2ÂÂ vcs6ÂÂÂ vcsa40
cpu_dma_latencyÂÂÂÂ ram11ÂÂÂÂÂÂ tty12ÂÂÂÂ tty52ÂÂÂ vcs20Â vcs60ÂÂ vcsa41
diskÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ram12ÂÂÂÂÂÂ tty13ÂÂÂÂ tty53ÂÂÂ vcs21Â vcs61ÂÂ vcsa42
driÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ram13ÂÂÂÂÂÂ tty14ÂÂÂÂ tty54ÂÂÂ vcs22Â vcs62ÂÂ vcsa43
dspÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ram14ÂÂÂÂÂÂ tty15ÂÂÂÂ tty55ÂÂÂ vcs23Â vcs63ÂÂ vcsa44
dvdÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ram15ÂÂÂÂÂÂ tty16ÂÂÂÂ tty56ÂÂÂ vcs24Â vcs7ÂÂÂ vcsa45
dvdrwÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ram16ÂÂÂÂÂÂ tty17ÂÂÂÂ tty57ÂÂÂ vcs25Â vcs8ÂÂÂ vcsa46
fb0ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ram2ÂÂÂÂÂÂÂ tty18ÂÂÂÂ tty58ÂÂÂ vcs26Â vcs9ÂÂÂ vcsa47
fdÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ram3ÂÂÂÂÂÂÂ tty19ÂÂÂÂ tty59ÂÂÂ vcs27Â vcsaÂÂÂ vcsa48
fullÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ram4ÂÂÂÂÂÂÂ tty2ÂÂÂÂÂ tty6ÂÂÂÂ vcs28Â vcsa0ÂÂ vcsa49
hidraw0ÂÂÂÂÂÂÂÂÂÂÂÂ ram5ÂÂÂÂÂÂÂ tty20ÂÂÂÂ tty60ÂÂÂ vcs29Â vcsa1ÂÂ vcsa5
hidraw1ÂÂÂÂÂÂÂÂÂÂÂÂ ram6ÂÂÂÂÂÂÂ tty21ÂÂÂÂ tty61ÂÂÂ vcs3ÂÂ vcsa10Â vcsa50
hpetÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ram7ÂÂÂÂÂÂÂ tty22ÂÂÂÂ tty62ÂÂÂ vcs30Â vcsa11Â vcsa51
inputÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ram8ÂÂÂÂÂÂÂ tty23ÂÂÂÂ tty63ÂÂÂ vcs31Â vcsa12Â vcsa52
kmemÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ram9ÂÂÂÂÂÂÂ tty24ÂÂÂÂ tty7ÂÂÂÂ vcs32Â vcsa13Â vcsa53
kmsgÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ randomÂÂÂÂÂ tty25ÂÂÂÂ tty8ÂÂÂÂ vcs33Â vcsa14Â vcsa54
logÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ rawÂÂÂÂÂÂÂÂ tty26ÂÂÂÂ tty9ÂÂÂÂ vcs34Â vcsa15Â vcsa55
loop0ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ rootÂÂÂÂÂÂÂ tty27ÂÂÂÂ ttyS0ÂÂÂ vcs35Â vcsa16Â vcsa56
loop1ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ rtcÂÂÂÂÂÂÂÂ tty28ÂÂÂÂ ttyS1ÂÂÂ vcs36Â vcsa17Â vcsa57
loop2ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ rtc0ÂÂÂÂÂÂÂ tty29ÂÂÂÂ ttyS2ÂÂÂ vcs37Â vcsa18Â vcsa58
loop3ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ scd0ÂÂÂÂÂÂÂ tty3ÂÂÂÂÂ ttyS3ÂÂÂ vcs38Â vcsa19Â vcsa59
loop4 sda tty30 urandom vcs39 vcsa2 vcsa6
loop5ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ sda1ÂÂÂÂÂÂÂ tty31ÂÂÂÂ usbmon0Â vcs4ÂÂ vcsa20Â vcsa60
loop6ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ sda2ÂÂÂÂÂÂÂ tty32ÂÂÂÂ usbmon1Â vcs40Â vcsa21Â vcsa61
loop7ÂÂÂÂÂÂÂÂÂÂÂÂÂÂ sda5ÂÂÂÂÂÂÂ tty33ÂÂÂÂ usbmon2Â vcs41Â vcsa22Â vcsa62
lp0ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ sdbÂÂÂÂÂÂÂÂ tty34ÂÂÂÂ usbmon3Â vcs42Â vcsa23Â vcsa63
mapperÂÂÂÂÂÂÂÂÂÂÂÂÂ sdb1ÂÂÂÂÂÂÂ tty35ÂÂÂÂ usbmon4Â vcs43Â vcsa24Â vcsa7
mcelogÂÂÂÂÂÂÂÂÂÂÂÂÂ sequencerÂÂ tty36ÂÂÂÂ usbmon5Â vcs44Â vcsa25Â vcsa8
memÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ sequencer2Â tty37ÂÂÂÂ usbmon6Â vcs45Â vcsa26Â vcsa9
mixerÂÂÂÂÂÂÂÂÂÂÂÂÂÂ sg0ÂÂÂÂÂÂÂÂ tty38ÂÂÂÂ usbmon7Â vcs46Â vcsa27Â vga_arbiter
netÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ sg1ÂÂÂÂÂÂÂÂ tty39ÂÂÂÂ usbmon8Â vcs47Â vcsa28Â zero
network_latencyÂÂÂÂ sg2ÂÂÂÂÂÂÂÂ tty4ÂÂÂÂÂ vcsÂÂÂÂÂ vcs48Â vcsa29
network_throughput shm tty40 vcs0 vcs49 vcsa3

---------------------

Thanks for taking the time guys!

On Thu, Sep 16, 2010 at 10:25 AM, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

One more time. Please, submit :-
# ls -l /dev/xen

Boris.

--- On Thu, 9/16/10, hurenkam <hurenkam@xxxxxxxxx> wrote:

From: hurenkam <hurenkam@xxxxxxxxx>

Subject: Re: [Xen-users] Re: Xen 4.0.1 on Ubuntu Lucid 10.04 - Desktop / Server - 64 Bits - With OpenGL (Intel GEM) enabled - From Linuxcon Brazil! :-D

To: "Priya" <pbhat@xxxxxxxxxxxx>
Cc: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, nunziaG84@xxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx, "Pasi KÃrkkÃinen" <pasik@xxxxxx>
Date: Thursday, September 16, 2010, 10:17 AM

Hi,

> And then when I reboot the machine, xend does not start. On issuing
> the command /etc/init.d/xend start, or status, there is no terminal
> output.
> When I type in "xend start" directly, I get the following error
> message:
>Â sudo xend start
>>
>> the output is:
>>
>> ERROR Internal error: Could not obtain handle on privileged command
> interface

Do you have xenfs mounted?
see if the following line comes up in the list if you type mount:

# mount
...
xenfs on /proc/xen type xenfs (rw)
...

If not, then you can try mounting it manually. If xenfs is compiled as
a module, you may have to modprobe it first. If it is not enabled in
your
kernel, then you have to rebuild your dom0 kernel, and enable it.

On my (Ubuntu Server 10.04.1 based) system, this gets mounted
automatically
by either udev or xend itself (it is not in fstab).

In my experience on this system, xend fails ususually due to one of the
following reasons:
1) Failure to mount xenfs (because it is not configured, or the module
is
not loaded).
2) Inconsistent installation of xentools (in wrong python directory or
mixed with older version).


Regards,
Mark.

_______________________________________________

Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

--
Priya Bhat

--
Priya Bhat

-----Inline Attachment Follows-----

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

--
Priya Bhat

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

--
Priya Bhat

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users