Attempt of prevu Intrepid Xen 3.3 Hypervisor at Ubuntu Hardy Dom0 (2.6.24-21-xen)

Quote:-
This is potentially a more time consuming backport but with Xen 3.3 being a huge improvement over 3.2 it would definitely help Ubuntu server market share to have Xen 3.3 available in Ubuntu 8.04. Many server operators will want Xen 3.3 but will want to continue running the LTS release rather than upgrade to Intrepid.
Current status of backports per Scott Kitterman :-
Because xen-3.3 is a new package for Hardy and so it needs a manual review by the archive admins. This is normal.

https://launchpad.net/ubuntu/hardy/+source/xen-3.3/3.3.0-1ubuntu7~hardy1

shows the status. It won’t be available until it no longer says ‘NEW’ in the builds section.
Proceed with “prevu” build to evaluate Intrepid Xen 3.3 Hypervisor at Hardy Dom0.

# apt-get install prevu
# DISTRO=hardy prevu-init
# wget \

https://launchpad.net/ubuntu/hardy/+source/xen-3.3/3.3.0-1ubuntu7~hardy1/+files/xen-3.3_3.3.0-1ubuntu7~hardy1.diff.gz

# wget \

https://launchpad.net/ubuntu/hardy/+source/xen-3.3/3.3.0-1ubuntu7~hardy1/+files/xen-3.3_3.3.0.orig.tar.gz

# wget \

https://launchpad.net/ubuntu/hardy/+source/xen-3.3/3.3.0-1ubuntu7~hardy1/+files/xen-3.3_3.3.0-1ubuntu7~hardy1.dsc

Now build :-

# /usr/bin/prevu xen-3.3_3.3.0-1ubuntu7~hardy1.dsc

. . . . . . . . . .
dh_builddeb -s
dpkg-deb --build debian/xen-hypervisor-3.3 ..
dpkg-deb: building package `xen-hypervisor-3.3' in `../xen-hypervisor-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb'.
dpkg-deb --build debian/xen-utils-3.3 ..
dpkg-deb: building package `xen-utils-3.3' in `../xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb'.
dpkg-deb --build debian/xen-docs-3.3 ..
dpkg-deb: building package `xen-docs-3.3' in `../xen-docs-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb'.
dpkg-deb --build debian/libxen3-dev ..
dpkg-deb: building package `libxen3-dev' in `../libxen3-dev_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb'.
dpkg-deb --build debian/libxen3 ..
dpkg-deb: building package `libxen3' in `../libxen3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb'.
dpkg-deb --build debian/python-xen-3.3 ..
dpkg-deb: building package `python-xen-3.3' in `../python-xen-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb'.
dpkg-genchanges >../xen-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.changes
dpkg-genchanges: including full source code in upload
dpkg-buildpackage: full upload; Debian-native package (full source is included)
Copying back the cached apt archive contents
-> new cache content libexpat1_2.0.1-0ubuntu1_amd64.deb added
-> new cache content libsm6_2%3a1.0.3-1_amd64.deb added
-> new cache content python-all_2.5.2-0ubuntu1_all.deb added
. . . . . . .
-> unmounting /var/cache/prevu/src/22498 filesystem
-> unmounting /var/cache/prevu/hardy-debs filesystem
-> unmounting dev/pts filesystem
-> unmounting proc filesystem
-> cleaning the build env
-> removing directory /var/cache/prevu/builds/22589 and its subdirectories
** Success!. You can find source packages and .debs at /var/cache/prevu/hardy-debs **

Build successful, attempt to install :-

root@boris-desktop:/var/cache/prevu/hardy-debs# ls -l

total 2620
-rwxr--r-- 1 root root 357 2008-11-03 03:35 install.sh
-rw-r--r-- 1 root root 147070 2008-11-03 03:29 libxen3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
-rw-r--r-- 1 root root 236020 2008-11-03 03:29 libxen3-dev_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
-rwxrwxr-x 1 root admin 4565 2008-11-03 03:29 Packages
-rw-r--r-- 1 root root 879276 2008-11-03 03:29 python-xen-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
-rw-r--r-- 1 root root 13022 2008-11-03 03:29 xen-docs-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
-rw-r--r-- 1 root root 472354 2008-11-03 03:29 xen-hypervisor-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
-rw-r--r-- 1 root root 890692 2008-11-03 03:29 xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb

