This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Re: Xen 4.0.1 on Ubuntu Lucid 10.04 - Desktop / Server -

To: Outback Dingo <outbackdingo@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
From: Priya <pbhat@xxxxxxxxxxxx>
Date: Thu, 16 Sep 2010 16:53:13 -0400
Cc: Boris Derzhavets <bderzhavets@xxxxxxxxx>, nunziaG84@xxxxxxxxx, hurenkam <hurenkam@xxxxxxxxx>, Pasi Kärkkäinen <pasik@xxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 16 Sep 2010 13:55:10 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type; bh=ZyPiBjfvBZsHlGlYw8icLGWZG7yD9t4C7T8RuRMTmwQ=; b=MHrD5yrd8VlcSKHEUxvC7dezpus00mFLn6dbFHX5mYVRkBEyHpMrywHPzs0BLQEb3a oM/NMtVCRJtRGXSOC3qsZOy5D4FQeFXVxk9i8ldMWCyDw03fQrevNM7GkkouyRtCqZN4 RmA4Zfchs0SD2aGghwAjWNDhh4RhirVlk8vFQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=pSrFYpUzOa3KI9yRpBIXkX5RoT0mTB7T1uWJ/y8p/plGSeOxLW0r/c4GFVoExpuX6l Ue7rpjkwapb96y7Ybg+BV4SrlMwn4oGeiOnBd/vatk1Yqn91//h+ws2Le8DXEH+9SMFW Webi5wG1AMXDCBBMv1pHTRugdxHIygomLurS8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTin+Ved4U1CCe0rDTkdNDWiBYbU_DNitWqUegTPz@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <806461.45149.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <AANLkTikX=1DGia5ZpM2sz6dVdS2wB-HhDXK0_mAy1=hM@xxxxxxxxxxxxxx> <AANLkTinHEjHhBjGq9shOMR66n32L-B7W2fBiLxS8xFbF@xxxxxxxxxxxxxx> <AANLkTin+Ved4U1CCe0rDTkdNDWiBYbU_DNitWqUegTPz@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
@Outback Dingo,

Could you please share you .config  and grub file and advice on what you did differently from the documentation to compile the xen kernel. 


On Thu, Sep 16, 2010 at 4:08 PM, Priya <pbhat@xxxxxxxxxxxx> 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- -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...
 chmod g-s /usr/src/ -R
 make deb-pkg
 dpkg -i ../linux-image-*.deb
 update-initramfs -c -k

 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 ----
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' {
        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- dummy=dummy root=/dev/sda4 i915.modeset=0 earlyprintk=xen ro
        module (hd0,4)/boot/initrd.img-
---- 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.


 Choose the right Grub2 menu entry...


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  --->                                         │ │ 
  │ └────────────────────────────────────────────────────────────────


--- 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.


--- 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 !


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!


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


--- 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


> 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
kernel, then you have to rebuild your dom0 kernel, and enable it.

On my (Ubuntu Server 10.04.1 based) system, this gets mounted
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
not loaded).
2) Inconsistent installation of xentools (in wrong python directory or
mixed with older version).



Priya Bhat

Priya Bhat

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

Xen-users mailing list

Xen-users mailing list

Priya Bhat

Xen-users mailing list

Priya Bhat

Priya Bhat

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>