On Sat, Nov 15, 2003 at 03:52:56PM -0500, Matt Ayres wrote:

Matt, have you *ever* managed to boot a virtual domain that has root on its own device? I'm having similar problems to you...I'm thinking there is something subtle going on, and might try your approach of starting with a fresh RedHat 9 system (currently it's SuSE 9).

I'm going to upgrade my JDK from 1.4.1_02 to Sun's 1.4.2, too.

Meanwhile, output looks like this:

# xenctl script -f/etc/xen-mynewdom14 Domain defaults: name XenoLinux size 0 vifs 1 domainImage /boot/xenolinux.gz domainInitRD null rootDevice /dev/sdd1 rootArgs null usrDevice null NWIP 137.229.71.14 NWGW 137.229.71.1 NWMask 255.255.255.240 MaxDomainNumber 20 NWNFSServer 169.254.1.0 NWNFSRoot null XIToolsDir /usr/local/bin/ args Failed to build domain using: /usr/local/bin/xi_build 8 /tmp/xen-image-32233.tmp
1
ip=137.229.71.14:169.254.1.0:137.229.71.1:255.255.255.240:grid-14.arsc.edu:eth0:off
root=/dev/sdd1 "

("xenctl domain list" says the domain exists, but it's not running and basically is only good for killing).

xen-mynewdom14 contains:

domain new -hgrid-14.arsc.edu -t" root=/dev/sdd1 DOMID=14 " physical grant -psdd1 -r domain start

(I've tried adding other devices, but all of /boot, /usr, /etc and so forth are on /dev/sdd1, with a custom fstab. /dev/sdd1 is not the root for any other domain, and is not mounted by others)

xenctl.xml contains:

<?xml version="1.0"?> <domctl_defaults> <domain_name>XenoLinux</domain_name> <domain_image>/boot/xenolinux.gz</domain_image> <domain_vifs>1</domain_vifs> <root_device>/dev/sdd1</root_device> <nw_ip>137.229.71.14</nw_ip> <nw_gw>=</nw_gw> <nw_mask>=</nw_mask> <nw_nfs_server>169.254.1.0</nw_nfs_server> <max_domain_number>20</max_domain_number> <xi_tools_dir>/usr/local/bin/</xi_tools_dir> </domctl_defaults>

The give and take between xenctl.xml and the script (xen-mynewdom14 in this case) just doesn't seem to matter. I know it is seeing /boot/xenolinux.gz because in earlier tests it wasn't. But what is going wrong is a mystery.

A working example of booting a virtual domain with a specific IP address from a specific (non-CD) device would be very helpful.

I'll grab the xeno-unstable again after this weekend, in the hopes that the problems are related to the Java program Bin mentioned.

-- Greg