root@boris-desktop:/var/cache/prevu/hardy-debs# ./install.sh

(Reading database ... 101659 files and directories currently installed.)
Preparing to replace libxen3 3.2.0-0ubuntu10 (using libxen3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb) ...
Unpacking replacement libxen3 ...
Selecting previously deselected package libxen3-dev.
Unpacking libxen3-dev (from libxen3-dev_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb) ...
Selecting previously deselected package python-xen-3.3.
Unpacking python-xen-3.3 (from python-xen-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb) ...
Replacing files in old package python-xen-3.2 ...
Selecting previously deselected package xen-docs-3.3.
Unpacking xen-docs-3.3 (from xen-docs-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb) ...
Selecting previously deselected package xen-hypervisor-3.3.
Unpacking xen-hypervisor-3.3 (from xen-hypervisor-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb) ...
Selecting previously deselected package xen-utils-3.3.
dpkg: regarding xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb containing xen-utils-3.3:
xen-utils-3.3 conflicts with xen-utils
xen-utils-3.2 provides xen-utils and is installed.
dpkg: error processing xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb (--install):
conflicting packages - not installing xen-utils-3.3
Setting up libxen3 (3.3.0-1ubuntu7~hardy1~8.04prevu1) ...
Setting up libxen3-dev (3.3.0-1ubuntu7~hardy1~8.04prevu1) ...
Setting up python-xen-3.3 (3.3.0-1ubuntu7~hardy1~8.04prevu1) ...
Setting up xen-docs-3.3 (3.3.0-1ubuntu7~hardy1~8.04prevu1) ...
Setting up xen-hypervisor-3.3 (3.3.0-1ubuntu7~hardy1~8.04prevu1) ...
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found Xen hypervisor 3.2, kernel: /boot/vmlinuz-2.6.24-21-xen
Found Xen hypervisor 3.3, kernel: /boot/vmlinuz-2.6.24-21-xen
Found kernel: /boot/vmlinuz-2.6.24-19-generic
Found kernel: /boot/memtest86+.bin
Replacing config file /var/run/grub/menu.lst with new version
Updating /boot/grub/menu.lst ... done
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb

