Hi Mukesh:
> Correct. Just git clone xen tree to match your version, then edit the file to add printk, then build xen. copy xen to target machine over to /boot. Then edit grub kernel line to boot new xen.
I after building Xen I tried a 'make install-xen' but got a problem with EFI_VENDOR not being defined.
See attached snapshot.
Looks like ‘make install-xen’ installed a xen kerneL in /boot
piet@piet-t3600:/boot$ ls -lt | more
total 94131
lrwxrwxrwx 1 root root 16 Sep 17 17:35 xen-4.4.gz -> xen-4.4.2-pre.gz
lrwxrwxrwx 1 root root 16 Sep 17 17:35 xen-4.gz -> xen-4.4.2-pre.gz
lrwxrwxrwx 1 root root 16 Sep 17 17:35 xen.gz -> xen-4.4.2-pre.gz
-rw-r--r-- 1 root root 844203 Sep 17 16:26
xen-4.4.2-pre.gz
-rw-r--r-- 1 root root 15440366 Sep 17 16:26 xen-syms-4.4.2-pre
-rw-r--r-- 1 root root 28743841 Aug 8 16:59 initrd.img-3.13.0-32-generic
drwxr-xr-x 5 root root 1024 Aug 8 16:58 grubdded to the /boot partition:
The grub default is “Ubuntu GNU/Linux, with Xen hypervisor” (see attached grub.cfg).
I’m rather rusty on the new and improved grub syntax. I’d prefer not bricking my Ubuntu workstation.
J
The various menu entry‘s under the Xen submenu look very similar. Currently is offering a 3.13.0-32 kernel
And a 3.13.0-24 kernel (modules are in /lib/modules).
Looks to me like I can easily provide a different multiboot line:
Currently:
multiboot /xen-4.4-amd64.gz
placeholder ${xen_rm_opts}
Change it to:
multiboot /xen-4.4.2-pre.gz placeholder ${xen_rm_opts}]
If xen fails to boot I should still be able to boot the original Ubuntu-14.04 stock linux kernels.
It’s not obvious how to easily make it possible to select between the two Xen images without
Potentially messing up system installation scripts.
-piet
--
Pete/Piet Delaney
O: +1 408 935-1813
C: +1 408 646-8557
H: +1 408 243-8872
Home Email: piet.delaney@xxxxxxxxx
-----Original Message-----
From: Mukesh Rathor [mailto:mukesh.rathor@xxxxxxxxxx]
Sent: Tuesday, September 16, 2014 7:16 PM
To: Pete Delaney
Cc: xen-devel@xxxxxxxxxxxxx; piet.delaney@xxxxxxxxx; Elaine Huang; Tedi Tedijanto
Subject: Re: gdbsx - xg_attach:Unable to pause domain:1; failed to attach to domain:1 errno:13
On Tue, 16 Sep 2014 22:58:37 +0000
Pete Delaney <pdelaney@xxxxxxxxxxxxxxx> wrote:
> Hi Mukesh:
>
>
>
> Thanks for your help on enabling gdbsx...
>
>
>
> > Hmm... that all seems ok then. Can you check your permissions on :
>
>
>
> > /proc/xen/privcmd
>
>
>
> root@piet-openxen-blade:~# ls -l /proc/xen/privcmd
>
> -rw------- 1 root root 0 Aug 11 13:37 /proc/xen/privcmd
>
>
>
> Privcmd seems to be a hypervisor call available from userland
>
> For Xen developers:
>
>
>
>
>
http://sanifool.com/2013/02/08/invoking-an-hypercall-from-userland-via
> -privcmd/
>
>
>
>
>
> > Other possibilities:
>
> > - do you have xsm enabled?
>
>
>
> Don't think so. I've heard this security stuff can get in the way.
>
> Doing a 'xl list -Z' doesn't show any security
> labels. [Wish I had
> Synergy Installed]
>
>
>
>
>
> >- can you put a printk in xen file common/domctl.c:
>
>
>
> Sure but first I likely need to start using the openxen code that I
> compiled from src.
>
> I'm currently using openxen installed via a Ubuntu 14.04 package.
>
>
>
> Mind explaining the best way to proceed on switching to the openxen
>
> That I compiled from source? I thought some of it might be installed
> at /usr/local/
>
> And perhaps just changing a search path or two will be sufficient.
>
>
>
> I suspect I'll need to put a new xen kernel on /boot and update the
> grub config.
Correct. Just git clone xen tree to match your version, then edit the file to add printk, then build xen. copy xen to target machine over to /boot. Then edit grub kernel line to boot new xen.
Mukesh
