Xen users - Jun 2008 - Installing a Debian Etch DomU using debootstrap

Hi,

I wanted to install a Debian Etch DomU under Xen 3.2.1. But I
constantly get the following error message when booting the DomU:

---
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
---

The DomU config file is:
---
disk = [ ''phy:/dev/mapper/xenvg-VM1,/dev/hda1,w'',
''phy:/dev/mapper/xenvg-VM1--swap,hda2,w'' ]
---

And its /etc/fstab:
---
/dev/hda1       /       ext3    defaults,errors=remount-ro      0 1
/dev/hda2       swap    swap    sw                              0 0
proc            /proc   proc    defaults                        0 0
sysfs           /sys    sysfs   defaults                        0 0
---

What is going on?

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sunday June 22 2008 10:04:00 am Thomas wrote:
> The DomU config file is:
> ---
> disk = [ ''phy:/dev/mapper/xenvg-VM1,/dev/hda1,w'',
> ''phy:/dev/mapper/xenvg-VM1--swap,hda2,w'' ]
Is that a typo? Did you mean ''xenvg-VM1-swap'' instead of
''xenvg-VM1 --swap''
(with a space and two dashes)?

Also, if you are using pygrub, instead of kernel/ramdisk, we will need to see 
your domu''s grub.conf also.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi,

The xenvg-VM1--swap is not a typo! I was also very surprised to
discover that when using lvm to create the swap lv using: lvcreate -n
VM1-swap, lvm creates a volume which name has a double dash in it. For
the space in the name, I don''t have this on my side, I have edited the
config just in case a weird character made his way in it, but no.

For booting the domU I use initrd, here is my file:
---
kernel="/boot/domU_32/vmlinuz-2.6.18-6-xen-686"
initrd="/boot/domU_32/initrd.img-2.6.18-6-xen-686"
---

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Actually my error message is the following:
---
No filesystem could mount root, tried:  cramfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
---

I also noticed that when installing using debootstrap, I do not have a
/etc/lilo.conf in my DomU. Could that be part of the problem?

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

I noticed a typo in my configuration file, I had typed "hda2" instead
of "/dev/hda2", but xen doesn''t care and keeps spitting me
the exact
same error message, as if nothing had changed...

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun June 22 2008, Thomas wrote:
> I wanted to install a Debian Etch DomU under Xen 3.2.1. But I
> constantly get the following error message when booting the DomU:
>
> ---
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(3,1) ---
>
> The DomU config file is:
> ---
> disk = [ ''phy:/dev/mapper/xenvg-VM1,/dev/hda1,w'',
> ''phy:/dev/mapper/xenvg-VM1--swap,hda2,w'' ]
> ---
I''m unsure if it''s possible to specifiy the absolute dm path
for the lv but
my setups all work with the following settings using a relative path 
(to /dev) for the lv within the vg (not using the dm path), e.g.:

disk = [ ''phy:vg0/lv-rootfs-terry,hda1,w'' ]

where the lv ist /dev/vg0/lv-rootfs-terry

$> ls -l /dev/vg0/lv-rootfs-terry
[...] /dev/vg0/lv-rootfs-terry -> /dev/mapper/vg0-lv--rootfs--terry

For your setup it would be
disk = [ ''phy:xenvg/VM1,hda1,w'' ]

Regards
Daniel

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

I think my problem is more related to ext3 module missing in the
kernel. Recall my error message:

---
No filesystem could mount root, tried:  cramfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
---

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Thomas wrote:
> I think my problem is more related to ext3 module missing in the
> kernel. Recall my error message:
> 
> ---
> No filesystem could mount root, tried:  cramfs
> Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(3,1)
> ---
> 
So, is it in the kernel being booted? Are you using an initrd or the like?

Does it load the partitions from your blockdevice correctly?

Regards, Dion

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Here is my config file:
----
  -*- mode: python; -*-
kernel="/boot/domU_32/vmlinuz-2.6.18-6-xen-686"
initrd="/boot/domU_32/initrd.img-2.6.18-6-xen-686"
memory = "256"
name = "VM1-2.6.18"
vif = [ ''mac=00:16:3e:00:00:01, ip=10.0.0.1'' ]
netmask = "255.255.255.0"
gateway = "10.0.0.128"
disk = [ ''phy:/dev/mapper/xenvg-VM1,/dev/hda1,w'',
''phy:/dev/mapper/xenvg-VM1--swap,/dev/hda2,w'' ]