I’ve tried to work with old package and force replacement as follows :-
root@boris-desktop:/var/cache/prevu/hardy-debs# dpkg -i –force-all xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
dpkg: regarding xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb containing xen-utils-3.3:
xen-utils-3.3 conflicts with xen-utils
xen-utils-3.2 provides xen-utils and is installed.
dpkg: warning – ignoring conflict, may proceed anyway !
dpkg: regarding xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb containing xen-utils-3.3:
xen-utils-3.2 conflicts with xen-utils
xen-utils-3.3 provides xen-utils and is to be installed.
dpkg: warning – ignoring conflict, may proceed anyway !
. . . .
To get HVM able obtain IP address via bridge i had to use vif = ['bridge=eth0'] in
profiles like :-
root@boris-desktop:/etc/xen/vm# cat intrepid.hvm
kernel = “/usr/lib/xen/boot/hvmloader”
builder = ‘hvm’
memory = 1024
name = “IntrepidHVM”
vcpus = 1
vif = [ 'bridge=eth0' ]
disk = [ 'phy:/dev/sdb14,hda,w!','phy:/dev/loop0,hdc:cdrom,r' ]
device_model = ‘/usr/lib/xen/bin/qemu-dm’
vnc=1
boot=’c’
Turning virtual NIC into a paravirtualized mode instead of a fully virtualized.
When vif=['type=ioemu,bridge=eth0'] HVM fails to bring up virtual network interface.
******************
Rebooted into:-
******************
title Xen 3.3 / Ubuntu 8.04.1, kernel 2.6.24-21-xen
root (hd0,11)
kernel /boot/xen-3.3.gz
module /boot/vmlinuz-2.6.24-21-xen root=UUID=4d4bfbb3-68bd-49b4-ace3-af3d17c8612b ro console=tty0
module /boot/initrd.img-2.6.24-21-xen
quiet
*******************
System status :-
*******************
root@boris-desktop:/etc/xen/vm# xm info
host : boris-desktop
release : 2.6.24-21-xen
version : #1 SMP Mon Aug 25 18:56:44 UTC 2008
machine : x86_64
nr_cpus : 2
nr_nodes : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 3005
hw_caps : bfebfbff:20100800:00000000:00000140:0008e3fd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 8191
free_memory : 34
node_to_cpu : node0:0-1
node_to_memory : node0:34
xen_major : 3
xen_minor : 3
xen_extra : .0
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu3)
cc_compile_by : root
cc_compile_domain :
cc_compile_date : Mon Nov 3 08:25:32 UTC 2008
xend_config_format : 4
root@boris-desktop:/etc/xen/vm# brctl show
bridge name bridge id STP enabled interfaces
eth0 8000.001e8c25cca5 no peth0
vif6.0
vnet0 8000.000000000000 yes
********************************************
Create Intrepid Server HVM DomU via :-
********************************************
root@boris-desktop:/etc/xen/vm# cat intrepid.hvm
kernel = “/usr/lib/xen/boot/hvmloader”
builder = ‘hvm’
memory = 2048
name = “IntrepidHVM”
vcpus = 1
vif = [ 'bridge=eth0' ]
disk = [ 'phy:/dev/sdb14,hda,w!','phy:/dev/loop0,hdc:cdrom,r' ]
device_model = ‘/usr/lib/xen/bin/qemu-dm’
vnc=1
boot=’d’
*****************************************************************************************************************
The first time am image for PV DomU will be created, you won’t find active Ethernet interface at HVM
DomU. However, install “Ubuntu Desktop” via tasksel at PV DomU will make it completely functional
to manage Intrepid Server HVM DomU. Seems like PV drivers for virtual NIC get installed on the
image device via tasksel’s procedure.
******************************************************************************************************************
Load Intrepid Server PV DomU via :-
root@boris-desktop:/etc/xen/vm# cat intrepid.py
name = ‘IntrepidPV’
bootloader=”/usr/bin/pygrub”
memory = ‘2048’
disk = ['phy:/dev/sdb14,xvda,w']
vif = [ 'mac=00:16:3e:00:00:00' ]
vfb = ['type=vnc,vncunused=1']
on_reboot = ‘restart’
on_crash = ‘restart’
# xm create intrepid.py
# vncviewer localhost:0
***************************
Check Intrepid PV DomU
***************************
root@boris-desktop:/etc/xen/vm# xm list -l IntrepidPV
(domain
(domid 6)
(on_crash restart)
(uuid a156eaf7-6375-f720-5a4a-03f376167b71)
(bootloader_args -q)
(vcpus 1)
(name IntrepidPV)
(on_poweroff destroy)
(on_reboot restart)
(bootloader /usr/bin/pygrub)
(maxmem 2048)
(memory 2048)
(shadow_memory 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1225704559.32)
(cpu_time 4.715455935)
(online_vcpus 1)
(image
(linux
(kernel )
(device_model /usr/lib64/xen/bin/qemu-dm)
(notes
(HV_START_LOW 18446603336221196288)
(FEATURES ‘!writable_page_tables|pae_pgdir_above_4gb’)
(VIRT_BASE 18446744071562067968)
(GUEST_VERSION 2.6)
(PADDR_OFFSET 0)
(GUEST_OS linux)
(HYPERCALL_PAGE 18446744071564201984)
(LOADER generic)
(SUSPEND_CANCEL 1)
(PAE_MODE yes)
(ENTRY 18446744071569531392)
(XEN_VERSION xen-3.0)
)
)
)
(status 2)
(state -b—-)
(store_mfn 2208645)
(console_mfn 2208644)
(device
(vif
(mac 00:16:3e:00:00:00)
(script vif-bridge)
(uuid 768ba10b-4fec-2342-c49c-9aa05c62c7ca)
(backend 0)
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 71ecda50-1039-4ef9-bf6e-17ef01964dee)
(dev xvda:disk)
(uname phy:/dev/sdb14)
(mode w)
(backend 0)
(bootable 1)
(VDI )
)
)
(device (vkbd (backend 0)))
(device
(vfb
(vncunused 1)
(uuid 017e4530-8d38-19aa-3d3c-ebf6832e7575)
(location localhost:5900)
(type vnc)
(display :0.0)
(xauthority /root/.Xauthority)
)
)
(device
(console
(protocol vt100)
(location 2)
(uuid d2851099-a26b-c84f-4bb1-091ba6eab1e3)
)
)
)





