|
|
|
|
|
|
|
|
|
|
xen-bugs
[Xen-bugs] xen 3.4 + linux 2.6.18.8 problems on booting domU's
Hi,
I have an PC with 4GB Ram and proc E8400, the problem is that centos 5.3 + xen 3.4 gives me headache.
I've tried xen 3.4 from the curent repository, also 3.4 the stable version + 2.6.18 hg in all combinations I get the follwing:
After install when I try to setup an domU with centos images for install (vmlinux/initrd), when it tries the video card and starting headless I get am blank screen and i must destroy the domU. If I try to start it again it gives me:
root@domU test]# xm create -c test.cfg Using config file "./test.cfg". Error: Not enough memory is available, and dom0 cannot be shrunk any further
I paste here the confs and errors from logs:
title Xen 3.4 / Linux 2.6.18.8 kernel /boot/xen.gz console=vga
module /boot/vmlinuz-2.6.18.8-xen root=LABEL=HD1-/ ro console=tty0 module /boot/initrd-2.6.18-xen..img
[root@domU test]# cat test.cfg # -*- mode: python; -*- #============================================================================ # Python configuration setup for 'xm create'. # This script sets the parameters used when a domain is created using 'xm create'. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #============================================================================
import os, re
arch_libdir = 'lib' arch = os.uname()[4] if os.uname()[0] == 'Linux' and re.search('64', arch): arch_libdir = 'lib64'
kernel = "/home/kits/vms/test/vmlinuz" builder='hvm'
ramdisk
= "/home/kits/vms/test/initrd.img" name = "test" maxmem = 256 memory = 256 vcpus = 1
disk = [ 'file:/home/kits/vms/test/test.disk,hda,w' ] vif = [ "bridge=eth1" ] device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' serial='pty' root = "/dev/xvda1 ro" extra="fastboot xencons=tty1"
physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is deprecated and breaks other things, it will be removed in January 2007. See Documentation/feature-removal-schedule.txt for details. This doesn't affect you in case you're using it for purely bridged traffic. blktap: ring-ref 770, event-channel 7, protocol 1 (x86_32-abi) BUG: unable to handle kernel NULL pointer dereference at virtual address 00000004 printing eip: c01655db 2c143000 -> *pde = 00000001:02eb8001 2bcb8000
-> *pme = 00000000:00000000 Oops: 0000 [#1] SMP Modules linked in: xt_state xt_physdev bridge ipv6 ip_conntrack_netbios_ns ip_conntrack nfnetlink iptable_filter ip_tables x_tables binfmt_misc sr_mod dm_mirror dm_multipath dm_mod video thermal sbs processor i2c_ec fan container button battery asus_acpi ac parport_pc lp parport nvram 8139too tsdev snd_hda_intel snd_hda_codec snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm evdev snd_timer snd soundcore pcspkr shpchp pci_hotplug snd_page_alloc ohci1394 ieee1394 sg i2c_i801 i2c_core usb_storage 8139cp mii ahci libusual 8250_pnp serio_raw ide_cd usbhid 8250 cdrom serial_core rtc ide_disk mptspi mptscsih scsi_transport_spi mptbase ata_piix libata sd_mod scsi_mod uhci_hcd ohci_hcd ehci_hcd usbcore ext3 jbd CPU: 1 EIP: 0061:[<c01655db>] Not tainted VLI EFLAGS:
00010202 (2.6.18.8-xen #1) EIP is at get_user_pages+0x6b/0x460 eax: 00000004 ebx: 00000040 ecx: 040a44fb edx: eb718800 esi: ec1eb2dc edi: 00000000 ebp: b7b74000 esp: eb05bd14 ds: 007b es: 007b ss: 0069 Process tapdisk (pid: 4470, ti=eb05a000 task=ec0b6bd0 task.ti=eb05a000) Stack: eb05bd18 00000000 ec2d0e40 ec0b6bd0 00000003 00000000 00000022 00000000 00000fff 00000000 00000040 00000001 00000000 ec011400 c01a0792 00000001 00000001 00000000 ec0114b8 00000000 00000000 00001000 00000000 00000000 Call Trace: [<c01a0792>] dio_get_page+0xc2/0x190 [<c01a1557>] __blockdev_direct_IO+0x597/0x1020 [<ee022382>] ext3_direct_IO+0xa2/0x1e0 [ext3] [<ee020560>] ext3_get_block+0x0/0x100
[ext3] [<c0155e77>] generic_file_direct_IO+0x87/0x140 [<c0156252>] __generic_file_aio_read+0x192/0x270 [<c0175f8a>] cache_alloc_refill+0x7a/0x5a0 [<c0156375>] generic_file_aio_read+0x45/0x60 [<c019973f>] aio_pread+0x3f/0xa0 [<c0199700>] aio_pread+0x0/0xa0 [<c019a425>] aio_run_iocb+0xa5/0x1b0 [<c0199c86>] __aio_get_req+0xa6/0x130 [<c0199700>] aio_pread+0x0/0xa0 [<c019ad09>] io_submit_one+0x159/0x320 [<c019b44a>] sys_io_submit+0x9a/0xf0 [<c01059bf>] syscall_call+0x7/0xb Code: ea e8 8a 34 00 00 85 c0 89 c6 0f 84 11 02 00 00 8b 48 18 f7 c1 00 00 00 04 74 75 8b 50 50 89 e8 2b 46 04 c1 e8 0c c1 e0 02 03 02 <8b> 00 85 c0 74 5f 8b 54 24 48 85 d2 74 1c 89 c2 8b 4c 24 48 8b EIP: [<c01655db>] get_user_pages+0x6b/0x460 SS:ESP 0069:eb05bd14 <7>vif3.0: no
IPv6 routers present PM: Removing info for xen-backend:console-3-0
|
_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-bugs] xen 3.4 + linux 2.6.18.8 problems on booting domU's,
John Joe <=
|
|
|
|
|