root = "/dev/hda1"

extra=''console=hvc0 xencons=hvc0''
-----



Here is what gets printed out when using the "xm create -c
VM1-2.6.18-6" command:

-------
Linux version 2.6.18-6-xen-686 (Debian 2.6.18.dfsg.1-18etch1)
(waldi@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian
4.1.1-21)) #1 SMP Sun Feb 10 22:43:13 UTC 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)
0MB HIGHMEM available.
264MB LOWMEM available.
ACPI in unprivileged domain disabled
Built 1 zonelists.  Total pages: 67584
Kernel command line: root=/dev/hda1 console=hvc0 xencons=hvc0
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Xen reported: 2999.962 MHz processor.
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Software IO TLB disabled
vmalloc area: d1000000-f51fe000, maxmem 2d7fe000
Memory: 255744k/270336k available (1580k kernel code, 6052k reserved,
588k data, 148k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 7503.68 BogoMIPS (lpj=15007366)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 2048K
Checking ''hlt'' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 12k freed
Brought up 1 CPUs
migration_cost=0
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
PCI: System does not support PCI
PCI: System does not support PCI
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1214153774.523:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
Using IPI No-Shortcut mode
netfront: device eth0 has copying receive path.
Registering block device major 3
XENBUS: Device with no driver: device/console/0
No filesystem could mount root, tried:  cramfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
------


Do you see anything fancy in the log?

Also I''d like to know what should be the folder name for modules
inside /lib/modules of my domU?


Best regards,

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

In my domU I have emptied my /lib/modules folders, and I get the exact
same error message, therefore the problem might be elsewhere.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

I also deleted my /etc/fstab in DomU, and I get the exact same error message.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sunday June 22 2008 11:58:54 am Thomas wrote:
> I also noticed that when installing using debootstrap, I do not have a
> /etc/lilo.conf in my DomU. Could that be part of the problem?
Since you are using kernel/ramdisk= in your config, ultimately no. I
don''t
know if Debian etch prefers lilo over grub, but if it''s like 
grub, /etc/lilo.conf would just be a link to something in /boot.

On Sunday June 22 2008 01:06:27 pm Thomas wrote:
> Here is my config file:
> ----
>   -*- mode: python; -*-
> kernel="/boot/domU_32/vmlinuz-2.6.18-6-xen-686"
> initrd="/boot/domU_32/initrd.img-2.6.18-6-xen-686"
> memory = "256"
> name = "VM1-2.6.18"
> vif = [ ''mac=00:16:3e:00:00:01, ip=10.0.0.1'' ]
> netmask = "255.255.255.0"
> gateway = "10.0.0.128"
> disk = [ ''phy:/dev/mapper/xenvg-VM1,/dev/hda1,w'',
> ''phy:/dev/mapper/xenvg-VM1--swap,/dev/hda2,w'' ]
>
> root = "/dev/hda1"
>
> extra=''console=hvc0 xencons=hvc0''
See next comment.
> Here is what gets printed out when using the "xm create -c
> VM1-2.6.18-6" command:
>
> -------
> Linux version 2.6.18-6-xen-686 (Debian 2.6.18.dfsg.1-18etch1)
[...]
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> Xen virtual console successfully installed as tty1
hvc0 is a pvops kernel thing (2.6.24 and up). 2.6.18 used xvc0 and tty1 
interchangeably, so you really don''t need the extra= line. (Not that
that has
anything to do with root not mounting.)
> Also I''d like to know what should be the folder name for modules
> inside /lib/modules of my domU?
As in the ''Linux version'' line above:
/lib/modules/2.6.18-6-xen-686 . You
should copy it over from a 2.6.18-6 Debian xen distro. Once your ramdisk is 
done setting up your initial device drivers necessary for finding and 
mounting your root device, it''s space is released, and all further
modprobes
are done from /lib/modules, so you will need it anyway, whether you use 
kernel/ramdisk= or bootloader=.

Of course, you haven''t even gotten that far if it can''t find
the root device
to mount. That''s why cleaning out /lib/modules and /etc/fstab
doesn''t
matter - *yet*. I''m not familiar w/debootstrap, and whether it creates
a
straight ext3 partition or whether it uses lvm, but your dom0 initrd from 
your ramdisk= line has to have all the proper modules to find your domu root 
device, and is your current problem. I can''t help you with what should
be in
there for your domu, but I can help with telling you what is in there now. 
Naturally, if your dom0 initrd is actually used to boot your dom0, you are 
going to want a new name for your initrd before you change it for your domu. 
(It looks like you put it in a separate subdir ''domu_32''.)

Do a ''file /boot/domU_32/initrd.img-2.6.18-6-xen-686''. It will
most likely
return and tell you it is a gzip-ed file. The contents of the ungzip-ed is 
either a tar or cpio archive. I''m assuming cpio. To see the contents,
do:

gunzip -c /boot/domU_32/initrd.img-2.6.18-6-xen-686 | cpio -t

You can use ''cpio -tv'' to get an ''ls -l''
style listing. Some distros have
the ''lsinitrd'' command to make this easier. (Relatively new, I
think. F9 has
it.)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Thomas wrote:
> I also deleted my /etc/fstab in DomU, and I get the exact same error
message.
>   
The kernel tries to mount the root fs because of root=/dev/hda1, so 
/etc/fstab in DomU has nothing to do with this at boot time. The same 
holds for /lib/modules in DomU. The ext3 driver (if that is where your 
root fs lives on)  has to come from your

/boot/domU_32/initrd.img-2.6.18-6-xen-686

I should unzip this and extract with cpio to verify the required modules are in.



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun, Jun 22, 2008 at 04:04:00PM +0200, Thomas wrote:
> I wanted to install a Debian Etch DomU under Xen 3.2.1. But I
> constantly get the following error message when booting the DomU:
Please provide the _complete_ config of the VM.
> ---
> Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(3,1)
> ---
This looks like a kernel which needs an initrd.

Bastian

-- 
Oblivion together does not frighten me, beloved.
		-- Thalassa (in Anne Mulhall''s body), "Return to Tomorrow",
		   stardate 4770.3.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi guys,

Thank you for your assistance. Here is the output of:
---
$ gunzip -c /boot_test/domU_32/initrd.img-2.6.18-6-xen-686 | cpio -t | grep ext3
lib/modules/2.6.18-6-xen-686/kernel/fs/ext3
lib/modules/2.6.18-6-xen-686/kernel/fs/ext3/ext3.ko
---

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun June 22 2008, Thomas wrote:
> Here is what gets printed out when using the "xm create -c
> VM1-2.6.18-6" command:
>
> Linux version 2.6.18-6-xen-686 (Debian 2.6.18.dfsg.1-18etch1)
> (waldi@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian
> 4.1.1-21)) #1 SMP Sun Feb 10 22:43:13 UTC 2008
> BIOS-provided physical RAM map:
>  Xen: 0000000000000000 - 0000000010800000 (usable)
> 0MB HIGHMEM available.
> 264MB LOWMEM available.
> ACPI in unprivileged domain disabled
> Built 1 zonelists.  Total pages: 67584
> Kernel command line: root=/dev/hda1 console=hvc0 xencons=hvc0
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 8192 bytes)
> Xen reported: 2999.962 MHz processor.
> Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
> Software IO TLB disabled
> vmalloc area: d1000000-f51fe000, maxmem 2d7fe000
> Memory: 255744k/270336k available (1580k kernel code, 6052k reserved,
> 588k data, 148k init, 0k highmem)
> Checking if this processor honours the WP bit even in supervisor mode...
> Ok. Calibrating delay using timer specific routine.. 7503.68 BogoMIPS
> (lpj=15007366) Security Framework v1.0.0 initialized
> SELinux:  Disabled at boot.
> Capability LSM initialized
> Mount-cache hash table entries: 512
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 2048K
> Checking ''hlt'' instruction... OK.
> SMP alternatives: switching to UP code
> Freeing SMP alternatives: 12k freed
> Brought up 1 CPUs
> migration_cost=0
> Grant table initialized
> NET: Registered protocol family 16
> Brought up 1 CPUs
> PCI: setting up Xen PCI frontend stub
> ACPI: Interpreter disabled.
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI: disabled
> xen_mem: Initialising balloon driver.
> PCI: System does not support PCI
> PCI: System does not support PCI
> NET: Registered protocol family 2
> IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
> TCP established hash table entries: 16384 (order: 5, 131072 bytes)
> TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
> TCP: Hash tables configured (established 16384 bind 8192)
> TCP reno registered
> audit: initializing netlink socket (disabled)
> audit(1214153774.523:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> Xen virtual console successfully installed as tty1
> Event-channel device installed.
> netfront: Initialising virtual ethernet driver.
> PNP: No PS/2 controller found. Probing ports directly.
> i8042.c: No controller found.
> mice: PS/2 mouse device common for all mice
> TCP bic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> NET: Registered protocol family 8
> NET: Registered protocol family 20
> Using IPI No-Shortcut mode
> netfront: device eth0 has copying receive path.
> Registering block device major 3
> XENBUS: Device with no driver: device/console/0
> No filesystem could mount root, tried:  cramfs
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(3,1) ------
It seems your domU kernel does not recognize the xen vbd - you should get 
something like
xen-vbd: registered block device major 3

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi,

I think I now understand the problem. I am missing the initrd file.
Where can I get the official image from?

I often see people putting the following in their configuration file:
--
kernel = "/boot/vmlinuz-2.6.18-4-xen-vserver-686"
ramdisk = "/boot/initrd.img-2.6.18-4-xen-vserver-686"
--

I know where to get the vmlinuz file, but where to get the initrd.img one?

I am using Debian Etch. Looking for the file manually, I was unable to
locate it anywhere in the repositories.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am Samstag, den 19.07.2008, 09:09 +0200 schrieb Thomas:
> Hi,
> 
> I think I now understand the problem. I am missing the initrd file.
> Where can I get the official image from?
> 
> I often see people putting the following in their configuration file:
> --
> kernel = "/boot/vmlinuz-2.6.18-4-xen-vserver-686"
> ramdisk = "/boot/initrd.img-2.6.18-4-xen-vserver-686"
> --
> 
> I know where to get the vmlinuz file, but where to get the initrd.img one?
You should create one by e.g.
mkinitramfs -o /boot/initrd.img-`uname -r` `uname -r`

Replace `uname -r` by the kernel version you want to create an initrd
for,
if you''re currently not running this kernel.

On debian it might be mkinitrd ,but its usage is similar.

cheers

Stephan


> 
> I am using Debian Etch. Looking for the file manually, I was unable to
> locate it anywhere in the repositories.
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
-- 
-- 
Stephan Seitz
Senior System Administrator

*netz-haut* e.K.
multimediale kommunikation

zweierweg 22
97074 würzburg

fon: +49 931 2876247
fax: +49 931 2876248

web: www.netz-haut.de <http://www.netz-haut.de/>

registriergericht: amtsgericht würzburg, hra 5054


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> You should create one by e.g.
> mkinitramfs -o /boot/initrd.img-`uname -r` `uname -r`
>
> Replace `uname -r` by the kernel version you want to create an initrd
> for,
> if you''re currently not running this kernel.
>
> On debian it might be mkinitrd ,but its usage is similar.
Hi stephan,

Hmm, this requires me to install initrd-tools on my dom0, I don''t like
to install anything at all on my dom0. I already trashed my server by
inadvertently installing the package xen-linux-system-2.6.18-4, I had
to reinstall everything from scratch.

Isn''t there a place where I can manually download that damn file?

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sat, 2008-07-19 at 10:26 +0200, Thomas wrote:
> Hmm, this requires me to install initrd-tools on my dom0, I don''t
like
> to install anything at all on my dom0.
that''s initrd-tools, one binary, some scripts and a hand full of
documentation files.
this package won''t break anything.
> Isn''t there a place where I can manually download that damn file?
no. the initrd file is generated on the fly when you install the
kernel package.

use:
dpkg-reconfigure linux-image-2.6.18-4-xen-vserver-686

hth,
tom.

-- 
Thomas "Duke" Hager                       {duke,hager}@sigsegv.at
GPG: 1024D/D27F858C            http://www.sigsegv.at/gpg/duke.gpg
================================================================"Never
Underestimate the Power of Stupid People in Large Groups."




_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Thanks Thomas,

At last I finally got my initrd now, but the domU doesn''t care a
single penny at all, as if I hadn''t done anything different.

I still get:
--
No filesystem could mount root, tried:  cramfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
--

Reading my previous emails, I just noticed that I am back to square
one as on the 22nd of June.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sat, 2008-07-19 at 14:14 +0200, Thomas wrote:
> Thanks Thomas,
you''re welcome :)
> Reading my previous emails, I just noticed that I am back to square
> one as on the 22nd of June.
can you describe how you created your domu image with debootstrap?
i tried that too once and failed miserably ;-)

btw, i use a simle net install to create new debian domUs.
works like a charm.

br,
tom.

-- 
Thomas "Duke" Hager                       {duke,hager}@sigsegv.at
GPG: 1024D/D27F858C            http://www.sigsegv.at/gpg/duke.gpg
================================================================"Never
Underestimate the Power of Stupid People in Large Groups."




_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi Tom,

I created 2 lvm volumes, one ext3 and the other one swap of course.
Then mounted my volume in a directory /mnt, issued the following
command:
debootstrap --arch amd64 etch /mnt http://ftp.debian.org/debian

Installation happens.

Here is my configuration file:
--
#  -*- mode: python; -*-
kernel = "/boot/vmlinuz-2.6.18-6-xen-amd64"
initrd = "/boot/initrd.img-2.6.18-6-xen-amd64"
memory = "256"
maxmem = "1024"
name = "debian64"
vif = [ ''mac=00:16:3e:00:00:05, ip=10.0.0.5'' ]
disk = [ ''phy:/dev/mapper/xenvg-debian64,/dev/hda1,w'',
         ''phy:/dev/mapper/xenvg-debian64--swap,/dev/hda2,w'' ]

root = "/dev/hda1"
extra=''console=hvc0 xencons=hvc0''
--

I have correctly set the fstab, and securetty in the domU.

