[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] XEN VT/VMX problems / xm create (detailed info + configs :)



Hello,

which Version of SDL you installed?

Which ebuild?

Please help!

Regards Roland

Am Mittwoch, 12. Juli 2006 00:33 schrieb John McCullough:
> I've had the best luck connecting manually with vnc.  You connect to the
> same port as the domainid.  For example:
>
> Name                              ID Mem(MiB) VCPUs State  Time(s)
> Domain-0                           0      257     2 r-----    73.7
> winxp-snap0                        4      256     1 r-----    29.7
>
> You would use "xvncviewer xenhost:4"
>
> SDL does work for me.  With respect to the cdrom, I've seen a note or
> two that suggest that you should use the actual cdrom device rather than
> the /dev/cdrom symlink.  The cdrom wasn't functioning as well as I would
> have liked, but I have been using an iso image of the cdrom instead.
>
> Using the iso image may help booting.
>
> Regards,
> John
>
> On Tue, Jul 11, 2006 at 02:07:15PM -0700, Simon Gao wrote:
> > I had the same problem on Gentoo with 2.6.16.18-xen, xen-3.0.2. Have you
> > made any progress?
> >
> > Simon Gao
> >
> > Thomas Grub wrote:
> > > Hi List!
> > >
> > > i am using xen-3.0.2-2 dom0 2.6.16-xen (Gentoo 2006.0 base) with SMP
> > > (Intel Core Duo 2x2GHz) and i got problems (finaly) getting 'xm create
> > > mywinxp.hvm' working. i spend almost a week now with reading many faq,
> > > doc, example configs...bla...bla.. so i think i am realy close to get
> > > it finaly running sooo please help :)
> > >
> > > ok, so - first i tried to use ebuilds (app-emulation/xen, etc.) - with
> > > no success (problems with system startup - initrd problems with my sda
> > > hd (serial ata -> scsi)). well...
> > >
> > > so i am currently using the xen-3.0.2-src.tgz.
> > > for building i am doing like the README told:
> > >   make linux-2.6-xen-config CONFIGMODE=menuconfig
> > >   make linux-2.6-xen-build
> > >   make linux-2.6-xen-install
> > >
> > > the kernel builds and boots without errors.
> > >
> > >>>> 'xend start' gives WARNING in xend.log "No vm path in store for
> > >>>> existing domain 0" is this critial ?
> > >
> > > [xend start - /var/log/xend.log]
> > >   [2006-06-12 04:31:52 xend] INFO (SrvDaemon:278) Xend Daemon started
> > >   [2006-06-12 04:31:52 xend] INFO (SrvDaemon:282) Xend changeset: Thu
> > > Apr 13 15:18:37 2006 +0100 9617 5802713c159b. [2006-06-12 04:31:52
> > > xend.XendDomainInfo] DEBUG (XendDomainInfo:200)
> > > XendDomainInfo.recreate({'paused': 0, 'cpu_time': 17850053001L,
> > > 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
> > > 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 1048576,
> > > 'maxmem_kb': -4, 'max_vcpu_id': 1, 'crashed': 0, 'running': 1,
> > > 'shutdown': 0, 'online_vcpus': 2, 'blocked': 0}) [2006-06-12 04:31:52
> > > xend.XendDomainInfo] INFO (XendDomainInfo:212) Recreating domain 0,
> > > UUID 00000000-0000-0000-0000-000000000000. [2006-06-12 04:31:52
> > > xend.XendDomainInfo] WARNING (XendDomainInfo:234) No vm path in store
> > > for existing domain 0 [2006-06-12 04:31:52 xend.XendDomainInfo] DEBUG
> > > (XendDomainInfo:671) Storing VM details: {'ssidref': '0', 'uuid':
> > > '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart',
> > > 'on_poweroff': 'destroy', 'name': 'Domain-0', 'vcpus': '2',
> > > 'vcpu_avail': '3', 'memory': '1024', 'on_crash': 'restart', 'maxmem':
> > > '1024'} [2006-06-12 04:31:52 xend.XendDomainInfo] DEBUG
> > > (XendDomainInfo:696) Storing domain details: {'cpu/0/availability':
> > > 'online', 'memory/target': '1048576', 'cpu/1/availability': 'online',
> > > 'name': 'Domain-0', 'console/limit': '1048576', 'vm':
> > > '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} [2006-06-12
> > > 04:31:52 xend] DEBUG (XendDomain:152) number of vcpus to use is 0
> > > [2006-06-12 04:31:52 xend.XendDomainInfo] DEBUG (XendDomainInfo:877)
> > > XendDomainInfo.handleShutdownWatch
> > >
> > > xend seems to work, here is the 'xm info':
> > >   host                   : localhost
> > >   release                : 2.6.16-xen
> > >   version                : #10 SMP Mon Jun 12 00:56:24 CEST 2006
> > >   machine                : i686
> > >   nr_cpus                : 2
> > >   nr_nodes               : 1
> > >   sockets_per_node       : 1
> > >   cores_per_socket       : 2
> > >   threads_per_core       : 1
> > >   cpu_mhz                : 1997
> > >   hw_caps                : bfe9fbff:00100000:00000000:00000140:0000c1a9
> > >   total_memory           : 2039
> > >   free_memory            : 987
> > >   xen_major              : 3
> > >   xen_minor              : 0
> > >   xen_extra              : .2-2
> > >   xen_caps               : xen-3.0-x86_32 hvm-3.0-x86_32
> > >   platform_params        : virt_start=0xfc000000
> > >   xen_changeset          : Thu Apr 13 15:18:37 2006 +0100
> > > 9617:5802713c159b cc_compiler            : gcc version 3.4.4 (Gentoo
> > > 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8) cc_compile_by          : root
> > >   cc_compile_domain      : (none)
> > >   cc_compile_date        : Tue Jun  6 19:14:34 CEST 2006
> > >
> > > so, i am trying to get an windows xp sp2 domU running. according to
> > > some howtos and posts i tried several xmdomains.cfgs. first i tried to
> > > do a cdrom install of windows xp. i used the xmexample.hvm file with
> > > the following modifications: memory = 256
> > >   acpi=0
> > >   disk = [ 'file:/xen/windows/xen_win_latest.img,ioemu:hda,w' ]
> > > (created with dd if=/dev/zero of=...) cdrom='/dev/cdrom'
> > >   boot='d'
> > >   sdl=1 (OR sdl=0 vnc=1 vncviewer=1)
> > >
> > > well if i try to boot with the sdl=1 option :
> > >   Using config file "xen_win_latest.hvm".
> > >   Started domain WindowsXP
> > >   xen windows #
> > >
> > > the cdrom drive is reading for about 1min ? but nothing happens :(
> > > while reading the State changes from b,r,etc. when the cdrom is finshed
> > > its 'r' 'xm list' showes:
> > >   WindowsXP                          4      256     1 r-----    87.2
> > >
> > > but no display :(
> > >
> > > conntect with xencosole to domid showed:
> > >   DSsDSsDSsDSs
> > >
> > > last lines of xend.log:
> > > [2006-06-12 05:51:16 xend] DEBUG (DevController:132) Waiting for
> > > devices irq. [2006-06-12 05:51:16 xend] DEBUG (DevController:132)
> > > Waiting for devices pci. [2006-06-12 05:51:16 xend] DEBUG
> > > (DevController:132) Waiting for devices ioports. [2006-06-12 05:51:16
> > > xend] DEBUG (DevController:132) Waiting for devices vtpm. [2006-06-12
> > > 05:51:16 xend] INFO (XendDomain:363) Domain WindowsXP (1) unpaused.
> > >
> > > maybe this is a problem with the SDL libs ? - i am not sure which
> > > version to choose. emerge of libsdl 1.2.8-r1. no sdl-devel avariable. i
> > > downloaded the rpm, extracted it and manualy reaplaced /usr/include and
> > > /usr/lib...
> > >
> > >>>> What detailed Version of the SDL libs is required for XEN ?
> > >
> > > ...
> > >
> > > so i tried the vnc support:
> > >   Using config file "xen_win_latest.hvm".
> > >   VNC= 1
> > >
> > >   VNC viewer for X version 4.0 - built Jun  7 2006 10:37:44
> > >   Copyright (C) 2002-2004 RealVNC Ltd.
> > >   See http://www.realvnc.com for information on VNC.
> > >   Started domain WindowsXP
> > >   xen windows #
> > >
> > > 'xm list' showes:
> > > WindowsXP                          2      256     1 -b----     0.0
> > >
> > > there is no read action on the cdrom drive. if i try to connect to it
> > > (VNC_VIEWER: of 'xm list --long') i get:
> > >   CConn: connected to host 127.0.0.1 port 5501
> > >
> > > ...but nothing happens...
> > >
> > > additional debug info from qemu-dm.debug:
> > > -vncconnect 127.0.0.1:5501 -d 2 -m 256 -cdrom /dev/cdrom -boot d
> > > -serial pty -vcpus 1 -domain-name WindowsXP -hda
> > > /xen/windows/xen_win_latest.img -macaddr 00:16:3e:6e:f2:44 -bridge
> > > xenbr0 -nics 1 -vnc -k en-us -vncport 5901
> > >
> > > :0.0
> > >
> > > ...and so i finaly installed a windows xp image with qemul (damn this
> > > took ages :) to use it with xen. i created a 'raw' disk image using 
> > > qemu-img (was this a fault ?): file winxp_qemu.img
> > >   winxp_qemu.img: x86 boot sector, Microsoft Windows XP MBR
> > >
> > > i changed the image and the boot option of the cfg file...
> > >
> > > with sdl - aggain the cdrom drive is accessed.
> > > 'xm list' showes:
> > >   WindowsXP                          2      256     1 -b----     11.16
> > > even after 10min+ there is still no state and still no graphic output
> > > :( (on some tries, instead of '-b----' the state was '------')
> > >
> > > with vnc the problems were quite the same as with booting from 'd'
> > > cdrom (mentioned above)...
> > >
> > > well... i am realy feeling like beeing close to get it finaly running,
> > > anyone got some suggestions or tips for me ? - and idea how to closer
> > > debug this problem ?
> > >
> > >
> > > greets xen0n
> > >
> > >
> > > ####  here some information about my configs / system: #####
> > >
> > > [grub.conf] << (no initrd -> scsi_mod etc [*] in kernel, system boots
> > > fine - without errors) title=Gentoo Linux 2.6.16 - Xen 3.0.2 DOM0 devel
> > >   kernel /boot/xen_boot/xen-3.0.gz dom0_mem=1G console=vga
> > >   module /boot/xen_boot/vmlinuz-2.6-xen_dom0 root=/dev/sda3 ro
> > > console=tty0
> > >
> > > [grep 'XEN' linux-2.6.16-xen/.config | grep -v '^#'] << (kernel
> > > compiled for dom0, anything wrong??) CONFIG_X86_XEN=y
> > >   CONFIG_XEN_PCIDEV_FRONTEND=y
> > >   CONFIG_XEN_PCIDEV_FE_DEBUG=y
> > >   CONFIG_XEN=y
> > >   CONFIG_XEN_INTERFACE_VERSION=0x00030101
> > >   CONFIG_XEN_PRIVILEGED_GUEST=y
> > >   CONFIG_XEN_BACKEND=y
> > >   CONFIG_XEN_BLKDEV_BACKEND=y
> > >   CONFIG_XEN_NETDEV_BACKEND=y
> > >   CONFIG_XEN_NETDEV_LOOPBACK=y
> > >   CONFIG_XEN_SCRUB_PAGES=y
> > >   CONFIG_XEN_SYSFS=y
> > >
> > > [grep 'SMP' linux-2.6.16-xen/.config] << (SMP support)
> > >   # CONFIG_X86_BIGSMP is not set
> > >   CONFIG_SMP=y
> > >   CONFIG_SMP_ALTERNATIVES=y
> > >   CONFIG_X86_FIND_SMP_CONFIG=y
> > >   CONFIG_X86_SMP=y
> > >
> > > [dmesg | grep CPU] << (SMP working - ACPI support)
> > >   Initializing CPU#0
> > >   CPU: After generic identify, caps: bfe9d3f1 00100000 00000000
> > > 00000000 0000c1a9 00000000 00000000 CPU: After vendor identify, caps:
> > > bfe9d3f1 00100000 00000000 00000000 0000c1a9 00000000 00000000 CPU: L1
> > > I cache: 32K, L1 D cache: 32K
> > >   CPU: L2 cache: 2048K
> > >   CPU: After all inits, caps: bfe9d3f1 00100000 00000000 00000140
> > > 0000c1a9 00000000 00000000 Brought up 2 CPUs
> > >   Initializing CPU#1
> > >   ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
> > >   ACPI: Processor [CPU0] (supports 8 throttling states)
> > >   ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
> > >   ACPI: Processor [CPU1] (supports 8 throttling states)
> > >
> > > [cat /proc/cpuinfo ...]
> > >   flags           : fpu tsc msr pae mce cx8 apic mtrr
> > >                     mca cmov pat clflush dts acpi mmx
> > >                     fxsr sse sse2 ss ht tm pbe nx constant_tsc pni
> > >                     monitor vmx est tm2 xtpr
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.