headers
Todd Deshane | 1 Feb 01:57
Favicon

Re: [XCP] No networking in XCP-XAPI on Debian 6

On Tue, Jan 31, 2012 at 1:36 PM, Srujan Kotikela <ksrujandas <at> gmail.com> wrote:
> Hi,
>
> I have followed the http://wiki.xen.org/wiki/XAPI_on_Ubuntu and installed
> xcp-xapi on Debian 6. Everything went smooth and everything looks fine. But
> after the reboot, the network is not working.
>
> Any ideas?
>

Did you try:
http://wiki.xen.org/wiki/Networking_with_the_XCP_toolstack

Thanks,
Todd

--

-- 
Todd Deshane
http://www.linkedin.com/in/deshantm
http://blog.xen.org/
http://wiki.xen.org/
Permalink | Reply | 1 comment |
headers
Zoran Tasic | 1 Feb 09:11
Favicon

(no subject)


Just for an addition on my previous message. This page I found on net, but can not understand what files are necessary:

So, one more time, please help
--
Zoran Tasic
_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users
Permalink | Reply | 0 comments |
headers
Zoran Tasic | 1 Feb 08:13
Favicon

XCP could not install through PXE Server

Hi, everyone,

For a last couple of days I have a problem to install XCP 1.1 on my HP Proliant.
Namely, only way that I could do installation is through existing PXE Server. But, what ever I tried, I get same error "Incorret or damaged kernel image" (image is not damaged, because I can install XCP 1.1 on any workstation with DVD ROM).

So, my question is:
On PXE server (i.e) Ubuntu, Windows, Debian is working fine and I need same settings for XCP, bellow those two lines I need to change, but I don't know with what exactly. Here are those two lines:

Label XEN CLoud Platform
Menu DEFAULT
KERNEL ???
APPEND ???

Could you please help me to solve my issue. Thanks in advance

--
Zoran Tasic
_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users
Permalink | Reply | 0 comments |
headers
Vincent Jean-François | 1 Feb 10:52
Favicon

Xen dom compilation & rpmlint issues (special intends to Michael Young)


Hello,

I've succeeded to compile dhe dom0 provided by Michael Young here : http://xenbits.xen.org/people/mayoung/testing/x86_64/kernel-2.6.32-131.12.1.el6.xendom0.x86_64.rpm

But I've experiencing errors while running rpmlint on the package :

kernel-XenDom0.x86_64: E: shared-lib-without-dependency-information /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso32-syscall.so
kernel-XenDom0.x86_64: E: missing-PT_GNU_STACK-section /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso32-syscall.so
The binary lacks a PT_GNU_STACK section.  This forces the dynamic linker to make the stack executable. 
Usual suspects include use of a non-GNU linker or an old GNU linker version.

kernel-XenDom0.x86_64: E: shared-lib-without-dependency-information /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso32-int80.so
kernel-XenDom0.x86_64: E: missing-PT_GNU_STACK-section /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso32-int80.so
The binary lacks a PT_GNU_STACK section.  This forces the dynamic linker to make the stack executable. 
Usual suspects include use of a non-GNU linker or an old GNU linker version.
kernel-XenDom0.x86_64: E: shared-lib-without-dependency-information /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso32-sysenter.so
kernel-XenDom0.x86_64: E: missing-PT_GNU_STACK-section /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso32-sysenter.so
The binary lacks a PT_GNU_STACK section.  This forces the dynamic linker to make the stack executable. 
Usual suspects include use of a non-GNU linker or an old GNU linker version.
kernel-XenDom0.x86_64: E: shared-lib-without-dependency-information /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso.so
kernel-XenDom0.x86_64: E: missing-PT_GNU_STACK-section /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso.so
The binary lacks a PT_GNU_STACK section.  This forces the dynamic linker to make the stack executable. 
Usual suspects include use of a non-GNU linker or an old GNU linker version.
kernel-XenDom0.x86_64: E: shared-lib-without-dependency-information /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso32-syscall.so
kernel-XenDom0.x86_64: E: missing-PT_GNU_STACK-section /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso32-syscall.so
The binary lacks a PT_GNU_STACK section.  This forces the dynamic linker to make the stack executable. 
Usual suspects include use of a non-GNU linker or an old GNU linker version.
kernel-XenDom0.x86_64: E: shared-lib-without-dependency-information /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso32-int80.so
kernel-XenDom0.x86_64: E: missing-PT_GNU_STACK-section /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso32-int80.so
The binary lacks a PT_GNU_STACK section.  This forces the dynamic linker to make the stack executable. 
Usual suspects include use of a non-GNU linker or an old GNU linker version.
kernel-XenDom0.x86_64: E: shared-lib-without-dependency-information /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso32-sysenter.so
kernel-XenDom0.x86_64: E: missing-PT_GNU_STACK-section /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso32-sysenter.so
The binary lacks a PT_GNU_STACK section.  This forces the dynamic linker to make the stack executable. 
Usual suspects include use of a non-GNU linker or an old GNU linker version.
kernel-XenDom0.x86_64: E: shared-lib-without-dependency-information /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso.so
kernel-XenDom0.x86_64: E: missing-PT_GNU_STACK-section /lib/modules/2.6.32-131.12.1.awl6.x86_64/vdso/vdso.so
The binary lacks a PT_GNU_STACK section.  This forces the dynamic linker to make the stack executable. 
Usual suspects include use of a non-GNU linker or an old GNU linker version.

Do you have any idea to fix that (other than changing rpmlint filtering) ?

JF

Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses
destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce
message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité
du message ne pouvant être assurée sur Internet, la responsabilité d'Atos ne pourra être
recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir
cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa
responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also
be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos liability cannot be triggered for the message
content. Although the sender endeavours to maintain a computer virus-free network, the sender does not
warrant that this transmission is virus-free and will not be liable for any damages resulting from any
virus transmitted.
Permalink | Reply | 0 comments |
headers
Likarpenkov Alexander | 1 Feb 11:31
Picon

Re: [Xen-devel] VGA passthough still not working

You yourself do something you can do, or is your only one link to the 
internet? You are able to answer questions or do not have enough of the 
cerebellum? Or config files provided or not flood.

 KRW> On Mon, Jan 23, 2012 at 12:53:50PM +0100, Sandi Romih wrote:
 ??>> Pasi,
 ??>>
 ??>> Yes, I did verify that IOMMU is enabled. I get this in my xm dmesg:
 ??>>
 ??>> (XEN) I/O virtualisation enabled
 ??>>
 ??>> (XEN) Intel VT-d Snoop Control supported.(XEN) Intel VT-d DMA
 ??>> Passthrough not supported.(XEN) Intel VT-d Queued Invalidation
 ??>> supported.(XEN) Intel VT-d Interrupt Remapping not supported.
 ??>>
 ??>> But I dont think I have this message (I am not near my system now, so
 ??>> I can not confirm)
 ??>>
 ??>> (XEN) I/O virtualisation for PV guests enabled
 ??>>
 ??>> I believe that many have managed to get VGA passthru working, but they
 ??>> generally dont post their stories. one only finds the problems they
 ??>> are encountering when searching about this. That is why it would be
 ??>> nice to put together a kind of manual in the wiki which would have all
 ??>> this info together in one location.

 KRW> http://lmgtfy.com/?q=Xen+VGA+passthrough
Permalink | Reply | 1 comment |
headers
Likarpenkov Alexander | 1 Feb 12:12
Picon

Re: [Xen-devel] VGA passthough still not working

I'm really sorry. something I do not understand true

 LA> You yourself do something you can do, or is your only one link to the
 LA> internet? You are able to answer questions or do not have enough of the
 LA> cerebellum? Or config files provided or not flood.

 KRW>> On Mon, Jan 23, 2012 at 12:53:50PM +0100, Sandi Romih wrote:
 ??>>> Pasi,
 ??>>>
 ??>>> Yes, I did verify that IOMMU is enabled. I get this in my xm dmesg:
 ??>>>
 ??>>> (XEN) I/O virtualisation enabled
 ??>>>
 ??>>> (XEN) Intel VT-d Snoop Control supported.(XEN) Intel VT-d DMA
 ??>>> Passthrough not supported.(XEN) Intel VT-d Queued Invalidation
 ??>>> supported.(XEN) Intel VT-d Interrupt Remapping not supported.
 ??>>>
 ??>>> But I dont think I have this message (I am not near my system now, so
 ??>>> I can not confirm)
 ??>>>
 ??>>> (XEN) I/O virtualisation for PV guests enabled
 ??>>>
 ??>>> I believe that many have managed to get VGA passthru working, but
 ??>>> they generally dont post their stories. one only finds the problems
 ??>>> they are encountering when searching about this. That is why it would
 ??>>> be nice to put together a kind of manual in the wiki which would have
 ??>>> all this info together in one location.

 KRW>> http://lmgtfy.com/?q=Xen+VGA+passthrough

--
? ?????????, ??????????? ?????????
??????? ???????-???????????
???????? IT, ???????????????????? ?????? VEGA
E-mail: al <at> ohosting.org.ua
???:  +380 63 617-18-62
Permalink | Reply | 0 comments |
headers
Hossein Ansari | 1 Feb 12:14
Picon

[xcp] problem in running xcp-networkd in ubuntu 11.10

Hi
I install the xcp from the http://wiki.xen.org/wiki/XAPI_on_Ubuntu.
But I got this error while configuring xcp-xapi:

xcp-networkd (1.3.2-1ubuntu1~oneiric1) wird eingerichtet ... Starting the XCP networking daemon: .............................. * failed to start xcp-networkd. invoke-rc.d: initscript xcp-networkd, action "start" failed.
when I comment the "2>/dev/null" in the script I see this error:

Fatal error: exception Unix.Unix_error(20, "open", "/etc/xcp/network.conf")
but there is not "/etc/xcp/network.conf"

I use ubuntu 11.10 and I install the openvswitch-datapath-dkms before.

Thanks for your answers.

Greetings
Hossein
_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users
Permalink | Reply | 2 comments |
headers
Ivan Fitenko | 1 Feb 14:40
Favicon

Re: How to find we are in Dom0 or DomU from a driver

Use xen_initial_domain() from xen/xen.h:

if (xen_initial_domain()) {
	/* Dom0-related code goes here*/

On Fri, Jan 20, 2012 at 04:04:39PM +0530, Venkatesh P N wrote:
> Hi,
> 
> I am currently using Citrix Xen6.0 Server and installed a couple of guests on
> it.
> 
> I am writing a PCI driver common for Dom0 and DomU.
> In the driver, I need to write the code like
> 
> If I am in Dom0
> {
> Do Dom0 related ops (physical driver)
> }
> else
> {
> Do DomU related ops. (virtual driver)
> }
> 
> So, How can we find out whether we are in Dom0 or DomU from the driver level.
> Other than "/proc/xen/capabilities", is there any kernel function or data
> structure to find out this.
> 
> Thanks
> Petla Venkatesh
> 

> _______________________________________________
> Xen-users mailing list
> Xen-users <at> lists.xensource.com
> http://lists.xensource.com/xen-users
Permalink | Reply | 0 comments |
headers
Ivan Fitenko | 1 Feb 14:50
Picon

Re: How to find we are in Dom0 or DomU from a driver

Use xen_initial_domain() from xen/xen.h:

if (xen_initial_domain()) {
        /* Dom0-related code goes here*/
.....

On Fri, Jan 20, 2012 at 04:04:39PM +0530, Venkatesh P N wrote:
> Hi,
> 
> I am currently using Citrix Xen6.0 Server and installed a couple of guests on
> it.
> 
> I am writing a PCI driver common for Dom0 and DomU.
> In the driver, I need to write the code like
> 
> If I am in Dom0
> {
> Do Dom0 related ops (physical driver)
> }
> else
> {
> Do DomU related ops. (virtual driver)
> }
> 
> So, How can we find out whether we are in Dom0 or DomU from the driver level.
> Other than "/proc/xen/capabilities", is there any kernel function or data
> structure to find out this.
> 
> Thanks
> Petla Venkatesh
> 

> _______________________________________________
> Xen-users mailing list
> Xen-users <at> lists.xensource.com
> http://lists.xensource.com/xen-users
Permalink | Reply | 0 comments |
headers
Todd Deshane | 1 Feb 15:56
Favicon

Re: Stubdom in Xen4.1.2

On Wed, Jan 25, 2012 at 6:03 PM, Jeff Mason <jmason <at> cputech.com> wrote:
> I am trying to run a HVM using stubdom in Xen4.1.2.  The file
> .../stubdom/README states that I need to set up a couple of things in
> /exports/usr/share/xen and then execute /usr/sbin/fs-backend.
>
> I cannot find any program (or associated source file) for fs-backend in
> my xen tree or in Ubuntu installation (using a self built kernel.org
> kernel for dom 0).  Does this still exist and does it still need to be run?
>

I'm not sure about those steps. The README might be out of date.
Anyone know for sure?

I know this is up-to-date:
http://wiki.xen.org/wiki/Device_Model_Stub_Domains

Hope that helps.

Thanks,
Todd

--

-- 
Todd Deshane
http://www.linkedin.com/in/deshantm
http://blog.xen.org/
http://wiki.xen.org/
Permalink | Reply | 1 comment |

Gmane