I installed linux-image-2.6.18-6-xen-amd64 in the dom0, I also copied
the modules to domU just in case. And it fails to mount the root fs.
Using a custom configuration file for compiling a vanilla kernel, it
works perfectly, but I would like to be able to use the packaged
kernel instead. Probably it is not compatible with debootstrap''s
debian install?

How did you install the DomU with netinstall? Do you have a resource
to point me to? a tutorial?

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sat, 2008-07-19 at 19:57 +0200, Thomas wrote:
> Hi Tom,
hi,
> I created 2 lvm volumes, one ext3 and the other one swap of course.
> Then mounted my volume in a directory /mnt, issued the following
> command:
> debootstrap --arch amd64 etch /mnt http://ftp.debian.org/debian
ic. you initialize your lv with an ext3 filesystems, so you don''t have
any partitions there. consequently, there is no /dev/hda1 for xen to
boot from.

tyr this config:

--
#  -*- mode: python; -*-
kernel = "/boot/vmlinuz-2.6.18-6-xen-amd64"
initrd = "/boot/initrd.img-2.6.18-6-xen-amd64"
memory = "256"
maxmem = "1024"
name = "debian64"
vif = [ ''mac=00:16:3e:00:00:05, ip=10.0.0.5'' ]
disk = [ ''phy:/dev/mapper/xenvg-debian64,/dev/hda,w'',
         ''phy:/dev/mapper/xenvg-debian64--swap,/dev/hdb,w'' ]

