Fedora-6 runs Donika-Konika in openSUSE-10.2's Xen

(1)Installing openSUSE10.2 and Fedora6 in the same PC

openSUSE 10.2 with XEN support had been already installed in /dev/sda6 in my PC.
/dev/sda1 was for swap and /dev/sda2 had been used other OS not needed now.
So I installed Fed6 into /dev/sda2.
Fed6 was installed also with XEN support(selecting "virtualization" package group on installation, as far as I remember).
Fed6's bootloader was not installed, Because I prefer SUSE's grub.

(2)Dual-booting configuration

To finish setting up, Fed6 must be rebooted at least once. So it's necessary to configure dual-booting

To my surprise, this Fed6 had only xen-modified kernel(and other configuration files) in its /boot folder!

System.map-2.6.18-1.2798.fc6xen symvers-2.6.18-1.2798.fc6xen.gz config-2.6.18-1.2798.fc6xen vmlinuz-2.6.18-1.2798.fc6xen initrd-2.6.18-1.2798.fc6xen.img xen-syms-2.6.18-1.2798.fc6

So in SUSE's /boot/grub/menu.list the bellow section was added: 

title Fedora6
    root (hd0,1)
    kernel /boot/xen.gz-2.6.18-1.2798.fc6
    module /boot/vmlinuz-2.6.18-1.2798.fc6xen root=/dev/sda2 ro vga=0x31a
    module /boot/initrd-2.6.18-1.2798.fc6xen.img

Please remember my fed6 is installed in /dev/sda2.

Now I can boot either SUSE or Fed6 from SUSE's light-blue colored grub menu.

(3) Fed6's xen-modified kernel won't boot by SUSE's Xen

Unfortunately above vmlinuz-2.6.18-1.2798.fc6xen kernel could not be used by SUSE's Xen. First I copied all files in Fed6's /boot folder to SUSE's /boot/fedora folder. Then I wrote this configuration file xmfedora1 
.

kernel = "/boot/fedora/vmlinuz-2.6.18-1.2798.fc6xen"
ramdisk = "/boot/fedora/initrd-2.6.18-1.2798.fc6xen.img"
name = "fedora"
vif = [ '' ]
memory=512
disk = [ 'phy:sda2,sda2,w' ]
root = "/dev/sda2 ro"
extra = "5"
Then hit the command: 
#xm create -c xmfedora1

Using config file "xmfedora1".
Error: (22, 'Invalid argument')
Ooops.

(4) Using SUSE's xen-modified kernels!

I got so yakekuso(desparate) and edited xmfedora1 to the xmfedora file to use SUSE's xen-modified kernel, as bellow. 

kernel = "/boot/vmlinuz-xen"
ramdisk = "/boot/initrd-xen"
name = "fedora"
memory = 512
vif = [ '' ]
disk = ['phy:sda2,sda2,w' ]
root = "/dev/sda2 ro"
extra = "5"

then,

