Re: [Xen-devel] Re: [Xen-users] XEN 4.0.1 + pv_ops Kernel + CentOS 5.5 x86_64, is there an easier way.

[Keir Fraser <keir@xxxxxxx>]

You may need a line like this in /etc/fstab:
none /proc/xen xenfs defaults 0 0

 -- Keir

On 13/12/2010 01:40, "David Gonzalez Herrera" <dgonzalezh@xxxxxxxxx> wrote:

> Changed it, and unfortunately the error when starting xend shows up again.
> 
> Thank you for your help I got a little further ;)
> 
> ---
> David Gonzalez H.
> DGHVoIP - OPEN SOURCE TELEPHONY SOLUTIONS
> Phone Bogotá: +(57-1)289-1168
> Phone Medellin: +(57-4)247-0985
> Mobile: +(57)315-838-8326
> MSN: david@xxxxxxxxxxxxxxxx
> Skype: davidgonzalezh
> WEB: http://www.dghvoip.com/
> Proud Linux User #294661
> 
> 
> On Sun, Dec 12, 2010 at 8:32 PM, Michael A. Collins <mike@xxxxxxxxxxx> wrote:
>> On Sun, 12 Dec 2010 15:59:49 -0500, David Gonzalez Herrera
>> <dgonzalezh@xxxxxxxxx> wrote:
>>> Why thank you for the quick reply :)
>>> 
>>> I've already tried all that, however not used the init=/sbin/upstart.
>>> It boots using the myoung pre-built RPM xend doesn't start, In fact I
>>> wanted to paste some of the output I get
>>> 
>>> [root@vmhost ~]# uname -r
>>> 2.6.32.26-174.xendom0.fc12.x86_64
>>> 
>>> grub.conf part
>>> 
>>> title Fedora (2.6.32.26-174.xendom0.fc12.x86_64)
>>>  root (hd0,0)
>>> kernel /xen.gz loglvl=all guest_loglvl=all noreboot lapic=debug
>>> iommu=off
>>> kernel /vmlinuz-2.6.32.26-174.xendom0.fc12.x86_64 ro
>>> root=/dev/mapper/gw-root init=/sbin/upstart nomodeset selinux=0
>>> rd_LVM_LV=gw/root rd_LVM_LV=gw/swap rd_NO_LUKS rd_NO_MD rd_NO_DM
>>> LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=es rhgb
>>> initrd /initramfs-2.6.32.26-174.xendom0.fc12.x86_64.img
>>> 
>> 
>> Your grub line is wrong, it should be module after the first kernel.  I'm
>> sure that replacing the second instance of kernel with module in your
>> grub.conf will get you a little further.
>>> The xen build howto also stated to use the "/proc/xen" mount on
>>> /etc/fstab, I have that but boot compains about the mountpoint not
>>> existing.
>>> 
>>> mount: mount point /proc/xen does not exist
>>> 
>>> and finally:
>>> 
>>> [root@vmhost ~]# xend
>>> ERROR Internal error: Could not obtain handle on privileged command
>>> interface (2 = No such file or directory)
>>> Traceback (most recent call last):
>>>   File "/usr/sbin/xend", line 16, in
>>>     from xen.xend.server import SrvDaemon
>>>   File
>>> "/usr/lib64/python2.7/site-packages/xen/xend/server/SrvDaemon.py",
>>> line 26, in
>>>     import relocate
>>>   File
>>> "/usr/lib64/python2.7/site-packages/xen/xend/server/relocate.py", line
>>> 28, in
>>>     from xen.xend import XendDomain
>>>   File "/usr/lib64/python2.7/site-packages/xen/xend/XendDomain.py",
>>> line 36, in
>>>     from xen.xend import XendOptions, XendCheckpoint,
>>> XendDomainInfo
>>>   File
>>> "/usr/lib64/python2.7/site-packages/xen/xend/XendCheckpoint.py", line
>>> 20, in
>>>     from xen.xend import balloon, sxp, image
>>>   File "/usr/lib64/python2.7/site-packages/xen/xend/image.py", line
>>> 46, in
>>>     xc = xen.lowlevel.xc.xc()
>>> xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle
>>> on privileged command interface (2 = No such file or directory)')
>>> 
>>> Weird 'cause that error only showed up when you don't have a xenified
>>> kernel loaded but my uname says the countrary, so I'm lost.
>>> 
>>> I'm compiling the kernel with the instructions/.config file found on
>>> your link, I'll try to boot it and will tell you the outcome.
>>> 
>>> Any ideas on what to do?
>>> 
>>> Thank you people.
>>> ---
>>> David Gonzalez H.
>>> DGHVoIP - OPEN SOURCE TELEPHONY SOLUTIONS
>>> Phone Bogotá: +(57-1)289-1168
>>> Phone Medellin: +(57-4)247-0985
>>>  Mobile: +(57)315-838-8326
>>> MSN: david@xxxxxxxxxxxxxxxx [1]
>>> Skype: davidgonzalezh
>>> WEB: http://www.dghvoip.com/ [2]
>>>  Proud Linux User #294661
>>> 
>>> On Sun, Dec 12, 2010 at 2:25 PM, Boris Derzhavets  wrote:
>>> 
>>> 
>>>> I've tried compiling the Kernel from Source, I've also tried Fedora
>>> 14, which has a flaky > pv_ops Dom0 kernel which DOESN'T work at all,
>>> but none of these seem to work.
>>> 
>>> http://www.linuxtoday.com/infrastructure/2010090900235OSSV [4]
>>> 
>>> Boris.
>>> 
>>> 
>>> --- On SUN, 12/12/10, DAVID GONZALEZ HERRERA __ wrote:
>>> 
>>> From: David Gonzalez Herrera
>>> Subject: [Xen-users] XEN 4.0.1 + pv_ops Kernel + CentOS 5.5 x86_64, is
>>> there an easier way.
>>>  To: "xen-users" , xen-devel@xxxxxxxxxxxxxxxxxxx [7]
>>> 
>>>  Date: Sunday, December 12, 2010, 12:42 PM
>>> 
>>> Hi
>>> 
>>> As you may've seen from my last posts I'm struggling to get the setup
>>> on my subject line to work without flaws.
>>> 
>>> I've tried compiling the Kernel from Source, I've also tried Fedora
>>> 14, which has a flaky pv_ops Dom0 kernel which DOESN'T work at all,
>>> but none of these seem to work.
>>> 
>>> I'm a mid-time XEN user, I just love it and want to stay away from KVM
>>>  but the migration path is too rough when you want pv_ops Dom0, and
>>> all seem to be just projects, TODOs and snapshots, nothing really
>>> serious IMHO there's lots of misleading info and there are many gaps
>>> on existing howtos, I've read that SuSE has back-ported some stuff
>>> from 2.6.3.x branch into 2.6.18 but I want native and I don't want to
>>> be toying around with Debian'ish stuff in production environments.
>>> 
>>> I'd like to keep using RH like system because of their robustness and
>>> because I'm used to work with it as a RHCE.
>>> 
>>> Please, would you help me find a distro which would integrate
>>> 
>>> RH like 
>>> XEN 4.0.1
>>> pv_ops Dom0 kernel
>>> 
>>> I want to run telephony stuff on them and tho I kinda got my Openvox
>>> A1200P card to work 50% of the times now with xen 4.0.1 it won't work
>>> but I guess that's because I'm using Kernel 2.6.18.x with XEN 4 which
>>> is not recommended.
>>> 
>>> Any advise will be deeply appreciated.
>>> 
>>> Thank you.
>>> 
>>> ---
>>> David Gonzalez H.
>>> DGHVoIP - OPEN SOURCE TELEPHONY SOLUTIONS
>>> Phone Bogotá: +(57-1)289-1168
>>>  Phone Medellin: +(57-4)247-0985
>>>  Mobile: +(57)315-838-8326
>>> MSN: david@xxxxxxxxxxxxxxxx [8]
>>> Skype: davidgonzalezh
>>> WEB: http://www.dghvoip.com/ [9]
>>>  Proud Linux User #294661
>>> 
>>> On Sun, Dec 12, 2010 at 12:20 PM, Ozan Safi  wrote:
>>> 
>>>  Hi,
>>> Has there been any development in the OVF support for Xen?
>>> It was in the roadmap of Xen 3.4
>>> (http://www.xen.org/download/roadmap.html [11])
>>> 
>>> 
>>> /Ozan
>>> _______________________________________________
>>>  Xen-users mailing list
>>>  Xen-users@xxxxxxxxxxxxxxxxxxx [12]
>>>  http://lists.xensource.com/xen-users [13]
>>> 
>>> 
>>> -----Inline Attachment Follows-----
>>> 
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx [14]
>>>  http://lists.xensource.com/xen-users [15]
>>> 
>>> 
>>> 
>>> Links:
>>> ------
>>> [1] mailto:david@xxxxxxxxxxxxxxxx
>>> [2] http://www.dghvoip.com/
>>> [3] mailto:bderzhavets@xxxxxxxxx
>>> [4] http://www.linuxtoday.com/infrastructure/2010090900235OSSV
>>> [5] mailto:dgonzalezh@xxxxxxxxx
>>> [6] mailto:xen-users@xxxxxxxxxxxxxxxxxxx
>>> [7] mailto:xen-devel@xxxxxxxxxxxxxxxxxxx
>>> [8] http://mc/compose?to=david@xxxxxxxxxxxxxxxx
>>> [9] http://www.dghvoip.com/
>>> [10] http://mc/compose?to=ozansafi@xxxxxxxxx
>>> [11] http://www.xen.org/download/roadmap.html
>>> [12] http://mc/compose?to=Xen-users@xxxxxxxxxxxxxxxxxxx
>>> [13] http://lists.xensource.com/xen-users
>>> [14] http://mc/compose?to=Xen-users@xxxxxxxxxxxxxxxxxxx
>>> [15] http://lists.xensource.com/xen-users
>> Mike
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



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