I have a server running SLES10SP1 with Xen enabled. I am able to fire off SLED10 installs inside Xen VMs just fine. I need to run (3) CentOS 4.5 VMs on it. CentOS kernel is not creating block devices for hd or iso image. any ideas? It doesn''t seem to care if there is this line in my config file: disk = [ ''file:/export/home/CentOS-4.5-x86_64-binDVD.iso,hdc,r'' ] After moving down the installation path and choosing "install from local CDROM" it gives me an error message: "No driver found. Unable to find any devices of the type needed for this installation type. Would you like to manually select your driver or use a driver disk?" I should also note that I grabbed the xen kernel and initrd from here too: http://mirror.centos.org/centos/4.5/os/x86_64/images/xen/ Are there incompatibilities? Between Xen/SLES/CentOS? Thanks, Scott A kernel log follows (this time was a try with the CentOS 5 kernel/initrd): Bootdata ok (command line is text) Linux version 2.6.18-8.el5xen (mockbuild@builder6.centos.org) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP Thu Mar 15 19:56:43 EDT 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) No mptable found. Built 1 zonelists. Total pages: 67584 Kernel command line: text Initializing CPU#0 PID hash table entries: 2048 (order: 11, 16384 bytes) Xen reported: 1994.999 MHz processor. Console: colour dummy device 80x25 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: 244464k/270336k available (2321k kernel code, 17356k reserved, 1312k data, 168k init) Calibrating delay using timer specific routine.. 4989.62 BogoMIPS (lpj=9979249) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K CPU: Physical Processor ID: 3 CPU: Processor Core ID: 1 (SMP-)alternatives turned off Brought up 1 CPUs checking if image is initramfs... it is Grant table initialized NET: Registered protocol family 16 ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 2B7A0 could not acquire Mutex [2] [20060707] Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default 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: 8192 (order: 5, 131072 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com> audit: initializing netlink socket (disabled) audit(1184261432.706:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key 991108A46E99ED4B - User ID: CentOS (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Bootdata ok (command line is text) Linux version 2.6.18-8.el5xen (mockbuild@builder6.centos.org) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP Thu Mar 15 19:56:43 EDT 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) No mptable found. Built 1 zonelists. Total pages: 67584 Kernel command line: text Initializing CPU#0 PID hash table entries: 2048 (order: 11, 16384 bytes) Xen reported: 1994.999 MHz processor. Console: colour dummy device 80x25 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: 244464k/270336k available (2321k kernel code, 17356k reserved, 1312k data, 168k init) Calibrating delay using timer specific routine.. 4989.62 BogoMIPS (lpj=9979249) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K CPU: Physical Processor ID: 3 CPU: Processor Core ID: 1 (SMP-)alternatives turned off Brought up 1 CPUs checking if image is initramfs... it is Grant table initialized NET: Registered protocol family 16 ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 2B7A0 could not acquire Mutex [2] [20060707] Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default 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: 8192 (order: 5, 131072 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com> audit: initializing netlink socket (disabled) audit(1184261432.706:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key 991108A46E99ED4B - User ID: CentOS (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 TCP bic registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vbd/5632 XENBUS: Device with no driver: device/console/0 Write protecting the kernel read-only data: 439k [9;0][8] Greetings. anaconda installer init version 11.1.2.36 starting mounting /proc filesystem... done creating /dev filesystem... done mounting /dev/pts (unix98 pty) filesystem... done mounting /sys filesystem... done anaconda installer init version 11.1.2.36 using /dev/xvc0 as console trying to remount root filesystem read write... done mounting /tmp as ramfs... done running install... running /sbin/loader _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Scott Serr wrote:> I have a server running SLES10SP1 with Xen enabled. I am able to fire > off SLED10 installs inside Xen VMs just fine. > > I need to run (3) CentOS 4.5 VMs on it. > > CentOS kernel is not creating block devices for hd or iso image. any ideas? > > It doesn''t seem to care if there is this line in my config file: > > disk = [ ''file:/export/home/CentOS-4.5-x86_64-binDVD.iso,hdc,r'' ]Hmm, you''re trying to boot an ISO in paravirtual mode? AFAIK this isn''t so easy as one would assume when having used other virtualization technologies before. If at all, you can _maybe_ expect it work halfways nice with HVM. But you might rather try bootstrapping centos with yum, as described here: http://faiwiki.informatik.uni-koeln.de/index.php/FAI_multi-distribution#bootstrapping_the_base_images__for_other_distributions (this is tested on Debian, it might or might not work on SuSE, I heard various reports on success and failure on other distributions). Or, you might search the web - I used to know where I found this, but have it not available now - there is a howto on how to start anaconda inside a domU to make the installation, that should work with SuSE, too. Take care to give enough(I don''t know a number, a good guess is 256 if on doubt) memory to the VM, otherwise Anaconda will likely hang in an undefined state without any error message. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Henning Sprang wrote:> Scott Serr wrote: > >> I have a server running SLES10SP1 with Xen enabled. I am able to fire >> off SLED10 installs inside Xen VMs just fine. >> >> I need to run (3) CentOS 4.5 VMs on it. >> >> CentOS kernel is not creating block devices for hd or iso image. any ideas? >> >> It doesn''t seem to care if there is this line in my config file: >> >> disk = [ ''file:/export/home/CentOS-4.5-x86_64-binDVD.iso,hdc,r'' ] >> > > Hmm, you''re trying to boot an ISO in paravirtual mode? > > AFAIK this isn''t so easy as one would assume when having used other > virtualization technologies before. > > If at all, you can _maybe_ expect it work halfways nice with HVM. > > But you might rather try bootstrapping centos with yum, as described > here: > http://faiwiki.informatik.uni-koeln.de/index.php/FAI_multi-distribution#bootstrapping_the_base_images__for_other_distributions > (this is tested on Debian, it might or might not work on SuSE, I heard > various reports on success and failure on other distributions). > >My experience with this approach is that yum hangs doing this on CentOS 4 and CentOS 5, on the "touch" commands run by various "%post" RPM function. You may need to set a lockfile with your build script, and set a little monitor widget to slap such touch processes in the head. Once you have a base minimum OS to your flavor, set it aside in a tarball for starting new configurations. Or, if you''re a complete weasel, you use the "mock" tool from Fedora Core to build full chroot cages, run "mock init", and do your upgrades inside the mock-built chroot.> Or, you might search the web - I used to know where I found this, but > have it not available now - there is a howto on how to start anaconda > inside a domU to make the installation, that should work with SuSE, too. > > Take care to give enough(I don''t know a number, a good guess is 256 if > on doubt) memory to the VM, otherwise Anaconda will likely hang in an > undefined state without any error message. >For CentOS 5, I find 512 works well. CentOS 4 was quite happy with 256: I haven''t looked at the exact difference. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nico Kadel-Garcia wrote:> Henning Sprang wrote: >> Scott Serr wrote: >> >>> I have a server running SLES10SP1 with Xen enabled. I am able to fire >>> off SLED10 installs inside Xen VMs just fine. >>> >>> I need to run (3) CentOS 4.5 VMs on it. >>> >>> CentOS kernel is not creating block devices for hd or iso image. any >>> ideas? >>> >>> It doesn''t seem to care if there is this line in my config file: >>> >>> disk = [ ''file:/export/home/CentOS-4.5-x86_64-binDVD.iso,hdc,r'' ] >>> >> >> Hmm, you''re trying to boot an ISO in paravirtual mode? >> >> AFAIK this isn''t so easy as one would assume when having used other >> virtualization technologies before. >> >> If at all, you can _maybe_ expect it work halfways nice with HVM. >> >> But you might rather try bootstrapping centos with yum, as described >> here: >> http://faiwiki.informatik.uni-koeln.de/index.php/FAI_multi-distribution#bootstrapping_the_base_images__for_other_distributions >> >> (this is tested on Debian, it might or might not work on SuSE, I heard >> various reports on success and failure on other distributions). >> >> > My experience with this approach is that yum hangs doing this on > CentOS 4 and CentOS 5, on the "touch" commands run by various "%post" > RPM function. You may need to set a lockfile with your build script, > and set a little monitor widget to slap such touch processes in the > head. Once you have a base minimum OS to your flavor, set it aside in > a tarball for starting new configurations. > > Or, if you''re a complete weasel, you use the "mock" tool from Fedora > Core to build full chroot cages, run "mock init", and do your upgrades > inside the mock-built chroot. > >> Or, you might search the web - I used to know where I found this, but >> have it not available now - there is a howto on how to start anaconda >> inside a domU to make the installation, that should work with SuSE, too. >> >> Take care to give enough(I don''t know a number, a good guess is 256 if >> on doubt) memory to the VM, otherwise Anaconda will likely hang in an >> undefined state without any error message. >> > For CentOS 5, I find 512 works well. CentOS 4 was quite happy with > 256: I haven''t looked at the exact difference.I''m giving the domU 512MB. Thank you both for your help. And I am just doing PV, forgot to say that. What is weird though is when the kernel boots I never see anything about a hard drive either, not just the CD... disk = [ ''file:/xen/dom1/disk0,hda,w'' ''file:/xen/cd/centos4.iso,hdc,r'' ] I''ve created the disk0 with dd. I''d expect the kernel to mention that the disk has no partitions on hda, as I''ve seen before. I also tried the front end device name of xvda. This page: http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU Has a full install from the network. SuSE domU on SuSE dom0 is so easy... I with I could get CentOS working. Thanks for any additional help or hints. -Scott _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Scott Serr wrote:> Nico Kadel-Garcia wrote: >> Henning Sprang wrote: >>> Scott Serr wrote: >>> >>>> I have a server running SLES10SP1 with Xen enabled. I am able to fire >>>> off SLED10 installs inside Xen VMs just fine. >>>> >>>> I need to run (3) CentOS 4.5 VMs on it. >>>> >>>> CentOS kernel is not creating block devices for hd or iso image. >>>> any ideas? >>>> >>>> It doesn''t seem to care if there is this line in my config file: >>>> >>>> disk = [ ''file:/export/home/CentOS-4.5-x86_64-binDVD.iso,hdc,r'' ] >>>> >>> >>> Hmm, you''re trying to boot an ISO in paravirtual mode? >>> >>> AFAIK this isn''t so easy as one would assume when having used other >>> virtualization technologies before. >>> >>> If at all, you can _maybe_ expect it work halfways nice with HVM. >>> >>> But you might rather try bootstrapping centos with yum, as described >>> here: >>> http://faiwiki.informatik.uni-koeln.de/index.php/FAI_multi-distribution#bootstrapping_the_base_images__for_other_distributions >>> >>> (this is tested on Debian, it might or might not work on SuSE, I heard >>> various reports on success and failure on other distributions). >>> >>> >> My experience with this approach is that yum hangs doing this on >> CentOS 4 and CentOS 5, on the "touch" commands run by various "%post" >> RPM function. You may need to set a lockfile with your build script, >> and set a little monitor widget to slap such touch processes in the >> head. Once you have a base minimum OS to your flavor, set it aside in >> a tarball for starting new configurations. >> >> Or, if you''re a complete weasel, you use the "mock" tool from Fedora >> Core to build full chroot cages, run "mock init", and do your >> upgrades inside the mock-built chroot. >> >>> Or, you might search the web - I used to know where I found this, but >>> have it not available now - there is a howto on how to start anaconda >>> inside a domU to make the installation, that should work with SuSE, >>> too. >>> >>> Take care to give enough(I don''t know a number, a good guess is 256 if >>> on doubt) memory to the VM, otherwise Anaconda will likely hang in an >>> undefined state without any error message. >>> >> For CentOS 5, I find 512 works well. CentOS 4 was quite happy with >> 256: I haven''t looked at the exact difference. > > I''m giving the domU 512MB. Thank you both for your help. And I am > just doing PV, forgot to say that. > > What is weird though is when the kernel boots I never see anything > about a hard drive either, not just the CD... > > disk = [ ''file:/xen/dom1/disk0,hda,w'' ''file:/xen/cd/centos4.iso,hdc,r'' ] > > I''ve created the disk0 with dd. I''d expect the kernel to mention that > the disk has no partitions on hda, as I''ve seen before. I also tried > the front end device name of xvda.It only whines that way if you use something like disk = [ ''file:/xen/dom1/disk0,hda1,w'' ''file:/xen/cd/centos4.iso,hdc,r'' ] You see the difference between hda, which describes a disk, and hda1, which describes a partition? They''re also usually seen as sda or, with RHEL, xvda.> This page: > http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU > Has a full install from the network. > > SuSE domU on SuSE dom0 is so easy... I with I could get CentOS working. > Thanks for any additional help or hints. > -Scott_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users