# xm create -c xmfedora
Using config file "xmfedora".
Started domain fedora
Linux version 2.6.18.2-34-xen (geeko@buildhost) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Mon Nov 27 11:46:27 UTC 2006
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000020800000 (usable)
0MB HIGHMEM available.
520MB LOWMEM available.
ACPI in unprivileged domain disabled
Allocating PCI resources starting at 30000000 (gap: 20800000:df800000)
Xen reported: 1999.998 MHz processor.
Built 1 zonelists.  Total pages: 133120
Kernel command line:  root=/dev/sda2 ro 5
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Software IO TLB disabled
vmalloc area: e1000000-fb7fe000, maxmem 33ffe000
Memory: 506880k/532480k available (1950k kernel code, 16920k reserved, 930k data, 184k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 5002.46 BogoMIPS (lpj=10004937)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
Compat vDSO mapped to fbffd000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 12k freed
checking if image is initramfs... it is
Freeing initrd memory: 7359k freed
Brought up 1 CPUs
migration_cost=0
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
Setting mem allocation to 524288 kiB
PCI: System does not support PCI
PCI: System does not support PCI
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1169671320.996:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
rtc: IRQ 8 is not free.
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 (usb?)
Failed to obtain physical IRQ 6
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
Using IPI No-Shortcut mode
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vif/0
Freeing unused kernel memory: 184k freed
Time: xen clocksource has been installed.
Boot logging started on /dev/tty1(/dev/console) at Wed Jan 24 20:42:04 2007
Creating device nodes with udev
netfront: Initialising virtual ethernet driver.
Loading xennet
netfront: device eth0 has flipping receive path.
Loading xenblk
Registering block device major 8
blkfront: sda2: barriers enabled
Loading jbd
Loading mbcache
Loading ext3
Waiting for device /dev/sda2 to appear:  ok
fsck 1.39 (29-May-2006)
[/bin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/sda2
/ (/dev/sda2): clean, 115355/7866240 files, 1017174/7865825 blocks
fsck succeeded. Mounting root device read-only.
Mounting root /dev/sda2
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-xen/modules.dep: No such file or directory

INIT: version 2.86 booting
                Welcome to Fedora Core
                Press 'I' to enter interactive startup.
Setting clock  (utc): 2007年  1月 25日 木曜日 05:42:08 JST [  OK  ]
Starting udev: udevd-event[866]: udev_db_add_device: unable to create db file '/dev/.udev/db/class@input@mice': No such file or directory
[  OK  ]
Loading default keymap (jp106): /etc/rc.d/rc.sysinit: line 383: /dev/tty0: No such file or directory
[FAILED]
Setting hostname fedora.noniko.com:  [  OK  ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda2
/: clean, 115355/7866240 files, 1017174/7865825 blocks
[  OK  ]
Remounting root filesystem in read-write mode:  [  OK  ]
Mounting local filesystems:  [  OK  ]
Enabling local filesystem quotas:  [  OK  ]
Enabling /etc/fstab swaps:  [  OK  ]
modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-xen/modules.dep: No such file or directory

INIT: Entering runlevel: 5
Entering non-interactive startup
Starting background readahead: [  OK  ]
Checking for hardware changes [  OK  ]
FATAL: Could not load /lib/modules/2.6.18.2-34-xen/modules.dep: No such file or directory
CRITICAL : [ipv6_test] Kernel is not compiled with IPv6 support
Bringing up loopback interface:  modprobe: FATAL: Could not load /lib/modules/2.6.18.2-34-xen/modules.dep: No such file or directory

arping: socket: Address family not supported by protocol
[  OK  ]
FATAL: Could not load /lib/modules/2.6.18.2-34-xen/modules.dep: No such file or directory
CRITICAL : [ipv6_test] Kernel is not compiled with IPv6 support
Starting system logger: [  OK  ]
Starting kernel logger: [  OK  ]
Starting irqbalance: [  OK  ]
Starting portmap: [  OK  ]
Starting NFS statd: [  OK  ]
Starting RPC idmapd: FATAL: Could not load /lib/modules/2.6.18.2-34-xen/modules.dep: No such file or directory
Starting system message bus: [  OK  ]
Can't open RFCOMM control socket: Address family not supported by protocol

Mounting other filesystems:  [  OK  ]
Starting PC/SC smart card daemon (pcscd): [  OK  ]
Starting hidd: Can't open HIDP control socket: Address family not supported by protocol
[FAILED]
Starting autofs:  Loading autofs4: [FAILED]
[FAILED]
Starting hpiod: [  OK  ]
Starting hpssd: [  OK  ]
Starting cups: [  OK  ]
Starting sshd: [  OK  ]
Starting sendmail: [  OK  ]
Starting sm-client: [  OK  ]
Starting console mouse services: no console device found[FAILED]
Starting crond: [  OK  ]
Starting xfs: [  OK  ]
Starting anacron: [  OK  ]
Starting atd: [  OK  ]
Starting background readahead: [  OK  ]
Starting yum-updatesd: [  OK  ]
Starting Avahi daemon: [  OK  ]
Starting HAL daemon: [  OK  ]
Starting smartd: [  OK  ]

Fedora Core release 6 (Zod)
Kernel 2.6.18.2-34-xen on an i686

fedora login:
Ahyahyahya! It booted! It's so mechakucha(rude) way, maybe this half-reptiled fedora would have many problems, but anyway it booted!

(5) Network problem - managed anyway

I logged into this fedora.
Indeed it has a problem to get DHCP address. But eth0 got a static address manually in fedora's console.

#/sbin/ifconfig eth0 192.168.1.88

(6)Starting vncserver

In fedora's console, as a user noniko,

$vncserver :1

At the first boot of vncserver required password.
After giving the password and starting the server, killed it once.

$vncserver -kill :1

Then went to $HOME/.vnc and edited xstartup file, uncommented the two lines below:

unset SESSION_MANAGER exec /etc/X11/xinit/xinitrc

saved xstarup file and booted vncserver again.

(7)Getting Fedora's desktop in SUSE

Leaving the fedora console as is, got back to SUSE's desktop and started Krdc.
Connected to

192.168.1.88:1

put the password to fedora's vncserver and here!

(8)Summary

Current problem is I must set network address of fedora vm each time I boot it.
But it shows how SUSE's Xen is mighty!

I would thank for any suggestion, advices to noniko@netbeans.jp.