David F Barrera
2004-Dec-15 20:40 UTC
[Xen-devel] Kernel panic - not syncing: Attempted to kill init!
I am trying to create an additional domain and have created a configuration file based on the examples. When I try to boot the domain, it eventually hits a Kernel panic, as follows: Red Hat nash version 4.1.18 starting Mounted /proc filesystem Mounting sysfs Creating /dev Starting udev Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! <0>Rebooting in 1 seconds.. ----------------------------------- I have tried using an initrd file, but it makes no difference. Any ideas or suggestions will be greatly appreciated! David Barrera ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Derrik Pates
2004-Dec-16 00:07 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
David F Barrera wrote:> I am trying to create an additional domain and have created a > configuration file based on the examples. When I try to boot the > domain, it eventually hits a Kernel panic, as follows: > > Red Hat nash version 4.1.18 starting > Mounted /proc filesystem > Mounting sysfs > Creating /dev > Starting udev > Creating root device > Mounting root filesystem > mount: error 6 mounting ext3 > mount: error 2 mounting none > Switching to new root > switchroot: mount failed: 22 > umount /initrd/dev failed: 2 > Kernel panic - not syncing: Attempted to kill init! > <0>Rebooting in 1 seconds.. > -----------------------------------Which RH flavor is this? I''ve so far had Fedora Core 2 and 3, as well as CentOS, running happily inside a Xen domain. What does the fstab for the domain''s root FS look like? Also, what does your domain definition file look like? -- Derrik Pates dpates@dsdk12.net ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
David F Barrera
2004-Dec-16 14:41 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
Derrik, Thanks for your response. Of course I should have given more details! (my bad). The distro I am using is RHEL 4 Beta 2 (Red Hat Enterprise Linux Desktop release 3.90 (Nahant) >>What does the fstab for the domain''s root FS look like? /dev/hdc1 / ext2 defaults 1 1 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 LABEL=SWAP-hdc2 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed 0 0 /dev/fd0 /media/floppy auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0 >>Also, what does your domain definition file look like? #----------------------------------------------------------------------------START OF DEFINITION FILE # Kernel image file. kernel = "/boot/vmlinuz-2.6.9-xenU" # Optional ramdisk. ramdisk = "/boot/initrd-fc3.img" # The domain build function. Default is ''linux''. builder=''linux'' # Initial memory allocation (in megabytes) for the new domain. memory = 64 # A name for your domain. All domains must have different names. name = "test1" # disk = [ ''phy:hda1,hda1,r'' ] disk = [ ''phy:hdc1,hdc1,r'' ] # Set if you want dhcp to allocate the IP address. dhcp="dhcp" # Set root device. root = "/dev/hdc1 ro" # Sets runlevel 4. extra = "4" #---------------------------------------------------------------------------- END OF DEFINITION FILE Derrik Pates wrote:> David F Barrera wrote: > >> I am trying to create an additional domain and have created a >> configuration file based on the examples. When I try to boot the >> domain, it eventually hits a Kernel panic, as follows: >> >> Red Hat nash version 4.1.18 starting >> Mounted /proc filesystem >> Mounting sysfs >> Creating /dev >> Starting udev >> Creating root device >> Mounting root filesystem >> mount: error 6 mounting ext3 >> mount: error 2 mounting none >> Switching to new root >> switchroot: mount failed: 22 >> umount /initrd/dev failed: 2 >> Kernel panic - not syncing: Attempted to kill init! >> <0>Rebooting in 1 seconds.. >> ----------------------------------- > > > Which RH flavor is this? I''ve so far had Fedora Core 2 and 3, as well > as CentOS, running happily inside a Xen domain. What does the fstab > for the domain''s root FS look like? Also, what does your domain > definition file look like? >------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Derrik Pates
2004-Dec-16 18:04 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
David F Barrera wrote:> The distro I am using is RHEL 4 Beta 2 (Red Hat Enterprise Linux > Desktop release 3.90 (Nahant)> /dev/hdc1 / ext2 defaults 1 1> LABEL=SWAP-hdc2 swap swap defaults 0 0 > /dev/hda /media/cdrom auto > pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed > 0 0> # disk = [ ''phy:hda1,hda1,r'' ] > disk = [ ''phy:hdc1,hdc1,r'' ]Well, the configuration of the virtual disk looks correct; the swap might disagree with it, but that shouldn''t appear until later in the boot process. Perhaps it''s an interaction with devfs? Do you have devfs enabled in your xenU (unprivileged domain) kernel? This gave me fits when I first began using Xen, mostly because it seems that the xenU prebuilt kernel that''s included with the binary pack has devfs support enabled, and this breaks things. The only other possibility I can think of is that you need to change the block-device import to read-write. -- Derrik Pates dpates@dsdk12.net ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
David F Barrera
2004-Dec-16 19:29 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
Derrik , Thanks for the feedback. Derrik Pates wrote:> David F Barrera wrote: > >> The distro I am using is RHEL 4 Beta 2 (Red Hat Enterprise Linux >> Desktop release 3.90 (Nahant) > > >> /dev/hdc1 / ext2 >> defaults 1 1 > > >> LABEL=SWAP-hdc2 swap swap >> defaults 0 0 >> /dev/hda /media/cdrom auto >> pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed >> 0 0 > > >> # disk = [ ''phy:hda1,hda1,r'' ] >> disk = [ ''phy:hdc1,hdc1,r'' ] > > > Well, the configuration of the virtual disk looks correct; the swap > might disagree with it, but that shouldn''t appear until later in the > boot process. Perhaps it''s an interaction with devfs? Do you have > devfs enabled in your xenU (unprivileged domain) kernel? This gave me > fits when I first began using Xen, mostly because it seems that the > xenU prebuilt kernel that''s included with the binary pack has devfs > support enabled, and this breaks things.I will try rebuilding the xenU kernel.> The only other possibility I can think of is that you need to change > the block-device import to read-write.I''ve already tried changing the block-device import to read-write. No difference. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
David F Barrera
2004-Dec-17 20:39 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
Derrick, I rebuilt the xenU kernel, with the devfs support disabled, and it makes no difference. It behaves in the same manner as the pre-built kernel that''s included with the binary pack. I am at a loss. I''ve been able to boot a kernel under xen on a SuSE Linux 9.0 machine, so I''ve had a little experience with this:-) Freeing unused kernel memory: 92k freed Red Hat nash version 4.1.18 starting Mounted /proc filesystem Mounting sysfs Creating /dev Starting udev Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! <0>Rebooting in 1 seconds.. David Barrera Derrik Pates wrote:> David F Barrera wrote: > >> The distro I am using is RHEL 4 Beta 2 (Red Hat Enterprise Linux >> Desktop release 3.90 (Nahant) > > >> /dev/hdc1 / ext2 >> defaults 1 1 > > >> LABEL=SWAP-hdc2 swap swap >> defaults 0 0 >> /dev/hda /media/cdrom auto >> pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed >> 0 0 > > >> # disk = [ ''phy:hda1,hda1,r'' ] >> disk = [ ''phy:hdc1,hdc1,r'' ] > > > Well, the configuration of the virtual disk looks correct; the swap > might disagree with it, but that shouldn''t appear until later in the > boot process. Perhaps it''s an interaction with devfs? Do you have > devfs enabled in your xenU (unprivileged domain) kernel? This gave me > fits when I first began using Xen, mostly because it seems that the > xenU prebuilt kernel that''s included with the binary pack has devfs > support enabled, and this breaks things. The only other possibility I > can think of is that you need to change the block-device import to > read-write. >------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Ian Pratt
2004-Dec-18 18:18 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
> Derrick, > > I rebuilt the xenU kernel, with the devfs support disabled, and it makes > no difference. It behaves in the same manner as the pre-built kernel > that''s included with the binary pack. I am at a loss. I''ve been able to > boot a kernel under xen on a SuSE Linux 9.0 machine, so I''ve had a > little experience with this:-)David, earlier in the boot messages do you see the hdc1 partition being found when the partition check happens? You''ll need to export the partition ''rw'' eventually, but that''s not your current problem. You might like to try exporting it as ''sda1'' or something to see if that helps. Not sure why it would, but I''ve heard folklore along these lines. Adding some more debugging to the linuxrc nash script might shed some light on the problem. Also, what happens if you skip the initrd and try booting directly off the disk. I doubt there''s anything in the initrd you need. Ian> Freeing unused kernel memory: 92k freed > Red Hat nash version 4.1.18 starting > Mounted /proc filesystem > Mounting sysfs > Creating /dev > Starting udev > Creating root device > Mounting root filesystem > mount: error 6 mounting ext3 > mount: error 2 mounting none > Switching to new root > switchroot: mount failed: 22 > umount /initrd/dev failed: 2 > Kernel panic - not syncing: Attempted to kill init! > <0>Rebooting in 1 seconds.. > > > David Barrera > > > Derrik Pates wrote: > > > David F Barrera wrote: > > > >> The distro I am using is RHEL 4 Beta 2 (Red Hat Enterprise Linux > >> Desktop release 3.90 (Nahant) > > > > > >> /dev/hdc1 / ext2 > >> defaults 1 1 > > > > > >> LABEL=SWAP-hdc2 swap swap > >> defaults 0 0 > >> /dev/hda /media/cdrom auto > >> pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed > >> 0 0 > > > > > >> # disk = [ ''phy:hda1,hda1,r'' ] > >> disk = [ ''phy:hdc1,hdc1,r'' ] > > > > > > Well, the configuration of the virtual disk looks correct; the swap > > might disagree with it, but that shouldn''t appear until later in the > > boot process. Perhaps it''s an interaction with devfs? Do you have > > devfs enabled in your xenU (unprivileged domain) kernel? This gave me > > fits when I first began using Xen, mostly because it seems that the > > xenU prebuilt kernel that''s included with the binary pack has devfs > > support enabled, and this breaks things. The only other possibility I > > can think of is that you need to change the block-device import to > > read-write. > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
David F Barrera
2004-Dec-20 16:08 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
Ian, Thanks for the reply and the suggestions. Some details about my setup: /dev/hdc3 is where xen0 is running /dev/hdc1 -- another partition that actually has a copy of RHEL 4 Beta 2 installed (working OS) /etc/fstab: # This file is edited by fstab-sync - see ''man fstab-sync'' for details /dev/hdc3 / ext2 defaults 1 1 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/hdc2 swap swap defaults 0 0 /dev/hda /media/cdrom auto pamconsole,ro,exec,noauto,managed 0 0 ~ The config file that I am using: # Kernel image file. kernel = "/boot/vmlinuz-2.6.9-xenU" # Optional ramdisk. ramdisk = "/boot/initrd-2.6.9-xenU.img" # The domain build function. Default is ''linux''. builder=''linux'' # Initial memory allocation (in megabytes) for the new domain. memory = 64 # A name for your domain. All domains must have different names. name = "test1" # disk = [ ''phy:hda1,hda1,r'' ] disk = [ ''phy:hdc1,hdc1,w'' ] # Set if you want dhcp to allocate the IP address. dhcp="dhcp" # Set root device. root = "/dev/hdc1 ro/" # Sets runlevel 4. extra = "4" #===========================================================================~ Ian Pratt wrote:>>Derrick, >> >>I rebuilt the xenU kernel, with the devfs support disabled, and it makes >>no difference. It behaves in the same manner as the pre-built kernel >>that''s included with the binary pack. I am at a loss. I''ve been able to >>boot a kernel under xen on a SuSE Linux 9.0 machine, so I''ve had a >>little experience with this:-) >> >> > >David, earlier in the boot messages do you see the hdc1 partition >being found when the partition check happens? > >This is the entire log: Linux version 2.6.9-xenU (root@dyn95394184.austin.ibm.com) (gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 Fri Dec 17 15:50:10 CST 2004 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000004000000 (usable) 64MB LOWMEM available. DMI not present. Built 1 zonelists Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/hdc1 ro/ 4 Initializing CPU#0 PID hash table entries: 512 (order: 9, 8192 bytes) Xen reported: 866.697 MHz processor. Using tsc for high-res timesource Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 61900k/65536k available (1569k kernel code, 3596k reserved, 429k data, 92k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K CPU: Intel Pentium III (Coppermine) stepping 06 Enabling unmasked SIMD FPU exception support... done. Checking ''hlt'' instruction... disabled checking if image is initramfs... it is Freeing initrd memory: 600k freed NET: Registered protocol family 16 Initializing Cryptographic API RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize Xen virtual console successfully installed as tty Event-channel device installed. Starting Xen Balloon driver xen_blk: Initialising virtual block device driver Using anticipatory io scheduler xen_net: Initialising virtual ethernet driver. NET: Registered protocol family 2 IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 4096 bind 8192) NET: Registered protocol family 1 NET: Registered protocol family 17 IP-Config: Incomplete network configuration information. Freeing unused kernel memory: 92k freed Red Hat nash version 4.1.18 starting Mounted /proc filesystem Mounting sysfs Creating /dev Starting udev Creating root device Mounting root filesystem mount: error 6 mounting ext2 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! <0>Rebooting in 1 seconds..>You''ll need to export the partition ''rw'' eventually, but that''s >not your current problem. > >Right. Already tried it.>You might like to try exporting it as ''sda1'' or something to see >if that helps. Not sure why it would, but I''ve heard folklore >along these lines. > >I had tried that (and hda1) before, but sda1 I get an error, too: [root@dyn95394184 xen]# xm create -c test1 vmid=1 Using config file "test1". Error: Error creating domain: vbd: Device not found: sda1>Adding some more debugging to the linuxrc nash script might shed >some light on the problem. > >I need to find out how to do this first...>Also, what happens if you skip the initrd and try booting >directly off the disk. I doubt there''s anything in the initrd you >need. > >I had tried it, also. I get a VFS error if I don''t use an initrd VFS: Cannot open root device "hdc1" or unknown-block(2,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) <0>Rebooting in 1 seconds..>Ian > > > > >>Freeing unused kernel memory: 92k freed >>Red Hat nash version 4.1.18 starting >>Mounted /proc filesystem >>Mounting sysfs >>Creating /dev >>Starting udev >>Creating root device >>Mounting root filesystem >>mount: error 6 mounting ext3 >>mount: error 2 mounting none >>Switching to new root >>switchroot: mount failed: 22 >>umount /initrd/dev failed: 2 >>Kernel panic - not syncing: Attempted to kill init! >> <0>Rebooting in 1 seconds.. >> >> >>David Barrera >> >> >>Derrik Pates wrote: >> >> >> >>>David F Barrera wrote: >>> >>> >>> >>>>The distro I am using is RHEL 4 Beta 2 (Red Hat Enterprise Linux >>>>Desktop release 3.90 (Nahant) >>>> >>>> >>> >>> >>>>/dev/hdc1 / ext2 >>>>defaults 1 1 >>>> >>>> >>> >>> >>>>LABEL=SWAP-hdc2 swap swap >>>>defaults 0 0 >>>>/dev/hda /media/cdrom auto >>>>pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed >>>>0 0 >>>> >>>> >>> >>> >>>># disk = [ ''phy:hda1,hda1,r'' ] >>>>disk = [ ''phy:hdc1,hdc1,r'' ] >>>> >>>> >>>Well, the configuration of the virtual disk looks correct; the swap >>>might disagree with it, but that shouldn''t appear until later in the >>>boot process. Perhaps it''s an interaction with devfs? Do you have >>>devfs enabled in your xenU (unprivileged domain) kernel? This gave me >>>fits when I first began using Xen, mostly because it seems that the >>>xenU prebuilt kernel that''s included with the binary pack has devfs >>>support enabled, and this breaks things. The only other possibility I >>>can think of is that you need to change the block-device import to >>>read-write. >>> >>> >>> >>------------------------------------------------------- >>SF email is sponsored by - The IT Product Guide >>Read honest & candid reviews on hundreds of IT Products from real users. >>Discover which products truly live up to the hype. Start reading now. >>http://productguide.itmanagersjournal.com/ >>_______________________________________________ >>Xen-devel mailing list >>Xen-devel@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/xen-devel >> >> > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://productguide.itmanagersjournal.com/ >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/xen-devel > > >------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
David F Barrera
2004-Dec-20 17:53 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
Ian, One thing about RHEL 4 is that the devices in /dev seem to be created dynamically, at boot time. When I mount the ''hdc1'' partition and go to the /dev directory, there is nothing in it, as on a SuSE 9.0 or earlier Red Hat installs. That is why I need an initrd, I suppose, to make or create those devices. David Ian Pratt wrote:>>Derrick, >> >>I rebuilt the xenU kernel, with the devfs support disabled, and it makes >>no difference. It behaves in the same manner as the pre-built kernel >>that''s included with the binary pack. I am at a loss. I''ve been able to >>boot a kernel under xen on a SuSE Linux 9.0 machine, so I''ve had a >>little experience with this:-) >> >> > >David, earlier in the boot messages do you see the hdc1 partition >being found when the partition check happens? > >You''ll need to export the partition ''rw'' eventually, but that''s >not your current problem. > >You might like to try exporting it as ''sda1'' or something to see >if that helps. Not sure why it would, but I''ve heard folklore >along these lines. > >Adding some more debugging to the linuxrc nash script might shed >some light on the problem. > >Also, what happens if you skip the initrd and try booting >directly off the disk. I doubt there''s anything in the initrd you >need. > >Ian > > > > >>Freeing unused kernel memory: 92k freed >>Red Hat nash version 4.1.18 starting >>Mounted /proc filesystem >>Mounting sysfs >>Creating /dev >>Starting udev >>Creating root device >>Mounting root filesystem >>mount: error 6 mounting ext3 >>mount: error 2 mounting none >>Switching to new root >>switchroot: mount failed: 22 >>umount /initrd/dev failed: 2 >>Kernel panic - not syncing: Attempted to kill init! >> <0>Rebooting in 1 seconds.. >> >> >>David Barrera >> >> >>Derrik Pates wrote: >> >> >> >>>David F Barrera wrote: >>> >>> >>> >>>>The distro I am using is RHEL 4 Beta 2 (Red Hat Enterprise Linux >>>>Desktop release 3.90 (Nahant) >>>> >>>> >>> >>> >>>>/dev/hdc1 / ext2 >>>>defaults 1 1 >>>> >>>> >>> >>> >>>>LABEL=SWAP-hdc2 swap swap >>>>defaults 0 0 >>>>/dev/hda /media/cdrom auto >>>>pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed >>>>0 0 >>>> >>>> >>> >>> >>>># disk = [ ''phy:hda1,hda1,r'' ] >>>>disk = [ ''phy:hdc1,hdc1,r'' ] >>>> >>>> >>>Well, the configuration of the virtual disk looks correct; the swap >>>might disagree with it, but that shouldn''t appear until later in the >>>boot process. Perhaps it''s an interaction with devfs? Do you have >>>devfs enabled in your xenU (unprivileged domain) kernel? This gave me >>>fits when I first began using Xen, mostly because it seems that the >>>xenU prebuilt kernel that''s included with the binary pack has devfs >>>support enabled, and this breaks things. The only other possibility I >>>can think of is that you need to change the block-device import to >>>read-write. >>> >>> >>> >>------------------------------------------------------- >>SF email is sponsored by - The IT Product Guide >>Read honest & candid reviews on hundreds of IT Products from real users. >>Discover which products truly live up to the hype. Start reading now. >>http://productguide.itmanagersjournal.com/ >>_______________________________________________ >>Xen-devel mailing list >>Xen-devel@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/xen-devel >> >> > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://productguide.itmanagersjournal.com/ >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/xen-devel > > >------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Ian Pratt
2004-Dec-20 19:02 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
> # Kernel image file. > kernel = "/boot/vmlinuz-2.6.9-xenU" > # Optional ramdisk. > ramdisk = "/boot/initrd-2.6.9-xenU.img" > # The domain build function. Default is ''linux''. > builder=''linux'' > # Initial memory allocation (in megabytes) for the new domain. > memory = 64 > # A name for your domain. All domains must have different names. > name = "test1" > # disk = [ ''phy:hda1,hda1,r'' ] > disk = [ ''phy:hdc1,hdc1,w'' ] > # Set if you want dhcp to allocate the IP address. > dhcp="dhcp" > # Set root device. > root = "/dev/hdc1 ro/"The ''/'' on the end of ''ro'' looks odd to me.> xen_blk: Initialising virtual block device driver > Using anticipatory io scheduler > xen_net: Initialising virtual ethernet driver. > NET: Registered protocol family 2 > IP: routing cache hash table of 512 buckets, 4Kbytes > TCP: Hash tables configured (established 4096 bind 8192) > NET: Registered protocol family 1 > NET: Registered protocol family 17 > IP-Config: Incomplete network configuration information. > Freeing unused kernel memory: 92k freed > Red Hat nash version 4.1.18 startingI can''t see any partitions being found at any point, so you''re doomed from here on in.> I had tried that (and hda1) before, but sda1 I get an error, too: > [root@dyn95394184 xen]# xm create -c test1 vmid=1 > Using config file "test1". > Error: Error creating domain: vbd: Device not found: sda1try disk = [ ''phy:hdc1,0801,w'' ] 0801 == sda1 Ian ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
David F Barrera
2004-Dec-20 19:45 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
Ian Pratt wrote:>># Kernel image file. >>kernel = "/boot/vmlinuz-2.6.9-xenU" >># Optional ramdisk. >>ramdisk = "/boot/initrd-2.6.9-xenU.img" >># The domain build function. Default is ''linux''. >>builder=''linux'' >># Initial memory allocation (in megabytes) for the new domain. >>memory = 64 >># A name for your domain. All domains must have different names. >>name = "test1" >># disk = [ ''phy:hda1,hda1,r'' ] >>disk = [ ''phy:hdc1,hdc1,w'' ] >># Set if you want dhcp to allocate the IP address. >>dhcp="dhcp" >># Set root device. >>root = "/dev/hdc1 ro/" >> >> > > >The ''/'' on the end of ''ro'' looks odd to me. > >Thx. Removing it did not make any difference.> > >>xen_blk: Initialising virtual block device driver >>Using anticipatory io scheduler >>xen_net: Initialising virtual ethernet driver. >>NET: Registered protocol family 2 >>IP: routing cache hash table of 512 buckets, 4Kbytes >>TCP: Hash tables configured (established 4096 bind 8192) >>NET: Registered protocol family 1 >>NET: Registered protocol family 17 >>IP-Config: Incomplete network configuration information. >>Freeing unused kernel memory: 92k freed >>Red Hat nash version 4.1.18 starting >> >> > >I can''t see any partitions being found at any point, so you''re >doomed from here on in. > >Agree.> > >>I had tried that (and hda1) before, but sda1 I get an error, too: >>[root@dyn95394184 xen]# xm create -c test1 vmid=1 >>Using config file "test1". >>Error: Error creating domain: vbd: Device not found: sda1 >> >> > > >try disk = [ ''phy:hdc1,0801,w'' ] > >0801 == sda1 > >No difference. Same Kernel panic> > > >Ian > > >------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Ian Pratt
2004-Dec-20 23:22 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
> >>I had tried that (and hda1) before, but sda1 I get an error, too: > >>[root@dyn95394184 xen]# xm create -c test1 vmid=1 > >>Using config file "test1". > >>Error: Error creating domain: vbd: Device not found: sda1 > > > >try disk = [ ''phy:hdc1,0801,w'' ] > > > >0801 == sda1 > > No difference. Same Kernel panicSomething odd is going on here -- I believe other people have had RHEL3 working. Can you mount hdc1 in dom 0 OK? Is there an sbin/init ? Is there a dev directory? It might be worth enabling the debugging printks in drivers/xen/blkfront/block.h and drivers/xen/blockback/common.h and rebuilding xen0 / xenU. Ian ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
David F Barrera
2004-Dec-21 15:43 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
Ian Pratt wrote:>>>>I had tried that (and hda1) before, but sda1 I get an error, too: >>>>[root@dyn95394184 xen]# xm create -c test1 vmid=1 >>>>Using config file "test1". >>>>Error: Error creating domain: vbd: Device not found: sda1 >>>> >>>> >>>try disk = [ ''phy:hdc1,0801,w'' ] >>> >>>0801 == sda1 >>> >>> >>No difference. Same Kernel panic >> >> > >Something odd is going on here -- I believe other people have had >RHEL3 working. > >I believe it. But RHEL 4 has some differences from RHEL 3, among them the fact that in RHEL 4 the devices in /dev are created dynamically. Thus, if I mount hdc1 and look at /dev, it is empty. However, /dev in hdc3 (xen0) has 671 entries. I have a SuSE 9.0 system where the drive that I export (equivalent to hdc1, in this case) has many devicen on /dev, meaning they are static; RHEL 3 is similar.>Can you mount hdc1 in dom 0 OK? >Yes: [root@dyn95394184 ~]# mount /dev/hdc1 /data1 [root@dyn95394184 ~]# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/hdc3 6372520 2732376 3316436 46% / none 251384 0 251384 0% /dev/shm /dev/hdc1 7055144 2422572 4274180 37% /data1 [root@dyn95394184 ~]#>Is there an sbin/init >[root@dyn95394184 ~]# ls /data1/sbin/init /data1/sbin/init [root@dyn95394184 ~]#>? Is there >a dev directory? > >Yes, but it is empty: [root@dyn95394184 dev]# pwd /data1/dev [root@dyn95394184 dev]# ls [root@dyn95394184 dev]#>It might be worth enabling the debugging printks in >drivers/xen/blkfront/block.h and drivers/xen/blockback/common.h >and rebuilding xen0 / xenU. > > >I created an image file to experiment, and it seems to go a little further. The problem has got to be related to the /dev issue. disk = [ ''file:/boot/initrd.x86.image,0801,w'' ] # Set if you want dhcp to allocate the IP address. # dhcp="dhcp" # Set root device. root = "/dev/sda1 ro" Red Hat nash version 4.1.18 starting Mounted /proc filesystem Mounting sysfs Creating /dev Starting udev Creating root device Mounting root filesystem Switching to new root init started: BusyBox v1.00-pre10 (2004.06.10-04:09+0000) multi-call binary Linux localhost.localdomain 2.6.9-xenU #1 Fri Dec 17 15:50:10 CST 2004 i686 unknown>Ian > > > > > >------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
David F Barrera
2004-Dec-21 18:53 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
Ian, As I indicated earlier, I created an image file, and I am able to boot xenU now: Red Hat Enterprise Linux Desktop release 3.90 (Nahant) Kernel 2.6.9-xenU on an i686 (none) login: I still can''t log in, but I will continue to add files to the image to make it work. In the image, I copied the contents of (hdc3) /dev to the image/dev. I still don''t understand why I can get xenU to boot using the system partition (hdc1). I''ll keep digging. David F Barrera> > > Ian Pratt wrote: > >>>>> I had tried that (and hda1) before, but sda1 I get an error, too: >>>>> [root@dyn95394184 xen]# xm create -c test1 vmid=1 >>>>> Using config file "test1". >>>>> Error: Error creating domain: vbd: Device not found: sda1 >>>>> >>>> >>>> try disk = [ ''phy:hdc1,0801,w'' ] >>>> >>>> 0801 == sda1 >>>> >>> >>> No difference. Same Kernel panic >>> >> >> >> Something odd is going on here -- I believe other people have had >> RHEL3 working. >> >> > I believe it. But RHEL 4 has some differences from RHEL 3, among them > the fact that in RHEL 4 the devices in /dev are created dynamically. > Thus, if I mount hdc1 and look at /dev, it is empty. However, /dev in > hdc3 (xen0) has 671 entries. I have a SuSE 9.0 system where the drive > that I export (equivalent to hdc1, in this case) has many devicen on > /dev, meaning they are static; RHEL 3 is similar. > >> Can you mount hdc1 in dom 0 OK? > > Yes: > > [root@dyn95394184 ~]# mount /dev/hdc1 /data1 > [root@dyn95394184 ~]# df > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/hdc3 6372520 2732376 3316436 46% / > none 251384 0 251384 0% /dev/shm > /dev/hdc1 7055144 2422572 4274180 37% /data1 > [root@dyn95394184 ~]# > >> Is there an sbin/init > > [root@dyn95394184 ~]# ls /data1/sbin/init > /data1/sbin/init > [root@dyn95394184 ~]# > >> ? Is there >> a dev directory? >> > Yes, but it is empty: > [root@dyn95394184 dev]# pwd > /data1/dev > [root@dyn95394184 dev]# ls > [root@dyn95394184 dev]# > >> It might be worth enabling the debugging printks in >> drivers/xen/blkfront/block.h and drivers/xen/blockback/common.h >> and rebuilding xen0 / xenU. >> >> >> > I created an image file to experiment, and it seems to go a little > further. The problem has got to be related to the /dev issue. > > disk = [ ''file:/boot/initrd.x86.image,0801,w'' ] > # Set if you want dhcp to allocate the IP address. > # dhcp="dhcp" > # Set root device. > root = "/dev/sda1 ro" > > > Red Hat nash version 4.1.18 starting > Mounted /proc filesystem > Mounting sysfs > Creating /dev > Starting udev > Creating root device > Mounting root filesystem > Switching to new root > init started: BusyBox v1.00-pre10 (2004.06.10-04:09+0000) multi-call > binary > Linux localhost.localdomain 2.6.9-xenU #1 Fri Dec 17 15:50:10 CST 2004 > i686 unknown > > >> Ian >> >> >> >> >> >> >------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
David F Barrera
2004-Dec-21 21:25 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
Ian, OK. I copied all the contents from (hdc3) /dev to (hdc1) /dev, and that let''s me boot xenU on hdc1. The problem, however, is that this is not they way RHEL 4 works--I need to figure out how the xen0 is able to boot off essentially the same setup. [root@dyn95394184 xen]# xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 495 0 r---- 126.0 test1 1 64 0 -b--- 2.0 9601 [root@dyn95394184 xen]# -------- Original Message -------- Subject: Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init! Date: Tue, 21 Dec 2004 12:53:15 -0600 From: David F Barrera <dfbp@us.ibm.com> To: xen-devel@lists.sourceforge.net References: <E1CgWrK-0003vv-00@mta1.cl.cam.ac.uk> <41C844BA.7020801@us.ibm.com> Ian, As I indicated earlier, I created an image file, and I am able to boot xenU now: Red Hat Enterprise Linux Desktop release 3.90 (Nahant) Kernel 2.6.9-xenU on an i686 (none) login: I still can''t log in, but I will continue to add files to the image to make it work. In the image, I copied the contents of (hdc3) /dev to the image/dev. I still don''t understand why I can get xenU to boot using the system partition (hdc1). I''ll keep digging. David F Barrera> > > Ian Pratt wrote: > >>>>> I had tried that (and hda1) before, but sda1 I get an error, too: >>>>> [root@dyn95394184 xen]# xm create -c test1 vmid=1 >>>>> Using config file "test1". >>>>> Error: Error creating domain: vbd: Device not found: sda1 >>>>> >>>> >>>> try disk = [ ''phy:hdc1,0801,w'' ] >>>> >>>> 0801 == sda1 >>>> >>> >>> No difference. Same Kernel panic >>> >> >> >> Something odd is going on here -- I believe other people have had >> RHEL3 working. >> >> > I believe it. But RHEL 4 has some differences from RHEL 3, among them > the fact that in RHEL 4 the devices in /dev are created dynamically. > Thus, if I mount hdc1 and look at /dev, it is empty. However, /dev in > hdc3 (xen0) has 671 entries. I have a SuSE 9.0 system where the drive > that I export (equivalent to hdc1, in this case) has many devicen on > /dev, meaning they are static; RHEL 3 is similar. > >> Can you mount hdc1 in dom 0 OK? > > Yes: > > [root@dyn95394184 ~]# mount /dev/hdc1 /data1 > [root@dyn95394184 ~]# df > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/hdc3 6372520 2732376 3316436 46% / > none 251384 0 251384 0% /dev/shm > /dev/hdc1 7055144 2422572 4274180 37% /data1 > [root@dyn95394184 ~]# > >> Is there an sbin/init > > [root@dyn95394184 ~]# ls /data1/sbin/init > /data1/sbin/init > [root@dyn95394184 ~]# > >> ? Is there >> a dev directory? >> > Yes, but it is empty: > [root@dyn95394184 dev]# pwd > /data1/dev > [root@dyn95394184 dev]# ls > [root@dyn95394184 dev]# > >> It might be worth enabling the debugging printks in >> drivers/xen/blkfront/block.h and drivers/xen/blockback/common.h >> and rebuilding xen0 / xenU. >> >> >> > I created an image file to experiment, and it seems to go a little > further. The problem has got to be related to the /dev issue. > > disk = [ ''file:/boot/initrd.x86.image,0801,w'' ] > # Set if you want dhcp to allocate the IP address. > # dhcp="dhcp" > # Set root device. > root = "/dev/sda1 ro" > > > Red Hat nash version 4.1.18 starting > Mounted /proc filesystem > Mounting sysfs > Creating /dev > Starting udev > Creating root device > Mounting root filesystem > Switching to new root > init started: BusyBox v1.00-pre10 (2004.06.10-04:09+0000) multi-call > binary > Linux localhost.localdomain 2.6.9-xenU #1 Fri Dec 17 15:50:10 CST 2004 > i686 unknown > > >> Ian >> >> >> >> >> >> >------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Ian Pratt
2004-Dec-22 02:30 UTC
RE: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
> I believe it. But RHEL 4 has some differences from RHEL 3, > among them the fact that in RHEL 4 the devices in /dev are > created dynamically. > Thus, if I mount hdc1 and look at /dev, it is empty. However, /dev in > hdc3 (xen0) has 671 entries. I have a SuSE 9.0 system where > the drive that I export (equivalent to hdc1, in this case) > has many devicen on /dev, meaning they are static; RHEL 3 is similar.Just to prove this theory, boot native Linux (or dom0), and ''cp -a'' the /dev directory over to the other domain''s file system. If you haven''t got a /dev/console bad things can happen. Ian ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Ian Pratt
2004-Dec-22 03:13 UTC
RE: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
> OK. I copied all the contents from (hdc3) /dev to (hdc1) > /dev, and that let''s me boot xenU on hdc1. The problem, > however, is that this is not they way RHEL 4 works--I need to > figure out how the xen0 is able to boot off essentially the > same setup.Have you tried using the xen0 kernel in the other domain? It''s possible there''s some difference in the .config that is causing this. Ian ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
David F Barrera
2004-Dec-22 15:39 UTC
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
Ian,
It was a setup problem after all. Mea culpa.
One thing I had to do was to change the /etc/fstab on the xenU partition
(hdc1 in my machine):
/dev/sda1 / ext2 defaults
1 1 <----------- I had the original /dev/hdc1 here
to match the xen config file:
disk = [ ''phy:hdc1,0801,w'' ] < ---- This suggestion you
gave to use
''0801'' and ''sda1'' works for some reason.
Using
''hdc1''
here and on the root = /dev/ line does NOT work, as you were aware.
root = "/dev/sda1 ro"
I need to have an initrd in order to have a console. It will not work
without it:
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.9-xenU"
# Optional ramdisk.
ramdisk = "/boot/initrd-2.6.9-xenU.img"
Thanks for all your suggestions!
David F Barrera
Ian Pratt wrote:
>>OK. I copied all the contents from (hdc3) /dev to (hdc1)
>>/dev, and that let''s me boot xenU on hdc1. The problem,
>>however, is that this is not they way RHEL 4 works--I need to
>>figure out how the xen0 is able to boot off essentially the
>>same setup.
>>
>>
>
>Have you tried using the xen0 kernel in the other domain? It''s
possible
>there''s some difference in the .config that is causing this.
>
>
I tried this just for kicks, and, of course, it worked.
>Ian
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel