Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Xen>
  3. Devel
windows bluescreen after restore
amino7 at yahoo
Apr 30, 2007, 10:51 AM
Post #1 of 8 (162 views)
Permalink
Hi there,

I used 3.0.5 rc3 and rc4 to test windows save/restore.
Whenever I restore a win 2003 or an xp guest, the guest blue-screens.
Absolutely repeatable. This worked well with earlier unstable builds.

I added some of the logs below - what else can I provide to help
debugging this?

Regards,
Amin

qemu-dm log

domid: 4
qemu: the number of cpus is 1
Watching /local/domain/4/logdirty/next-active
qemu_map_cache_init nr_buckets = 10000
shared page at pfn 1ffff
buffered io page at pfn 1fffd
Time offset set 0
xs_read(): vncpasswd get error. /vm/83323cd4-5819-2db4-a7db-e3ea9d9da6a6/
vncpasswd.
cirrus_vga_load:re-enable vga acc.lfb_addr=0xf0000000, lfb_end=0xf0800000.
usb_mouse_load:add usb_tablet_event.
Triggered log-dirty buffer switch
I/O request not ready: 0, ptr: 0, port: c002, data: 4, count: 1, size: 1
reset requested in cpu_handle_ioreq.
Issued domain 4 reboot


xend.log

[2007-04-30 18:35:12 2798] DEBUG (XendDomainInfo:210) XendDomainInfo.restore(['domain', ['domid', '3'], ['on_crash', 'destroy'], ['uuid', '83323cd4-5819-2db4-a7db-e3ea9
d9da6a6'], ['bootloader_args'], ['vcpus', '1'], ['name', 'WinXP_1'], ['on_poweroff', 'destroy'], ['on_reboot', 'destroy'], ['bootloader'], ['maxmem', '512'], ['memory',
'512'], ['shadow_memory', '5'], ['vcpu_avail', '1'], ['cpu_weight', '256'], ['cpu_cap', '0'], ['features'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['
start_time', '1177950322.67'], ['cpu_time', '275.278881106'], ['online_vcpus', '1'], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['acpi', '1'], ['apic'
, '1'], ['boot', 'c'], ['device_model', '/usr/lib64/xen/bin/qemu-dm'], ['display', ':0'], ['isa', '0'], ['localtime', '0'], ['monitor', '0'], ['nographic', '0'], ['pae'
, '1'], ['rtc_timeoffset', '0'], ['stdvga', '0'], ['usb', '1'], ['usbdevice', 'tablet'], ['vncconsole', '1'], ['vncunused', '1'], ['xauthority', '/root/.xauthYGCR5r'],
['notes', ['SUSPEND_CANCEL', '1']]]], ['status', '2'], ['state', '-b----'], ['store_mfn', '131070'], ['device', ['vif', ['bridge', 'xenbr0'], ['uuid', '72626c56-91dd-bd
2f-de56-e978fae677da'], ['script', 'vif-bridge'], ['mac', '00:16:3e:00:00:aa'], ['type', 'ioemu'], ['backend', '0']]], ['device', ['vbd', ['uname', 'file:/nfs/xen/image
s/WinXP_1/xp_overlay.qcow'], ['uuid', '0ec69e37-3cb5-3241-217c-f7358cb76f3a'], ['mode', 'w'], ['dev', 'hda:disk'], ['backend', '0'], ['bootable', '1']]], ['device', ['v
kbd', ['backend', '0']]], ['device', ['vfb', ['uuid', '83ea558f-77b1-b977-aa0d-8e0cf4ec27c9'], ['vnclisten', '0.0.0.0'], ['location', '0.0.0.0:5900'], ['type', 'vnc'],
['display', ':0'], ['xauthority', '/root/.xauthYGCR5r']]], ['device', ['console', ['protocol', 'vt100'], ['location', '3'], ['uuid', '5cfa7dc4-bb05-a181-f1de-3d5d36f00a
69']]]])
[2007-04-30 18:35:12 2798] DEBUG (XendDomainInfo:1411) XendDomainInfo.constructDomain
[2007-04-30 18:35:12 2798] DEBUG (balloon:113) Balloon: 539380 KiB free; need 2048; done.
[2007-04-30 18:35:12 2798] DEBUG (XendDomain:434) Adding Domain: 4
[2007-04-30 18:35:12 2798] DEBUG (XendDomainInfo:1966) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '5', 'uuid': '83323cd4-5819-2db4-a7db-e3ea9d9da6a
6', 'on_reboot': 'destroy', 'start_time': '1177950322.67', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'destroy', 'vcpus': '1', 'vcpu_avail': '1',
'image': '(hvm (kernel /usr/lib/xen/boot/hvmloader) (acpi 1) (apic 1) (boot c) (device_model /usr/lib64/xen/bin/qemu-dm) (display :0) (isa 0) (localtime 0) (monitor 0)
(nographic 0) (pae 1) (rtc_timeoffset 0) (stdvga 0) (usb 1) (usbdevice tablet) (vncconsole 1) (vncunused 1) (xauthority /root/.xauthYGCR5r) (notes (SUSPEND_CANCEL 1)))'
, 'name': 'WinXP_1'}
[2007-04-30 18:35:12 2798] INFO (XendDomainInfo:1313) createDevice: vkbd : {'uuid': 'e75cc595-76a1-08a9-4145-1c21ca77820c', 'backend': '0'}
[2007-04-30 18:35:12 2798] DEBUG (DevController:115) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vkbd/4/0'} to /local/d
omain/4/device/vkbd/0.
[2007-04-30 18:35:12 2798] DEBUG (DevController:117) DevController: writing {'frontend-id': '4', 'domain': 'WinXP_1', 'frontend': '/local/domain/4/device/vkbd/0', 'stat
e': '1', 'online': '1'} to /local/domain/0/backend/vkbd/4/0.
[2007-04-30 18:35:12 2798] INFO (XendDomainInfo:1313) createDevice: vfb : {'other_config': {'vnclisten': '0.0.0.0', 'type': 'vnc', 'display': ':0', 'xauthority': '/root
/.xauthYGCR5r'}, 'xauthority': '/root/.xauthYGCR5r', 'vnclisten': '0.0.0.0', 'location': '0.0.0.0:5900', 'type': 'vnc', 'display': ':0', 'uuid': '83ea558f-77b1-b977-aa0
d-8e0cf4ec27c9'}
[2007-04-30 18:35:12 2798] DEBUG (DevController:115) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vfb/4/0'} to /local/do
main/4/device/vfb/0.
[2007-04-30 18:35:12 2798] DEBUG (DevController:117) DevController: writing {'domain': 'WinXP_1', 'frontend': '/local/domain/4/device/vfb/0', 'uuid': '83ea558f-77b1-b97
7-aa0d-8e0cf4ec27c9', 'vnclisten': '0.0.0.0', 'state': '1', 'location': '0.0.0.0:5900', 'online': '1', 'frontend-id': '4', 'type': 'vnc', 'display': ':0', 'xauthority':
'/root/.xauthYGCR5r'} to /local/domain/0/backend/vfb/4/0.
[2007-04-30 18:35:12 2798] INFO (XendDomainInfo:1313) createDevice: console : {'protocol': 'vt100', 'location': '3', 'uuid': '5cfa7dc4-bb05-a181-f1de-3d5d36f00a69'}
[2007-04-30 18:35:12 2798] DEBUG (DevController:115) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/console/4/0'} to /loca
l/domain/4/device/console/0.
[2007-04-30 18:35:12 2798] DEBUG (DevController:117) DevController: writing {'domain': 'WinXP_1', 'protocol': 'vt100', 'uuid': '5cfa7dc4-bb05-a181-f1de-3d5d36f00a69', '
frontend': '/local/domain/4/device/console/0', 'state': '1', 'location': '3', 'online': '1', 'frontend-id': '4'} to /local/domain/0/backend/console/4/0.
[2007-04-30 18:35:12 2798] INFO (XendDomainInfo:1313) createDevice: vbd : {'uuid': '0ec69e37-3cb5-3241-217c-f7358cb76f3a', 'bootable': 1, 'driver': 'paravirtualised', '
dev': 'hda:disk', 'uname': 'file:/nfs/xen/images/WinXP_1/xp_overlay.qcow', 'mode': 'w', 'backend': '0'}
[2007-04-30 18:35:12 2798] DEBUG (DevController:115) DevController: writing {'backend-id': '0', 'virtual-device': '768', 'device-type': 'disk', 'state': '1', 'backend':
'/local/domain/0/backend/vbd/4/768'} to /local/domain/4/device/vbd/768.
[2007-04-30 18:35:12 2798] DEBUG (DevController:117) DevController: writing {'domain': 'WinXP_1', 'frontend': '/local/domain/4/device/vbd/768', 'uuid': '0ec69e37-3cb5-3
241-217c-f7358cb76f3a', 'dev': 'hda', 'state': '1', 'params': '/nfs/xen/images/WinXP_1/xp_overlay.qcow', 'mode': 'w', 'online': '1', 'frontend-id': '4', 'type': 'file'}
to /local/domain/0/backend/vbd/4/768.
[2007-04-30 18:35:12 2798] INFO (XendDomainInfo:1313) createDevice: vif : {'bridge': 'xenbr0', 'uuid': '72626c56-91dd-bd2f-de56-e978fae677da', 'script': 'vif-bridge', '
mac': '00:16:3e:00:00:aa', 'type': 'ioemu', 'backend': '0'}
[2007-04-30 18:35:12 2798] DEBUG (DevController:115) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vif/4/0'} to /local/do
main/4/device/vif/0.
[2007-04-30 18:35:12 2798] DEBUG (DevController:117) DevController: writing {'bridge': 'xenbr0', 'domain': 'WinXP_1', 'handle': '0', 'uuid': '72626c56-91dd-bd2f-de56-e9
78fae677da', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/4/device/vif/0', 'mac': '00:16:3e:00:00:aa', 'online': '1', 'frontend-id'
: '4', 'type': 'ioemu'} to /local/domain/0/backend/vif/4/0.
[2007-04-30 18:35:12 2798] DEBUG (XendDomainInfo:824) Storing domain details: {'console/port': '3', 'name': 'WinXP_1', 'console/limit': '1048576', 'image/suspend-cancel
': '1', 'domid': '4', 'vm': '/vm/83323cd4-5819-2db4-a7db-e3ea9d9da6a6', 'cpu/0/availability': 'online', 'memory/target': '524288', 'control/platform-feature-multiproces
sor-suspend': '1', 'store/port': '2'}
[2007-04-30 18:35:12 2798] INFO (XendCheckpoint:191) restore hvm domain 4, apic=1, pae=1
[2007-04-30 18:35:12 2798] DEBUG (XendCheckpoint:201) restore:shadow=0x5, _static_max=0x20000000, _static_min=0x0,
[2007-04-30 18:35:12 2798] DEBUG (balloon:113) Balloon: 538344 KiB free; need 529408; done.
[2007-04-30 18:35:12 2798] DEBUG (XendCheckpoint:213) [xc_restore]: /usr/lib64/xen/bin/xc_restore 4 4 2 3 1 1 1
[2007-04-30 18:35:12 2798] INFO (XendCheckpoint:349) xc_domain_restore start: p2m_size = 100000
[2007-04-30 18:35:12 2798] INFO (XendCheckpoint:349) Reloading memory pages: 0%
[2007-04-30 18:35:20 2798] INFO (XendCheckpoint:349) Received all pages (0 races)
[2007-04-30 18:35:20 2798] INFO (XendCheckpoint:349) Restore exit with rc=0
[2007-04-30 18:35:20 2798] DEBUG (XendCheckpoint:320) store-mfn 131070
[2007-04-30 18:35:21 2798] DEBUG (XendDomainInfo:1595) XendDomainInfo.completeRestore
[2007-04-30 18:35:21 2798] DEBUG (image:330) args: boot, val: c
[2007-04-30 18:35:21 2798] DEBUG (image:330) args: fda, val: None
[2007-04-30 18:35:21 2798] DEBUG (image:330) args: fdb, val: None
[2007-04-30 18:35:21 2798] DEBUG (image:330) args: soundhw, val: None
[2007-04-30 18:35:21 2798] DEBUG (image:330) args: localtime, val: 0
[2007-04-30 18:35:21 2798] DEBUG (image:330) args: serial, val: None
[2007-04-30 18:35:21 2798] DEBUG (image:330) args: std-vga, val: 0
[2007-04-30 18:35:21 2798] DEBUG (image:330) args: isa, val: 0
[2007-04-30 18:35:21 2798] DEBUG (image:330) args: acpi, val: 1
[2007-04-30 18:35:21 2798] DEBUG (image:330) args: usb, val: 1
[2007-04-30 18:35:21 2798] DEBUG (image:330) args: usbdevice, val: tablet
[2007-04-30 18:35:21 2798] DEBUG (image:330) args: k, val: None
[2007-04-30 18:35:21 2798] INFO (image:445) spawning device models: /usr/lib64/xen/bin/qemu-dm [.'/usr/lib64/xen/bin/qemu-dm', '-d', '4', '-vcpus', '1', '-boot', 'c', '-
acpi', '-usb', '-usbdevice', 'tablet', '-domain-name', 'WinXP_1', '-net', 'nic,vlan=1,macaddr=00:16:3e:00:00:aa,model=rtl8139', '-net', 'tap,vlan=1,bridge=xenbr0', '-vn
cunused', '-vnclisten', '0.0.0.0', '-loadvm', '/tmp/xen.qemu-dm.4', '-vncviewer']
[2007-04-30 18:35:21 2798] INFO (image:449) device model pid: 5479
[2007-04-30 18:35:21 2798] DEBUG (XendDomainInfo:824) Storing domain details: {'console/port': '3', 'name': 'WinXP_1', 'console/limit': '1048576', 'vm': '/vm/83323cd4-5
819-2db4-a7db-e3ea9d9da6a6', 'domid': '4', 'image/suspend-cancel': '1', 'cpu/0/availability': 'online', 'memory/target': '524288', 'control/platform-feature-multiproces
sor-suspend': '1', 'store/ring-ref': '131070', 'store/port': '2'}
[2007-04-30 18:35:21 2798] DEBUG (XendDomainInfo:824) Storing domain details: {'console/port': '3', 'name': 'WinXP_1', 'console/limit': '1048576', 'vm': '/vm/83323cd4-5
819-2db4-a7db-e3ea9d9da6a6', 'domid': '4', 'image/suspend-cancel': '1', 'cpu/0/availability': 'online', 'memory/target': '524288', 'control/platform-feature-multiproces
sor-suspend': '1', 'store/ring-ref': '131070', 'store/port': '2'}
[2007-04-30 18:35:21 2798] DEBUG (XendDomainInfo:905) XendDomainInfo.handleShutdownWatch
[2007-04-30 18:35:21 2798] DEBUG (XendDomainInfo:1609) XendDomainInfo.completeRestore done
[2007-04-30 18:35:21 2798] DEBUG (DevController:148) Waiting for devices vif.
[2007-04-30 18:35:21 2798] DEBUG (DevController:153) Waiting for 0.
[2007-04-30 18:35:21 2798] DEBUG (DevController:539) hotplugStatusCallback /local/domain/0/backend/vif/4/0/hotplug-status.
[2007-04-30 18:35:21 2798] DEBUG (DevController:553) hotplugStatusCallback 1.
[2007-04-30 18:35:21 2798] DEBUG (DevController:148) Waiting for devices usb.
[2007-04-30 18:35:21 2798] DEBUG (DevController:148) Waiting for devices vbd.
[2007-04-30 18:35:21 2798] DEBUG (DevController:153) Waiting for 768.
[2007-04-30 18:35:21 2798] DEBUG (DevController:539) hotplugStatusCallback /local/domain/0/backend/vbd/4/768/hotplug-status.
[2007-04-30 18:35:21 2798] DEBUG (DevController:553) hotplugStatusCallback 1.
[2007-04-30 18:35:21 2798] DEBUG (DevController:148) Waiting for devices irq.
[2007-04-30 18:35:21 2798] DEBUG (DevController:148) Waiting for devices vkbd.
[2007-04-30 18:35:21 2798] DEBUG (DevController:148) Waiting for devices vfb.
[2007-04-30 18:35:21 2798] DEBUG (vfbif:94) skip waiting for HVM vfb
[2007-04-30 18:35:21 2798] DEBUG (DevController:148) Waiting for devices console.
[2007-04-30 18:35:21 2798] DEBUG (DevController:153) Waiting for 0.
[2007-04-30 18:35:21 2798] DEBUG (DevController:148) Waiting for devices pci.
[2007-04-30 18:35:21 2798] DEBUG (DevController:148) Waiting for devices ioports.
[2007-04-30 18:35:21 2798] DEBUG (DevController:148) Waiting for devices tap.
[2007-04-30 18:35:21 2798] DEBUG (DevController:148) Waiting for devices vtpm.




_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Re: windows bluescreen after restore [ In reply to ]
Tim.Deegan at xensource
May 1, 2007, 1:59 AM
Post #2 of 8 (149 views)
Permalink
Hi,

At 17:51 +0000 on 30 Apr (1177955485), Amin wrote:
> I used 3.0.5 rc3 and rc4 to test windows save/restore.
> Whenever I restore a win 2003 or an xp guest, the guest blue-screens.
> Absolutely repeatable. This worked well with earlier unstable builds.

Is this with all 2k3/xp guests? It's working OK for me. What flavour
of xen and dom0 are you using? (i.e. the output of 'xm info')
What stop code is printed on the bluescreens?
Does reinstalling windows help at all?

Cheers,

Tim.

--
Tim Deegan <Tim.Deegan@xensource.com>, XenSource UK Limited
Registered office c/o EC2Y 5EB, UK; company number 05334508

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Re: windows bluescreen after restore [ In reply to ]
amino7 at yahoo
May 1, 2007, 2:54 PM
Post #3 of 8 (149 views)
Permalink
Hi Tim,

information below. Reinstalling windows didn't help. It happens with all 2k3 and xp guests.
IRQL_NOT_LESS_OR_EQUAL
*** STOP: 0x0000000A (0x00000018, 0x00000002, 0x00000000, 0x80523F59)

Another time, I got this one:
*** STOP: 0x0000008E (0xC0000005, 0x805433C0, 0xF8DC3A74, 0x00000000)

Thanks
Amin


xm info:
release : 2.6.18-xen
version : #1 SMP Mon Apr 30 17:10:57 CEST 2007
machine : x86_64
nr_cpus : 2
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2800
hw_caps : bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001
total_memory : 4095
free_memory : 526
xen_major : 3
xen_minor : 0
xen_extra : -unstable
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : Sat Mar 31 19:02:09 2007 +0100 14687:8f9ca49175ce
cc_compiler : gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)
cc_compile_by : amin
cc_compile_domain :
cc_compile_date : Mon Apr 2 19:33:17 CEST 2007
xend_config_format : 4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
RE: Re: windows bluescreen after restore [ In reply to ]
Ian.Pratt at cl
May 1, 2007, 3:37 PM
Post #4 of 8 (152 views)
Permalink
> information below. Reinstalling windows didn't help. It happens with
> all 2k3 and xp guests.
> IRQL_NOT_LESS_OR_EQUAL
> *** STOP: 0x0000000A (0x00000018, 0x00000002, 0x00000000, 0x80523F59)

Are you doing save/restore cycles on the same machine, or moving the image between machines?

At what point does the guest crash? Immediately after the restore, or a few seconds later?

When you have a saved image that crashes on restore, it would be interesting to try restoring the image again and see if the guest crashes again (is the error the same?). Repeat several times. This should give us a clue as to whether the error is 'baked in' to the saved image, or occurs during restore.

Thanks,
Ian


> Thanks
> Amin
>
>
> xm info:
> release : 2.6.18-xen
> version : #1 SMP Mon Apr 30 17:10:57 CEST 2007
> machine : x86_64
> nr_cpus : 2
> nr_nodes : 1
> sockets_per_node : 1
> cores_per_socket : 2
> threads_per_core : 1
> cpu_mhz : 2800
> hw_caps :
> bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001
> total_memory : 4095
> free_memory : 526
> xen_major : 3
> xen_minor : 0
> xen_extra : -unstable
> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler : credit
> xen_pagesize : 4096
> platform_params : virt_start=0xffff800000000000
> xen_changeset : Sat Mar 31 19:02:09 2007 +0100
> 14687:8f9ca49175ce
> cc_compiler : gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)
> cc_compile_by : amin
> cc_compile_domain :
> cc_compile_date : Mon Apr 2 19:33:17 CEST 2007
> xend_config_format : 4
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
RE: Re: windows bluescreen after restore [ In reply to ]
guy at neocleus
May 2, 2007, 4:25 AM
Post #5 of 8 (156 views)
Permalink
IRQL_NOT_LESS_OR_EQUAL happens when a kernel thread with high priority tries to access a virtual address which is paged to the disk (since the paging mechanism in windows runs in a lower priority of the thread). Most of the chances that this is around paging...

If you can reproduce the bug and it happens any time that you do save/restore, I would suggest to try to tun the guest with paging disabled (System Properties -> Advanced -> Performace [Settings] -> Advanced -> Virtual Memory [Change] -> Select "No paging file") and then try to do save&resote.

STOP 0x8E is KERNEL_MODE_EXCEPTION_NOT_HANDLED and could be a side effect...

Thanks,
Guy.

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Ian Pratt
> Sent: Wednesday, May 02, 2007 1:38 AM
> To: Amin; xen-devel@lists.xensource.com
> Subject: RE: [Xen-devel] Re: windows bluescreen after restore
>
> > information below. Reinstalling windows didn't help. It
> happens with
> > all 2k3 and xp guests.
> > IRQL_NOT_LESS_OR_EQUAL
> > *** STOP: 0x0000000A (0x00000018, 0x00000002, 0x00000000,
> 0x80523F59)
>
> Are you doing save/restore cycles on the same machine, or
> moving the image between machines?
>
> At what point does the guest crash? Immediately after the
> restore, or a few seconds later?
>
> When you have a saved image that crashes on restore, it would
> be interesting to try restoring the image again and see if
> the guest crashes again (is the error the same?). Repeat
> several times. This should give us a clue as to whether the
> error is 'baked in' to the saved image, or occurs during restore.
>
> Thanks,
> Ian
>
>
> > Thanks
> > Amin
> >
> >
> > xm info:
> > release : 2.6.18-xen
> > version : #1 SMP Mon Apr 30 17:10:57 CEST 2007
> > machine : x86_64
> > nr_cpus : 2
> > nr_nodes : 1
> > sockets_per_node : 1
> > cores_per_socket : 2
> > threads_per_core : 1
> > cpu_mhz : 2800
> > hw_caps :
> > bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001
> > total_memory : 4095
> > free_memory : 526
> > xen_major : 3
> > xen_minor : 0
> > xen_extra : -unstable
> > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p
> hvm-3.0-x86_32
> > hvm-3.0-x86_32p hvm-3.0-x86_64
> > xen_scheduler : credit
> > xen_pagesize : 4096
> > platform_params : virt_start=0xffff800000000000
> > xen_changeset : Sat Mar 31 19:02:09 2007 +0100
> > 14687:8f9ca49175ce
> > cc_compiler : gcc version 4.1.1 20070105 (Red
> Hat 4.1.1-51)
> > cc_compile_by : amin
> > cc_compile_domain :
> > cc_compile_date : Mon Apr 2 19:33:17 CEST 2007
> > xend_config_format : 4
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
RE: Re: windows bluescreen after restore [ In reply to ]
Mats.Petersson at amd
May 2, 2007, 4:42 AM
Post #6 of 8 (158 views)
Permalink
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Guy Zana
> Sent: 02 May 2007 12:26
> To: Ian Pratt; Amin; xen-devel@lists.xensource.com
> Subject: RE: [Xen-devel] Re: windows bluescreen after restore
>
> IRQL_NOT_LESS_OR_EQUAL happens when a kernel thread with high
> priority tries to access a virtual address which is paged to
> the disk (since the paging mechanism in windows runs in a
> lower priority of the thread). Most of the chances that this
> is around paging...

Or it's doing a wait or some such at a IRQL (priority level) that is
higher than what the scheduler runs at. In fact, the reason that you
can't page something in at high IRQL has to do with the fact hat the
scheduler is blocked at this level, and the page-in mechanism is a
separate process, which means that it would be necessary to reschedule
in the kernel. Since any "wait" operation will cause rescheduling, those
are also blocked at this level.

Most likely is that the guest memory mapping or some such got very
confused.

>
> If you can reproduce the bug and it happens any time that you
> do save/restore, I would suggest to try to tun the guest with
> paging disabled (System Properties -> Advanced -> Performace
> [Settings] -> Advanced -> Virtual Memory [Change] -> Select
> "No paging file") and then try to do save&resote.
>
> STOP 0x8E is KERNEL_MODE_EXCEPTION_NOT_HANDLED and could be a
> side effect...

Also points to a memory mapping (or other memory corruption) problem in
my experience.

[.I did two years of graphics driver development, and I've managed to get
my fair share of both of these bugchecks].

--
Mats
>
> Thanks,
> Guy.
>
> > -----Original Message-----
> > From: xen-devel-bounces@lists.xensource.com
> > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of
> Ian Pratt
> > Sent: Wednesday, May 02, 2007 1:38 AM
> > To: Amin; xen-devel@lists.xensource.com
> > Subject: RE: [Xen-devel] Re: windows bluescreen after restore
> >
> > > information below. Reinstalling windows didn't help. It
> > happens with
> > > all 2k3 and xp guests.
> > > IRQL_NOT_LESS_OR_EQUAL
> > > *** STOP: 0x0000000A (0x00000018, 0x00000002, 0x00000000,
> > 0x80523F59)
> >
> > Are you doing save/restore cycles on the same machine, or
> > moving the image between machines?
> >
> > At what point does the guest crash? Immediately after the
> > restore, or a few seconds later?
> >
> > When you have a saved image that crashes on restore, it would
> > be interesting to try restoring the image again and see if
> > the guest crashes again (is the error the same?). Repeat
> > several times. This should give us a clue as to whether the
> > error is 'baked in' to the saved image, or occurs during restore.
> >
> > Thanks,
> > Ian
> >
> >
> > > Thanks
> > > Amin
> > >
> > >
> > > xm info:
> > > release : 2.6.18-xen
> > > version : #1 SMP Mon Apr 30 17:10:57 CEST 2007
> > > machine : x86_64
> > > nr_cpus : 2
> > > nr_nodes : 1
> > > sockets_per_node : 1
> > > cores_per_socket : 2
> > > threads_per_core : 1
> > > cpu_mhz : 2800
> > > hw_caps :
> > > bfebfbff:20100800:00000000:00000180:0000e43d:00000000:00000001
> > > total_memory : 4095
> > > free_memory : 526
> > > xen_major : 3
> > > xen_minor : 0
> > > xen_extra : -unstable
> > > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p
> > hvm-3.0-x86_32
> > > hvm-3.0-x86_32p hvm-3.0-x86_64
> > > xen_scheduler : credit
> > > xen_pagesize : 4096
> > > platform_params : virt_start=0xffff800000000000
> > > xen_changeset : Sat Mar 31 19:02:09 2007 +0100
> > > 14687:8f9ca49175ce
> > > cc_compiler : gcc version 4.1.1 20070105 (Red
> > Hat 4.1.1-51)
> > > cc_compile_by : amin
> > > cc_compile_domain :
> > > cc_compile_date : Mon Apr 2 19:33:17 CEST 2007
> > > xend_config_format : 4
> > >
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xensource.com
> > > http://lists.xensource.com/xen-devel
> >
>



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Re: Re: windows bluescreen after restore [ In reply to ]
Tim.Deegan at xensource
May 2, 2007, 5:05 AM
Post #7 of 8 (149 views)
Permalink
At 07:25 -0400 on 02 May (1178090752), Guy Zana wrote:
> IRQL_NOT_LESS_OR_EQUAL happens when a kernel thread with high priority tries to access a virtual address which is paged to the disk (since the paging mechanism in windows runs in a lower priority of the thread). Most of the chances that this is around paging...
>
> If you can reproduce the bug and it happens any time that you do save/restore, I would suggest to try to tun the guest with paging disabled (System Properties -> Advanced -> Performace [Settings] -> Advanced -> Virtual Memory [Change] -> Select "No paging file") and then try to do save&resote.
>
> STOP 0x8E is KERNEL_MODE_EXCEPTION_NOT_HANDLED and could be a side effect...

Both of these stop codes are cause by the kernel taking a page fault
when it didn't expect one (at a higher TPR level than the PF handler, or
in non-paged memory). This is probably because either CPU state
(CR3/CR4/EFER) or memory (guest pagetables) have been corrupted by the
save/restore, so the shadow code sees garbage in the guest's pagetables
and passes a pagefault to the guest.

Tim.

--
Tim Deegan <Tim.Deegan@xensource.com>, XenSource UK Limited
Registered office c/o EC2Y 5EB, UK; company number 05334508

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Re: windows bluescreen after restore [ In reply to ]
amino7 at yahoo
May 2, 2007, 6:41 AM
Post #8 of 8 (150 views)
Permalink
Hi Ian,

I do the save/restore on the same machine, and the image crashed
immediately after restore. And restoring over and over again just crashed
consistently.

A few hours ago, I uninstalled everything from my FC6, redownloaded and
recompiled once again, and for some reason both rc4 and latest unstable
are working now.

I did 7 save/restore cycles on XP. In one of the restores, explorer
crashed - but came up again. Don't know if this is caused by xen, or just
plain windows.

So.... sorry about taking up your time!

cu
Amin


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

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal