A x86_64 dom0 can run both x86_64 and i386 domUs.
If the Intel VT technology is available to you then I would attempt a Xen Full Virtualization Example:
In your case you may want to use a physical hard drive (phy: rather then file:) for your disk configuration.
> > # -*- mode: python; -*-
> > #========================================================================
> >==== # Python configuration setup for 'xm create'.
> > # This script sets the parameters used when a domain is created using 'xm
> > create'.
> > # You use a separate script for each domain you want to create, or
> > # you can set the parameters for the domain on the xm command line.
> > #========================================================================
> >====
> >
> > import os, re
> > arch = os.uname()[4]
> > if re.search('64', arch):
> > arch_libdir = 'lib64'
> > else:
> > arch_libdir = 'lib'
> >
> > #------------------------------------------------------------------------
> >---- # Kernel image file.
> > kernel = "/usr/lib/xen/boot/hvmloader"
> >
> > # The domain build function. HVM domain uses 'hvm'.
> > builder='hvm'
> >
> > # Initial memory allocation (in megabytes) for the new domain.
> > memory = 384
> >
> > # A name for your domain. All domains must have different names.
> > name = "name"
> >
> > #------------------------------------------------------------------------
> >----- # the number of cpus guest platform has, default=1
> > #vcpus=1
> >
> > # enable/disable HVM guest PAE, default=0 (disabled)
> > #pae=0
> >
> > # enable/disable HVM guest ACPI, default=0 (disabled)
> > #acpi=0
> >
> > # enable/disable HVM guest APIC, default=0 (disabled)
> > #apic=0
> >
> > # List of which CPUS this domain is allowed to use, default Xen picks
> > #cpus = "" # leave to Xen to pick
> > #cpus = "0" # all vcpus run on CPU0
> > #cpus = "0-3,5,^1" # run on cpus 0,2,3,5
> >
> > # Optionally define mac and/or bridge for the network interfaces.
> > # Random MACs are assigned if not given.
> > #vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0' ]
> > # type=ioemu specify the NIC is an ioemu device not netfront
> > vif = [ 'type=ioemu, bridge=xenbr0' ]
> >
> > #------------------------------------------------------------------------
> >---- # Define the disk devices you want the domain to have access to, and
> > # what you want them accessible as.
> > # Each disk entry is of the form phy:UNAME,DEV,MODE
> > # where UNAME is the device, DEV is the device name the domain will see,
> > # and MODE is r for read-only, w for read-write.
> >
> > #disk = [ 'phy:hda1,hda1,r' ]
> > disk = [ 'file:/var/lib/xen/images/winxp.img,ioemu:hda,w' ]
> >
> > #------------------------------------------------------------------------
> >---- # Configure the behaviour when a domain exits. There are three
> > 'reasons' # for a domain to stop: poweroff, reboot, and crash. For each
> > of these you # may specify:
> > #
> > # "destroy", meaning that the domain is cleaned up as normal;
> > # "restart", meaning that a new domain is started in place of
> > the old # one;
> > # "preserve", meaning that no clean-up is done until the domain
> > is # manually destroyed (using xm destroy, for
> > example); or # "rename-restart", meaning that the old domain is not
> > cleaned up, but is # renamed and a new domain started
> > in its place. #
> > # The default is
> > #
> > #
> > #
> > #
> > #
> > # For backwards compatibility we also support the deprecated option
> > restart #
> > # restart = 'onreboot' means
> > #
> > #
> > #
> > # restart = 'always' means
> > #
> > #
> > #
> > # restart = 'never' means
> > #
> > #
> >
> >
> >
> >
> >
> > #========================================================================
> >====
> >
> > # New stuff
> > device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
> >
> > #------------------------------------------------------------------------
> >----- # Disk image for
> > cdrom='/dev/sr0'
> >
> > #------------------------------------------------------------------------
> >----- # boot on floppy (a), hard disk (c) or CD-ROM (d)
> > boot='d'
> > #------------------------------------------------------------------------
> >----- # write to temporary files instead of disk image files
> > #snapshot=1
> >
> > #------------------------------------------------------------------------
> >---- # enable SDL library for graphics, default = 0
> > sdl=1
> >
> > #------------------------------------------------------------------------
> >---- # enable VNC library for graphics, default = 1
> > vnc=0
> >
> > #------------------------------------------------------------------------
> >---- # enable spawning vncviewer(only valid when vnc=1), default = 1
> > vncviewer=0
> >
> > #------------------------------------------------------------------------
> >---- # no graphics, use serial port
> > #nographic=0
> >
> > #------------------------------------------------------------------------
> >---- # enable stdvga, default = 0 (use cirrus logic device model)
> > stdvga=0
> >
> > #------------------------------------------------------------------------
> >----- # serial port re-direct to pty deivce, /dev/pts/n
> > # then xm console or minicom can connect
> > serial='pty'
> >
> > #------------------------------------------------------------------------
> >---- # enable ne2000, default = 0(use pcnet)
> > ne2000=0
> >
> >
> > #------------------------------------------------------------------------
> >----- # enable audio support
> > #audio=1
> >
> >
> > #------------------------------------------------------------------------
> >----- # set the real time clock to local time [default=0 i.e. set to
> > utc] #localtime=1
> >
> >
> > #------------------------------------------------------------------------
> >----- # start in full screen
> > #full-screen=1
-M
> From: iain.t.morris@xxxxxxxxx
> Date: Tue, 19 Jan 2010 09:39:45 -0800
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] old Athlon system on an x86_64
>
> Sorry if the answer to this question is obvious but,
>
> I have an ailing server running slackware with AMD Athlon processors. I'd like to virtualize it on a server running Xen, which is a Xeon x86_64 system. Is this even possible with the different architectures? I don't believe the kernel (2.4) is highly customized, but I'm not sure what other issues I might run into.
>
> Thanks,
>
> -Iain
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
Tell the whole story with photos, right from your Messenger window. Learn how!
|
