Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
All vm are setting to timing shutdown. when starting vm, get BOSD of 0x0000005C, restart still get this error. Send shutdown commond and start again , the guest start normally.
Version-Release number of selected component (if applicable):
RHEV-guest-tools-3.5.4
qemu-kvm-rhev-2.1.2-23
seabios-bin-1.7.5
How reproducible:
Probability
Steps to Reproduce:
1./usr/libexec/qemu-kvm -name nce1a042b-f053-419c-86fe-39cd2f47c29a -S -machine rhel6.5.0,accel=kvm,usb=off -cpu SandyBridge,+vmx,hv_relaxed -m 10240 -realtime mlock=off -smp 4,maxcpus=32,sockets=16,cores=2,threads=1 -uuid ce1a042b-f053-419c-86fe-39cd2f47c29a -smbios type=1,manufacturer=SdcOS,product=SdcOS Hypervisor,version=2.1-Alpaca,serial=00000000-0000-0000-0000-AC1F6B625C4C,uuid=ce1a042b-f053-419c-86fe-39cd2f47c29a -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/nce1a042b-f053-419c-86fe-39cd2f47c29a.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2018-08-21T10:32:39,clock=vm,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -drive if=none,security_uuid=*********,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/b43257eb-4867-4766-aa05-e00261e98954/145817f8-23b2-4ac7-b37c-ea71930a12c5/images/b30cbe8e-e6b8-4e64-bfe0-db004003bc1d/971bca65-b766-48d9-aa10-3de9687939c7,if=none,security_uuid=*********,id=drive-virtio-disk0,format=qcow2,serial=b30cbe8e-e6b8-4e64-bfe0-db004003bc1d,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=37,id=hostnet0,vhost=on,vhostfd=38 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:36:60:3d,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/ce1a042b-f053-419c-86fe-39cd2f47c29a.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/ce1a042b-f053-419c-86fe-39cd2f47c29a.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -spice tls-port=5905,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,streaming-video=filter,disable-copy-paste-toclient,disable-copy-paste-toguest,disable-agent-file-xfer,seamless-migration=on -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,vgamem_mb=16,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x5 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on
windebug dump file:
Loading Dump File [C:\Users\a\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: srv*d:\symbolslocal*http://msdl.microsoft.com/download/symbols;D:\symbolslocal
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03c66000 PsLoadedModuleList = 0xfffff800`03eabe90
Debug session time: Mon Jul 30 09:13:32.602 2018 (UTC + 8:00)
System Uptime: 0 days 0:00:07.696
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
The context is partially valid. Only x86 user-mode context is available.
The wow64exts extension must be loaded to access 32-bit state.
.load wow64exts will do this if you haven't loaded it already.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck BE, {fffff8800551d210, 28b837161, fffff8800265af70, b}
Page 24a69f not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
16.0: kd:x86> bugcheck
^ Operation not supported by current debuggee error in 'bugcheck'
16.0: kd:x86> !bugcheck
No export bugcheck found
16.0: kd:x86> dd
00000000`00000000 ???????? ???????? ???????? ????????
00000000`00000010 ???????? ???????? ???????? ????????
00000000`00000020 ???????? ???????? ???????? ????????
00000000`00000030 ???????? ???????? ???????? ????????
00000000`00000040 ???????? ???????? ???????? ????????
00000000`00000050 ???????? ???????? ???????? ????????
00000000`00000060 ???????? ???????? ???????? ????????
00000000`00000070 ???????? ???????? ???????? ????????
16.0: kd:x86> r
The context is partially valid. Only x86 user-mode context is available.
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=00000000
eip=00000000 esp=00000000 ebp=00000000 iopl=0 nv up di pl nz na po nc
cs=0000 ss=0000 ds=0000 es=0000 fs=0000 gs=0000 efl=00000000
00000000`00000000 ?? ???
16.0: kd:x86> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8800551d210, Virtual address for the attempted write.
Arg2: 000000028b837161, PTE contents.
Arg3: fffff8800265af70, (reserved)
Arg4: 000000000000000b, (reserved)
Debugging Details:
------------------
Page 24a69f not present in the dump file. Type ".hh dbgerr004" for details
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xBE
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000
STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 0x0
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: INVALID_KERNEL_CONTEXT
Followup: MachineOwner
---------
Additional info:
(In reply to Yan Vugenfirer from comment #6)
> Hello,
>
> Can you please provide the dump file?
>
> At the beginning of the analysis that was added to BZ there is no call stack
> ("kb" command).
>
> Thanks!
I have upload dump file， 3 parts zip files
Thanks！
1. Does not look like original qemu. The dump file shows: "SYSTEM_MANUFACTURER: SdcOS SYSTEM_PRODUCT_NAME: SdcOS Hypervisor SYSTEM_VERSION: 2.1-Alpaca"
2. Extremely old drivers, build 104 (from 2013)
3. The system is not updated at all (there are a lot of KB fixing problems in original Win7 SP1)
4. Dump is problematic a little, to see something need ".effmach amd64", but anyway the reason of failure is not seen
5. The reporter does not respond, the repro procedure is unclear
6. Suggest to close, if needed open another one with updated drivers and operating system
Comment 15Red Hat Bugzilla
2023-09-14 04:33:24 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days