root = "/dev/hda"
extra=''console=hvc0 xencons=hvc0''
--

> I have correctly set the fstab, and securetty in the domU.
you got to modify your fstab now, because /dev/hda is your /
and /dev/hdb is swap.
> I installed linux-image-2.6.18-6-xen-amd64 in the dom0, I also copied
> the modules to domU just in case. And it fails to mount the root fs.
> Using a custom configuration file for compiling a vanilla kernel, it
> works perfectly,
it does?
i can''t image that any domu kernel can boot with your setup. but then
again, i don''t know the debootstrap magic ;-)
> How did you install the DomU with netinstall? Do you have a resource
> to point me to? a tutorial?
yes, http://wiki.debian.org/DebianInstaller/Xen

you simply boot the kernel with the netinstaller initrd and install the
domu the same way as any other debian system.

hth,
tom.

-- 
Thomas "Duke" Hager                       {duke,hager}@sigsegv.at
GPG: 1024D/D27F858C            http://www.sigsegv.at/gpg/duke.gpg
================================================================"Never
Underestimate the Power of Stupid People in Large Groups."




_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi,

Using /dev/hda and /dev/hdb, yields the following error message:
---
Registering block device major 3
 hda: unknown partition table
 hdb: unknown partition table
XENBUS: Device with no driver: device/console/0
No filesystem could mount root, tried:  cramfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,0)
---

I am pretty sure, that /dev/hda1 and /dev/hda2 must be used in Xen.

I have also tested something surprising, I have simply commented out
all my lines in /etc/fstab, and I get the exact same error message!
This means the problem occurs before fstab gets hit.

I have seen a lot of thread about this problem with people moving from
a 2.6.8 kernel to a 2.6.1x+ kernel (not in particular xen setups).

I don''t understand why I am having this problem as I am using an
"official" packaged xen kernel!?

I have installed the following package: linux-image-2.6.18-6-xen-amd64
in my dom0, should I install anything else? Am I the only person to
experience this problem?

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun, 2008-07-20 at 15:58 +0200, Thomas wrote:
> Registering block device major 3
>  hda: unknown partition table
>  hdb: unknown partition table
at least xen sees the discs now.
> I am pretty sure, that /dev/hda1 and /dev/hda2 must be used in Xen.
no, i really don''t think so.

i tested the debootstrap procedure on my xen server and it works fine.

i did:

- create a logical volume with 10G
- create an ext3 fs on this lv
- mount the lv somewhere (/mnt/loop in my case)
- debootstrap the new lv with: debootstrap lenny /mnt/loop \
  ftp://ftp.at.debian.org/debian/
- mount /proc to /mnt/loop/proc, chroot into /mnt/loop and run
  dselect to install the rest of the required software
- exit chroot, unmount /mnt/loop/proc
- rsync -a /lib/modules/2.6.18-6-xen-amd64 /mnt/loop/lib/modules/
- unmount /mnt/loop

i booted this domU with the following config:

kernel = "/boot/vmlinuz-2.6.18-6-xen-amd64"
ramdisk = "/boot/initrd.img-2.6.18-6-xen-amd64"
builder=''linux''
memory = 256
name = "centauri"
vcpus = 1
vif = [ ''mac=00:16:3e:14:07:88, bridge=xenlan'' ]
disk = [ ''phy:/dev/babylon/xen_test,hda,w'' ]
hostname="centauri"
root = "/dev/hda ro"
extra = "3 noirqdebug"

on_poweroff = ''destroy''
on_reboot   = ''restart''
on_crash    = ''restart''

everything went fine, the domu successfully booted into runlevel 3.

maybe you should give the netinstall method a try?

kr,
tom.

-- 
Thomas "Duke" Hager                       {duke,hager}@sigsegv.at
GPG: 1024D/D27F858C            http://www.sigsegv.at/gpg/duke.gpg
================================================================"Never
Underestimate the Power of Stupid People in Large Groups."




_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

I''ll forget about the debootstrap method, there is certainly a step I
am missing somewhere.

I actually do prefer the netinst method because it is not tied to a
specific distro. On the link posted previously about using netinst I
couldn''t find any relevant information. How do I attach a cdrom / iso
to a domU? And how to tell the domU to boot on that device?

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, 2008-07-21 at 12:38 +0200, Thomas wrote:
> I actually do prefer the netinst method because it is not tied to a
> specific distro. On the link posted previously about using netinst I
> couldn''t find any relevant information. How do I attach a cdrom /
iso
> to a domU? And how to tell the domU to boot on that device?
you don''t. the installer is located in debian''s netboot
initrd. there''s
no need for a cdrom or iso.

br,
tom.

-- 

Thomas "Duke" Hager                       {duke,hager}@sigsegv.at
GPG: 1024D/D27F858C            http://www.sigsegv.at/gpg/duke.gpg
================================================================"Never
Underestimate the Power of Stupid People in Large Groups."



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

I don''t follow you on this one. So I don''t even have to
download the
netinstall iso from debian.org?

On 7/22/08, Thomas Hager <duke@sigsegv.at> wrote:
> On Mon, 2008-07-21 at 12:38 +0200, Thomas wrote:
> > I actually do prefer the netinst method because it is not tied to a
> > specific distro. On the link posted previously about using netinst I
> > couldn''t find any relevant information. How do I attach a
cdrom / iso
> > to a domU? And how to tell the domU to boot on that device?
> you don''t. the installer is located in debian''s netboot
initrd. there''s
> no need for a cdrom or iso.
>
> br,
> tom.
>
> --
>
> Thomas "Duke" Hager                       {duke,hager}@sigsegv.at
> GPG: 1024D/D27F858C            http://www.sigsegv.at/gpg/duke.gpg
> ================================================================>
"Never Underestimate the Power of Stupid People in Large Groups."
>
>
>
> _______________________________________________
> 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

On Tue, 2008-07-22 at 21:54 +0200, Thomas wrote:
> I don''t follow you on this one. So I don''t even have to
download the
> netinstall iso from debian.org?
well, you have to download the iso, mount it once and copy the initrd
contained in the netinst iso to your xen server. then you boot a domu
with this initrd and the net installer will run.

br,
tom.

-- 

Thomas "Duke" Hager                       {duke,hager}@sigsegv.at
GPG: 1024D/D27F858C            http://www.sigsegv.at/gpg/duke.gpg
================================================================"Never
Underestimate the Power of Stupid People in Large Groups."



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi Thomas,

Where is located the initrd file inside the netinstall archive? I have
found something in tools/lodlin16.zip is that it?

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, 2008-08-18 at 23:13 +0200, Thomas wrote:
> Hi Thomas,
hi,
> Where is located the initrd file inside the netinstall archive? I have
> found something in tools/lodlin16.zip is that it?
there''s no tools/lodlin16.zip in the netboot archive. i fetched mine
from here:

http://ftp.debian.org/debian/dists/etch/main/installer-amd64/current/images/netboot/netboot.tar.gz

this archive contains the file debian-installer/amd64/initrd.gz.

hth,
tom.

-- 
Thomas "Duke" Hager                               duke@sigsegv.at
GPG: 1024D/D27F858C            http://www.sigsegv.at/gpg/duke.gpg
================================================================"Never
Underestimate the Power of Stupid People in Large Groups."



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Thanks Thomas,

Acutally I had downloaded this archive:
http://cdimage.debian.org/debian-cd/4.0_r4a/amd64/iso-cd/debian-40r4a-amd64-netinst.iso

That''s why I was a bit puzzled.

I will try to install a VM with this method and see how it turns out.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

I have failed trying to install a VM using Debian''s Installer with the
netinst.  The boot sequence ends with the following error message:
---
Registering block device major 202
XENBUS: Device with no driver: device/console/0
No filesystem could mount root, tried:  cramfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(202,1)
---

I tried to follow the very thin documentation from this link:
http://wiki.debian.org/DebianInstaller/Xen

I don''t understand how to do the step: "You need to copy the DomU
kernel''s /lib/modules/<version> to the initrd. "

Here is my config file for the domU:
---
#  -*- mode: python; -*-
kernel = "/boot/vmlinuz-2.6.18-6-xen-amd64"
initrd = "/tmp/debian-installer/amd64/initrd.gz"
memory = "256"
maxmem = "1024"
name = "VM1"
vif = [ ''mac=00:16:3e:00:00:05, ip=10.0.0.5'' ]
disk = [ ''phy:/dev/mapper/xenvg-VM1,/dev/xvda1,w'',
         ''phy:/dev/mapper/xenvg-VM1--swap,/dev/xvda2,w'' ]

root = "/dev/xvda1"
extra = ''console=hvc0 xencons=hvc0''
---

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> I don''t understand how to do the step: "You need to copy the
DomU
> kernel''s /lib/modules/<version> to the initrd. "
>
On Dom0, do:

uname -r
(make sure the output is the -xen kernel)

Then do:

mkinitramfs -o /tmp/debian-installer/amd64/initrd.img-2.6.18-6-xen-amd64
  `uname -r`

That command will create the initrd named:
/tmp/debian-installer/amd64/initrd.img-2.6.18-6-xen-amd64
using the modules on your dom0 that will work in the domU

Then, change this line in your domU config
> initrd = "/tmp/debian-installer/amd64/initrd.gz"
to:
initrd = "/tmp/debian-installer/amd64/initrd.img-2.6.18-6-xen-amd64"


Hope that helps.
Cheers,
Todd

-- 
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Why do I need to completely regenerate the initrd file? I just want to
use the Netboot Debian Installer initrd, I would expect it to run out
of the box!? Moreover my dom0 uses a custom kernel whereas my domU
will be using an official xen kernel.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun, Aug 31, 2008 at 10:08 AM, Thomas <iamkenzo@gmail.com>
wrote:
> Why do I need to completely regenerate the initrd file? I just want to
> use the Netboot Debian Installer initrd, I would expect it to run out
> of the box!? Moreover my dom0 uses a custom kernel whereas my domU
> will be using an official xen kernel.
>
I see, so you just want to add it... you should be able to extract and mount
the initrd.gz file. I don''t know the exact commands but the basic idea
would
be:

<unzip the initrd>
mount -o loop <the extracted initrd> /mnt/<somemountpoint>
cp /lib/modules/<xen kernel version>/<the modules you need>
/mnt/<the
mountpoint>
umount /mnt/<the mountpoint>
<compress the initrd back>

Hope that helps,
Cheers,
Todd

-- 
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

When mounting the uncompressed initrd file, it asks me for a file
system, I tried, cramfs, ext3 they both failed.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun, 2008-08-31 at 16:39 +0200, Thomas wrote:
> When mounting the uncompressed initrd file, it asks me for a file
> system, I tried, cramfs, ext3 they both failed.
The initrd is actually a cpio archive. The following forum thread should
get you going:

http://ubuntuforums.org/archive/index.php/t-243612.html

I do remember seeing some FUSE gizmo that allowed you to mount and
interact with a cpio (or gzip / zip / etc) archive, however I can''t
recall the name of it at the moment.

Cheers,
--Tim

-- 
Monkey + Typewriter = Echoreply ( http://echoreply.us )


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

I am still having the problem with the tty. I cannot xm console into a
running domU.

My setup is: dom0: Debian Etch with a custom kernel. My domU is a
Debian Etch with kernel 2.6.18-6-xen-amd64

I have discovered that for domU with 2.6.18 one must use xvc0, and
with kernels >= 2.6.25 one must use hvc0.

I have finally managed to use debootstrap to create a VM. When my VM
gets created, I see the console appear if I use "xm create -c VM", and
the console is tty1. But if I do ctrl+] to leave the console, I can no
longer "xm console" into. However when I do "xm reboot VM",
then if I
am fast enough, I can "xm console" into it.

What is wrong with my configuration? I know I am missing a piece in
this puzzle what is it? This is getting crazy.

Here is my configuration file:
---
extra = ''console=xvc0 xencons=xvc0'' # Use xvc0 for kernel
2.6.18
#extra = ''console=hvc0 xencons=hvc0'' # Use hvc0 for kernels
>= 2.6.25
---

My /etc/inittab:
---
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6
---

/etc/securetty:
---
 /etc/securetty: list of terminals on which root is allowed to login.
# See securetty(5) and login(1).
console
xvc0
hvc0
...
----

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> Here is my configuration file:
> ---
> extra = ''console=xvc0 xencons=xvc0'' # Use xvc0 for kernel
2.6.18
Try extra=''xencons=tty''

Cheers,
Todd

-- 
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi Todd,

It still didn''t work for me. Therefore I suspect the problem to be
somewhere else.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, Sep 1, 2008 at 12:33 PM, Thomas <iamkenzo@gmail.com>
wrote:
> Hi Todd,
>
> It still didn''t work for me. Therefore I suspect the problem to be
> somewhere else.
>
Try changing your /etc/inittab

for the tty1 line,

change it to xvc0

then, the console=xvc0 should work.

Hope that helps,
Cheers,
Todd

P.S. Maybe a fresh thread would be in order? ;)

-- 
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi Todd, modifying the inittab file made things even worse as now,
even at boot time the console never shows up. I have created a new
thread for that specific problem.

Thank you for your assistance.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users