I just started using xen and need some help getting going. I''m using
xen-3.3. So far I''ve created two kernels by editing configs/Linux.mk so
that I have 2.6.18.8-xen and 2.6.18-8-xenU. The xen kernel has some
extra configuration options, the xenU kernel is the default config that
comes with the xen distribution.
I''m booted into the xen dom0 kernel and have created a root disk for
the
domU machine. The bootup screen gets to the point where it says
"Continue..." and doesn''t get further. I tried using
gdbserver-xen but
the backtrace I see is useless hex addresses, I can''t get any useful
info from it. I''m not sure how to debug further. Can anyone provide a
tip?
Here is the console from domU:
$ sudo xm console test
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Xen virtual console successfully installed as xvc0
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
xen-vbd: registered block device major 8
blkfront: sda2: barriers enabled
XENBUS: Device with no driver: device/console/0
Freeing unused kernel memory: 140k freed
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
***************************************************************
***************************************************************
** WARNING: Currently emulating unsupported memory accesses **
** in /lib/tls glibc libraries. The emulation is **
** slow. To ensure full performance you should **
** install a ''xen-friendly'' (nosegneg) version of
**
** the library, or disable tls support by executing **
** the following as root: **
** mv /lib/tls /lib/tls.disabled **
** Offending process: modprobe (pid=663) **
***************************************************************
***************************************************************
Continuing...
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I guess this problem is related to TLS and the Xen documentation says something to disable TLS. Abdul Qadeer On Thu, Feb 12, 2009 at 6:44 AM, Jon Rafkind <rafkind@cs.utah.edu> wrote:> I just started using xen and need some help getting going. I''m using > xen-3.3. So far I''ve created two kernels by editing configs/Linux.mk so that > I have 2.6.18.8-xen and 2.6.18-8-xenU. The xen kernel has some extra > configuration options, the xenU kernel is the default config that comes with > the xen distribution. > > I''m booted into the xen dom0 kernel and have created a root disk for the > domU machine. The bootup screen gets to the point where it says > "Continue..." and doesn''t get further. I tried using gdbserver-xen but the > backtrace I see is useless hex addresses, I can''t get any useful info from > it. I''m not sure how to debug further. Can anyone provide a tip? > > Here is the console from domU: > > $ sudo xm console test > io scheduler cfq registered > RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize > Xen virtual console successfully installed as xvc0 > Event-channel device installed. netfront: Initialising > virtual ethernet driver. > i8042.c: No controller found. mice: PS/2 mouse device > common for all mice > TCP bic registered NET: Registered protocol family 1 > NET: Registered protocol family 17 > Using IPI No-Shortcut mode xen-vbd: registered block device major 8 > blkfront: sda2: barriers enabled XENBUS: Device with no driver: > device/console/0 > Freeing unused kernel memory: 140k freed kjournald starting. Commit > interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > > *************************************************************** > *************************************************************** > ** WARNING: Currently emulating unsupported memory accesses ** > ** in /lib/tls glibc libraries. The emulation is ** > ** slow. To ensure full performance you should ** > ** install a ''xen-friendly'' (nosegneg) version of ** > ** the library, or disable tls support by executing ** > ** the following as root: ** > ** mv /lib/tls /lib/tls.disabled ** > ** Offending process: modprobe (pid=663) ** > *************************************************************** > *************************************************************** > Continuing... > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Abdul Qadeer wrote:> I guess this problem is related to TLS and the Xen documentation > says something to disable TLS. >Well I already disabled tls (by moving it to tls.disabled) and anyway that directory was empty so I don''t know what its complaining about. The message shows up even when I "disabled" tls.> > Abdul Qadeer > > On Thu, Feb 12, 2009 at 6:44 AM, Jon Rafkind <rafkind@cs.utah.edu > <mailto:rafkind@cs.utah.edu>> wrote: > > I just started using xen and need some help getting going. I''m > using xen-3.3. So far I''ve created two kernels by editing > configs/Linux.mk so that I have 2.6.18.8-xen and 2.6.18-8-xenU. > The xen kernel has some extra configuration options, the xenU > kernel is the default config that comes with the xen distribution. > > I''m booted into the xen dom0 kernel and have created a root disk > for the domU machine. The bootup screen gets to the point where it > says "Continue..." and doesn''t get further. I tried using > gdbserver-xen but the backtrace I see is useless hex addresses, I > can''t get any useful info from it. I''m not sure how to debug > further. Can anyone provide a tip? > > Here is the console from domU: > > $ sudo xm console test > io scheduler cfq registered > RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize > Xen virtual console successfully installed as xvc0 > Event-channel device installed. netfront: > Initialising virtual ethernet driver. > i8042.c: No controller found. mice: PS/2 mouse > device common for all mice > TCP bic registered NET: Registered protocol > family 1 > NET: Registered protocol family 17 > Using IPI No-Shortcut mode xen-vbd: registered block device > major 8 > blkfront: sda2: barriers enabled XENBUS: Device with no > driver: device/console/0 > Freeing unused kernel memory: 140k freed kjournald starting. > Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > > *************************************************************** > *************************************************************** > ** WARNING: Currently emulating unsupported memory accesses ** > ** in /lib/tls glibc libraries. The emulation is ** > ** slow. To ensure full performance you should ** > ** install a ''xen-friendly'' (nosegneg) version of ** > ** the library, or disable tls support by executing ** > ** the following as root: ** > ** mv /lib/tls /lib/tls.disabled ** > ** Offending process: modprobe (pid=663) ** > *************************************************************** > *************************************************************** > > Continuing... > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> > http://lists.xensource.com/xen-users > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Abdul Qadeer wrote:> I guess this problem is related to TLS and the Xen documentation > says something to disable TLS. > >Check the archives. On a CentOS/Red Hat/Fedora host platform it''s just a question of creating a file called, say /etc/ld.so.conf.d/xen.conf (the .conf suffix is importat and put this in it: # This directive teaches ldconfig to search in nosegneg subdirectories # and cache the DSOs there with extra bit 0 set in their hwcap match # fields. In Xen guest kernels, the vDSO tells the dynamic linker to # search in nosegneg subdirectories and to match this extra hwcap bit # in the ld.so.cache file. hwcap 0 nosegneg You should probably run /sbin/ldconfig afterwards and then reboot. jch _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jon Rafkind wrote:> Here is the console from domU: > > > *************************************************************** > *************************************************************** > ** WARNING: Currently emulating unsupported memory accesses ** > ** in /lib/tls glibc libraries. The emulation is ** > ** slow. To ensure full performance you should ** > ** install a ''xen-friendly'' (nosegneg) version of ** > ** the library, or disable tls support by executing ** > ** the following as root: ** > ** mv /lib/tls /lib/tls.disabled ** > ** Offending process: modprobe (pid=663) ** > *************************************************************** > *************************************************************** > > Continuing...It might only be that you don''t have a VPS physical console, and that your VPS is fully booted, but you can''t see it. There are few things to check. First, check that your VPS has a "console" device in /dev. Mount your domU filesystem in the dom0, go in /dev and do: /dev/MAKEDEV console If you are using a modern Xen kernel and hypervisor, you should check the parameters of the startup file. Check that it has the following option: extra = "4 TERM=xterm xencons=tty console=tty1" Then start your VPS and watch it booting. Note that once it''s booted up, you should check that it has a xen friendly libc6 installed (in Debian, you would do "apt-get install libc6-xen"). I hope that helps. Thomas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > extra = "4 TERM=xterm xencons=tty console=tty1" > > Then start your VPS and watch it booting. Note that once it''s booted up, > you should check that it has a xen friendly libc6 installed (in Debian, > you would do "apt-get install libc6-xen"). > >Thanks. These extra arguments were what I was missing. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users