Suse 10.1 AMD64 Xen3 New to Xen. The dom0 is up and running. I am trying to get my first domU working. My approach is to use precompiled images from jailtime.org. After some manual tinkering with the .cfg file the domU proceeds to boot but stalls with the following error. I cannot get past this - any ideas ? Brian Using config file "/etc/xen/vm/vm1". Started domain vm1 Bootdata ok (command line is root=/dev/hda6 ro TERM=xterm) Linux version 2.6.16.13-4-xen (geeko@buildhost) (gcc version 4.1.0 (SUSE Linux)) #1 SMP Wed May 3 04:53:23 UTC 2006 No mptable found. Built 1 zonelists Kernel command line: root=/dev/hda6 ro TERM=xterm Initializing CPU#0 PID hash table entries: 2048 (order: 11, 65536 bytes) Xen reported: 1790.826 MHz processor. Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Software IO TLB disabled Memory: 246300k/270336k available (1846k kernel code, 23728k reserved, 780k data, 140k init) Calibrating delay using timer specific routine.. 4480.03 BogoMIPS (lpj=8960079) Security Framework v1.0.0 initialized Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) checking if image is initramfs... it is Freeing initrd memory: 6312k freed Brought up 1 CPUs migration_cost=0 DMI not present or invalid. Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Subsystem revision 20060127 ACPI: Interpreter disabled. xen_mem: Initialising balloon driver. PCI: System does not support PCI PCI: System does not support PCI TC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca) IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ audit: initializing netlink socket (disabled) audit(1151874627.793:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones i8042.c: No controller found. isa bounce pool size: 16 pages RAMDISK driver initialized: 16 RAM disks of 128000K size 1024 blocksize Xen virtual console successfully installed as tty1 Event-channel device installed. mice: PS/2 mouse device common for all mice input: PC Speaker as /class/input/input0 md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 3, 32768 bytes) TCP established hash table entries: 16384 (order: 6, 262144 bytes) TCP bind hash table entries: 16384 (order: 6, 262144 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered NET: Registered protocol family 1 XENBUS: Timeout connecting to devices! Write protecting the kernel read-only data: 328k Starting udevd Creating devices Loading xennet netfront: Initialising virtual ethernet driver. Loading xenblk Registering block device major 3 Loading reiserfs Waiting for device /dev/hda6 to appear: ..............................not found -- exiting to /bin/sh ------------------------------------ My config file isk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,hda7,w'' ] memory = 256 vcpus = 1 builder = ''linux'' name = ''vm1'' vif = [ ''mac=00:16:3e:01:fa:c9'' ] localtime = 0 on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' extra = ''TERM=xterm'' kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root = "/dev/hda6 ro" ------------------------------------ File system Filesystem Size Used Avail Use% Mounted on /dev/hda6 7.0G 6.2G 805M 89% / udev 437M 220K 437M 1% /dev /dev/hda7 11G 4.0G 6.3G 39% /home /dev/hda1 20G 17G 2.3G 89% /mnt/data1 -- Powered by Suse Linux 9.2 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon July 3 2006 19:20, Brian wrote: [snip]> Kernel command line: root=/dev/hda6 ro TERM=xterm> Waiting for device /dev/hda6 to appear: > ..............................not found -- exiting to /bin/sh > > ------------------------------------ > My config file > > isk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,hda7,w'' ]the "hda7" might be at fault... [assuming the missing ''d'' is a cut/paste issue...] jerry _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Jul 03, 2006 at 08:00:15PM -0500, Jerry Amundson wrote:> On Mon July 3 2006 19:20, Brian wrote: > [snip] > > Kernel command line: root=/dev/hda6 ro TERM=xterm > > > Waiting for device /dev/hda6 to appear: > > ..............................not found -- exiting to /bin/sh > > > > ------------------------------------ > > My config file > > > > isk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,hda7,w'' ] > > the "hda7" might be at fault... > [assuming the missing ''d'' is a cut/paste issue...] > > jerryHmmm, not sure what is going on. tried altering that line. It is a new install of Suse 10.1. Brian netfront: Initialising virtual ethernet driver. Loading xenblk Registering block device major 3 hda:Loading reiserfs Waiting for device /dev/hda6 to appear: unknown partition table ata_id[459]: main: HDIO_GET_IDENTITY failed for ''/dev/.tmp-3-0'' ..............................not found -- exiting to /bin/sh $ +++Grub config++++ ###Don''t change this comment - YaST2 identifier: Original name: xen### title XEN root (hd0,5) kernel /boot/xen.gz module /boot/vmlinuz-xen root=/dev/hda6 vga=0x31a resume=/dev/hda5 splash=silent showopts module /boot/initrd-xen> > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Powered by Suse Linux 9.2 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Are you certain that shoudn''t be a ''sda'' not ''hda'' ? (Are you using SATA drives?) Try altering the line to read: disk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,sda1,w'' ] And likewise edit : root=/dev/hda6 ro to root=/dev/sda1 ro and see what happens. You may also consider giving the dom-u some swap space :) But that''s some fun for after you get it to boot. HTH Tim On Tue, 2006-07-04 at 11:01 +0930, Brian wrote:> On Mon, Jul 03, 2006 at 08:00:15PM -0500, Jerry Amundson wrote: > > On Mon July 3 2006 19:20, Brian wrote: > > [snip] > > > Kernel command line: root=/dev/hda6 ro TERM=xterm > > > > > Waiting for device /dev/hda6 to appear: > > > ..............................not found -- exiting to /bin/sh > > > > > > ------------------------------------ > > > My config file > > > > > > isk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,hda7,w'' ] > > > > the "hda7" might be at fault... > > [assuming the missing ''d'' is a cut/paste issue...] > > > > jerry > > Hmmm, not sure what is going on. tried altering that line. > It is a new install of Suse 10.1. > Brian > > netfront: Initialising virtual ethernet driver. > Loading xenblk > Registering block device major 3 > hda:Loading reiserfs > Waiting for device /dev/hda6 to appear: unknown partition table > ata_id[459]: main: HDIO_GET_IDENTITY failed for ''/dev/.tmp-3-0'' > ..............................not found -- exiting to /bin/sh > $ > > +++Grub config++++ > > ###Don''t change this comment - YaST2 identifier: Original name: xen### > title XEN > root (hd0,5) > kernel /boot/xen.gz > module /boot/vmlinuz-xen root=/dev/hda6 vga=0x31a resume=/dev/hda5 > splash=silent showopts > module /boot/initrd-xen > > > > > > > > _______________________________________________ > > 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, Jul 04, 2006 at 09:44:37AM +0800, Tim Post wrote:> Are you certain that shoudn''t be a ''sda'' not ''hda'' ? (Are you using > SATA drives?) > > Try altering the line to read: > > disk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,sda1,w'' ] > > And likewise edit : > > root=/dev/hda6 ro to root=/dev/sda1 ro > > and see what happens. You may also consider giving the dom-u some swap > space :) But that''s some fun for after you get it to boot. >I checked. It is an ata device. Checked the partition table. Any idea what a W95 Ext''d partition is ? This is a Suse 10.1 system. Brian Disk /dev/hda: 40.0 GB, 40020664320 bytes 255 heads, 63 sectors/track, 4865 cylinders, total 78165360 sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System /dev/hda1 63 41013944 20506941 83 Linux /dev/hda2 * 41013945 78156224 18571140 f W95 Ext''d (LBA) /dev/hda5 41014008 42363404 674698+ 82 Linux swap / Solaris /dev/hda6 42363468 56837969 7237251 83 Linux /dev/hda7 56838033 78156224 10659096 83 Linux Also fstab dev/hda6 / reiserfs acl,user_xattr /dev/hda7 /home reiserfs acl,user_xattr /dev/hda5 swap swap defaults proc /proc proc defaults sysfs /sys sysfs noauto debugfs /sys/kernel/debug debugfs noauto usbfs /proc/bus/usb usbfs noauto devpts /dev/pts devpts mode=0620,gid=5 /dev/hda1 /mnt/data1 auto noauto,user> HTH > > Tim > > On Tue, 2006-07-04 at 11:01 +0930, Brian wrote: > > On Mon, Jul 03, 2006 at 08:00:15PM -0500, Jerry Amundson wrote: > > > On Mon July 3 2006 19:20, Brian wrote: > > > [snip] > > > > Kernel command line: root=/dev/hda6 ro TERM=xterm > > > > > > > Waiting for device /dev/hda6 to appear: > > > > ..............................not found -- exiting to /bin/sh > > > > > > > > ------------------------------------ > > > > My config file > > > > > > > > isk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,hda7,w'' ] > > > > > > the "hda7" might be at fault... > > > [assuming the missing ''d'' is a cut/paste issue...] > > > > > > jerry > > > > Hmmm, not sure what is going on. tried altering that line. > > It is a new install of Suse 10.1. > > Brian > > > > netfront: Initialising virtual ethernet driver. > > Loading xenblk > > Registering block device major 3 > > hda:Loading reiserfs > > Waiting for device /dev/hda6 to appear: unknown partition table > > ata_id[459]: main: HDIO_GET_IDENTITY failed for ''/dev/.tmp-3-0'' > > ..............................not found -- exiting to /bin/sh > > $ > > > > +++Grub config++++ > > > > ###Don''t change this comment - YaST2 identifier: Original name: xen### > > title XEN > > root (hd0,5) > > kernel /boot/xen.gz > > module /boot/vmlinuz-xen root=/dev/hda6 vga=0x31a resume=/dev/hda5 > > splash=silent showopts > > module /boot/initrd-xen > > > > > > > > > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > >-- Powered by Suse Linux 9.2 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue July 4 2006 05:06, Brian wrote:> On Tue, Jul 04, 2006 at 09:44:37AM +0800, Tim Post wrote: > > Are you certain that shoudn''t be a ''sda'' not ''hda'' ? (Are you > > using SATA drives?) > > > > Try altering the line to read: > > > > disk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,sda1,w'' ] > > > > And likewise edit : > > > > root=/dev/hda6 ro to root=/dev/sda1 ro > > > > and see what happens. You may also consider giving the dom-u some > > swap space :) But that''s some fun for after you get it to boot. > > I checked. It is an ata device. Checked the partition table. Any idea > what a W95 Ext''d partition is ? This is a Suse 10.1 system. > BrianDid to make the suggested changes and try it? The W95 Ext''d is just a sort of place holder for the higher partitions after it.> Disk /dev/hda: 40.0 GB, 40020664320 bytes > 255 heads, 63 sectors/track, 4865 cylinders, total 78165360 sectors > Units = sectors of 1 * 512 = 512 bytes > > Device Boot Start End Blocks Id System > /dev/hda1 63 41013944 20506941 83 Linux > /dev/hda2 * 41013945 78156224 18571140 f W95 Ext''d > (LBA) /dev/hda5 41014008 42363404 674698+ 82 Linux > swap / Solaris /dev/hda6 42363468 56837969 7237251 83 > Linux /dev/hda7 56838033 78156224 10659096 83 Linux > > Also fstab > > dev/hda6 / reiserfs acl,user_xattr > /dev/hda7 /home reiserfs acl,user_xattr > /dev/hda5 swap swap defaults > proc /proc proc defaults > sysfs /sys sysfs noauto > debugfs /sys/kernel/debug debugfs noauto > usbfs /proc/bus/usb usbfs noauto > devpts /dev/pts devpts mode=0620,gid=5 > /dev/hda1 /mnt/data1 auto noauto,userThose are from dom0 - the domU has no concept of any of it... jerry _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jul 04, 2006 at 09:44:37AM +0800, Tim Post wrote:> Are you certain that shoudn''t be a ''sda'' not ''hda'' ? (Are you using > SATA drives?) > > Try altering the line to read: > > disk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,sda1,w'' ] > > And likewise edit : > > root=/dev/hda6 ro to root=/dev/sda1 ro >Ok, the log now shows tarting udevd Creating devices Loading xennet netfront: Initialising virtual ethernet driver. Loading xenblk Registering block device major 8 Loading reiserfs Waiting for device /dev/sda6 to appear: ok rootfs: major=8 minor=6 devn=2054 Mounting root /dev/sda6 mount: unknown filesystem type ''ext3'' umount: /dev: device is busy umount: /dev: device is busy Kernel panic - not syncing: Attempted to kill init! _____________________________________________ The vm1 config file is now disk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,sda6,w'' ] memory = 256 vcpus = 1 builder = ''linux'' name = ''vm1'' vif = [ ''mac=00:16:3e:01:fa:c9'' ] localtime = 0 on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' extra = ''TERM=xterm'' kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root = "/dev/sda6 ro" ______________________________________ According to df -h the home partition is hda7. When I change the line disk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,sda7,w'' ] the system reverts to the old problem .....waiting for hda6 to appear. Brian - Powered by Suse Linux 9.2 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Brian, Why are you setting the root device in the dom-u to be /dev/sda6 ? Your dom-u has no such partition specified to be created in the config. Since you are using ATA drives, you are correct that it should be ''hda'' and not ''sda''. Change all instances of ''hda6'' to ''hda1'' in your configuration file and all should be well. You are specifying how the dom-u deals with your gentoo image file when making it into a drive. (what disk it becomes on the dom-u side), this has absolutely nothing to do with dom-0. In other words, this line : disk = [ ''file:/home/poncho/gentoo/gentoo.2006-1.img,hda1,w'' ] Is telling the dom-u to mount that image as its own hda1. root=/dev/hda1 ro is telling it that the newly created hda1 should also be the root file system, initially read only (as any Linux system would boot ..), then remount as read-write once init starts. I can''t help you further with this issue unless you make these corrections first :) Again, completely forget hda6. You''re also still missing a swap file system, which I really recommend due to the amount of RAM you''ve allocated the dom-u or you''ll be back shortly wondering about malloc() error messages ;) Thanks Tim On Wed, 2006-07-05 at 09:48 +0930, Brian wrote:> On Tue, Jul 04, 2006 at 09:44:37AM +0800, Tim Post wrote: > > Are you certain that shoudn''t be a ''sda'' not ''hda'' ? (Are you using > > SATA drives?) > > > > Try altering the line to read: > > > > disk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,sda1,w'' ] > > > > And likewise edit : > > > > root=/dev/hda6 ro to root=/dev/sda1 ro > > > > Ok, the log now shows > > tarting udevd > Creating devices > Loading xennet > netfront: Initialising virtual ethernet driver. > Loading xenblk > Registering block device major 8 > Loading reiserfs > Waiting for device /dev/sda6 to appear: ok > rootfs: major=8 minor=6 devn=2054 > Mounting root /dev/sda6 > mount: unknown filesystem type ''ext3'' > umount: /dev: device is busy > umount: /dev: device is busy > Kernel panic - not syncing: Attempted to kill init! > > _____________________________________________ > > The vm1 config file is now > > disk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,sda6,w'' ] > memory = 256 > vcpus = 1 > builder = ''linux'' > name = ''vm1'' > vif = [ ''mac=00:16:3e:01:fa:c9'' ] > localtime = 0 > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > extra = ''TERM=xterm'' > kernel = "/boot/vmlinuz-xen" > ramdisk = "/boot/initrd-xen" > root = "/dev/sda6 ro" > > ______________________________________ > > According to df -h the home partition is hda7. When I change the line > disk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,sda7,w'' ] > the system reverts to the old problem .....waiting for hda6 to appear. > > Brian > - > Powered by Suse Linux 9.2 > > > _______________________________________________ > 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
Tim, many thanks. Slowly getting the message. Your explanation has been helpful. Brian On Wed, Jul 05, 2006 at 09:29:12AM +0800, Tim Post wrote:> Brian, > > Why are you setting the root device in the dom-u to be /dev/sda6 ? Your > dom-u has no such partition specified to be created in the config. > > Since you are using ATA drives, you are correct that it should be ''hda'' > and not ''sda''. > > Change all instances of ''hda6'' to ''hda1'' in your configuration file and > all should be well. You are specifying how the dom-u deals with your > gentoo image file when making it into a drive. (what disk it becomes on > the dom-u side), this has absolutely nothing to do with dom-0.Ok. My config file disk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,hda1,w'' ] memory = 256 vcpus = 1 builder = ''linux'' name = ''vm1'' vif = [ ''mac=00:16:3e:01:fa:c9'' ] localtime = 0 on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' extra = ''TERM=xterm'' kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root = "/dev/hda1 ro" Log indicates part success etfront: Initialising virtual ethernet driver. Loading xenblk Registering block device major 3 Loading reiserfs Waiting for device /dev/hda1 to appear: ok rootfs: major=3 minor=1 devn=769 Mounting root /dev/hda1 mount: unknown filesystem type ''ext3'' umount: /dev: device is busy umount: /dev: device is busy Kernel panic - not syncing: Attempted to kill init! ------------------------------------------> In other words, this line : > > disk = [ ''file:/home/poncho/gentoo/gentoo.2006-1.img,hda1,w'' ] > > Is telling the dom-u to mount that image as its own hda1.Ok,> > root=/dev/hda1 ro is telling it that the newly created hda1 should also > be the root file system, initially read only (as any Linux system would > boot ..), then remount as read-write once init starts. > > I can''t help you further with this issue unless you make these > corrections first :) Again, completely forget hda6.Yes, thanks for trying to point this out.> > You''re also still missing a swap file system, which I really recommend > due to the amount of RAM you''ve allocated the dom-u or you''ll be back > shortly wondering about malloc() error messages ;)A swap file came with the gentoo.img. It is in the same directory at the moment.> > Thanks > TimHe looks to the sky ;) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Brian - This looks like the issue : mount: unknown filesystem type ''ext3'' What does /etc/fstab in the dom-u''s image itself tell you? You may need to mount it as a loop device on dom-0 first. Make sure the dom-u is not running or idle in error when you do this (on dom-0) mkdir /testing mount -o loop /home/poncho/gentoo/gentoo.2006-0.img /testing cat /testing/etc/fstab Need to be sure its not conflicting. I''m not sure how the image you downloaded is setup by default. I use provisioning scripts on dom-0 to make /etc/passwd fstab (and other things specific to each dom-u) from templates when I make them. You can also try just nulling /etc/fstab on the dom-u and rebooting, but keep a copy, i.e. (while still mounted) cp /testing/etc/fstab /testing/etc/fstab.backup cat /dev/null > /testing/etc/fstab Then unmount your local mount of the filesystem (make sure first you aren''t in /testing or you''ll get a device busy error) umount /testing Then try again. I''m sure this is something very trivial. HTH Tim On Wed, 2006-07-05 at 12:14 +0930, Brian wrote:> Tim, many thanks. Slowly getting the message. Your explanation has been > helpful. > Brian > > On Wed, Jul 05, 2006 at 09:29:12AM +0800, Tim Post wrote: > > Brian, > > > > Why are you setting the root device in the dom-u to be /dev/sda6 ? Your > > dom-u has no such partition specified to be created in the config. > > > > Since you are using ATA drives, you are correct that it should be ''hda'' > > and not ''sda''. > > > > Change all instances of ''hda6'' to ''hda1'' in your configuration file and > > all should be well. You are specifying how the dom-u deals with your > > gentoo image file when making it into a drive. (what disk it becomes on > > the dom-u side), this has absolutely nothing to do with dom-0. > > Ok. > > My config file > > disk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,hda1,w'' ] > memory = 256 > vcpus = 1 > builder = ''linux'' > name = ''vm1'' > vif = [ ''mac=00:16:3e:01:fa:c9'' ] > localtime = 0 > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > extra = ''TERM=xterm'' > kernel = "/boot/vmlinuz-xen" > ramdisk = "/boot/initrd-xen" > root = "/dev/hda1 ro" > > > Log indicates part success > > etfront: Initialising virtual ethernet driver. > Loading xenblk > Registering block device major 3 > Loading reiserfs > Waiting for device /dev/hda1 to appear: ok > rootfs: major=3 minor=1 devn=769 > Mounting root /dev/hda1 > mount: unknown filesystem type ''ext3'' > umount: /dev: device is busy > umount: /dev: device is busy > Kernel panic - not syncing: Attempted to kill init! > > ------------------------------------------ > > In other words, this line : > > > > disk = [ ''file:/home/poncho/gentoo/gentoo.2006-1.img,hda1,w'' ] > > > > Is telling the dom-u to mount that image as its own hda1. > > Ok, > > > > root=/dev/hda1 ro is telling it that the newly created hda1 should also > > be the root file system, initially read only (as any Linux system would > > boot ..), then remount as read-write once init starts. > > > > I can''t help you further with this issue unless you make these > > corrections first :) Again, completely forget hda6. > > Yes, thanks for trying to point this out. > > > > You''re also still missing a swap file system, which I really recommend > > due to the amount of RAM you''ve allocated the dom-u or you''ll be back > > shortly wondering about malloc() error messages ;) > > A swap file came with the gentoo.img. It is in the same directory at the > moment. > > > > Thanks > > Tim > > He looks to the sky ;) > > _______________________________________________ > 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
Brian, also thought about something I usually take for granted after I pushed send - the kernel you''re using to boot the dom-u was compiled with ext3 support, yes? On Wed, 2006-07-05 at 12:14 +0930, Brian wrote:> Tim, many thanks. Slowly getting the message. Your explanation has been > helpful. > Brian > > On Wed, Jul 05, 2006 at 09:29:12AM +0800, Tim Post wrote: > > Brian, > > > > Why are you setting the root device in the dom-u to be /dev/sda6 ? Your > > dom-u has no such partition specified to be created in the config. > > > > Since you are using ATA drives, you are correct that it should be ''hda'' > > and not ''sda''. > > > > Change all instances of ''hda6'' to ''hda1'' in your configuration file and > > all should be well. You are specifying how the dom-u deals with your > > gentoo image file when making it into a drive. (what disk it becomes on > > the dom-u side), this has absolutely nothing to do with dom-0. > > Ok. > > My config file > > disk = [ ''file:/home/poncho/gentoo/gentoo.2006-0.img,hda1,w'' ] > memory = 256 > vcpus = 1 > builder = ''linux'' > name = ''vm1'' > vif = [ ''mac=00:16:3e:01:fa:c9'' ] > localtime = 0 > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > extra = ''TERM=xterm'' > kernel = "/boot/vmlinuz-xen" > ramdisk = "/boot/initrd-xen" > root = "/dev/hda1 ro" > > > Log indicates part success > > etfront: Initialising virtual ethernet driver. > Loading xenblk > Registering block device major 3 > Loading reiserfs > Waiting for device /dev/hda1 to appear: ok > rootfs: major=3 minor=1 devn=769 > Mounting root /dev/hda1 > mount: unknown filesystem type ''ext3'' > umount: /dev: device is busy > umount: /dev: device is busy > Kernel panic - not syncing: Attempted to kill init! > > ------------------------------------------ > > In other words, this line : > > > > disk = [ ''file:/home/poncho/gentoo/gentoo.2006-1.img,hda1,w'' ] > > > > Is telling the dom-u to mount that image as its own hda1. > > Ok, > > > > root=/dev/hda1 ro is telling it that the newly created hda1 should also > > be the root file system, initially read only (as any Linux system would > > boot ..), then remount as read-write once init starts. > > > > I can''t help you further with this issue unless you make these > > corrections first :) Again, completely forget hda6. > > Yes, thanks for trying to point this out. > > > > You''re also still missing a swap file system, which I really recommend > > due to the amount of RAM you''ve allocated the dom-u or you''ll be back > > shortly wondering about malloc() error messages ;) > > A swap file came with the gentoo.img. It is in the same directory at the > moment. > > > > Thanks > > Tim > > He looks to the sky ;) > > _______________________________________________ > 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 Wed, Jul 05, 2006 at 11:25:12AM +0800, Tim Post wrote:> Brian, also thought about something I usually take for granted after I > pushed send - the kernel you''re using to boot the dom-u was compiled > with ext3 support, yes?>From my checks (had to search for the Xen kernel sources) yes it isinstalled as a module. I wonder if the xen initrd needs to have ext3 available as a module. Still going on this... Brian> > etfront: Initialising virtual ethernet driver. > > Loading xenblk > > Registering block device major 3 > > Loading reiserfs > > Waiting for device /dev/hda1 to appear: ok > > rootfs: major=3 minor=1 devn=769 > > Mounting root /dev/hda1 > > mount: unknown filesystem type ''ext3'' > > umount: /dev: device is busy > > umount: /dev: device is busy > > Kernel panic - not syncing: Attempted to kill init! > > > > ------------------------------------------ > > > In other words, this line : > > > > > > disk = [ ''file:/home/poncho/gentoo/gentoo.2006-1.img,hda1,w'' ] > > > > > > Is telling the dom-u to mount that image as its own hda1. > > > > Ok, > > > > > > root=/dev/hda1 ro is telling it that the newly created hda1 should also > > > be the root file system, initially read only (as any Linux system would > > > boot ..), then remount as read-write once init starts. > > > > > > I can''t help you further with this issue unless you make these > > > corrections first :) Again, completely forget hda6. > > > > Yes, thanks for trying to point this out. > > > > > > You''re also still missing a swap file system, which I really recommend > > > due to the amount of RAM you''ve allocated the dom-u or you''ll be back > > > shortly wondering about malloc() error messages ;) > > > > A swap file came with the gentoo.img. It is in the same directory at the > > moment. > > > > > > Thanks > > > Tim > > > > He looks to the sky ;) > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > >-- Powered by Suse Linux 9.2 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Jul 05, 2006 at 06:06:01PM +0930, Brian wrote:> On Wed, Jul 05, 2006 at 11:25:12AM +0800, Tim Post wrote: > > Brian, also thought about something I usually take for granted after I > > pushed send - the kernel you''re using to boot the dom-u was compiled > > with ext3 support, yes? >Suse 10.1 box Yay ! the Fedora5 image from jailtime.org has booted. Short version, I had to run mkinitrd with ext3 support. Some issues remain - especially the failure to load modules - see below log - and networking is not fully functional. Brian Long post ahead if you are interested My config disk = [ ''file:/etc/xen/fedora/fedora.fc5.img,hda1,w'' , ''file:/etc/xen/fedora/fedora.swap,hda2,w'' ] memory = 256 vcpus = 1 builder = ''linux'' name = ''vm2'' vif = [ ''mac=00:16:3e:34:8f:88'' ] localtime = 0 on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' extra = '' TERM=xterm'' #bootloader = ''/usr/lib/xen/boot/domUloader.py'' #bootentry = ''hda6:/boot/vmlinuz-xen, /boot/initrd-xen'' kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root = "/dev/hda1 ro" In an earlier post you can see boot complains about ext3 when trying to read the fedora5 image file. I needed to include this in the initrd tv:/home/poncho # mkinitrd -m ext3 -k vmlinuz-xen -i initrd-xen Root device: /dev/hda6 (mounted on / as reiserfs) Module list: ext3 (xennet xenblk) Kernel image: /boot/vmlinuz-xen Initrd image: /boot/initrd-xen Shared libs: lib64/ld-2.4.so lib64/libacl.so.1.1.0 lib64/libattr.so.1.1.0 lib64/libc-2.4.so lib64/libdl-2 .4.so lib64/libhistory.so.5.1 lib64/libncurses.so.5.5 lib64/libpthread-2.4.so lib64/libreadline.so.5.1 lib64 /librt-2.4.so lib64/libuuid.so.1.2 Driver modules: ide-core ide-disk scsi_mod sd_mod libata sata_sil atiixp Xen domU modules: xennet xenblk Filesystem modules: jbd ext3 Including: initramfs fsck.reiserfs No bootsplash for kernel flavor xen 12473 blocks +++++++++++++++++++++++++++++++++++++++ The startup log tv:/home/poncho # xm create vm2 -c Using config file "/etc/xen/vm/vm2". Started domain vm2 Bootdata ok (command line is root=/dev/hda1 ro TERM=xterm) Linux version 2.6.16.13-4-xen (geeko@buildhost) (gcc version 4.1.0 (SUSE Linux)) #1 SMP Wed May 3 04:53:23 UTC 2006 No mptable found. Built 1 zonelists Kernel command line: root=/dev/hda1 ro TERM=xterm Initializing CPU#0 PID hash table entries: 2048 (order: 11, 65536 bytes) Xen reported: 1790.825 MHz processor. Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Software IO TLB disabled Memory: 246360k/270336k available (1846k kernel code, 23656k reserved, 780k data, 140k init) Calibrating delay using timer specific routine.. 4479.95 BogoMIPS (lpj=8959905) Security Framework v1.0.0 initialized Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) checking if image is initramfs... it is Freeing initrd memory: 6236k freed Brought up 1 CPUs migration_cost=0 DMI not present or invalid. Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Subsystem revision 20060127 ACPI: Interpreter disabled. xen_mem: Initialising balloon driver. PCI: System does not support PCI PCI: System does not support PCI TC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca) IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ audit: initializing netlink socket (disabled) audit(1153177567.636:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones i8042.c: No controller found. isa bounce pool size: 16 pages RAMDISK driver initialized: 16 RAM disks of 128000K size 1024 blocksize Xen virtual console successfully installed as tty1 Event-channel device installed. mice: PS/2 mouse device common for all mice input: PC Speaker as /class/input/input0 md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 3, 32768 bytes) TCP established hash table entries: 16384 (order: 6, 262144 bytes) TCP bind hash table entries: 16384 (order: 6, 262144 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered NET: Registered protocol family 1 XENBUS: Timeout connecting to devices! Write protecting the kernel read-only data: 328k Starting udevd Creating devices Loading xennet netfront: Initialising virtual ethernet driver. Loading xenblk Registering block device major 3 Loading jbd Loading ext3 Waiting for device /dev/hda1 to appear: ok rootfs: major=3 minor=1 devn=769 Mounting root /dev/hda1 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. modprobe: FATAL: Could not load /lib/modules/2.6.16.13-4-xen/modules.dep: No such file or directory INIT: version 2.86 booting Welcome to Fedora Core Press ''I'' to enter interactive startup. Setting clock : Mon Jul 17 19:06:19 EDT 2006 [ OK ] Setting hostname fc5_pristine: [ OK ] Checking filesystems [ OK ] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling swap space: [ OK ] modprobe: FATAL: Could not load /lib/modules/2.6.16.13-4-xen/modules.dep: No such file or directory INIT: Entering runlevel: 3 Entering non-interactive startup Bringing up loopback interface: modprobe: FATAL: Could not load /lib/modules/2.6.16.13-4-xen/modules.dep: No such file or directory arping: socket: Address family not supported by protocol [ OK ] Bringing up interface eth0: Determining IP information for eth0...modprobe: FATAL: Could not load /lib/modules/2.6.16.13-4-xen/modules.dep: No such file or directory failed. [FAILED] Starting system logger: [ OK ] Starting kernel logger: [ OK ] Starting sshd: [ OK ] Fedora Core release 5 (Bordeaux) Kernel 2.6.16.13-4-xen on an x86_64 fc5_pristine login: root Password: ============================================================= Here you will see the Networking and modules -- parts are missing. root@fc5_pristine /]# lsmod Module Size Used by ext3 138000 1 jbd 72128 1 ext3 xenblk 20896 1 xennet 25472 0 ============================================= [root@fc5_pristine /]# ifconfig eth0 Link encap:Ethernet HWaddr 00:16:3E:34:8F:88 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:37 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11886 (11.6 KiB) TX bytes:0 (0.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:288 (288.0 b) TX bytes:288 (288.0 b) ================================================== [root@fc5_pristine /]# ping 192.168.1.80 connect: Network is unreachable =================================================== -- Powered by Suse Linux 9.2 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I am trying to get "Windows Server 2003 Enterprise x64 Edition" to install as an HVM. It gets as far as booting but then complains that I have no APIC. /proc/cpuinfo on the Dom0 says I have apic. My config file has a line apic = 1 Any ideas as to what else is required. System SuSE 10.1 (boxed). Xen as supplied. Geoff _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Geoff Streeter wrote:> I am trying to get "Windows Server 2003 Enterprise x64 Edition" to > install as an HVM. It gets as far as booting but then complains that I > have no APIC. > > /proc/cpuinfo on the Dom0 says I have apic. My config file has a line > apic = 1 > > Any ideas as to what else is required. > > System SuSE 10.1 (boxed). Xen as supplied. > > Geoff >why not do what the xen manual suggests: set apic=0 ? Greetz, Andrej _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
At 2006-07-18 18:19 +0200, Andrej Radonic wrote:>Geoff Streeter wrote: >>I am trying to get "Windows Server 2003 Enterprise x64 Edition" to >>install as an HVM. It gets as far as booting but then complains that I >>have no APIC. >> >>/proc/cpuinfo on the Dom0 says I have apic. My config file has a line >>apic = 1 >> >>Any ideas as to what else is required. >> >>System SuSE 10.1 (boxed). Xen as supplied. >> >>Geoff >why not do what the xen manual suggests: set apic=0 >? >Greetz, >AndrejThat was the default, and I used it first. I set "apic = 1" after I first got the message during boot of Windows Server install. Setting "apic = 0" produces exactly the same message from windows. Incidentally, it says "the operating system you are loading does not have APIC enabled" ... Is there a choice as to wether it is a firmware supplied service or an operating system supplied service? Geoff _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users