WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] The Problem of Creating a domain

To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] The Problem of Creating a domain
From: "Inaba" <B8844014@xxxxxxxxxxxxxxxxx>
Date: Tue, 17 Feb 2004 16:02:27 +0800
Delivery-date: Tue, 17 Feb 2004 08:29:16 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <E1Asec0-0004hV-00@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thanks for all the helps !!

When I create the domain 1, I received the message as bellow in
xen_read_domain console:

[10] modprobe: Can't open dependencies file
/lib/modules/2.4.24-xeno/modules.dep (No such file or directory)
[10] Remounting root filesystem in read-write mode:  [  OK  ]
[10] Mounting local filesystems:  [  OK  ]
[10] Turning on process accounting [  OK  ]
[10] INIT: Entering runlevel: 4
[10] Entering non-interactive startup
[10] Setting network parameters:  [  OK  ]
[10] Bringing up loopback interface:  [  OK  ]
[10] Starting system logger: [  OK  ]
[10] Starting kernel logger: [  OK  ]
[10] Initializing random number generator:  [  OK  ]
[10] Starting sshd:[  OK  ]
[10] Starting crond: [  OK  ]
[10] Starting xfs: [  OK  ]
[10] Starting anacron: [  OK  ]
[10]
[10] eth0      Link encap:Ethernet  HWaddr AA:00:00:63:8B:C7
[10]           inet addr:163.25.117.195  Bcast:163.25.117.255
Mask:255.255.255.0
[10]           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
[10]           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
[10]           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
[10]           collisions:0 txqueuelen:1000
[10]           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
[10]
[10] cat: /usr/XenDemoCD/buildinfo.txt: No such file or directory
[10] INIT: no more processes left in this runlevel

Is that means that the boot sequence of domain1 done ? (I guess not)

But I could not use ssh root@xxxxxxxxxxx to access domain 1 ?

And I use the command #xc_dom_control.py list, it shows :

{'cpu_time': 47000774876L, 'stopped': 0, 'name': 'Domain-0', 'mem_kb':
131072, 'dom': 0, 'running': 1, 'cpu': 0}
{'cpu_time': 5224622362L, 'stopped': 0, 'name': 'This is VM 1', 'mem_kb':
65536, 'dom': 10, 'running': 0, 'cpu': 0}

What's the problem in the domain1 booting?

cheers,

Inaba

----- Original Message ----- 
From: "Steven Hand" <Steven.Hand@xxxxxxxxxxxx>
To: "Inaba" <m9244001@xxxxxxxxxxxxxxxxx>
Cc: "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxx>; "xen-devel"
<xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Sent: Monday, February 16, 2004 5:00 PM
Subject: Re: [Xen-devel] The Problem of Creating a domain


>
> > I have editted the /etc/fstab like this
> >
> > /dev/hda1               /                       ext3    defaults
1 1
> > none                       /dev/pts                devpts
gid=5,mode=620  0
> > 0
> > /dev/hda5               /domain                 ext3    defaults
1 2
> > none                       /proc                   proc    defaults
0
> > 0
> > none                       /dev/shm                tmpfs   defaults
0
> > 0
> > /dev/hda2               /work                   ext3    defaults
1 2
> > /dev/hda3               swap                    swap    defaults
0 0
> >
> > but when I created a new domain, some errors still occurred in
filesystem
> > checking as below
> >
> > [1] Checking filesystems
> > [1] fsck.ext3Possibly non-existent or swap device?
> > [1] Possibly non-existent or swap device?
> > [1] Checking all file systems.
> > [1] [/sbin/fsck.ext3 (1) -- /domain] fsck.ext3 -a /dev/hda5
> > [1] [/sbin/fsck.ext3 (1) -- /work] fsck.ext3 -a /dev/hda2
> > [1] : No such device or address while trying to open /dev/hda5
> > [1] fsck.ext3: No such device or address while trying to open /dev/hda2
> > [1] [FAILED]
> > [1]
> > [1] *** An error occurred during the file system check.
> > [1] *** Dropping you to a shell; the system will reboot
> > [1] *** when you leave the shell.
> > [1] Give root password for maintenance
> >
> > I think may be there are some errors in  /etc/fstab but I could not find
it
>
>
> The above error message means "there is no device called /dev/hda5".
> This means that you have not exported it as a vbd to this domain.
>
> The vbd exports and the /etc/fstab for every domain (except 0) need
> to be "in sync".
>
>
>
> > another dumb problem:
> >
> > my vbd_list is set like this
> >
> > vbd_list = [ ('phy:hda5','hda5','w' ), ('phy:hda3','hda3','w') ]
> >
> > but it shows the error message as below
> >
> > Warning: one or more hard disk extents are
> >          writeable by two or more domains simultaneously.
> > ERROR: This kind of disk sharing is not allowed
> >         at the current safety level (0).
>
> My guess is that you have either hda5 or hda3 (or both) mounted
> read-write in domain 0. If the tool let you proceed, you would
> end up moulinexing the partitions (you cannot allow two domains
> to mount the same partition read-write as they will make independent
> and inconsistent updates).
>
> To fix this, unmout (or remount read-only) /dev/hda5 and/or /dev/hda3
>
>
> > and then I changed the vbd_list as
> >
> > vbd_list = [ ('phy:hda1','hda1','w' ), ('phy:hda3','hda3','w') ]
> >
> > It could continue the domain booting sequence
>
> Well this would cause the problem you observed above: you have now
> not exported hda5 to the new domain, and so when it tries to access
> it it discovers that it is not there.
>
>
> > Why I can't use /dev/hda5 as the vbd_list?
>
> This is not a sane question -- if you mean why can you not have
> hda5 in the vbd_list, the answer is almost certainly as explained
> above.
>
>
> > Is there any clear document that descirbe how to install Xen from
> > xeno-1.2.tar.gz step by step?
>
> There are a number of howtos as mentioned in Ian's last message:
>
>
>    Jans' excellent Xen FAQ:
>    http://xen.epiuse.com/xen-faq.txt
>
>    Bin Ren's HOWTO:
>    http://www.cl.cam.ac.uk/~br260/doc/xeno-1.1-howto.txt
>
>    Yan-Ching's HOWTO:
>    http://www.csc.liv.ac.uk/~u2ycc/xen/xen-install-domain-fs-howto.txt
>
>    Xen for Grid by Greg Newby:
>    http://www.arsc.edu/~newby/grid/xen-for-grid.txt
>
>
> However I do not think any of these go into sufficient detail for you.
>
>
> cheers,
>
> S.
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel





-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel