Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Xen 3.0.2 problems on amd64
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64
View previous topic :: View next topic  
Author Message
bnys
n00b
n00b


Joined: 29 Nov 2006
Posts: 1

PostPosted: Wed Nov 29, 2006 8:38 pm    Post subject: Xen 3.0.2 problems on amd64 Reply with quote

I am having a lot of trouble getting app-emulation/xen-3.0.2 to work. I have previously set up Xen (3.0.1) on both a dual opteron box and an AM2 based box and it worked fine. I have set up a new dual Opteron (socket 940) box (same as the other box that works with 3.0.1) and done a fresh install with the 2006.1 profile, etc.

My USE flags have 'nptlonly' set. I started with a fresh stage-3, then adjusted the USE flags (and package.keywords with ~amd64 for xen/xen-tools/xen-sources). I did an emerge -eND world, built a generic (non-xen) kernel and made sure I had a working system before emerging Xen/etc. I'm using GCC 4.x.

The Xen dom0 boots fine, but I can not get any domU to boot - there are absolutely no console messages (with '-c' passed to 'xm create'), the domU just seems to immediately reboot. Setting 'on_crash' or 'on_reboot' to 'preserve' doesn't help with debugging and the logs really don't contain much useful info, except that the VM was shut down because it was "rebooting too fast".

I built the example domU that comes with Xen (mini-os) - and it does give a little console output before spilling out a bunch of GPF memory/errors, etc.

Has anyone else worked with 3.0.2 on X86_64 from a *current/updated* system (with portage on/after: November 28, 2006) and had it work OK?

-- Burl.
Back to top
View user's profile Send private message
drdreff
n00b
n00b


Joined: 02 Dec 2006
Posts: 17

PostPosted: Thu Dec 14, 2006 11:02 pm    Post subject: My fight with Xen... Reply with quote

I had a simmilar problem but I'm bringing up Xen 3.0.2 fresh. My DomU will only come up to "Waiting for devices vtpm" I was missing "nptonly" from my use flags so I'll try that now.

~drdreff
Back to top
View user's profile Send private message
kox
n00b
n00b


Joined: 07 Jan 2005
Posts: 30
Location: Czech Republic

PostPosted: Fri Dec 15, 2006 3:11 pm    Post subject: Reply with quote

I thought that nptonly is for 32bit only.

Anyway I tried succesfully 3.0.2 on 32bit and 64bit without problems.
I was running 64bit version without "nptonly" in make.conf

You can try 3.0.3 ebuild from offical gentoo xen maintainer.
http://overlays.gentoo.org/dev/aross/browser

Try to post your make.conf, grub and hw specs.
I think ther is definitely something wrong with your config.
How much memory you assigned to dom0 from all your physical RAM?
Back to top
View user's profile Send private message
GJtje
n00b
n00b


Joined: 07 Nov 2004
Posts: 63
Location: Amsterdam, NL

PostPosted: Sat Dec 16, 2006 10:07 am    Post subject: Reply with quote

It's working fine here, without any useflags.

You should get some log output.
Back to top
View user's profile Send private message
Vulpes_
Tux's lil' helper
Tux's lil' helper


Joined: 24 Apr 2004
Posts: 119
Location: Hungary

PostPosted: Tue Jan 09, 2007 3:37 pm    Post subject: Reply with quote

I have similar problems. Fresh 64bit install of 2006.1 on a Core2Duo, Xen 3.0.3 from the link above with xen-sources 2.6.18. Dom0 loads without problems (well, I ran onto the nvidia-drivers incompatibility issue, but that's another story), but I can not initiate an already installed WinXP as a DomU. I have a suspicion that something is wrong with the "disk" section of the config file, but since I found almost no documentation on running a DomU from a different disk instead of az image file, I can not be sure. My other suspicion is in connection with the first one, as the 2.6.18 kernel does not fully support the AHCI SATA controller of my P965-DS4. Kernel 2.6.19 is fine, but does not exist as xen-sources yet.

Code:
szakadt-3 xen # xm create test.hvm
Using config file "test.hvm".
Started domain WinXP
szakadt-3 xen #


And that's it. No error messages, no reply from Xen or WinXP, no new window in X, nothing. The DomU seems to run, but there is no indication about it's status.

Code:
szakadt-3 xen # xm list -l
(domain
    (domid 0)
    (uuid 00000000-0000-0000-0000-000000000000)
    (vcpus 2)
    (cpu_weight 1.0)
    (memory 961)
    (shadow_memory 0)
    (maxmem 1882)
    (features )
    (name Domain-0)
    (on_poweroff destroy)
    (on_reboot restart)
    (on_crash restart)
    (state r-----)
    (shutdown_reason poweroff)
    (cpu_time 409.341401806)
    (online_vcpus 2)
)
(domain
    (domid 9)
    (uuid 26c65a65-34b0-3868-06ef-86d9fdb8feb3)
    (vcpus 1)
    (cpu_weight 1.0)
    (memory 1024)
    (shadow_memory 8)
    (maxmem 1024)
    (features )
    (name WinXP)
    (on_poweroff destroy)
    (on_reboot restart)
    (on_crash restart)
    (image
        (hvm
            (kernel /usr/lib/xen/boot/hvmloader)
            (root '/dev/sda1 rw')
            (device_model /usr/lib64/xen/bin/qemu-dm)
            (vcpus 1)
            (boot b)
            (serial pty)
            (vncunused 1)
            (sdl 1)
            (display :0.0)
            (xauthority /root/.xauthTGdqst)
            (usb 1)
            (usbdevice tablet)
        )
    )
    (device
        (vif
            (backend 0)
            (script vif-bridge)
            (bridge xenbr0)
            (mac 00:16:3e:74:32:ad)
            (type ioemu)
        )
    )
    (device (vbd (backend 0) (dev hdd:disk) (uname phy:/dev/sda1) (mode w)))
    (state ------)
    (shutdown_reason poweroff)
    (cpu_time 0.003646571)
    (online_vcpus 1)
    (up_time 8.81830096245)
    (start_time 1168352415.12)
    (store_mfn 85737)
)
szakadt-3 xen #


Code:
szakadt-3 xen # cat /etc/xen/test.hvm

import os, re
arch = os.uname()[4]
if re.search('64', arch):
    arch_libdir = 'lib64'
else:
    arch_libdir = 'lib'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 1024
shadow_memory = 8
name = "WinXP"
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk = ['phy:/dev/sda1,ioemu:hdd,w']
root = "/dev/sda1 rw"
cdrom='/dev/cdroms/cdrom0'
boot='b'
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
#console='ttyS0'
sdl=1
vnc=0
stdvga=0
serial='pty'
usb=1
usbdevice='tablet'
szakadt-3 xen #


Code:
szakadt-3 xen # emerge --info
Portage 2.1.1-r2 (default-linux/amd64/2006.1, gcc-4.1.1, glibc-2.4-r4, 2.6.18-xen x86_64)
=================================================================
System uname: 2.6.18-xen x86_64 Intel(R) Core(TM)2 CPU          6300  @ 1.86GHz
Gentoo Base System version 1.12.6
Last Sync: Tue, 09 Jan 2007 08:50:01 +0000
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: 1.3.7, 2.0.30
dev-lang/python:     2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.61
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.14
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=nocona -O2 -pipe -mno-tls-direct-seg-refs"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /usr/X11R6/bin/startx"
CXXFLAGS="-march=nocona -O2 -pipe -mno-tls-direct-seg-refs"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.inf.elte.hu/ ftp://gentoo.inf.elte.hu/ ftp://ftp.nyx.hu/gentoo http://ftp.snt.utwente.nl/pub/os/linux/gentoo ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo ftp://mirror.scarlet-internet.nl/pub/gentoo "
LANG="hu_HU@euro"
LC_ALL="hu_HU@euro"
LINGUAS="en hu"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/portage/local/layman/mozilla /usr/portage/local/layman/xen"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="amd64 X acpi alsa alsa_cards_hda_intel alsa_pcm_plugins_adpcm alsa_pcm_plugins_alaw alsa_pcm_plugins_asym alsa_pcm_plugins_copy alsa_pcm_plugins_dmix alsa_pcm_plugins_dshare alsa_pcm_plugins_dsnoop alsa_pcm_plugins_empty alsa_pcm_plugins_extplug alsa_pcm_plugins_file alsa_pcm_plugins_hooks alsa_pcm_plugins_iec958 alsa_pcm_plugins_ioplug alsa_pcm_plugins_ladspa alsa_pcm_plugins_lfloat alsa_pcm_plugins_linear alsa_pcm_plugins_meter alsa_pcm_plugins_mulaw alsa_pcm_plugins_multi alsa_pcm_plugins_null alsa_pcm_plugins_plug alsa_pcm_plugins_rate alsa_pcm_plugins_route alsa_pcm_plugins_share alsa_pcm_plugins_shm alsa_pcm_plugins_softvol apache apache2 apm arts berkdb bitmap-fonts bzip2 cddb cdr cli cracklib crypt cups dlloader dri dts dvd dvdr elibc_glibc exif fortran ftp gdbm gpm gtk gtk2 hal ieee1394 input_devices_keyboard input_devices_mouse isdnlog java javascript kde kernel_linux libg++ linguas_en linguas_hu lm_sensors mp3 mpi mplayer msn mysql ncurses nls nptl nptlonly nvidia opengl pam pcre pdf perl php ppds pppd python qt qt2 qt3 readline reflection samba sdl sensord session spl ssl tcpd truetype truetype-fonts type1-fonts udev unicode usb userland_GNU video_cards_nv video_cards_nvidia video_cards_vesa xml xorg zlib"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS

szakadt-3 xen #


Any ideas?
Back to top
View user's profile Send private message
Vulpes_
Tux's lil' helper
Tux's lil' helper


Joined: 24 Apr 2004
Posts: 119
Location: Hungary

PostPosted: Wed Jan 10, 2007 11:23 am    Post subject: Xen Reply with quote

Update: I recompiled xen and xen-tools with USE="ioemu", and after this the DomU starts with a window, although I still have problems with the export of block devices, namely the disks. Either the DomU can not see any disks, or the DomU Grub complains about missing disks. Still needs working on...
Back to top
View user's profile Send private message
GJtje
n00b
n00b


Joined: 07 Nov 2004
Posts: 63
Location: Amsterdam, NL

PostPosted: Wed Jan 10, 2007 11:17 pm    Post subject: Reply with quote

The configuration files change with every release so double check those are correct. :)
Back to top
View user's profile Send private message
Vulpes_
Tux's lil' helper
Tux's lil' helper


Joined: 24 Apr 2004
Posts: 119
Location: Hungary

PostPosted: Thu Jan 11, 2007 9:10 am    Post subject: Reply with quote

GJtje wrote:
The configuration files change with every release so double check those are correct. :)


Code:
disk = ['phy:/dev/sda,hda,w']
root = "/dev/sda1 rw"
This way, Xen starts Grub, but Grub can not find any disks to boot, therefore it stops with Error 21.

If I modify the "disk" line to anything else (hda to sda, sda1, etc.), not even Grub is started, but I get:
Code:
Boot from Hard Disk 0 failed
FATAL: Could not read the boot disk


I have two SATA drives, sda1 is the WinXP boot partition. Gentoo resides on sdb. I am all out of clues...
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64 All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum