Hi!
May anyone assist me with booting FreeBSD DomU (under Debian Dom0). Now
I''m using the kernel-current, downloaded from Kip Macy site at
http://www.fsmware.com/xenofreebsd/7.0/download/
The problem is that I can''t specify _any_ root, the kernel can
recognize:
Mount point / had 1 dangling refs
Manual root filesystem specification:
<fstype>:<device> Mount <device> using filesystem
<fstype>
eg. ufs:da0s1a
? List valid disk boot devices
<empty line> Abort manual input
mountroot>
And here I''m stuck since it even doesn''t allow me to enter a
char.
I''ve tried several vfs.root.mountfrom specifications per googled
advises,
including /dev/md0, /dev/xbd0a and /dev/xb769a, but with no success.
What I''m doing wrong?
Thanks in advance.
--
Andrey V Khavryuchenko
Software Development Company http://www.kds.com.ua/
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Folks,
"AVK" == Andrey Khavryuchenko wrote:
AVK> I''ve tried several vfs.root.mountfrom specifications per
googled advises,
AVK> including /dev/md0, /dev/xbd0a and /dev/xb769a, but with no success.
Sorry, found a typo in config file
Now it boots and finds the root partition:
[XEN]
Trying to mount root from ufs:/dev/xbd769s1a
Loading configuration files.
Entropy harvesting: interrupts ethernet point_to_point kickstart.
swapon: /dev/ad0s1b: No such file or directory
Starting file system checks:
/dev/xbd769s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/xbd769s1a: clean, 128085 free (1765 frags, 15790 blocks, 1.2%
fragmentation)
Can''t stat /dev/ad0s1e: No such file or directory
Can''t stat /dev/ad0s1f: No such file or directory
Can''t stat /dev/ad0s1d: No such file or directory
Can''t stat /dev/ad1s1c: No such file or directory
Can''t stat /dev/ad0s1e: No such file or directory
Can''t stat /dev/ad1s1c: No such file or directory
Can''t stat /dev/ad0s1e: No such file or directory
/dev/ad0s1e: CAN''T CHECK FILE SYSTEM.
/dev/ad0s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Can''t stat /dev/ad1s1c: No such file or directory
/dev/ad1s1c: CAN''T CHECK FILE SYSTEM.
/dev/ad1s1c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Can''t stat /dev/ad0s1f: No such file or directory
Can''t stat /dev/ad0s1f: No such file or directory
/dev/ad0s1f: CAN''T CHECK FILE SYSTEM.
/dev/ad0s1f: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Can''t stat /dev/ad0s1d: No such file or directory
Can''t stat /dev/ad0s1d: No such file or directory
/dev/ad0s1d: CAN''T CHECK FILE SYSTEM.
/dev/ad0s1d: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
THE FOLLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENCY:
ufs: /dev/ad0s1e (/tmp), ufs: /dev/ad1s1c (/mnt), ufs: /dev/ad0s1f
(/usr), ufs: /dev/ad0s1d (/var)
Automatic file system check failed; help!
Oct 13 09:57:53 init: /bin/sh on /etc/rc terminated abnormally, going to single
user mode
Enter full pathname of shell or RETURN for /bin/sh:
Failure to boot is natural, since I''ve used unmodified FreeBSD qemu
image.
Sorry for troubling.
--
Andrey V Khavryuchenko
Software Development Company http://www.kds.com.ua/
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
post your xm config file- i think root needs to be 0x03 or something. On Mon, 16 Oct 2006, Andrey Khavryuchenko wrote:> Date: Mon, 16 Oct 2006 12:26:05 +0300 > From: Andrey Khavryuchenko <akhavr@gmail.com> > To: xen-users@lists.xensource.com > Subject: [Xen-users] booting FreeBSD DomU > > Hi! > > May anyone assist me with booting FreeBSD DomU (under Debian Dom0). Now > I''m using the kernel-current, downloaded from Kip Macy site at > http://www.fsmware.com/xenofreebsd/7.0/download/ > > The problem is that I can''t specify _any_ root, the kernel can recognize: > > Mount point / had 1 dangling refs > > Manual root filesystem specification: > <fstype>:<device> Mount <device> using filesystem <fstype> > eg. ufs:da0s1a > ? List valid disk boot devices > <empty line> Abort manual input > > mountroot> > > And here I''m stuck since it even doesn''t allow me to enter a char. > > I''ve tried several vfs.root.mountfrom specifications per googled advises, > including /dev/md0, /dev/xbd0a and /dev/xb769a, but with no success. > > What I''m doing wrong? > > Thanks in advance. > > -- > Andrey V Khavryuchenko > Software Development Company http://www.kds.com.ua/ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Okay, to fix that one you need to fix the fstab so the device names are correct. Are you using Macy''s root filesystem? that is perhaps the easiest way to do it. use his file for /, then use your new vbd as a second disk; then you can login and verify that things like the fstab are correct before you boot directly into your vbd. On Mon, 16 Oct 2006, Andrey Khavryuchenko wrote:> "AVK" == Andrey Khavryuchenko wrote: > > AVK> I''ve tried several vfs.root.mountfrom specifications per googled advises, > AVK> including /dev/md0, /dev/xbd0a and /dev/xb769a, but with no success. > > Sorry, found a typo in config file > > Now it boots and finds the root partition: > > [XEN] > Trying to mount root from ufs:/dev/xbd769s1a > Loading configuration files. > Entropy harvesting: interrupts ethernet point_to_point kickstart. > swapon: /dev/ad0s1b: No such file or directory > Starting file system checks: > /dev/xbd769s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/xbd769s1a: clean, 128085 free (1765 frags, 15790 blocks, 1.2% fragmentation) > Can''t stat /dev/ad0s1e: No such file or directory > Can''t stat /dev/ad0s1f: No such file or directory > Can''t stat /dev/ad0s1d: No such file or directory > Can''t stat /dev/ad1s1c: No such file or directory > Can''t stat /dev/ad0s1e: No such file or directory > Can''t stat /dev/ad1s1c: No such file or directory > Can''t stat /dev/ad0s1e: No such file or directory > /dev/ad0s1e: CAN''T CHECK FILE SYSTEM. > /dev/ad0s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > Can''t stat /dev/ad1s1c: No such file or directory > /dev/ad1s1c: CAN''T CHECK FILE SYSTEM. > /dev/ad1s1c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > Can''t stat /dev/ad0s1f: No such file or directory > Can''t stat /dev/ad0s1f: No such file or directory > /dev/ad0s1f: CAN''T CHECK FILE SYSTEM. > /dev/ad0s1f: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > Can''t stat /dev/ad0s1d: No such file or directory > Can''t stat /dev/ad0s1d: No such file or directory > /dev/ad0s1d: CAN''T CHECK FILE SYSTEM. > /dev/ad0s1d: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > THE FOLLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENCY: > ufs: /dev/ad0s1e (/tmp), ufs: /dev/ad1s1c (/mnt), ufs: /dev/ad0s1f (/usr), ufs: /dev/ad0s1d (/var) > Automatic file system check failed; help! > Oct 13 09:57:53 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode > Enter full pathname of shell or RETURN for /bin/sh: > > Failure to boot is natural, since I''ve used unmodified FreeBSD qemu image. > > Sorry for troubling. > > -- > Andrey V Khavryuchenko > Software Development Company http://www.kds.com.ua/ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Luke, "LC" == Luke Crawford wrote: LC> post your xm config file- i think root needs to be 0x03 or something. "LC" == Luke Crawford wrote: LC> Okay, to fix that one you need to fix the fstab so the device names LC> are correct. Yes, I know. LC> Are you using Macy''s root filesystem? that is perhaps the easiest way LC> to do it. use his file for /, then use your new vbd as a second disk; LC> then you can login and verify that things like the fstab are correct LC> before you boot directly into your vbd. No, I''m using the filesystem from fresh FreeBSD 6.1 install in qemu. Worked nicely after /etc/fstab and ttys where changed. -- Andrey V Khavryuchenko Software Development Company http://www.kds.com.ua/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Maybe Matching Threads
- GELI partition mount on boot fails after 7.0 -> 7.1-PRERELEASE upgrade
- Need clarifications: Xen and winXP HVM: pci direct access, USB, desktop resolution
- Help on syncing a windows server
- /usr: create/symlink failed, no inodes free
- bugged sysinstall, bsdlabel, zfs, gmirror - recept for disaster :)