I had a supermicro server SuperServer 1027R-WRF4+ and a old Dell PowerEdge 2950.
In both machines I setup centos 6.5, which is running 3.10.34-11.el6.centos.alt.x86_64.
I follow Xen4Cen wiki to setup Xen, I had other servers running Centos 5.x without issues.
Now, once I build my vm's dom-u centos 6.5/centos 5.9 both x64, I receive different erros, let me show u the message I receive in my console for centos 6.5 dum-u.
xl console oerp-server PCI: Fatal: No config space access function found ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space
Something related to ipmi in my server which is enable by default? can be, now what happen is I try to boot xentos 5.9 x64 dom-u:
Brought up 1 CPUs checking if image is initramfs... it is Grant table initialized NET: Registered protocol family 16 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: 65536 (order: 7, 524288 bytes) TCP established hash table entries: 262144 (order: 10, 4194304 bytes) TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) TCP: Hash tables configured (established 262144 bind 65536) TCP reno registered audit: initializing netlink socket (disabled) type=2000 audit(1402907331.494:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API alg: No test for crc32c (crc32c-generic) ksign: Installing public key data Loading keyring - Added public key 691B840A64868995 - 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 brd: module loaded 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/51712 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0 Initalizing network drop monitor service Write protecting the kernel read-only data: 506k Red Hat nash version 5.1.19.6 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading jbd.ko module Loading ext3.ko module Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 1) Loading dm-mod.ko module device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading dm-mem-cache.ko module Loading dm-region_hash.ko module Loading dm-message.ko module Loading dm-raid45.ko module device-mapper: dm-raid45: initialized v0.2594l Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!
Looks is not finding the dom-u disk.
In both cases I'm using almost the same settings:
name = "centos5" uuid = "5020979f-8dae-105d-df56-9fb28d377aa2" bootloader = "/usr/bin/pygrub" memory = 2048 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" disk = [ "tap:aio:/ext4/centos5/disk.img,xvda,w" ] vif = [ "mac=X:X:X:X:X:X,bridge=xenbr0,script=vif-bridge" ]
The main line of centos stock without Xen continue using kernel 2.6.x, but Xen is using the new line 3.x.
Anyone else with this issue?
Thanks for your time.
On Mon, Jun 16, 2014 at 08:42:49AM -0700, Periko Support wrote:
I had a supermicro server SuperServer 1027R-WRF4+ and a old Dell PowerEdge 2950.
In both machines I setup centos 6.5, which is running 3.10.34-11.el6.centos.alt.x86_64.
I follow Xen4Cen wiki to setup Xen, I had other servers running Centos 5.x without issues.
Now, once I build my vm's dom-u centos 6.5/centos 5.9 both x64, I receive different erros, let me show u the message I receive in my console for centos 6.5 dum-u.
xl console oerp-server PCI: Fatal: No config space access function found ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space
Something related to ipmi in my server which is enable by default? can be, now what happen is I try to boot xentos 5.9 x64 dom-u:
So if I understand you correct - in 5.9 you did not see this, but in 6.5 you do?
And the error is that some driver that looks to be built in is telling you that it can't set up I/O space? Well, that is OK - if it can't it cannot.
Brought up 1 CPUs checking if image is initramfs... it is Grant table initialized NET: Registered protocol family 16 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: 65536 (order: 7, 524288 bytes) TCP established hash table entries: 262144 (order: 10, 4194304 bytes) TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) TCP: Hash tables configured (established 262144 bind 65536) TCP reno registered audit: initializing netlink socket (disabled) type=2000 audit(1402907331.494:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API alg: No test for crc32c (crc32c-generic) ksign: Installing public key data Loading keyring
- Added public key 691B840A64868995
- 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 brd: module loaded 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/51712 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0 Initalizing network drop monitor service Write protecting the kernel read-only data: 506k Red Hat nash version 5.1.19.6 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading jbd.ko module Loading ext3.ko module Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 1) Loading dm-mod.ko module device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading dm-mem-cache.ko module Loading dm-region_hash.ko module Loading dm-message.ko module Loading dm-raid45.ko module device-mapper: dm-raid45: initialized v0.2594l Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!
Looks is not finding the dom-u disk.
In both cases I'm using almost the same settings:
name = "centos5" uuid = "5020979f-8dae-105d-df56-9fb28d377aa2" bootloader = "/usr/bin/pygrub" memory = 2048 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" disk = [ "tap:aio:/ext4/centos5/disk.img,xvda,w" ] vif = [ "mac=X:X:X:X:X:X,bridge=xenbr0,script=vif-bridge" ]
The main line of centos stock without Xen continue using kernel 2.6.x, but Xen is using the new line 3.x.
Anyone else with this issue?
Thanks for your time. _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
--------------------------------------- So if I understand you correct - in 5.9 you did not see this, but in 6.5 you do? --------------------------------------
Yes, just with centos 6.5 dom-u.
But none of both vm's run.
On Mon, Jun 16, 2014 at 10:15 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
On Mon, Jun 16, 2014 at 08:42:49AM -0700, Periko Support wrote:
I had a supermicro server SuperServer 1027R-WRF4+ and a old Dell PowerEdge 2950.
In both machines I setup centos 6.5, which is running 3.10.34-11.el6.centos.alt.x86_64.
I follow Xen4Cen wiki to setup Xen, I had other servers running Centos 5.x without issues.
Now, once I build my vm's dom-u centos 6.5/centos 5.9 both x64, I receive different erros, let me show u the message I receive in my console for centos 6.5 dum-u.
xl console oerp-server PCI: Fatal: No config space access function found ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space
Something related to ipmi in my server which is enable by default? can be, now what happen is I try to boot xentos 5.9 x64 dom-u:
So if I understand you correct - in 5.9 you did not see this, but in 6.5 you do?
And the error is that some driver that looks to be built in is telling you that it can't set up I/O space? Well, that is OK - if it can't it cannot.
Brought up 1 CPUs checking if image is initramfs... it is Grant table initialized NET: Registered protocol family 16 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: 65536 (order: 7, 524288 bytes) TCP established hash table entries: 262144 (order: 10, 4194304 bytes) TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) TCP: Hash tables configured (established 262144 bind 65536) TCP reno registered audit: initializing netlink socket (disabled) type=2000 audit(1402907331.494:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API alg: No test for crc32c (crc32c-generic) ksign: Installing public key data Loading keyring
- Added public key 691B840A64868995
- 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 brd: module loaded 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/51712 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0 Initalizing network drop monitor service Write protecting the kernel read-only data: 506k Red Hat nash version 5.1.19.6 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading jbd.ko module Loading ext3.ko module Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 1) Loading dm-mod.ko module device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading dm-mem-cache.ko module Loading dm-region_hash.ko module Loading dm-message.ko module Loading dm-raid45.ko module device-mapper: dm-raid45: initialized v0.2594l Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!
Looks is not finding the dom-u disk.
In both cases I'm using almost the same settings:
name = "centos5" uuid = "5020979f-8dae-105d-df56-9fb28d377aa2" bootloader = "/usr/bin/pygrub" memory = 2048 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" disk = [ "tap:aio:/ext4/centos5/disk.img,xvda,w" ] vif = [ "mac=X:X:X:X:X:X,bridge=xenbr0,script=vif-bridge" ]
The main line of centos stock without Xen continue using kernel 2.6.x, but Xen is using the new line 3.x.
Anyone else with this issue?
Thanks for your time. _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
On Mon, Jun 16, 2014 at 10:21:45AM -0700, Periko Support wrote:
So if I understand you correct - in 5.9 you did not see this, but in 6.5 you do?
Yes, just with centos 6.5 dom-u.
But none of both vm's run.
Please do not top post. .. snip.. .. snip..
Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 1) Loading dm-mod.ko module device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading dm-mem-cache.ko module Loading dm-region_hash.ko module Loading dm-message.ko module Loading dm-raid45.ko module device-mapper: dm-raid45: initialized v0.2594l Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!
Ah, that is because you do not have xen-blkfront loaded in your initrd. Somehow it thinks it is called 'xenblk'. If you recreate your initrd (either dracut or mkinitrd) make sure you specify that you want to have the 'xen-blkfront' driver as part of it. The usual parameter is '--add' or such.
How did you generate your initrd?
On 06/16/2014 12:37 PM, Konrad Rzeszutek Wilk wrote:
On Mon, Jun 16, 2014 at 10:21:45AM -0700, Periko Support wrote:
So if I understand you correct - in 5.9 you did not see this, but in 6.5 you do?
Yes, just with centos 6.5 dom-u.
But none of both vm's run.
Please do not top post. .. snip.. .. snip..
Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 1) Loading dm-mod.ko module device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading dm-mem-cache.ko module Loading dm-region_hash.ko module Loading dm-message.ko module Loading dm-raid45.ko module device-mapper: dm-raid45: initialized v0.2594l Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!
Ah, that is because you do not have xen-blkfront loaded in your initrd. Somehow it thinks it is called 'xenblk'. If you recreate your initrd (either dracut or mkinitrd) make sure you specify that you want to have the 'xen-blkfront' driver as part of it. The usual parameter is '--add' or such.
How did you generate your initrd?
Probably auto generated as part of the kernel install process ... The Xen4CentOS project uses blkap2.5 that is rolled into our kernel.
All the modules SHOULD load initially and it should work, although, I have not tested it at all on ipmi ... so if we need to do anything special then lets figure out what that is and get it into Xen4CentOS stack.
Thanks, Johnny Hughes
On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
On Mon, Jun 16, 2014 at 10:21:45AM -0700, Periko Support wrote:
So if I understand you correct - in 5.9 you did not see this, but in 6.5 you do?
Yes, just with centos 6.5 dom-u.
But none of both vm's run.
Please do not top post. .. snip.. .. snip..
Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 1) Loading dm-mod.ko module device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading dm-mem-cache.ko module Loading dm-region_hash.ko module Loading dm-message.ko module Loading dm-raid45.ko module device-mapper: dm-raid45: initialized v0.2594l Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!
Ah, that is because you do not have xen-blkfront loaded in your initrd. Somehow it thinks it is called 'xenblk'. If you recreate your initrd (either dracut or mkinitrd) make sure you specify that you want to have the 'xen-blkfront' driver as part of it. The usual parameter is '--add' or such.
How did you generate your initrd? _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
No, I'm using the instructions from xen4centos project. Nothing manually.
U mention 2 things:
For centos6 is normal the error, I have to connect to my console using other methods and see if centos6 dom-u is running, I will let u know. 2nd u mention that we need a module xen-blkfront for centos5 dom-u, hope the developers read this and fix this asap.
Thanks.
On Mon, Jun 16, 2014 at 10:46 AM, Periko Support pheriko.support@gmail.com wrote:
On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
On Mon, Jun 16, 2014 at 10:21:45AM -0700, Periko Support wrote:
So if I understand you correct - in 5.9 you did not see this, but in 6.5 you do?
Yes, just with centos 6.5 dom-u.
But none of both vm's run.
Please do not top post. .. snip.. .. snip..
Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 1) Loading dm-mod.ko module device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading dm-mem-cache.ko module Loading dm-region_hash.ko module Loading dm-message.ko module Loading dm-raid45.ko module device-mapper: dm-raid45: initialized v0.2594l Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!
Ah, that is because you do not have xen-blkfront loaded in your initrd. Somehow it thinks it is called 'xenblk'. If you recreate your initrd (either dracut or mkinitrd) make sure you specify that you want to have the 'xen-blkfront' driver as part of it. The usual parameter is '--add' or such.
How did you generate your initrd? _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
No, I'm using the instructions from xen4centos project. Nothing manually.
U mention 2 things:
For centos6 is normal the error, I have to connect to my console using other methods and see if centos6 dom-u is running, I will let u know. 2nd u mention that we need a module xen-blkfront for centos5 dom-u, hope the developers read this and fix this asap.
Thanks.
If u need info from me, let me know, because this happen in both servers with different year of manufacturing. and different centos version 5.9/6.0.
Thanks for your time!!!
On Mon, Jun 16, 2014 at 10:51:54AM -0700, Periko Support wrote:
On Mon, Jun 16, 2014 at 10:46 AM, Periko Support pheriko.support@gmail.com wrote:
On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
On Mon, Jun 16, 2014 at 10:21:45AM -0700, Periko Support wrote:
So if I understand you correct - in 5.9 you did not see this, but in 6.5 you do?
Yes, just with centos 6.5 dom-u.
But none of both vm's run.
Please do not top post. .. snip.. .. snip..
Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 1) Loading dm-mod.ko module device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading dm-mem-cache.ko module Loading dm-region_hash.ko module Loading dm-message.ko module Loading dm-raid45.ko module device-mapper: dm-raid45: initialized v0.2594l Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!
Ah, that is because you do not have xen-blkfront loaded in your initrd. Somehow it thinks it is called 'xenblk'. If you recreate your initrd (either dracut or mkinitrd) make sure you specify that you want to have the 'xen-blkfront' driver as part of it. The usual parameter is '--add' or such.
How did you generate your initrd? _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
No, I'm using the instructions from xen4centos project. Nothing manually.
U mention 2 things:
For centos6 is normal the error, I have to connect to my console using other methods and see if centos6 dom-u is running, I will let u know. 2nd u mention that we need a module xen-blkfront for centos5 dom-u, hope the developers read this and fix this asap.
Thanks.
If u need info from me, let me know, because this happen in both servers with different year of manufacturing. and different centos version 5.9/6.0.
Huh?
You do not need any developers. You just need to regenerate your initrd to have extra drivers. That is it.
Thanks for your time!!! _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
On Mon, Jun 16, 2014 at 10:55 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
On Mon, Jun 16, 2014 at 10:51:54AM -0700, Periko Support wrote:
On Mon, Jun 16, 2014 at 10:46 AM, Periko Support pheriko.support@gmail.com wrote:
On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
On Mon, Jun 16, 2014 at 10:21:45AM -0700, Periko Support wrote:
So if I understand you correct - in 5.9 you did not see this, but in 6.5 you do?
Yes, just with centos 6.5 dom-u.
But none of both vm's run.
Please do not top post. .. snip.. .. snip..
> Loading xenblk.ko module > XENBUS: Waiting for devices to initialise: > 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... > XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, > remote state 1) > Loading dm-mod.ko module > device-mapper: uevent: version 1.0.3 > device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com > Loading dm-log.ko module > Loading dm-mirror.ko module > Loading dm-zero.ko module > Loading dm-snapshot.ko module > Loading dm-mem-cache.ko module > Loading dm-region_hash.ko module > Loading dm-message.ko module > Loading dm-raid45.ko module > device-mapper: dm-raid45: initialized v0.2594l > Scanning and configuring dmraid supported devices > Scanning logical volumes > Reading all physical volumes. This may take a while... > No volume groups found > Activating logical volumes > Volume group "VolGroup00" not found > Creating root device. > Mounting root filesystem. > mount: could not find filesystem '/dev/root' > Setting up other filesystems. > Setting up new root fs > setuproot: moving /dev failed: No such file or directory > no fstab.sys, mounting internal defaults > setuproot: error mounting /proc: No such file or directory > setuproot: error mounting /sys: No such file or directory > Switching to new root and running init. > unmounting old /dev > unmounting old /proc > unmounting old /sys > switchroot: mount failed: No such file or directory > Kernel panic - not syncing: Attempted to kill init!
Ah, that is because you do not have xen-blkfront loaded in your initrd. Somehow it thinks it is called 'xenblk'. If you recreate your initrd (either dracut or mkinitrd) make sure you specify that you want to have the 'xen-blkfront' driver as part of it. The usual parameter is '--add' or such.
How did you generate your initrd? _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
No, I'm using the instructions from xen4centos project. Nothing manually.
U mention 2 things:
For centos6 is normal the error, I have to connect to my console using other methods and see if centos6 dom-u is running, I will let u know. 2nd u mention that we need a module xen-blkfront for centos5 dom-u, hope the developers read this and fix this asap.
Thanks.
If u need info from me, let me know, because this happen in both servers with different year of manufacturing. and different centos version 5.9/6.0.
Huh?
You do not need any developers. You just need to regenerate your initrd to have extra drivers. That is it.
Thanks for your time!!! _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Understand that, but if exist something to be done to have the fix for the whole community will be better, don't u think?
On Mon, Jun 16, 2014 at 11:10 AM, Periko Support pheriko.support@gmail.com wrote:
On Mon, Jun 16, 2014 at 10:55 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
On Mon, Jun 16, 2014 at 10:51:54AM -0700, Periko Support wrote:
On Mon, Jun 16, 2014 at 10:46 AM, Periko Support pheriko.support@gmail.com wrote:
On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
On Mon, Jun 16, 2014 at 10:21:45AM -0700, Periko Support wrote:
So if I understand you correct - in 5.9 you did not see this, but in 6.5 you do?
Yes, just with centos 6.5 dom-u.
But none of both vm's run.
Please do not top post. .. snip.. .. snip..
>> Loading xenblk.ko module >> XENBUS: Waiting for devices to initialise: >> 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... >> XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, >> remote state 1) >> Loading dm-mod.ko module >> device-mapper: uevent: version 1.0.3 >> device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com >> Loading dm-log.ko module >> Loading dm-mirror.ko module >> Loading dm-zero.ko module >> Loading dm-snapshot.ko module >> Loading dm-mem-cache.ko module >> Loading dm-region_hash.ko module >> Loading dm-message.ko module >> Loading dm-raid45.ko module >> device-mapper: dm-raid45: initialized v0.2594l >> Scanning and configuring dmraid supported devices >> Scanning logical volumes >> Reading all physical volumes. This may take a while... >> No volume groups found >> Activating logical volumes >> Volume group "VolGroup00" not found >> Creating root device. >> Mounting root filesystem. >> mount: could not find filesystem '/dev/root' >> Setting up other filesystems. >> Setting up new root fs >> setuproot: moving /dev failed: No such file or directory >> no fstab.sys, mounting internal defaults >> setuproot: error mounting /proc: No such file or directory >> setuproot: error mounting /sys: No such file or directory >> Switching to new root and running init. >> unmounting old /dev >> unmounting old /proc >> unmounting old /sys >> switchroot: mount failed: No such file or directory >> Kernel panic - not syncing: Attempted to kill init!
Ah, that is because you do not have xen-blkfront loaded in your initrd. Somehow it thinks it is called 'xenblk'. If you recreate your initrd (either dracut or mkinitrd) make sure you specify that you want to have the 'xen-blkfront' driver as part of it. The usual parameter is '--add' or such.
How did you generate your initrd? _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
No, I'm using the instructions from xen4centos project. Nothing manually.
U mention 2 things:
For centos6 is normal the error, I have to connect to my console using other methods and see if centos6 dom-u is running, I will let u know. 2nd u mention that we need a module xen-blkfront for centos5 dom-u, hope the developers read this and fix this asap.
Thanks.
If u need info from me, let me know, because this happen in both servers with different year of manufacturing. and different centos version 5.9/6.0.
Huh?
You do not need any developers. You just need to regenerate your initrd to have extra drivers. That is it.
Thanks for your time!!! _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Understand that, but if exist something to be done to have the fix for the whole community will be better, don't u think?
Latest news, I connect to dom-u centos 6.5 x64 over vnc and is booting and got this after waiting:
xl console oerp-server PCI: Fatal: No config space access function found ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.32-431.el6.x86_64 #1 Call Trace: [<ffffffff815271fa>] ? panic+0xa7/0x16f [<ffffffff81077622>] ? do_exit+0x862/0x870 [<ffffffff8118a865>] ? fput+0x25/0x30 [<ffffffff81077688>] ? do_group_exit+0x58/0xd0 [<ffffffff81077717>] ? sys_exit_group+0x17/0x20 [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b
Thanks.
On Mon, Jun 16, 2014 at 11:34 AM, Periko Support pheriko.support@gmail.com wrote:
On Mon, Jun 16, 2014 at 11:10 AM, Periko Support pheriko.support@gmail.com wrote:
On Mon, Jun 16, 2014 at 10:55 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
On Mon, Jun 16, 2014 at 10:51:54AM -0700, Periko Support wrote:
On Mon, Jun 16, 2014 at 10:46 AM, Periko Support pheriko.support@gmail.com wrote:
On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
On Mon, Jun 16, 2014 at 10:21:45AM -0700, Periko Support wrote: > --------------------------------------- > So if I understand you correct - in 5.9 you did not see this, but > in 6.5 you do? > -------------------------------------- > > Yes, just with centos 6.5 dom-u. > > But none of both vm's run.
Please do not top post. .. snip.. .. snip.. > >> Loading xenblk.ko module > >> XENBUS: Waiting for devices to initialise: > >> 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... > >> XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, > >> remote state 1) > >> Loading dm-mod.ko module > >> device-mapper: uevent: version 1.0.3 > >> device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com > >> Loading dm-log.ko module > >> Loading dm-mirror.ko module > >> Loading dm-zero.ko module > >> Loading dm-snapshot.ko module > >> Loading dm-mem-cache.ko module > >> Loading dm-region_hash.ko module > >> Loading dm-message.ko module > >> Loading dm-raid45.ko module > >> device-mapper: dm-raid45: initialized v0.2594l > >> Scanning and configuring dmraid supported devices > >> Scanning logical volumes > >> Reading all physical volumes. This may take a while... > >> No volume groups found > >> Activating logical volumes > >> Volume group "VolGroup00" not found > >> Creating root device. > >> Mounting root filesystem. > >> mount: could not find filesystem '/dev/root' > >> Setting up other filesystems. > >> Setting up new root fs > >> setuproot: moving /dev failed: No such file or directory > >> no fstab.sys, mounting internal defaults > >> setuproot: error mounting /proc: No such file or directory > >> setuproot: error mounting /sys: No such file or directory > >> Switching to new root and running init. > >> unmounting old /dev > >> unmounting old /proc > >> unmounting old /sys > >> switchroot: mount failed: No such file or directory > >> Kernel panic - not syncing: Attempted to kill init!
Ah, that is because you do not have xen-blkfront loaded in your initrd. Somehow it thinks it is called 'xenblk'. If you recreate your initrd (either dracut or mkinitrd) make sure you specify that you want to have the 'xen-blkfront' driver as part of it. The usual parameter is '--add' or such.
How did you generate your initrd? _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
No, I'm using the instructions from xen4centos project. Nothing manually.
U mention 2 things:
For centos6 is normal the error, I have to connect to my console using other methods and see if centos6 dom-u is running, I will let u know. 2nd u mention that we need a module xen-blkfront for centos5 dom-u, hope the developers read this and fix this asap.
Thanks.
If u need info from me, let me know, because this happen in both servers with different year of manufacturing. and different centos version 5.9/6.0.
Huh?
You do not need any developers. You just need to regenerate your initrd to have extra drivers. That is it.
Thanks for your time!!! _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Understand that, but if exist something to be done to have the fix for the whole community will be better, don't u think?
Latest news, I connect to dom-u centos 6.5 x64 over vnc and is booting and got this after waiting:
xl console oerp-server PCI: Fatal: No config space access function found ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.32-431.el6.x86_64 #1 Call Trace: [<ffffffff815271fa>] ? panic+0xa7/0x16f [<ffffffff81077622>] ? do_exit+0x862/0x870 [<ffffffff8118a865>] ? fput+0x25/0x30 [<ffffffff81077688>] ? do_group_exit+0x58/0xd0 [<ffffffff81077717>] ? sys_exit_group+0x17/0x20 [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b
Thanks.
I add the module to initrd, didn't fix the issue.
At the end, is a bug ?
On Mon, Jun 16, 2014 at 09:09:04PM -0700, Periko Support wrote:
On Mon, Jun 16, 2014 at 11:34 AM, Periko Support pheriko.support@gmail.com wrote:
On Mon, Jun 16, 2014 at 11:10 AM, Periko Support pheriko.support@gmail.com wrote:
On Mon, Jun 16, 2014 at 10:55 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
On Mon, Jun 16, 2014 at 10:51:54AM -0700, Periko Support wrote:
On Mon, Jun 16, 2014 at 10:46 AM, Periko Support pheriko.support@gmail.com wrote:
On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote: > On Mon, Jun 16, 2014 at 10:21:45AM -0700, Periko Support wrote: >> --------------------------------------- >> So if I understand you correct - in 5.9 you did not see this, but >> in 6.5 you do? >> -------------------------------------- >> >> Yes, just with centos 6.5 dom-u. >> >> But none of both vm's run. > > Please do not top post. > .. snip.. > .. snip.. >> >> Loading xenblk.ko module >> >> XENBUS: Waiting for devices to initialise: >> >> 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... >> >> XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, >> >> remote state 1) >> >> Loading dm-mod.ko module >> >> device-mapper: uevent: version 1.0.3 >> >> device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com >> >> Loading dm-log.ko module >> >> Loading dm-mirror.ko module >> >> Loading dm-zero.ko module >> >> Loading dm-snapshot.ko module >> >> Loading dm-mem-cache.ko module >> >> Loading dm-region_hash.ko module >> >> Loading dm-message.ko module >> >> Loading dm-raid45.ko module >> >> device-mapper: dm-raid45: initialized v0.2594l >> >> Scanning and configuring dmraid supported devices >> >> Scanning logical volumes >> >> Reading all physical volumes. This may take a while... >> >> No volume groups found >> >> Activating logical volumes >> >> Volume group "VolGroup00" not found >> >> Creating root device. >> >> Mounting root filesystem. >> >> mount: could not find filesystem '/dev/root' >> >> Setting up other filesystems. >> >> Setting up new root fs >> >> setuproot: moving /dev failed: No such file or directory >> >> no fstab.sys, mounting internal defaults >> >> setuproot: error mounting /proc: No such file or directory >> >> setuproot: error mounting /sys: No such file or directory >> >> Switching to new root and running init. >> >> unmounting old /dev >> >> unmounting old /proc >> >> unmounting old /sys >> >> switchroot: mount failed: No such file or directory >> >> Kernel panic - not syncing: Attempted to kill init! > > > > Ah, that is because you do not have xen-blkfront loaded in your initrd. > Somehow it thinks it is called 'xenblk'. If you recreate your initrd > (either dracut or mkinitrd) make sure you specify that you want to > have the 'xen-blkfront' driver as part of it. The usual parameter > is '--add' or such. > > How did you generate your initrd? > _______________________________________________ > CentOS-virt mailing list > CentOS-virt@centos.org > http://lists.centos.org/mailman/listinfo/centos-virt
No, I'm using the instructions from xen4centos project. Nothing manually.
U mention 2 things:
For centos6 is normal the error, I have to connect to my console using other methods and see if centos6 dom-u is running, I will let u know. 2nd u mention that we need a module xen-blkfront for centos5 dom-u, hope the developers read this and fix this asap.
Thanks.
If u need info from me, let me know, because this happen in both servers with different year of manufacturing. and different centos version 5.9/6.0.
Huh?
You do not need any developers. You just need to regenerate your initrd to have extra drivers. That is it.
Thanks for your time!!! _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Understand that, but if exist something to be done to have the fix for the whole community will be better, don't u think?
Latest news, I connect to dom-u centos 6.5 x64 over vnc and is booting and got this after waiting:
xl console oerp-server PCI: Fatal: No config space access function found ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.32-431.el6.x86_64 #1 Call Trace: [<ffffffff815271fa>] ? panic+0xa7/0x16f [<ffffffff81077622>] ? do_exit+0x862/0x870 [<ffffffff8118a865>] ? fput+0x25/0x30 [<ffffffff81077688>] ? do_group_exit+0x58/0xd0 [<ffffffff81077717>] ? sys_exit_group+0x17/0x20 [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b
Thanks.
I add the module to initrd, didn't fix the issue.
Can you post the full dmesg output please? Do you see 'xen-blkfront' being loaded on it?
At the end, is a bug ? _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
On Tue, Jun 17, 2014 at 8:19 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
On Mon, Jun 16, 2014 at 09:09:04PM -0700, Periko Support wrote:
On Mon, Jun 16, 2014 at 11:34 AM, Periko Support pheriko.support@gmail.com wrote:
On Mon, Jun 16, 2014 at 11:10 AM, Periko Support pheriko.support@gmail.com wrote:
On Mon, Jun 16, 2014 at 10:55 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
On Mon, Jun 16, 2014 at 10:51:54AM -0700, Periko Support wrote:
On Mon, Jun 16, 2014 at 10:46 AM, Periko Support pheriko.support@gmail.com wrote: > On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk > konrad.wilk@oracle.com wrote: >> On Mon, Jun 16, 2014 at 10:21:45AM -0700, Periko Support wrote: >>> --------------------------------------- >>> So if I understand you correct - in 5.9 you did not see this, but >>> in 6.5 you do? >>> -------------------------------------- >>> >>> Yes, just with centos 6.5 dom-u. >>> >>> But none of both vm's run. >> >> Please do not top post. >> .. snip.. >> .. snip.. >>> >> Loading xenblk.ko module >>> >> XENBUS: Waiting for devices to initialise: >>> >> 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... >>> >> XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, >>> >> remote state 1) >>> >> Loading dm-mod.ko module >>> >> device-mapper: uevent: version 1.0.3 >>> >> device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com >>> >> Loading dm-log.ko module >>> >> Loading dm-mirror.ko module >>> >> Loading dm-zero.ko module >>> >> Loading dm-snapshot.ko module >>> >> Loading dm-mem-cache.ko module >>> >> Loading dm-region_hash.ko module >>> >> Loading dm-message.ko module >>> >> Loading dm-raid45.ko module >>> >> device-mapper: dm-raid45: initialized v0.2594l >>> >> Scanning and configuring dmraid supported devices >>> >> Scanning logical volumes >>> >> Reading all physical volumes. This may take a while... >>> >> No volume groups found >>> >> Activating logical volumes >>> >> Volume group "VolGroup00" not found >>> >> Creating root device. >>> >> Mounting root filesystem. >>> >> mount: could not find filesystem '/dev/root' >>> >> Setting up other filesystems. >>> >> Setting up new root fs >>> >> setuproot: moving /dev failed: No such file or directory >>> >> no fstab.sys, mounting internal defaults >>> >> setuproot: error mounting /proc: No such file or directory >>> >> setuproot: error mounting /sys: No such file or directory >>> >> Switching to new root and running init. >>> >> unmounting old /dev >>> >> unmounting old /proc >>> >> unmounting old /sys >>> >> switchroot: mount failed: No such file or directory >>> >> Kernel panic - not syncing: Attempted to kill init! >> >> >> >> Ah, that is because you do not have xen-blkfront loaded in your initrd. >> Somehow it thinks it is called 'xenblk'. If you recreate your initrd >> (either dracut or mkinitrd) make sure you specify that you want to >> have the 'xen-blkfront' driver as part of it. The usual parameter >> is '--add' or such. >> >> How did you generate your initrd? >> _______________________________________________ >> CentOS-virt mailing list >> CentOS-virt@centos.org >> http://lists.centos.org/mailman/listinfo/centos-virt > > No, I'm using the instructions from xen4centos project. Nothing manually. > > U mention 2 things: > > For centos6 is normal the error, I have to connect to my console using > other methods and see if centos6 dom-u is running, I will let u know. > 2nd u mention that we need a module xen-blkfront for centos5 dom-u, > hope the developers read this and fix this asap. > > Thanks.
If u need info from me, let me know, because this happen in both servers with different year of manufacturing. and different centos version 5.9/6.0.
Huh?
You do not need any developers. You just need to regenerate your initrd to have extra drivers. That is it.
Thanks for your time!!! _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Understand that, but if exist something to be done to have the fix for the whole community will be better, don't u think?
Latest news, I connect to dom-u centos 6.5 x64 over vnc and is booting and got this after waiting:
xl console oerp-server PCI: Fatal: No config space access function found ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space ipmi_si: Could not set up I/O space Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.32-431.el6.x86_64 #1 Call Trace: [<ffffffff815271fa>] ? panic+0xa7/0x16f [<ffffffff81077622>] ? do_exit+0x862/0x870 [<ffffffff8118a865>] ? fput+0x25/0x30 [<ffffffff81077688>] ? do_group_exit+0x58/0xd0 [<ffffffff81077717>] ? sys_exit_group+0x17/0x20 [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b
Thanks.
I add the module to initrd, didn't fix the issue.
Can you post the full dmesg output please? Do you see 'xen-blkfront' being loaded on it?
At the end, is a bug ? _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
The issue is that I cannot connect to the dom-u to get the output, exist a way for this?
.snip..
I add the module to initrd, didn't fix the issue.
Can you post the full dmesg output please? Do you see 'xen-blkfront' being loaded on it?
The issue is that I cannot connect to the dom-u to get the output, exist a way for this?
You did it before didn't you?
On Tue, Jun 17, 2014 at 8:45 AM, Konrad Rzeszutek Wilk konrad.wilk@oracle.com wrote:
.snip..
I add the module to initrd, didn't fix the issue.
Can you post the full dmesg output please? Do you see 'xen-blkfront' being loaded on it?
The issue is that I cannot connect to the dom-u to get the output, exist a way for this?
You did it before didn't you? _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
The output u see was from dom-u Centos5, that one show us a different message:
(SMP-)alternatives turned off Brought up 1 CPUs checking if image is initramfs... it is Grant table initialized NET: Registered protocol family 16 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: 65536 (order: 7, 524288 bytes) TCP established hash table entries: 262144 (order: 10, 4194304 bytes) TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) TCP: Hash tables configured (established 262144 bind 65536) TCP reno registered audit: initializing netlink socket (disabled) type=2000 audit(1403020147.615:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API alg: No test for crc32c (crc32c-generic) ksign: Installing public key data Loading keyring - Added public key 691B840A64868995 - 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 brd: module loaded 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/51712 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0 Initalizing network drop monitor service Write protecting the kernel read-only data: 506k Red Hat nash version 5.1.19.6 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading jbd.ko module Loading ext3.ko module Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s.......... 240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 1) Loading dm-mod.ko module device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading dm-mem-cache.ko module Loading dm-region_hash.ko module Loading dm-message.ko module Loading dm-raid45.ko module device-mapper: dm-raid45: initialized v0.2594l Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!
This one? Centos 5.9x64 dom-u
-
Johnny Hughes -
Konrad Rzeszutek Wilk -
Periko Support