Re: [CentOS-virt] understanding problems
This is wrong. A bridge does not need an ip address itself to pass traffic from interface A to interface C, so it could look like this: hw interface a --- bridge b --- vm interface c 192.168.1.3 none192.168.1.4 Keep in mind that bridging takes place on layer 2: https://en.wikipedia.org/wiki/Bridging_%28networking%29 HTH Am 14.06.2014 08:41, schrieb lee: But when you attach them to bridges and don't have IP addresses on the bridges, then they are unreachable. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] understanding problems
On 06/16/2014 08:55 PM, Sven Kieske wrote: A bridge does not need an ip address itself to pass traffic from interface A to interface C, Correct, but... so it could look like this: hw interface a --- bridge b --- vm interface c 192.168.1.3 none192.168.1.4 Wrong. In the above configuration the IP address 192.168.1.3 won't be recognized. That IP needs to be on the bridge in order to work on the host. This is what the OP was referring to with this statement: Am 14.06.2014 08:41, schrieb lee: But when you attach them to bridges and don't have IP addresses on the bridges, then they are unreachable. Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Preferred method of provisioning VM images
On 06/10/2014 05:21 PM, Lars Kurth wrote: == #4 Cloud Image from Cloud Image SIG == We could rely on pre-built cloud images from the Cloud Images SIG. People could just download the cloud image once it's done and customize it, rather than installing / building their own. Advantages: seems easy Disadvantages: coordination with Cloud Images SIG. May not be flexible enough We ship a test/devel grade CentOS-6-x86_64-pv image ( well, its a qcow2 image, should work for pvhvm as well, the fstab is label driven ).[1] The biggest problem in doing pre-baked images is the instance metadata. We need to find an easy way to get network settings into the instance and the root password ( or key ), and finally - in some cases, console redirection/setup, but i dont think the console is a deal breaker or a big deal. The network and access credentials however are. In a typical cloud environ this info would come from the cloud controller's metadata service; on a typical virtualised setup though this becomes an issue ( and isnt really Xen specific ). We could work around this by making some assumptions, we could 'own' dnsmasq and ensure that either libvirt is running and doing dhcp, otherwise we do the dhcp with some sane defaults, or we setup a script to 'instantiate image', which asks how the user wants to setup the instance ( pvhvm, hvm, pv ), the root password or key to use, and the network settings ( and if this is run on the dom0, we could even ask what bridge or device to connect with as well as the settings ).[2] Ofcourse, having these images pushed from here mean that clouds or virtualised environs that have metadata services are able to just-use the image as is, not needing any more tooling etc. And we can easily push monthly image updates and when things like heartbleed come around, there is a single place we need to update. - KB [1]: http://cloud.centos.org/centos/6/devel/ [2] might need to pull in all of libguestfs to make the changes, which in turn has its own challenges if run inside a virtualised environ. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Centos 6.5 Xen Stock cannot run dom-u PCI: Fatal: - ipmi_si
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-de...@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
Re: [CentOS-virt] Centos 6.5 Xen Stock cannot run dom-u PCI: Fatal: - ipmi_si
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-de...@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:
Re: [CentOS-virt] Centos 6.5 Xen Stock cannot run dom-u PCI: Fatal: - ipmi_si
--- 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.w...@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
Re: [CentOS-virt] Are xen and centos incompatible?
On Sat, Jun 14, 2014 at 09:07:51AM +0200, lee wrote: Konrad Rzeszutek Wilk konrad.w...@oracle.com writes: Hm, xen kinda makes the cpus and their power management invisible, too: root@heimdall:~# xenpm get-cpufreq-para [CPU0] failed to get cpufreq parameter [...] root@heimdall:~# xenpm get-cpufreq-states root@heimdall:~# So I guess it could as well make it so that lspci doesn't show passed-out devices. I am wondering if you are using an older kernel. The xen-acpi-processor driver should be loaded which would give the C and P states to the hypervisor. Which in turn would result in those above commands providing the right data. Linux heimdall 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux This is what comes in Debian. Unfortunately, this kernel crashes when I'm copying data to a domU NFS server over the network :(( I need to find out how to get some useful information out of it to make a bug report. How do I know whether the xen-acpi-processor driver is loaded or not? lsmod But it looks like v3.4 and later were the kernels that started having this driver. That would explain why it does not exist as you are using 3.2. BTW, getting some info in dmesg might be nice, like a message saying xen-pciback: device 06:00.0 can be passed through to guests. We could You just need to boot with 'debug' - and it should tell you that a device is being assigned to another guest (when assigning). Also at bootup it will tell you that it is seizinging. Just do 'dmesg | grep pciback' and you will get it. Ok, I enabled debugging. Maybe that also helps to get some more info about the crashes. actually see right away if it did work or not. That a device disappears isn't too great as indication, especially not when lspci still lists it. Of course, you could use the command (which I don't remember) to show devices that can be passed through. But that may just work as well as Such as xl or xm pci-list-assignable? yes 'xenpm get-cpufreq-states': Apparently, there aren't any CPUs ... See if xen-acpi-processor is loaded or built in. Unless it's called processor, it doesn't seem to exist: root@heimdall:~# lsmod |grep proc processor 28149 1 acpi_cpufreq thermal_sys18040 1 processor root@heimdall:~# grep -i proces /boot/config-3.2.0-4-amd64 |less root@heimdall:~# find /lib/modules/3.2.0-4-amd64/ -name *proces* /lib/modules/3.2.0-4-amd64/kernel/drivers/acpi/processor.ko root@heimdall:~# find /lib/modules/3.2.0-4-amd64/ -name *xen* /lib/modules/3.2.0-4-amd64/kernel/drivers/net/xen-netfront.ko /lib/modules/3.2.0-4-amd64/kernel/drivers/net/xen-netback /lib/modules/3.2.0-4-amd64/kernel/drivers/net/xen-netback/xen-netback.ko /lib/modules/3.2.0-4-amd64/kernel/drivers/net/ethernet/qlogic/netxen /lib/modules/3.2.0-4-amd64/kernel/drivers/net/ethernet/qlogic/netxen/netxen_nic.ko /lib/modules/3.2.0-4-amd64/kernel/drivers/watchdog/xen_wdt.ko /lib/modules/3.2.0-4-amd64/kernel/drivers/xen /lib/modules/3.2.0-4-amd64/kernel/drivers/xen/xen-gntalloc.ko /lib/modules/3.2.0-4-amd64/kernel/drivers/xen/xen-gntdev.ko /lib/modules/3.2.0-4-amd64/kernel/drivers/xen/xen-evtchn.ko /lib/modules/3.2.0-4-amd64/kernel/drivers/xen/xen-pciback /lib/modules/3.2.0-4-amd64/kernel/drivers/xen/xen-pciback/xen-pciback.ko /lib/modules/3.2.0-4-amd64/kernel/drivers/xen/xenfs /lib/modules/3.2.0-4-amd64/kernel/drivers/xen/xenfs/xenfs.ko /lib/modules/3.2.0-4-amd64/kernel/drivers/block/xen-blkfront.ko /lib/modules/3.2.0-4-amd64/kernel/drivers/block/xen-blkback /lib/modules/3.2.0-4-amd64/kernel/drivers/block/xen-blkback/xen-blkback.ko /lib/modules/3.2.0-4-amd64/kernel/drivers/pci/xen-pcifront.ko root@heimdall:~# grep -i proces /boot/config-3.2.0-4-amd64 CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y # Processor type and features CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_PROCESSOR_AGGREGATOR=m # Audio decoders, processors and mixers root@heimdall:~# grep -i xen /boot/config-3.2.0-4-amd64 CONFIG_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=128 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set CONFIG_MICROCODE_XEN=y CONFIG_PCI_XEN=y CONFIG_XEN_PCIDEV_FRONTEND=m CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_XEN_BLKDEV_BACKEND=m CONFIG_NETXEN_NIC=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_NETDEV_BACKEND=m CONFIG_INPUT_XEN_KBDDEV_FRONTEND=y CONFIG_HVC_XEN=y CONFIG_XEN_WDT=m CONFIG_XEN_FBDEV_FRONTEND=y # Xen driver support CONFIG_XEN_BALLOON=y #
Re: [CentOS-virt] Centos 6.5 Xen Stock cannot run dom-u PCI: Fatal: - ipmi_si
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-de...@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
Re: [CentOS-virt] Centos 6.5 Xen Stock cannot run dom-u PCI: Fatal: - ipmi_si
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-de...@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 signature.asc Description: OpenPGP digital signature ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Centos 6.5 Xen Stock cannot run dom-u PCI: Fatal: - ipmi_si
On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk konrad.w...@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-de...@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. ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Centos 6.5 Xen Stock cannot run dom-u PCI: Fatal: - ipmi_si
On Mon, Jun 16, 2014 at 10:46 AM, Periko Support pheriko.supp...@gmail.com wrote: On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk konrad.w...@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-de...@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!!! ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Centos 6.5 Xen Stock cannot run dom-u PCI: Fatal: - ipmi_si
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.supp...@gmail.com wrote: On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk konrad.w...@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-de...@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
Re: [CentOS-virt] Centos 6.5 Xen Stock cannot run dom-u PCI: Fatal: - ipmi_si
On Mon, Jun 16, 2014 at 10:55 AM, Konrad Rzeszutek Wilk konrad.w...@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.supp...@gmail.com wrote: On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk konrad.w...@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-de...@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? ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Centos 6.5 Xen Stock cannot run dom-u PCI: Fatal: - ipmi_si
On Mon, Jun 16, 2014 at 11:10 AM, Periko Support pheriko.supp...@gmail.com wrote: On Mon, Jun 16, 2014 at 10:55 AM, Konrad Rzeszutek Wilk konrad.w...@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.supp...@gmail.com wrote: On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk konrad.w...@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-de...@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: [815271fa] ? panic+0xa7/0x16f [81077622] ? do_exit+0x862/0x870 [8118a865] ? fput+0x25/0x30 [81077688] ? do_group_exit+0x58/0xd0 [81077717] ? sys_exit_group+0x17/0x20 [8100b072] ? system_call_fastpath+0x16/0x1b Thanks. ___ CentOS-virt
Re: [CentOS-virt] Centos 6.5 Xen Stock cannot run dom-u PCI: Fatal: - ipmi_si
On Mon, Jun 16, 2014 at 11:34 AM, Periko Support pheriko.supp...@gmail.com wrote: On Mon, Jun 16, 2014 at 11:10 AM, Periko Support pheriko.supp...@gmail.com wrote: On Mon, Jun 16, 2014 at 10:55 AM, Konrad Rzeszutek Wilk konrad.w...@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.supp...@gmail.com wrote: On Mon, Jun 16, 2014 at 10:37 AM, Konrad Rzeszutek Wilk konrad.w...@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-de...@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: [815271fa] ? panic+0xa7/0x16f [81077622] ? do_exit+0x862/0x870 [8118a865] ? fput+0x25/0x30 [81077688] ? do_group_exit+0x58/0xd0 [81077717] ? sys_exit_group+0x17/0x20 [8100b072] ?
