On 04/07/2012 05:52, dhaneshk k wrote: > Please ignore my previous mail with the same subject line because there was > a terrible formatting mistake. > Please see the attached pdf which briefs the problem in assigning the IP > address to the netbsd virtual machine. > The Xen VM is running on Debian/ GNU Linux. > > Please find the attached document for detailed description. > > Any hints much appreciated.
Why do you think asking about NetBSD on a FreeBSD list is going to give
you better reesults than asking about NetBSD on a NetBSD list? Or even
on a Xen list?
Out of all the information in your message, you describe the actual
issues pretty baldly.
-- unable to set the IP number in a Xen instance
* How exactly did you try to set the IP Address manually?
* What happened?
Showing ifconfig(8) output for the interface concerned would be good.
-- avoiding the necessity for human interaction when booting on Amazon EC2
Your description looks as if the netbsd image is stopping at single user
mode, which it will do if there are certain problems. A typical reason
for this would be the need to run fsck to fix filesystem problems, but
there are many other possible causes. Look at the console output just
before it prompts you for which shell to run to work out what the actual
problem is.
Once you've got the system booting up to multi-user correctly, the
normal init scripts should take care of running dhclient etc. for you,
given that you have configured them properly.
Cheers,
Matthew
PS. FreeBSD runs well as a Xen domU (ie guest) instance, both on
generic Xen and on Amazon EC2. See http://wiki.freebsd.org/FreeBSD/Xen
FreeBSD doesn't have Xen dom0 (ie host) support yet.
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
signature.asc
Description: OpenPGP digital signature
