xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Gonzalez Herrera <dgonzalezh@gmail.com>
To: Boris Derzhavets <bderzhavets@yahoo.com>
Cc: xen-devel@lists.xensource.com, xen-users <xen-users@lists.xensource.com>
Subject: Re: XEN 4.0.1 + pv_ops Kernel + CentOS 5.5 x86_64, is there an easier way.
Date: Sun, 12 Dec 2010 15:59:49 -0500	[thread overview]
Message-ID: <AANLkTimEKkfh4hsXddo3D9s-hPyu4Exoa4mq5oOVv8xY@mail.gmail.com> (raw)
In-Reply-To: <729793.63221.qm@web56104.mail.re3.yahoo.com>


[-- Attachment #1.1: Type: text/plain, Size: 5791 bytes --]

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

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 <module>
    from xen.xend.server import SrvDaemon
  File "/usr/lib64/python2.7/site-packages/xen/xend/server/SrvDaemon.py",
line 26, in <module>
    import relocate
  File "/usr/lib64/python2.7/site-packages/xen/xend/server/relocate.py",
line 28, in <module>
    from xen.xend import XendDomain
  File "/usr/lib64/python2.7/site-packages/xen/xend/XendDomain.py", line 36,
in <module>
    from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo
  File "/usr/lib64/python2.7/site-packages/xen/xend/XendCheckpoint.py", line
20, in <module>
    from xen.xend import balloon, sxp, image
  File "/usr/lib64/python2.7/site-packages/xen/xend/image.py", line 46, in
<module>
    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@planetaradio.net
Skype: davidgonzalezh
WEB: http://www.dghvoip.com/
Proud Linux User #294661


On Sun, Dec 12, 2010 at 2:25 PM, Boris Derzhavets <bderzhavets@yahoo.com>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
>
> Boris.
>
> --- On *Sun, 12/12/10, David Gonzalez Herrera <dgonzalezh@gmail.com>*wrote:
>
>
> From: David Gonzalez Herrera <dgonzalezh@gmail.com>
> Subject: [Xen-users] XEN 4.0.1 + pv_ops Kernel + CentOS 5.5 x86_64, is
> there an easier way.
> To: "xen-users" <xen-users@lists.xensource.com>,
> xen-devel@lists.xensource.com
> 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@planetaradio.net <http://mc/compose?to=david@planetaradio.net>
> Skype: davidgonzalezh
> WEB: http://www.dghvoip.com/
> Proud Linux User #294661
>
>
> On Sun, Dec 12, 2010 at 12:20 PM, Ozan Safi <ozansafi@gmail.com<http://mc/compose?to=ozansafi@gmail.com>
> > 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
> )
>
> /Ozan
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com<http://mc/compose?to=Xen-users@lists.xensource.com>
> http://lists.xensource.com/xen-users
>
>
>
> -----Inline Attachment Follows-----
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com<http://mc/compose?to=Xen-users@lists.xensource.com>
> http://lists.xensource.com/xen-users
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 8452 bytes --]

[-- Attachment #2: Type: text/plain, Size: 137 bytes --]

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

  reply	other threads:[~2010-12-12 20:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 17:42 XEN 4.0.1 + pv_ops Kernel + CentOS 5.5 x86_64, is there an easier way David Gonzalez Herrera
2010-12-12 19:25 ` [Xen-users] " Boris Derzhavets
2010-12-12 20:59   ` David Gonzalez Herrera [this message]
2010-12-13  1:32     ` Michael A. Collins
2010-12-13  1:40       ` David Gonzalez Herrera
2010-12-13 10:01         ` Re: [Xen-users] " Keir Fraser
2010-12-13  6:00     ` Boris Derzhavets
2010-12-13 10:00       ` [Xen-devel] " Ian Campbell
2010-12-13 10:10     ` Re: [Xen-users] " M A Young

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTimEKkfh4hsXddo3D9s-hPyu4Exoa4mq5oOVv8xY@mail.gmail.com \
    --to=dgonzalezh@gmail.com \
    --cc=bderzhavets@yahoo.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).