Identical Win2K3 domU's. One panics dom0, other runs fine

Identical Win2K3 domU's. One panics dom0, other runs fine

[Don Faulkner]

[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]

Hi there. Sorry for interrupting, but I was referred here from xen-users.
(See 
http://lists.xensource.com/archives/html/xen-users/2008-04/msg00081.html 
for reference)

I'm running Xubuntu 7.10 (Feisty) and using Feisty's xen packages. (xen 
version 3.1).

I have two hvm domUs, each running Windows 2003. The first runs fine. It 
installed, booted, and ran with no problems. For the second domU, I 
duplicated the config file and changed the name, Ethernet MAC, and disk. 
The second domU boots, but cannot finish the Win2003 install without a 
dom0 kernel panic. It doesn't matter whether the first domU is running 
or not, or what order they're started in. The first domU continues to 
run fine.

Any help would be appreciated. I'm attaching the configs from both 
domU's as well as the relevant portion of my syslog regarding the last 
panic I had.

cepheus is the working domU
perseus is the broken domU  (causing the panic)
xen dom0 panic.txt is the syslog excerpt.

Thanks for listening.
-- 
Don Faulkner

[-- Attachment #2: xen dom0 panic.txt --]
[-- Type: text/plain, Size: 4156 bytes --]

Mar 26 16:59:58 legion kernel: [25706.054808] BUG: unable to handle kernel NULL pointer dereference at virtual address 0000011c
Mar 26 16:59:58 legion kernel: [25706.054822]  printing eip:
Mar 26 16:59:58 legion kernel: [25706.054824] c019bdad
Mar 26 16:59:58 legion kernel: [25706.054830] 1e04e000 -> *pde = 00000001:27ed6001
Mar 26 16:59:58 legion kernel: [25706.054833] 07cd6000 -> *pme = 00000000:00000000
Mar 26 16:59:58 legion kernel: [25706.054838] Oops: 0000 [#1]
Mar 26 16:59:58 legion kernel: [25706.054840] SMP
Mar 26 16:59:58 legion kernel: [25706.054845] Modules linked in: loop xt_tcpudp xt_physdev tun iptable_filter ip_tables x_tables af_packet bridge ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi scsi_transport_iscsi ppdev video button dock sbs ac container battery parport_pc lp parport pcspkr serial_core shpchp pci_hotplug ipv6 evdev ext3 jbd mbcache ata_generic sg usbhid hid sd_mod mptsas mptscsih mptbase scsi_transport_sas ata_piix bnx2 qla3xxx qla4xxx libata scsi_mod uhci_hcd ehci_hcd usbcore thermal processor fan fuse apparmor commoncap
Mar 26 16:59:58 legion kernel: [25706.054933] CPU:    0
Mar 26 16:59:58 legion kernel: [25706.054934] EIP:    0061:[drop_buffers+29/240]    Not tainted VLI
Mar 26 16:59:58 legion kernel: [25706.054935] EFLAGS: 00010296   (2.6.22-14-xen #1)
Mar 26 16:59:58 legion kernel: [25706.054945] EIP is at drop_buffers+0x1d/0xf0
Mar 26 16:59:58 legion kernel: [25706.054949] eax: 00000000   ebx: e01a7814   ecx: c1db36a0   edx: 0000011c
Mar 26 16:59:58 legion kernel: [25706.054952] esi: c0437178   edi: c1db36a0   ebp: c1db36b8   esp: c04cdddc
Mar 26 16:59:58 legion kernel: [25706.054956] ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0069
Mar 26 16:59:58 legion kernel: [25706.054960] Process kswapd0 (pid: 202, ti=c04cc000 task=de082000 task.ti=c04cc000)
Mar 26 16:59:58 legion kernel: [25706.054963] Stack: c019bb44 c0176e75 c019bb44 e01a7814 c04cde04 e01a7814 c1db36a0 00000000
Mar 26 16:59:58 legion kernel: [25706.054976]        c1db36b8 c019beb6 00000000 c1db36a0 c03c0c00 00000001 c015b8c3 c04cdf14
Mar 26 16:59:58 legion kernel: [25706.054988]        00000000 c04cdf04 c04cdf0c c03c118c c03c1180 c04cdf84 0000000f 00000000
Mar 26 16:59:58 legion kernel: [25706.055000] Call Trace:
Mar 26 16:59:58 legion kernel: [25706.055004]  [free_buffer_head+20/48] free_buffer_head+0x14/0x30
Mar 26 16:59:58 legion kernel: [25706.055010]  [kmem_cache_free+133/240] kmem_cache_free+0x85/0xf0
Mar 26 16:59:58 legion kernel: [25706.055017]  [free_buffer_head+20/48] free_buffer_head+0x14/0x30
Mar 26 16:59:58 legion kernel: [25706.055032]  [try_to_free_buffers+54/144] try_to_free_buffers+0x36/0x90
Mar 26 16:59:58 legion kernel: [25706.055042]  [shrink_inactive_list+1971/2320] shrink_inactive_list+0x7b3/0x910
Mar 26 16:59:58 legion kernel: [25706.055072]  [__pagevec_release+21/32] __pagevec_release+0x15/0x20
Mar 26 16:59:58 legion kernel: [25706.055079]  [shrink_active_list+993/1280] shrink_active_list+0x3e1/0x500
Mar 26 16:59:58 legion kernel: [25706.055109]  [shrink_zone+180/288] shrink_zone+0xb4/0x120
Mar 26 16:59:58 legion kernel: [25706.055121]  [kswapd+828/1136] kswapd+0x33c/0x470
Mar 26 16:59:58 legion kernel: [25706.055140]  [autoremove_wake_function+0/80] autoremove_wake_function+0x0/0x50
Mar 26 16:59:58 legion kernel: [25706.055150]  [complete+64/96] complete+0x40/0x60
Mar 26 16:59:58 legion kernel: [25706.055160]  [kswapd+0/1136] kswapd+0x0/0x470
Mar 26 16:59:58 legion kernel: [25706.055167]  [kthread+66/112] kthread+0x42/0x70
Mar 26 16:59:58 legion kernel: [25706.055172]  [kthread+0/112] kthread+0x0/0x70
Mar 26 16:59:58 legion kernel: [25706.055179]  [kernel_thread_helper+7/16] kernel_thread_helper+0x7/0x10
Mar 26 16:59:58 legion kernel: [25706.055189]  =======================
Mar 26 16:59:58 legion kernel: [25706.055191] Code: e3 5b 5e c3 8d 76 00 8d bc 27 00 00 00 00 55 57 89 c7 56 53 83 ec 14 89 54 24 10 8b 00 f6 c4 08 0f 84 ce 00 00 00 8b 77 0c 89 f2 <8b> 02 f6 c4 08 74 0d 8b 47 10 85 c0 74 06 f0 0f ba 68 3c 14 8b
Mar 26 16:59:58 legion kernel: [25706.055253] EIP: [drop_buffers+29/240] drop_buffers+0x1d/0xf0 SS:ESP 0069:c04cdddc

[-- Attachment #3: cepheus --]
[-- Type: text/plain, Size: 444 bytes --]

kernel = "/usr/lib/xen-ioemu-3.1/boot/hvmloader"
builder='hvm'
memory = 512
name = "cepheus"
vcpus=1
pae=0
acpi=0
apic=0
#cpus = ""
vif = 	[ 
	'type=ioemu, mac=00:16:3E:59:7E:F3, ip=10.5.4.18, bridge=xenbr0' 
	]
disk = 	[ 
	'phy:/dev/sdb,ioemu:hda,w', 
	]
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'destroy'
device_model = '/usr/lib/xen-ioemu-3.1/bin/qemu-dm'
boot='c'
sdl=0
vnc=1
vncviewer=0
stdvga=0
serial='pty'
ne2000=0

[-- Attachment #4: perseus --]
[-- Type: text/plain, Size: 510 bytes --]

kernel = "/usr/lib/xen-ioemu-3.1/boot/hvmloader"
builder='hvm'
memory = 512
name = "perseus"
vcpus=1
pae=1
acpi=1
apic=0
#cpus = ""
vif = 	[ 
	'type=ioemu, mac=00:16:3E:11:AC:6E, ip=10.5.4.19, bridge=xenbr0' 
	]
disk = 	[ 
	'phy:/dev/sdc,ioemu:hda,w', 
        'file:/var/xenimages/win2k3_r2_x86_disc1.iso,hdc:cdrom,r'
	]
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'destroy'
device_model = '/usr/lib/xen-ioemu-3.1/bin/qemu-dm'
boot='d'
sdl=0
vnc=1
vncviewer=0
stdvga=0
serial='pty'
ne2000=0

[-- Attachment #5: Type: text/plain, Size: 138 bytes --]

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

Re: Identical Win2K3 domU's. One panics dom0, other runs fine

[Keir Fraser]

I'd suggest trying a different dom0, e.g., build your own taken from:
 # hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg

 -- Keir

On 4/4/08 18:56, "Don Faulkner" <dfaulkner@enginst.org> wrote:

> Hi there. Sorry for interrupting, but I was referred here from xen-users.
> (See 
> http://lists.xensource.com/archives/html/xen-users/2008-04/msg00081.html
> for reference)
> 
> I'm running Xubuntu 7.10 (Feisty) and using Feisty's xen packages. (xen
> version 3.1).
> 
> I have two hvm domUs, each running Windows 2003. The first runs fine. It
> installed, booted, and ran with no problems. For the second domU, I
> duplicated the config file and changed the name, Ethernet MAC, and disk.
> The second domU boots, but cannot finish the Win2003 install without a
> dom0 kernel panic. It doesn't matter whether the first domU is running
> or not, or what order they're started in. The first domU continues to
> run fine.
> 
> Any help would be appreciated. I'm attaching the configs from both
> domU's as well as the relevant portion of my syslog regarding the last
> panic I had.
> 
> cepheus is the working domU
> perseus is the broken domU  (causing the panic)
> xen dom0 panic.txt is the syslog excerpt.
> 
> Thanks for listening.