On Sat, Nov 15, 2003 at 03:52:56PM -0500, Matt Ayres wrote:
> I took the plunge and re-installed this server with RedHat 9. I no
> longer receive the Java exception errors. I am having a problem with
> the domains finding their root device. I've tried to specify it
> everywhere possible.
> ...
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
> My script consists of:
>
> domain new -ntest1 -k16768 -v1 -4192.168.1.51 -g192.168.1.1
> -htest1.office.tektonic.net -d/dev/sda2 -tro root=/dev/sda2
> -ainit=/linuxrc 4 DOMID=2
> physical grant -psda2 -r
> domain start
>
> Everything starts up fine, but it cannot find the root device. Here are
> some snippets from the console:
>
> [18] Kernel command line:
> ip=192.168.1.51:169.254.1.0:192.168.1.1:255.255.0.0:test1.office.tektonic.net:eth0:off
> init=/linuxrc root=/dev/sda2 ro
> ...
> [18] root_device_name = sda2
> [18] VFS: Cannot open root device "sda2" or 08:02
> [18] Please append a correct "root=" boot option
> [18] Kernel panic: VFS: Unable to mount root fs on 08:02
>
>
> I've tried to specify "/dev/sda2" in as many places as possible, however
> it keeps on trying to load just "sda2". I am using xen-unstable as I am
> testing under VMware and need the BusLogic SCSI support.
>
> On Fri, 2003-11-14 at 19:25, Bin Ren wrote:
> > On 15 Nov 2003, at 00:14, Matt Ayres wrote:
> >
> > > Seems it comes back to the prior Java problem.
> > >
> > > [root@vpc docs]# xenctl script -f/etc/xen-mynewdom
> > > Domain defaults:
> > > name XenoLinux
> > > size 8192
> > > vifs 1
> > > domainImage /boot/xenolinux.gz
> > > domainInitRD null
> > > rootDevice /dev/hda2
> > > rootArgs ro
> > > usrDevice null
> > > NWIP 169.254.1.0+
> > > NWGW 169.254.1.0
> > > NWMask 255.255.0.0
> > > MaxDomainNumber 128
> > > NWNFSServer 169.254.1.0
> > > NWNFSRoot null
> > > XIToolsDir /install/bin/
> > > args init=/linuxrc 4 DOMID=+
> > > Domain created with arguments:
> > > /install/bin/xi_create 8192 XenoLinux
> > > Domain built with arguments:
> > > /install/bin/xi_build 21 /tmp/xen-image-11626.tmp 1
> > > ip=169.254.1.21:169.254.1.0:169.254.1.0:255.255.0.0::eth0:off
> > > init=/linuxrc 4 DOMID=21 root=/dev/hda2 ro
> > > VIF 0 initialized with arguments:
> > > /install/bin/xi_vifinit 21 0 169.254.1.21
> >
> > Anyway, we nearly had our xencel scripts work. Just add one line
> > to /etc/xen-mynewdom:
> >
> > domain new
> > physical grant -p/dev/hda2
> > domain start
> >
> > And then try again. See any further message after
> > /install/bin/xi_vifinit ..... ?
> >
> > If you want to see XenoLinux boot message in the newly created domain,
> > run as root:
> >
> > xen_nat_enable
> > xen_read_console&
> >
> > before run 'xenctl'
> >
> > >
> > > ****************
> > > Another exception has been detected while we were handling last error.
> > > Dumping information about last error:
> > > ERROR REPORT FILE = (N/A)
> > > PC = 0x40402f52
> > > SIGNAL = 11
> > > FUNCTION NAME = (N/A)
> > > OFFSET = 0xFFFFFFFF
> > > LIBRARY NAME = (N/A)
> > > Please check ERROR REPORT FILE for further information, if there is
> > > any.
> > > Good bye.
> > > /install/bin/xenctl: line 13: 2997 Unknown signal 33 $JAVA $ARGS
> > > -jar $(dirname $0)/xenctl-cmdline.jar $*
> >
> > This is very weird.
> >
> > Please first try the above to see whether the new domain starts running
> > or not.
> >
> > -- Bin
> >
> >
> >
> > -------------------------------------------------------
> > This SF. Net email is sponsored by: GoToMyPC
> > GoToMyPC is the fast, easy and secure way to access your computer from
> > any Web browser or wireless device. Click here to Try it Free!
> > https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
> --
> Matt Ayres <matta@xxxxxxxxxxxx>
> TekTonic
>
>
>
> -------------------------------------------------------
> This SF. Net email is sponsored by: GoToMyPC
> GoToMyPC is the fast, easy and secure way to access your computer from
> any Web browser or wireless device. Click here to Try it Free!
> https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Home