Hi guys! I installed XEN 4.0 on Debian Squeeze but I cannot get the first DomU (not an image) started. Attached you will find /etc/xen/xen1.conf and the result of "xm create -c /etc/xen/xen1.conf" in xen1.log. Can you help me? What did I wrong? Is it about the fstab in xen1 (see also attached)? Many thanks in advance! Regards Stefan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, Are your modules compiled into the kernel? If not you need a RAM disk Ian -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Stefan Sent: 03 July 2011 13:19 To: xen-users@lists.xensource.com Subject: [Xen-users] XEN DomU isn''t starting... Hi guys! I installed XEN 4.0 on Debian Squeeze but I cannot get the first DomU (not an image) started. Attached you will find /etc/xen/xen1.conf and the result of "xm create -c /etc/xen/xen1.conf" in xen1.log. Can you help me? What did I wrong? Is it about the fstab in xen1 (see also attached)? Many thanks in advance! Regards Stefan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2011/7/3 Stefan <hest@lavabit.com>:> Hi guys! > > I installed XEN 4.0 on Debian Squeeze but I cannot get the first DomU > (not an image) started. > > Attached you will find /etc/xen/xen1.conf and the result of "xm create > -c /etc/xen/xen1.conf" in xen1.log. > > Can you help me? What did I wrong?Lots of things.> Is it about the fstab in xen1 (see > also attached)?Part of it, yes. To make it simple, are you following a tuturial? If yes, you should follow it EXACTLY, down to the same kernel and Xen version. If not, and you''re a beginner to Xen, then I highly suggest you use a GUI frontend (e.g. virt-manager), setup a NEW domU using network install (a Centos or Debian domU is usually a good start), then learn from the generated config files and images. The long version, you''re booting using a kernel from dom0, but WITHTOUT and initrd. That''s fine if you know what you''re doing, but from the output it seems that you don''t. For starters, you need xen frontend block device driver loaded, and usually it''s built as module (xen-blkfront) on modern distros. Then there''s the fact that you use hda on both domU config file and fstab. It was deprecated a long time ago, and using it may lead to confusion as newer kernels will silently rename it to xvda or xvde. There might be other problems, but start with those two. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Fajar, as it was hard to find a XEN4/Squeeze-Tutorial I''ve tried my best by reading several documentations and now (with your help) I''m see a little progress.> The long version, you''re booting using a kernel from dom0, but > WITHTOUT and initrd. That''s fine if you know what you''re doing, but > from the output it seems that you don''t. For starters, you need xen > frontend block device driver loaded, and usually it''s built as module > (xen-blkfront) on modern distros.Now using initrd the domu is starting and accessible but...> Then there''s the fact that you use hda on both domU config file and > fstab. It was deprecated a long time ago, and using it may lead to > confusion as newer kernels will silently rename it to xvda or xvde.I also changed hda1 respectively hda2 in /etc/xen/xen1.conf and fstab on the domu into xvda1 and xvda2.> There might be other problems, but start with those two.As I said domu is accessible but... I foudn several mount problems and the last line before ash-shell starts is "/bin/sh: can''t access tty; job control turned off". I''m looking forward hearing from you (if you still wish). Greetings from Hilden Stefan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Jul 4, 2011 at 3:30 AM, Stefan <hest@lavabit.com> wrote:> As I said domu is accessible but... I foudn several mount problems andwhat problems?> the last line before ash-shell starts is "/bin/sh: can''t access tty; job > control turned off".Full boot log might help find out what''s wrong. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Fajar, Hello List,>> As I said domu is accessible but... I foudn several mount problems >> and > > what problems?It seems to me that Dom0 is not handing over /dev/xvda1 and /dev/xvda2 to DomU. Root (on /dev/xvda1) is not accessible... This is the output on the screen: -------------- Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/xvda1 does not exist. Dropping to a shell! BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash) Enter ''help'' for a list of built-in commands. /bin/sh: can''t access tty; job control turned off (initramfs) --------------> Full boot log might help find out what''s wrong.Attached the dmesg of the DomU and again fstab (of DomU) and xen.conf. Many thanks in advance for your kind help! Regards Stefan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Jul 8, 2011 at 9:56 PM, Stefan <hest@lavabit.com> wrote:> Hello Fajar, > Hello List, > >>> As I said domu is accessible but... I foudn several mount problems >> and >> >> what problems? > > It seems to me that Dom0 is not handing over /dev/xvda1 and /dev/xvda2 > to DomU. Root (on /dev/xvda1) is not accessible... >This might be the cause disk = [ ''phy:/dev/mapper/data-xen1,/dev/xvda1,w'', ''phy:/dev/mapper/data-xen1_swap,/dev/xvda2,w'' ] try disk = [ ''phy:/dev/mapper/data-xen1,xvda1,w'', ''phy:/dev/mapper/data-xen1_swap,xvda2,w'' ]> This is the output on the screen: > -------------- > Gave up waiting for root device. Common problems: > - Boot args (cat /proc/cmdline) > - Check rootdelay= (did the system wait long enough?) > - Check root= (did the system wait for the right device?) > - Missing modules (cat /proc/modules; ls /dev) > ALERT! /dev/xvda1 does not exist. Dropping to a shell! > > > BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash) > Enter ''help'' for a list of built-in commands. > > /bin/sh: can''t access tty; job control turned off > (initramfs) > -------------- > >> Full boot log might help find out what''s wrong. > > Attached the dmesg of the DomU and again fstab (of DomU) and xen.conf.You''re attaching "xm dmesg". Not needed in this case. What''s needed is full log of domU during boot, which you do NOT attach. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello!> This might be the cause > > disk = [ ''phy:/dev/mapper/data-xen1,/dev/xvda1,w'', > ''phy:/dev/mapper/data-xen1_swap,/dev/xvda2,w'' ] > > try > > disk = [ ''phy:/dev/mapper/data-xen1,xvda1,w'', > ''phy:/dev/mapper/data-xen1_swap,xvda2,w'' ]I already tried with /dev/... or without /dev/... on disk and root but it doesn''t changed anything.> You''re attaching "xm dmesg". Not needed in this case. What''s needed is > full log of domU during boot, which you do NOT attach.I got mad on this and wipe everything of the HDD and tried again from the beginning with another tutorial... now it''s working! Most probably the old installation had a SCSI problem? Stefan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Reasonably Related Threads
- pygrub error booting iso
- domU startup freezes at "Starting plymouth"
- Disk add fails while domain creation, which uses disk backend- "storage driver domain" with xen-4.3.0 , with errors libxl.c:2125
- Disk add fails while domain creation, which uses disk backend- "storage driver domain" with xen-4.3.0 , with errors libxl.c:2125
- Can''t find root when start vm