Hi all, I have an HP server with a P410i RAID controller. I''m using Debian Sid/Squeeze with the Debian 2.6.32-5-xen-amd64 kernel. If I boot the kernel without the xen hypervisor (version 3.4 also from Debian) then I can mount the partitions on the CCISS device. If I boot with the hypervisor, the initramfs fails to mount root. I can see the device nodes in /dev/cciss/c0d0p?, I can use ''dd'' to successfully read from the devices, but when I try to mount in the initramfs environment, I get a "file does not exist" error. So, somehow with the hypervisor the kernel driver for cciss doesn''t work but without the hypervisor it does. I''ve seen some other reports similar to this, but there seem to be no resolutions, and sample configs don''t seem to be included in the archives. Currently, I''ve only used prebuilt packages for things, but I''m willing to compile if someone has suggestions for what to try. Thanks, Brynnen. -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> <> Brynnen Owen ( this space for rent )<> <> owen@illinois.edu ( )<> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, May 12, 2010 at 4:40 AM, <owen@illinois.edu> wrote:> Hi all, > > I have an HP server with a P410i RAID controller. I''m using Debian > Sid/Squeeze with the Debian 2.6.32-5-xen-amd64 kernel. If I boot the > kernel without the xen hypervisor (version 3.4 also from Debian) then > I can mount the partitions on the CCISS device.which kernel is that? Can you really boot 2.6.32-5-xen-amd64 kernel without the hypervisor? Or are you using some other kernel for non-xen boot? Also, what version of udev do you have, and what''s the value of CONFIG_SYSFS_DEPRECATED=y CONFIG_SYSFS_DEPRECATED_V2 on your kernel config (usually available on /boot/config*)? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > ?I have an HP server with a P410i RAID controller. ?I''m using Debian > > Sid/Squeeze with the Debian 2.6.32-5-xen-amd64 kernel. ?If I boot the > > kernel without the xen hypervisor (version 3.4 also from Debian) then > > I can mount the partitions on the CCISS device. > > which kernel is that? Can you really boot 2.6.32-5-xen-amd64 kernel > without the hypervisor? Or are you using some other kernel for non-xen > boot? > > Also, what version of udev do you have, and what''s the value of > CONFIG_SYSFS_DEPRECATED=y > CONFIG_SYSFS_DEPRECATED_V2 on your kernel config (usually available on > /boot/config*)?I don''t see a CONFIG_SYSFS_DEPRECATED except CONFIG_SYSFS_DEPRECATED_V2: # CONFIG_SYSFS_DEPRECATED_V2 is not set CONFIG_SYSFS=y virt1:~ 293 # uname -a Linux cirssvirt1.lis.illinois.edu 2.6.32-5-xen-amd64 #1 SMP Mon May 3 12:36:28 UTC 2010 x86_64 GNU/Linux There''s no /proc/xen directory. virt1:/boot 298 # grep -i xen config-2.6.32-5-xen-amd64 CONFIG_XEN=y CONFIG_XEN_MAX_DOMAIN_MEMORY=32 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set CONFIG_SWIOTLB_XEN=y CONFIG_MICROCODE_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_DOM0_PCI=y # CONFIG_XEN_PCI_PASSTHROUGH is not set CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=y CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_NETXEN_NIC=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_KBDDEV_FRONTEND=y CONFIG_HVC_XEN=y CONFIG_XEN_FBDEV_FRONTEND=y CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=m CONFIG_XEN_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_BLKDEV_TAP=m CONFIG_XEN_BLKBACK_PAGEMAP=y CONFIG_XEN_PCIDEV_BACKEND=y CONFIG_XEN_PCIDEV_BACKEND_VPCI=y # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=m CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=y CONFIG_XEN_GNTDEV=y CONFIG_XEN_S3=y CONFIG_ACPI_PROCESSOR_XEN=m -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> <> Brynnen Owen ( this space for rent )<> <> owen@illinois.edu ( )<> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Well, I figured out this problem. Does this make sense? The first command line option for the kernel appears to have been eaten. This is the option that specified the root filesystem. Since the root filesystem wasn''t specified, the filesystem driver wasn''t loaded, hence the inability to mount. If I specified the root filesystem twice in a row, then the system boots both with and without the hypervisor. So, either due to grub-pc or my not understanding something about xen, if the hypervisor boots, the first kernel argument appears to be eaten, but if the kernel boots without the hypervisor, the first argument is not eaten. This was confirmed by looking at /proc/cmdline. On Wed, May 12, 2010 at 09:26:35AM -0500, owen@illinois.edu wrote:> > > ?I have an HP server with a P410i RAID controller. ?I''m using Debian > > > Sid/Squeeze with the Debian 2.6.32-5-xen-amd64 kernel. ?If I boot the > > > kernel without the xen hypervisor (version 3.4 also from Debian) then > > > I can mount the partitions on the CCISS device. > > > > which kernel is that? Can you really boot 2.6.32-5-xen-amd64 kernel > > without the hypervisor? Or are you using some other kernel for non-xen > > boot? > > > > Also, what version of udev do you have, and what''s the value of > > CONFIG_SYSFS_DEPRECATED=y > > CONFIG_SYSFS_DEPRECATED_V2 on your kernel config (usually available on > > /boot/config*)? > > I don''t see a CONFIG_SYSFS_DEPRECATED except > CONFIG_SYSFS_DEPRECATED_V2: > > # CONFIG_SYSFS_DEPRECATED_V2 is not set > CONFIG_SYSFS=y > > > virt1:~ 293 # uname -a > Linux cirssvirt1.lis.illinois.edu 2.6.32-5-xen-amd64 #1 SMP Mon May 3 12:36:28 UTC 2010 x86_64 GNU/Linux > > There''s no /proc/xen directory. > > virt1:/boot 298 # grep -i xen config-2.6.32-5-xen-amd64 > CONFIG_XEN=y > CONFIG_XEN_MAX_DOMAIN_MEMORY=32 > CONFIG_XEN_SAVE_RESTORE=y > # CONFIG_XEN_DEBUG_FS is not set > CONFIG_SWIOTLB_XEN=y > CONFIG_MICROCODE_XEN=y > CONFIG_XEN_DOM0=y > CONFIG_XEN_PRIVILEGED_GUEST=y > CONFIG_XEN_DOM0_PCI=y > # CONFIG_XEN_PCI_PASSTHROUGH is not set > CONFIG_PCI_XEN=y > CONFIG_XEN_PCIDEV_FRONTEND=y > CONFIG_XEN_BLKDEV_FRONTEND=m > CONFIG_NETXEN_NIC=m > CONFIG_XEN_NETDEV_FRONTEND=m > CONFIG_XEN_KBDDEV_FRONTEND=y > CONFIG_HVC_XEN=y > CONFIG_XEN_FBDEV_FRONTEND=y > CONFIG_XEN_BALLOON=y > CONFIG_XEN_SCRUB_PAGES=y > CONFIG_XEN_DEV_EVTCHN=m > CONFIG_XEN_BACKEND=y > CONFIG_XEN_NETDEV_BACKEND=y > CONFIG_XEN_BLKDEV_BACKEND=y > CONFIG_XEN_BLKDEV_TAP=m > CONFIG_XEN_BLKBACK_PAGEMAP=y > CONFIG_XEN_PCIDEV_BACKEND=y > CONFIG_XEN_PCIDEV_BACKEND_VPCI=y > # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set > # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set > # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set > # CONFIG_XEN_PCIDEV_BE_DEBUG is not set > CONFIG_XENFS=m > CONFIG_XEN_COMPAT_XENFS=y > CONFIG_XEN_SYS_HYPERVISOR=y > CONFIG_XEN_XENBUS_FRONTEND=y > CONFIG_XEN_GNTDEV=y > CONFIG_XEN_S3=y > CONFIG_ACPI_PROCESSOR_XEN=m > > -- > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > <> Brynnen Owen ( this space for rent )<> > <> owen@illinois.edu ( )<> > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> <> Brynnen Owen ( this space for rent )<> <> owen@illinois.edu ( )<> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, May 17, 2010 at 9:01 PM, <owen@illinois.edu> wrote:> Well, I figured out this problem. Does this make sense? > > The first command line option for the kernel appears to have been > eaten.It''s a known thing with grub2 (which is what grub-pc is). Glad you got it worked out though. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users