Run tasksel to install Ubuntu Desktop at PV DomU



Setup VNC at PV DomU and login via vncviewer from Dom0:-

vnclogin





Now we can also load Intrepid Server HVM DomU with PV driver for virtual NIC.

startintrepidhvm

Solaris Nevada (build 101) has been installed in DHCP mode as PV DomU via profile :-
root@boris-desktop:/etc/xen/vm# cat snv101.py
name = ‘SolarisPVM’
memory = ‘1024’
disk = [ 'phy:/dev/loop1,6:cdrom,r', 'phy:/dev/sdb13,0,w!' ]
vif = [ 'bridge=eth0' ]
bootloader = ‘/usr/bin/pygrub’
kernel = ‘/boot/platform/i86xpv/kernel/amd64/unix’
ramdisk = ‘/boot/amd64/x86.miniroot’
extra = ‘/platform/i86xpv/kernel/amd64/unix – nowin -B install_media=cdrom’
Installation succeeded.
**********************************
Start up SNV_101 PV DomU
**********************************
root@boris-desktop:/etc/xen/vm# uname -a
Linux boris-desktop 2.6.24-21-xen #1 SMP Mon Aug 25 18:56:44 UTC 2008 x86_64 GNU/Linux
root@boris-desktop:/etc/xen/vm# xm info|grep xen_
xen_major : 3
xen_minor : 3
xen_extra : .0
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
xen_changeset : unavailable
root@boris-desktop:/etc/xen/vm# xm create -c snv101.pyrun
Using config file “./snv101.pyrun”.
Started domain SolarisPVM
v3.3.0 chgset ‘unavailable’
SunOS Release 5.11 Version snv_101 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: dhcppc7
/dev/rdsk/c0d0s7 is clean
Reading ZFS config: done.
syslogd: line 45: WARNING: loghost could not be resolved

dhcppc7 console login: root
Password:
Last login: Mon Nov 3 14:46:59 on console
Nov 3 14:51:56 dhcppc7 login: ROOT LOGIN /dev/console
Sun Microsystems Inc. SunOS 5.11 snv_101 November 2008
# bash
bash-3.2# ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
xnf0: flags=201004843 mtu 1500 index 2
inet 192.168.1.40 netmask ffffff00 broadcast 192.168.1.255
ether 0:16:3e:63:46:96
lo0: flags=2002000849 mtu 8252 index 1
inet6 ::1/128
bash-3.2# nslookup lxer.com
Server: 80.254.111.254
Address: 80.254.111.254#53

Non-authoritative answer:
Name: lxer.com
Address: 207.210.216.38
bash-3.2#




*******************
Update 12/11/08
*******************
Please be advised , as of November 11 Hardy Backports provide Xen 3.3 packages .
They may be installed nicely via Synaptic Manager.

synaptic1

synaptic2

synaptic3

About these ads

