[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] XEN-4.1.1 and linux kernel 3.0-rc5



Can't start systemï

On Tue, Jul 5, 2011 at 3:11 AM, Dipl.-Ing. Thomas Wagner
<t.wagner@xxxxxxxx> wrote:
> I am trying to get XEN-4.1.1 running with linux kernel 3.0-rc5
>
> System:
> Hardware: HP DL585 G2
> openSuse 11.4 + last available packages for XEN
>
> Following packages are installed:
> zeus:~ # rpm -q -a |grep xen
> xen-libs-4.1.1_02-145.1.x86_64
> kernel-xen-base-2.6.39.2-3.1.x86_64
> xen-4.1.1_02-145.1.x86_64
> kernel-xen-2.6.39.2-3.1.x86_64
> xen-tools-4.1.1_02-145.1.x86_64
>
> zeus:~ # rpm -q -a |grep virt
> libvirt-client-0.9.2-136.1.x86_64
> libvirt-python-0.9.2-136.1.x86_64
> virt-utils-1.1.5-21.1.x86_64
> virt-viewer-0.3.1-23.4.x86_64
> virt-manager-0.8.7-53.1.x86_64
> libvirt-0.9.2-136.1.x86_64
>
>
> These XEN-udev rules are active:
>
> SUBSYSTEM=="xen-backend", KERNEL=="tap*", RUN+="/etc/xen/scripts/blktap
> $env{ACTION}"
> SUBSYSTEM=="xen-backend", KERNEL=="vbd*", RUN+="/etc/xen/scripts/block
> $env{ACTION}"
> SUBSYSTEM=="xen-backend", KERNEL=="vtpm*", RUN+="/etc/xen/scripts/vtpm
> $env{ACTION}"
> SUBSYSTEM=="xen-backend", KERNEL=="vif2-*", RUN+="/etc/xen/scripts/vif2
> $env{ACTION}"
> SUBSYSTEM=="xen-backend", KERNEL=="vif-*", ACTION=="online",
> RUN+="/etc/xen/scripts/vif-setup online type_if=vif"
> SUBSYSTEM=="xen-backend", KERNEL=="vif-*", ACTION=="offline",
> RUN+="/etc/xen/scripts/vif-setup offline type_if=vif"
> SUBSYSTEM=="xen-backend", KERNEL=="vscsi*", RUN+="/etc/xen/scripts/vscsi
> $env{ACTION}"
> SUBSYSTEM=="xen-backend", ACTION=="remove",
> RUN+="/etc/xen/scripts/xen-hotplug-cleanup"
> KERNEL=="evtchn", NAME="xen/%k"
> SUBSYSTEM=="xen", KERNEL=="blktap[0-9]*", NAME="xen/%k", MODE="0600"
> SUBSYSTEM=="blktap2", KERNEL=="blktap[0-9]*", NAME="xen/blktap-2/%k",
> MODE="0600"
> KERNEL=="blktap-control", NAME="xen/blktap-2/control", MODE="0600"
> KERNEL=="gntdev", NAME="xen/%k", MODE="0600"
> KERNEL=="pci_iomul", NAME="xen/%k", MODE="0600"
> KERNEL=="tapdev[a-z]*", NAME="xen/blktap-2/tapdev%m", MODE="0600"
> SUBSYSTEM=="net", KERNEL=="tap*", ACTION=="add",
> RUN+="/etc/xen/scripts/vif-setup $env{ACTION} type_if=tap"
> KERNELS=="xen", KERNEL=="xvd*", SUBSYSTEM=="block", OPTIONS+="last_rule"
>
>
> ===================================
>
> /etc/init.d/xencommons
>
> I have modified this startscript for the new naming convention of the xen
> modules.
>
> do_start () {
> Â Â Â Âlocal time=0
> Â Â Â Âlocal timeout=30
>
> Â Â Â Â# Load XEN backend modules
> Â Â Â Â# NB: They could be loaded later, e.g. when dom0 hotplug events
> occur,
> Â Â Â Â# but for now it's safest to have them loaded here.
> Â Â Â Âmodprobe evtchn 2>/dev/null || true
> Â Â Â Âmodprobe gntdev 2>/dev/null || true
> Â Â Â Âmodprobe blktap 2>/dev/null || true
> Â Â Â Âmodprobe blkbk 2>/dev/null || true
> Â Â Â Âmodprobe netbk 2>/dev/null || true
> Â Â Â Âmodprobe usbbk 2>/dev/null || true
> Â Â Â Â# xenblk (frontend module) is needed in dom0, allowing it to use
> vbds
> Â Â Â Âmodprobe xenblk 2>/dev/null || true
>
> Â Â Â Â# THOMAS
> Â Â Â Âmodprobe xen-evtchn 2>/dev/null || true
> Â Â Â Âmodprobe xenfs 2>/dev/null || true
> Â Â Â Âmodprobe xen-gntdev 2>/dev/null || true
> Â Â Â Âmodprobe xen-gntalloc 2>/dev/null || true
> Â Â Â Âmodprobe xen-alloc 2>/dev/null || true
> Â Â Â Âmodprobe xen-blkfront 2>/dev/null || true
> Â Â Â Â#modprobe xen_wdt 2>/dev/null || true
> Â Â Â Âmodprobe xen-netfront 2>/dev/null || true
> Â Â Â Âmodprobe xenbus_probe_frontend 2>/dev/null || true
> Â Â Â Âmodprobe xen-platform-pci 2>/dev/null || true
> Â Â Â Âmodprobe xen-pcifront 2>/dev/null || true
> Â Â Â Âmodprobe xen-fbfront 2>/dev/null || true
> Â Â Â Âmodprobe xen-kbdfront 2>/dev/null || true
>
>
> After running this script following kernel modules are loaded
>
> zeus:~ # lsmod |grep xen
> xen_netfront      16627 Â0
> xen_gntalloc      Â3968 Â0
> xen_gntdev       Â5782 Â0
> xen_evtchn       Â4823 Â1
> xen_blkfront      11517 Â0
> xenbus_probe_frontend   2521 Â2 xen_netfront,xen_blkfront,[permanent]
> xenfs          9563 Â1
>
> In syslog these lines appear:
>
> Jul Â4 18:34:37 zeus xenstored: Checking store complete.
> Jul Â4 18:34:37 zeus kernel: XENBUS: Unable to read cpu state
>
>
> After starting the next part of XEN with
> /etc/init.d/xend start
>
> I get these lines in syslog.
>
> Jul Â4 18:36:26 zeus BLKTAPCTRL[5491]: blktapctrl.c:868: blktapctrl: v1.0.0
> Jul Â4 18:36:26 zeus BLKTAPCTRL[5491]: blktapctrl.c:870: Found driver: [raw
> image (aio)]
> Jul Â4 18:36:26 zeus BLKTAPCTRL[5491]: blktapctrl.c:870: Found driver: [raw
> image (sync)]
> Jul Â4 18:36:26 zeus BLKTAPCTRL[5491]: blktapctrl.c:870: Found driver:
> [vmware image (vmdk)]
> Jul Â4 18:36:26 zeus BLKTAPCTRL[5491]: blktapctrl.c:870: Found driver:
> [ramdisk image (ram)]
> Jul Â4 18:36:26 zeus BLKTAPCTRL[5491]: blktapctrl.c:870: Found driver: [qcow
> disk (qcow)]
> Jul Â4 18:36:26 zeus BLKTAPCTRL[5491]: blktapctrl.c:870: Found driver:
> [qcow2 disk (qcow2)]
> Jul Â4 18:36:26 zeus BLKTAPCTRL[5491]: blktapctrl.c:870: Found driver: [raw
> image (cdrom)]
> Jul Â4 18:36:26 zeus BLKTAPCTRL[5491]: blktapctrl_linux.c:86: blktap0 open
> failed
> Jul Â4 18:36:26 zeus BLKTAPCTRL[5491]: blktapctrl.c:938: couldn't open
> blktap interface
> Jul Â4 18:36:26 zeus BLKTAPCTRL[5491]: blktapctrl.c:1001: Unable to start
> blktapctrl
>
> ==================================
>
> If I try to start a vm which was created with opensuse 11.4 "out of the box"
> I get these lines in syslog
>
>
> Jul Â4 18:37:47 zeus logger: /etc/xen/scripts/block: Writing
> backend/vbd/1/51712/hotplug-error Path closed or removed during hotplug add:
> backend/vbd/1/51712 state: 1 backend/vbd/1/51712/hotplug-status error to
> xenstore.
> Jul Â4 18:37:47 zeus logger: /etc/xen/scripts/block: Path closed or removed
> during hotplug add: backend/vbd/1/51712 state: 1
> Jul Â4 18:38:04 zeus logger: /etc/xen/scripts/xen-hotplug-cleanup:
> XENBUS_PATH=backend/console/1/0
> Jul Â4 18:38:04 zeus logger: /etc/xen/scripts/xen-hotplug-cleanup:
> XENBUS_PATH=backend/vfb/1/0
> Jul Â4 18:38:04 zeus logger: /etc/xen/scripts/xen-hotplug-cleanup:
> XENBUS_PATH=backend/vkbd/1/0
>
>
> /var/log/xen/qemu-dm-template.log
>
> domid: 1
> Warning: vlan 0 is not connected to host network
> char device redirected to /dev/pts/6
> /usr/src/packages/BUILD/xen-4.1.1-testing/tools/ioemu-dir/hw/xen_blktap.c:70
> 4: Init blktap pipes
> xs_read(): target get error. /local/domain/1/target.
> xs_read(): vncpasswd get error.
> /vm/7fdf20a8-08b1-8d01-09e9-cfe8ca12de7d-4/vncpasswd.
> char device redirected to /dev/pts/7
>
> =======================================
>
> zeus:~ # xm dmesg
> Â__ Â__ Â Â Â Â Â Â_ Â_ Â Â_ Â _ Â Â ___ ____ Â Â _ _ Â_ Â____ Â _
> Â\ \/ /___ _ __ Â | || | Â/ | / | Â / _ \___ \ Â / | || || ___| / |
> Â\ Â// _ \ '_ \ Â| || |_ | | | | Â| | | |__) |__| | || ||___ \ | |
> Â/ Â\ Â__/ | | | |__ Â _|| |_| | Â| |_| / __/|__| |__ Â _|__) || |
> Â/_/\_\___|_| |_| Â Â|_|(_)_(_)_|___\___/_____| Â|_| Â|_||____(_)_|
> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â |_____|
> (XEN) Xen version 4.1.1_02-145.1 (abuild@) (gcc version 4.5.1 20101208
> [gcc-4_5-branch revision 167585] (SUSE Linux) ) Fri Jul Â1 19:43:28 UTC 2011
> (XEN) Latest ChangeSet: 23079
> (XEN) Bootloader: GNU GRUB 0.97
> (XEN) Command line:
> (XEN) Video information:
> (XEN) ÂVGA is text mode 80x25, font 8x16
> (XEN) ÂVBE/DDC methods: V2; EDID transfer time: 2 seconds
> (XEN) Disc information:
> (XEN) ÂFound 1 MBR signatures
> (XEN) ÂFound 1 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN) Â0000000000000000 - 000000000009f400 (usable)
> (XEN) Â000000000009f400 - 00000000000a0000 (reserved)
> (XEN) Â00000000000f0000 - 0000000000100000 (reserved)
> (XEN) Â0000000000100000 - 000000007fd4e000 (usable)
> (XEN) Â000000007fd4e000 - 000000007fd56000 (ACPI data)
> (XEN) Â000000007fd56000 - 000000007fd57000 (usable)
> (XEN) Â000000007fd57000 - 0000000080000000 (reserved)
> (XEN) Â00000000e0000000 - 00000000f0000000 (reserved)
> (XEN) Â00000000fec00000 - 00000000fed00000 (reserved)
> (XEN) Â00000000fee00000 - 00000000fee10000 (reserved)
> (XEN) Â00000000ffc00000 - 0000000100000000 (reserved)
> (XEN) Â0000000100000000 - 000000067ffff000 (usable)
> (XEN) ACPI: RSDP 000F4F00, 0024 (r2 HP Â Â)
> (XEN) ACPI: XSDT 7FD4ED80, 0074 (r1 HP   ProLiant    Â2  ?   162E)
> (XEN) ACPI: FACP 7FD4EE00, 00F4 (r3 HP Â Â A07 Â Â Â Â Â Â 2 Â ? Â Â 162E)
> (XEN) ACPI: DSDT 7FD4EF00, 4A6D (r1 HP Â Â Â Â DSDT Â Â Â Â1 INTL 20030228)
> (XEN) ACPI: FACS 7FD4E100, 0040
> (XEN) ACPI: SPCR 7FD4E140, 0050 (r1 HP Â Â SPCRRBSU Â Â Â Â1 Â ? Â Â 162E)
> (XEN) ACPI: HPET 7FD4E1C0, 0038 (r1 HP   ProLiant    Â2  ?   162E)
> (XEN) ACPI: SPMI 7FD4E200, 0040 (r5 HP   ProLiant    Â1  ?   162E)
> (XEN) ACPI: ERST 7FD4E240, 01D0 (r1 HP   ProLiant    Â1  ?   162E)
> (XEN) ACPI: FFFF 7FD4E440, 00C6 (r1 HP   ProLiant    Â2       0)
> (XEN) ACPI: SRAT 7FD4E600, 01A0 (r1 AMD Â ÂFAM_F_10 Â Â Â Â2 AMD Â Â Â Â 1)
> (XEN) ACPI: FFFF 7FD4EA00, 0176 (r1 HP   ProLiant    Â1  ?   162E)
> (XEN) ACPI: BERT 7FD4EB80, 0030 (r1 HP   ProLiant    Â1  ?   162E)
> (XEN) ACPI: HEST 7FD4EBC0, 0170 (r1 HP   ProLiant    Â1  ?   162E)
> (XEN) System RAM: 24572MB (25162676kB)
> (XEN) Domain heap initialised DMA width 31 bits
> (XEN) ERST table is invalid
> (XEN) Found and enabled local APIC!
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Detected 2612.045 MHz processor.
> (XEN) Initing memory sharing.
> (XEN) AMD-Vi: IOMMU not found!
> (XEN) I/O virtualisation disabled
> (XEN) Platform timer is 25.000MHz HPET
> (XEN) Allocated console ring of 16 KiB.
> (XEN) HVM: ASIDs enabled.
> (XEN) SVM: Supported advanced features:
> (XEN) Â- none
> (XEN) HVM: SVM enabled
> (XEN) Brought up 1 CPUs
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) ÂXen Âkernel: 64-bit, lsb, compat32
> (XEN) ÂDom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1701000
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN) ÂDom0 alloc.: Â 0000000230000000->0000000238000000 (6152948 pages to
> be allocated)
> (XEN) ÂInit. ramdisk: 000000067ef16000->000000067fdffc00
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN) ÂLoaded kernel: ffffffff81000000->ffffffff81701000
> (XEN) ÂInit. ramdisk: ffffffff81701000->ffffffff825eac00
> (XEN) ÂPhys-Mach map: ffffffff825eb000->ffffffff85523ef0
> (XEN) ÂStart info: Â Âffffffff85524000->ffffffff855244b4
> (XEN) ÂPage tables: Â ffffffff85525000->ffffffff85554000
> (XEN) ÂBoot stack: Â Âffffffff85554000->ffffffff85555000
> (XEN) ÂTOTAL: Â Â Â Â ffffffff80000000->ffffffff85800000
> (XEN) ÂENTRY ADDRESS: ffffffff81468200
> (XEN) Dom0 has maximum 1 VCPUs
> (XEN) Scrubbing Free RAM: .done.
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> (XEN) Xen is relinquishing VGA console.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to
> Xen)
> (XEN) Freed 232kB init memory.
> (XEN) traps.c:2456:d0 Domain attempted WRMSR 00000000c0010004 from
> 0x0000d7be79555450 to 0x000000000000abcd.
> (XEN) ERROR: Unable to locate IOAPIC for GSI 1
> (XEN) No IOAPIC for GSI 1
> (XEN) ERROR: Unable to locate IOAPIC for GSI 12
> (XEN) No IOAPIC for GSI 12
> (XEN) ERROR: Unable to locate IOAPIC for GSI 4
> (XEN) No IOAPIC for GSI 4
> (XEN) ERROR: Unable to locate IOAPIC for GSI 11
> (XEN) No IOAPIC for GSI 11
> (XEN) ERROR: Unable to locate IOAPIC for GSI 10
> (XEN) No IOAPIC for GSI 10
> (XEN) ERROR: Unable to locate IOAPIC for GSI 11
> (XEN) No IOAPIC for GSI 11
> (XEN) ERROR: Unable to locate IOAPIC for GSI 10
> (XEN) No IOAPIC for GSI 10
> (XEN) ERROR: Unable to locate IOAPIC for GSI 5
> (XEN) No IOAPIC for GSI 5
> (XEN) ERROR: Unable to locate IOAPIC for GSI 11
> (XEN) No IOAPIC for GSI 11
> (XEN) ERROR: Unable to locate IOAPIC for GSI 10
> (XEN) No IOAPIC for GSI 10
> (XEN) ERROR: Unable to locate IOAPIC for GSI 10
> (XEN) No IOAPIC for GSI 10
> (XEN) ERROR: Unable to locate IOAPIC for GSI 10
> (XEN) No IOAPIC for GSI 10
> (XEN) ERROR: Unable to locate IOAPIC for GSI 10
> (XEN) No IOAPIC for GSI 10
> (XEN) ERROR: Unable to locate IOAPIC for GSI 11
> (XEN) No IOAPIC for GSI 11
> (XEN) ERROR: Unable to locate IOAPIC for GSI 11
> (XEN) No IOAPIC for GSI 11
> (XEN) ERROR: Unable to locate IOAPIC for GSI 11
> (XEN) No IOAPIC for GSI 11
> (XEN) ERROR: Unable to locate IOAPIC for GSI 11
> (XEN) No IOAPIC for GSI 11
> (XEN) traps.c:2456:d1 Domain attempted WRMSR 00000000c0010004 from
> 0x0000d7be79555450 to 0x000000000000abcd.
>
>
>
>
> Does anybody know what I am doing wrong?
>
> regards
> Thomas
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>



-- 
Best Regards
August

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.