dom0 kernel bug at shutdown of hvm windows server

Dec 5 12:27:53 sigma kernel: [ 367.025191] kernel BUG at /build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/arch/i386/mm/hypervisor.c:167!
Dec 5 12:27:53 sigma kernel: [ 367.025330] invalid opcode: 0000 [#1]
Dec 5 12:27:53 sigma kernel: [ 367.025436] SMP
Dec 5 12:27:53 sigma kernel: [ 367.025712] Modules linked in: xt_physdev iptable_filter ip_tables x_tables af_packet bridge video battery container sbs button dock ac ext3 jbd mbcache loop coretemp ipmi_devintf ipmi_si ipmi_msghandler i2c_i801 i2c_core parport_pc lp parport psmouse serio_raw pcspkr serial_core shpchp pci_hotplug ipv6 evdev reiserfs ata_piix sg sd_mod ata_generic libata ehci_hcd uhci_hcd usbcore mptsas mptscsih mptbase scsi_transport_sas scsi_mod e1000 dm_mirror dm_snapshot dm_mod thermal processor fan fuse apparmor commoncap
Dec 5 12:27:53 sigma kernel: [ 367.031161] CPU: 0
Dec 5 12:27:53 sigma kernel: [ 367.031162] EIP: 0061:[xen_pgd_pin+96/112] Not tainted VLI
Dec 5 12:27:53 sigma kernel: [ 367.031163] EFLAGS: 00010282 (2.6.22-14-xen #1)
Dec 5 12:27:53 sigma kernel: [ 367.031495] EIP is at xen_pgd_pin+0x60/0x70
Dec 5 12:27:53 sigma kernel: [ 367.031607] eax: ffffffea ebx: ea9b3ee4 ecx: 00000001 edx: 00000000
Dec 5 12:27:53 sigma kernel: [ 367.031721] esi: 00007ff0 edi: 00000000 ebp: c0cd39f0 esp: ea9b3ee4
Dec 5 12:27:53 sigma kernel: [ 367.031835] ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0069
Dec 5 12:27:53 sigma kernel: [ 367.031947] Process block (pid: 7856, ti=ea9b2000 task=c0cd2530 task.ti=ea9b2000)
Dec 5 12:27:53 sigma kernel: [ 367.032064] Stack: 00000002 0007e4fb 004fb000 00009f60 eac9c1b8 c0114aef c6171380 c0114b22
Dec 5 12:27:53 sigma kernel: [ 367.032969] 01200011 c01209cf eac9cd2c 00000000 ea9b3f8c c13a73b4 c61713b4 c0cd3ab0
Dec 5 12:27:53 sigma kernel: [ 367.033869] ea9b3fb8 bf8b4b3c 00000000 e9064e00 c0cd39f0 c6171380 c13a7380 eac9c1c4
Dec 5 12:27:53 sigma kernel: [ 367.034765] Call Trace:
Dec 5 12:27:53 sigma kernel: [ 367.034976] [__pgd_pin+47/64] __pgd_pin+0x2f/0x40
Dec 5 12:27:53 sigma kernel: [ 367.035174] [mm_pin+34/48] mm_pin+0x22/0x30
Dec 5 12:27:53 sigma kernel: [ 367.035373] [copy_process+4191/4608] copy_process+0x105f/0x1200
Dec 5 12:27:53 sigma kernel: [ 367.035582] [do_fork+118/560] do_fork+0x76/0x230
Dec 5 12:27:53 sigma kernel: [ 367.035782] [copy_to_user+48/96] copy_to_user+0x30/0x60
Dec 5 12:27:53 sigma kernel: [ 367.035984] [sys_clone+54/64] sys_clone+0x36/0x40
Dec 5 12:27:53 sigma kernel: [ 367.036186] [syscall_call+7/11] syscall_call+0x7/0xb
Dec 5 12:27:53 sigma kernel: [ 367.036387] [wait_for_completion_interruptible+304/336] wait_for_completion_interruptible+0x130/0x150
Dec 5 12:27:53 sigma kernel: [ 367.036592] =======================
Dec 5 12:27:53 sigma kernel: [ 367.036700] Code: 89 e3 b9 01 00 00 00 31 d2 be f0 7f 00 00 e8 88 83 fe ff 85 c0 78 14 83 c4 0c 5b 5e c3 39 c2 72 cd 0f 0b eb fe 8d b6 00 00 00 00 <0f> 0b eb fe 8d b6 00 00 00 00 8d bf 00 00 00 00 56 89 c2 53 83
Dec 5 12:27:53 sigma kernel: [ 367.042395] EIP: [xen_pgd_pin+96/112] xen_pgd_pin+0x60/0x70 SS:ESP 0069:ea9b3ee4
Dec 5 12:27:54 sigma kerne...

qemu log when using qemu-dm device model (not qemu-dm.debug):

domid: 5
qemu: the number of cpus is 1
Watching /local/domain/5/logdirty/next-active
qemu_map_cache_init nr_buckets = 4000
shared page at pfn 3ffff
buffered io page at pfn 3fffd
Time offset set 0
xs_read(): vncpasswd get error. /vm/b5cf9b34-cb6f-0c08-53ec-2a0fb4b09c94/vncpasswd.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Triggered log-dirty buffer switch
xs_write(/vm/b5cf9b34-cb6f-0c08-53ec-2a0fb4b09c94/rtc/timeoffset, rtc/timeoffset): write error
xs_write(/vm/b5cf9b34-cb6f-0c08-53ec-2a0fb4b09c94/rtc/timeoffset, rtc/timeoffset): write error
xs_write(/vm/b5cf9b34-cb6f-0c08-53ec-2a0fb4b09c94/rtc/timeoffset, rtc/timeoffset): write error
xs_write(/vm/b5cf9b34-cb6f-0c08-53ec-2a0fb4b09c94/rtc/timeoffset, rtc/timeoffset): write error
shutdown requested in cpu_handle_ioreq
Issued domain 5 poweroff

I was experiencing a similar problem with a hvm windows XP domU.

Specifying a smaller pool of memory for my dom0 appears to have made it go away for now.

ie. in my grub configuration I added a dom0_mem parameter to the end of my kernel line:

title Xen 3.1 / Ubuntu 7.10, kernel 2.6.22-14-xen
root (hd0,0)
kernel /xen-3.1.gz com2=115200 console=com2l dom0_mem=524288
module /vmlinuz-2.6.22-14-xen root=/dev/mapper/store-chalmers--root ro console=tty0 console=xvc xencons=xvc swiotlb=64
module /initrd.img-2.6.22-14-xen
quiet

Hasn't failed yet, although I have not done exhaustive testing. Just thought I'd share a potential workaround.

Hi novaki,

The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. Care to test the linux-image-2.6.24-11-xen and verify if this is still an issue? Thanks.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".