37 Responses to Attempt of prevu Intrepid Xen 3.3 Hypervisor at Ubuntu Hardy Dom0 (2.6.24-21-xen)

  1. aronzak says:

    Was it worth all that effort?

    By the way, you can use for code blocks

  2. Zero says:

    Can’t find the “install.sh” at:

    /var/cache/prevu/hardy-debs/

    Anyone that can post its contents here, so I can save it manually?

  3. dbaxps says:

    1. Sure, install.sh has to be written manually :
    dpkg -i libxen3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb \
    libxen3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb \
    . . . . . . . . . . . .
    However, “apt-get install” gets broken after force install xen-utils-3.3
    and you would have take care of that:- apt-get -f install.

    2. Hardy Backports already provide all packages. Synaptic manager resolves
    dependencies automatically when you install xen-hypervisor-3.3 and xen-utils-3.3 removing
    ubuntu-xen-server, xen-utils-3.2 and phyton-lib 5.2. I am not quite sure regarding old
    phyton package name.

  4. Zero says:

    Trying to install:

    ‘xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb’

    will generate an error message:

    # dpkg -i xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
    dpkg: regarding xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb containing xen-utils-3.3:
    xen-utils-3.3 conflicts with xen-utils
    xen-utils-3.2 provides xen-utils and is installed.
    dpkg: error processing xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb (–install):
    conflicting packages – not installing xen-utils-3.3
    Errors were encountered while processing:
    xen-utils-3.3_3.3.0-1ubuntu7~hardy1~8.04prevu1_amd64.deb
    #

    How do I pass by that?

  5. Zero says:

    Solved it by removing the old version first.

    # apt-get -f remove xen-utils-3.2
    :)

  6. robert says:

    Could you plase show snv101.pyrun?

  7. dbaxps says:

    Zero,
    Are you done ?
    If no, view :-
    Backport Intrepid Xen 3.3 Hypervisor to Ubuntu Hardy Dom0 (2.6.24-21-xen)

    http://lxer.com/module/newswire/view/112045/index.html

    Stuff is already in Hardy Backports . No pain at all.

  8. dbaxps says:

    SNV101 PV runtime profile is pretty much standard :-

    name = ‘SolarisPVM’
    # bootloader=”/usr/bin/pygrub”
    memory = ‘1024′
    disk = ['phy:/dev/sdb13,0,w' ]
    vif = [ 'bridge=eth0' ]

  9. Zero says:

    Jepp!
    Found it out! Just uncommented the backport repository in the sources.list!

    # nano /etc/apt/sources.list

    ==================================
    deb http://th.archive.ubuntu.com/ubuntu/ hardy-backports main restricted universe multiverse
    deb-src http://th.archive.ubuntu.com/ubuntu/ hardy-backports main restricted universe multiverse
    ==================================

    # apt-get install xen-utils-3.3

    Voila!

  10. Zero says:

    Forgot… Should be like this:

    # apt-get install xen-utils-3.3 libxen3-dev xen-docs-3.3 xen-hypervisor-3.3

    Voila!

  11. dbaxps says:

    You are doing grate !
    Try to load Synaptic Manager (main gnome menus) you’ll be surprised.
    You just mark packages to install via GUI and SM will resolve conflicts for you,
    just prompting you to confirm.

  12. Zero says:

    Aww…
    I’m not using the Ubuntu Desktop. Server only! :)

  13. No Go says:

    That didn’t work for me. :(

    Running:
    # apt-get install xen-utils-3.3 libxen3-dev xen-docs-3.3 xen-hypervisor-3.3

    Everything will get install alright. But when creating a new guest, I’ll get the following error:

    # xm create /etc/xen/xenwin.cfg
    Using config file “/etc/xen/xenwin.cfg”.
    Error: Creating domain failed: name=xenhvm
    # _

    I used a configuration file that worked fine on the 3.2 version. Or does it have to be modified for the 3.3 version? New commands? New structure?

  14. dbaxps says:

    Zero,
    You can run tasksel and select option “Install Ubuntu Desktop”
    400 MB download. It’s up to you.

  15. dbaxps says:

    No Go,
    Please , submit:-
    Status after upgrade.
    # xm info
    # brtcl show
    Before you run “xm create”
    # /etc/xen/xenwin.cfg
    # losetup -a

  16. No Go says:

    Sure! :)

    # xm info
    ————————————-
    host : cyrus-xen
    release : 2.6.24-21-xen
    version : #1 SMP Wed Oct 22 01:07:57 UTC 2008
    machine : x86_64
    nr_cpus : 2
    nr_nodes : 1
    cores_per_socket : 2
    threads_per_core : 1
    cpu_mhz : 2405
    hw_caps : 178bf3ff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f:00000000
    virt_caps :
    total_memory : 3838
    free_memory : 128
    node_to_cpu : node0:0-1
    node_to_memory : node0:128
    xen_major : 3
    xen_minor : 2
    xen_extra : .1-rc1-pre
    xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
    xen_scheduler : credit
    xen_pagesize : 4096
    platform_params : virt_start=0xffff800000000000
    xen_changeset : unavailable
    cc_compiler : gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)
    cc_compile_by : buildd
    cc_compile_domain : buildd
    cc_compile_date : Fri Apr 11 01:13:51 UTC 2008
    xend_config_format : 4
    ————————————-

    # brtcl show (?)
    ————————————-
    -bash: brtcl: command not found
    ————————————-

    /etc/xen/xenwin.cfg
    ————————————-
    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 = 512
    shadow_memory = 8
    name = “xenhvm”
    uuid = “f92d4a0c-eaaf-b319-ba32-1b40367a771f”
    vcpus = 1
    vif = [ 'type=ioemu, bridge=xenbr0' ]
    disk = [ 'tap:aio:/home/xen/domains/windows/xenwin.img,ioemu:hda,w', 'phy:/dev/cdrom,hdc:cdrom,r' ]
    device_model = ‘/usr/’ + arch_libdir + ‘/xen/bin/qemu-dm’
    # boot on floppy (a), hard disk (c) or CD-ROM (d)
    # default: hard disk, cd-rom, floppy
    boot=”dc”
    sdl=1
    vnc = 1
    vncunused = 0
    vnclisten = “0.0.0.0”
    vncdisplay = “5”
    stdvga=0
    serial=’pty’
    usbdevice=’tablet’
    pae = 1
    acpi = 1
    apic = 1
    localtime = 1
    on_poweroff = “destroy”
    on_reboot = “restart”
    on_crash = “restart”
    ————————————-

    # losetup -a (?)
    # _
    (didn’t display anything)

  17. dbaxps says:

    Command:-
    # brctl show
    will report xen-bridge name in first column . Say eth0 (eth1)
    then vif =['type=ioemu,bridge=eth0 ]
    Next:-
    xen-minor should be 3 in your report 2
    Do :-
    # man losetup

  18. No Go says:

    Ok, the commad “brctl” was misspelled. Onther try:

    # brctl show
    bridge name bridge id STP enabled interfaces
    eth0 8000.001fd055560c no peth0

    # losetup -a
    # _
    (Doesn’t show anything. No loop devices?)

    “xen-minor should be 3 in your report 2″
    Isn’t the package really upgraded?

    I did “man losetup” and read, but not 100% sure how to use that command still. I’ve been using Linux (ubuntu) Desktop for 2 years, played with Linux textmode server for about 9 months. I love it, but there is a learning curve though. The Linux community is great, people helping each other. The Xen is great as well. But it’s very trixy to learn. So I’m doing my best! :)

  19. dbaxps says:

    >“xen-minor should be 3 in your report 2″
    >Isn’t the package really upgraded?
    “3” is a must , otherwise you are at Xen 3.2.1rc1-pre Hardy Dom0 , i.e. NO UPGRADE happened
    Anyway :-

    vif =['type=ioemu,bridge=eth0' ]

    You may copy via dd CD to ISO image.
    # dd if=/dev/cdrom of=/etc/xen/isos/winxp.oso
    # losetup /dev/loop0 /etc/xen/isos/winxp.oso
    # losetup -a

    disk =[ 'tap:aio:/etc/xen/images/disk.img,,hda,w','phy:/dev/loop0:hdc:cdrom,r']

  20. No Go says:

    “NO UPGRADE happened”…?
    Try running the “apt-get install” one more time then?

    CD image…
    Can’t get the CD image to work. Only the Physical drive works. That’s strange indeed. I have tried both my existing burnable CD ISO’s and created one ISO from the physical drive. No luck!

    This one works fine:
    disk = [ 'tap:aio:/home/xen/domains/win/xenwin.img,ioemu:hda,w', 'phy:/dev/cdrom,hdc:cdrom,r' ]

    This oine doesn’t:
    disk = [ 'tap:aio:/home/xen/domains/win/xenwin.img,ioemu:hda,w', 'tap:aio:/home/xen/domains/windows/win2k3.iso,hdc:cdrom,r' ]

  21. dbaxps says:

    No Go,
    Try to read and understand article above or http://bderzhavets.wordpress.com/2008/11/13/backport-intrepid-xen-33-hypervisor-at-ubuntu-hardy-dom0-2624-21-xen/. Second one is much easier to reproduce.
    You don’t follow directions.
    Your physical device works – fine.

  22. No Go says:

    This is GREAT! All my problems are solved!!
    Many thanks!!!

    First, I removed the 3.3 package, plus the “python-xen-3.2″ (which were still installed). Then, I installed the 3.3 package again. Now it works fine!

    And then, your loop suggestion worked as well:
    ‘phy:/dev/loop0,hdc:cdrom,r’

    So why does all the tutorials and the guys out there suggest that this one should be used?
    ‘tap:aio:/home/xen/iso/win2k3-32/image.iso,hdc:cdrom,r’

    BTW… Is there a way to automate the:
    “losetup /dev/loop0 /etc/xen/isos/winxp.oso”
    to work inside the config file?

  23. No Go says:

    Bad news…

    The previous made Windows guests dosn’t seem to be stable. They freeze after 5-10 secs, after the desktop shows up. Doesn’t look 100% healthy.

    Looks like I’m forced to stick with the 3.2, if no solution turns up… :(

  24. dbaxps says:

    >The previous made Windows guests doesn’t seem to be stable. They freeze after 5-10 secs, after the desktop
    > shows up. Doesn’t look 100% healthy.

    1. How confident are you , that newly created WinXP HVMs at Xen 3.3 Hardy Dom0 are stable ?
    Might be backport issue. If answer is “STABLE” ,then

    2. Submit HVM profiles you use at Xen 3.3 Hardy Dom0.
    It shouldn’t be matter. Image created for DomU usually works OK with upgraded Hypervisor .That’s not Ubuntu specific feature.

    Once again, i suspect backport issue , not images corruption or incompatibility.

  25. No Go says:

    The guests are inside an image file, which were created on 3.2 version. I then copied those .img files to a another harddisk, which I swap for testing the 3.3 backport. It’s 6 guest images. Everyone got the same symptom. Freezing after 5-10 secs, after the guest’s desktop is showing.

    I used the following configuration for all six 3.3 guests. Just changed the uuid and vnc port:

    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 = 512
    shadow_memory = 8
    name = “xenhvm”
    uuid = “f92d4a0c-eaaf-b319-ba32-1b40367a771f”
    vcpus = 1
    vif = [ 'type=ioemu, bridge=xenbr0' ]
    disk = [ 'tap:aio:/home/xen/dom/win/xenwin.img,ioemu:hda,w' ]
    device_model = ‘/usr/’ + arch_libdir + ‘/xen/bin/qemu-dm’
    boot=”dc”
    sdl=1
    vnc = 1
    vncunused = 0
    vnclisten = “0.0.0.0”
    vncdisplay = “5”
    stdvga=0
    serial=’pty’
    usbdevice=’tablet’
    pae = 1
    acpi = 1
    apic = 1
    localtime = 1
    on_poweroff = “destroy”
    on_reboot = “restart”
    on_crash = “restart”

  26. dbaxps says:

    No Go,
    Run:-
    # brctl show
    at Xen 3.3 Hardy Dom0.
    Xen bridge would be eth0 (1).
    How can you have network with ?
    vif=[ 'type=ioemu, bridge=xenbr0' ]
    Next:-
    usb=1
    usbdevice=”tablet”
    Where is :-
    usb=1
    in your profile ?

  27. No Go says:

    # brctl show
    bridge name bridge id STP enabled interfaces
    eth0 8000.001fd055560c no peth0

    “How can you have network with ?
    vif=[ 'type=ioemu, bridge=xenbr0' ]”

    -I don’t know! :) Just followed a tutorial from the internet:

    http://www.virtuatopia.com/index.php/Virtualizing_Windows_Server_2008_with_Xen

    So I have now changed it to:
    vif = [ 'type=ioemu, bridge=eth0' ]

    “Where is :-
    usb=1
    in your profile ?”

    Hmm… There wasn’t any in the example I found.
    So I have now added:
    usb=1
    to my guest config file.

    -Tested again… Still freezes!

    I made “apt-get -f install” again, which showed:

    # apt-get -f install
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    The following packages were automatically installed and are no longer required:
    debootstrap libconfig-inifiles-perl libtext-template-perl libcurl3 xen-tools libxml2 binutils linux-xen
    Use ‘apt-get autoremove’ to remove them.
    0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

    If I make “apt-get autoremove”, the Xen kernel gets deleted. I tried that on another installation.

    Looks like there is something wrong with the backport….

  28. No Go says:

    Your link…
    I have already tested the instructions inside that page. Only difference is that I used the Ubuntu Hardy Server. Do I have to use (upgrade) to the Ubuntu Desktop after I installed the Xen kernel?

    I tried once to convert the 8.04.1 Xen-server into a Desktop. But the Host network didn’t work 100% then. I think the DNS lookup failed. I could reach other computers in the local network though. But I gave up on that project.

  29. tim says:

    just a silly thought will this workon a 32 bit machine main page indicates 64 bit
    but this could turn turn into a really good how to.

    tim

  30. tim says:

    thats 32 bit Intel?

    tim

  31. dbaxps says:

    At mean time you don’t have to “prevu” due to Hardy backports have been updated on November 11-th 2008
    Just try to reproduce another “howto” on 32-bit Intel .Worked fine on the most recent Core2Duo based boxes .
    Backport Intrepid Xen 3.3 Hypervisor to Hardy Dom0 via Synaptic Manager :-

    http://bderzhavets.wordpress.com/2008/11/13/backport-intrepid-xen-33-hypervisor-at-ubuntu-hardy-dom0-2624-21-xen/

  32. tim says:

    thanks dbaxps

    i donot have Core2Duo

    but thanks for feedback

    tim

  33. dbaxps says:

    I am not saying, that C2D is required, i am saying that i tested backport on C2D & Ubuntu Hardy Dom0 (64-bit.)
    I am wondering would it work on 32-bit Intel ?
    You may install Hardy Desktop 32-bit, following second “howto” , and look for packages via Synaptic Manager.If mentioned packages are in place, most probably you done.

  34. tim says:

    dbaxps:

    thanks

    following 2nd howto

    sorry but which is the 1st and which is the 2nd

    brain dead monday

    tim

  35. dbaxps says:

    This one is needed.
    Backport Intrepid Xen 3.3 Hypervisor to Hardy Dom0 via Synaptic Manager :-

    http://bderzhavets.wordpress.com/2008/11/13/backport-intrepid-xen-33-hypervisor-at-ubuntu-hardy-dom0-2624-21-xen/

    If no Xen 3.3 packages show up via Synaptic Manager, then build 32-bit debian packages via “prevu” procedure described at the top of this page. I guess “prevu” build should understand environment due to command:-
    wget https://launchpad.net/ubuntu/hardy/+source/xen-3.3/3.3.0-1ubuntu7~hardy1/+files/xen-3.3_3.3.0.orig.tar.gz

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: