[Bug 1846816] Re: Booting error on AIX 6.1 "Illegal Trap Instruction Interrupt in Kernel""
qemu-system-ppc64 should support AIX 5.3/6.1/7.1. If those OSes don't
have virtio, then provide another way which simulates the machine's way
to support the disk accessing.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1846816
Title:
Booting error on AIX 6.1 "Illegal Trap Instruction Interrupt in
Kernel""
Status in QEMU:
Won't Fix
Bug description:
# ls -ltr
total 8750584
-rw-rw-r-- 1 linux linux 4274997248 Oct 4 18:33 AIX.vol1.iso
-rw-rw-r-- 1 linux linux 4293888000 Oct 4 18:45 AIX.vol2.iso
-rw-rw-r-- 1 linux linux 391485440 Oct 4 18:50 AIX.vol3.iso
-rw-r--r-- 1 root root 204608 Oct 4 19:00 AIX61.img
# qemu-system-ppc64 -cpu POWER8,compat=power7 -machine pseries -m 8192
-serial mon:stdio \
> -drive file=/qemu/AIX61.img,if=none,id=drive-virtio-disk0 \
> -device virtio-scsi-pci,id=scsi -device scsi-hd,drive=drive-virtio-disk0 \
> -cdrom /qemu/AIX.vol1.iso \
> -prom-env boot-command='boot cdrom: -s verbose'
VNC server running on ::1:5900
qemu-system-ppc64: warning: TCG doesn't support requested feature,
cap-ibs=workaround
SLOF **
QEMU Starting
Build Date = Jul 3 2019 12:26:14
FW Version = git-ba1ab360eebe6338
Press "s" to enter Open Firmware.
Populating /vdevice methods
Populating /vdevice/vty@7100
Populating /vdevice/nvram@7101
Populating /vdevice/l-lan@7102
Populating /vdevice/v-scsi@7103
SCSI: Looking for devices
8200 CD-ROM : "QEMU QEMU CD-ROM 2.5+"
Populating /pci@8002000
00 (D) : 1234 qemu vga
00 0800 (D) : 1033 0194serial bus [ usb-xhci ]
00 1000 (D) : 1af4 1004virtio [ scsi ]
Populating /pci@8002000/scsi@2
SCSI: Looking for devices
100 DISK : "QEMU QEMU HARDDISK2.5+"
Installing QEMU fb
Scanning USB
XHCI: Initializing
USB Keyboard
USB mouse
No console specified using screen & keyboard
Welcome to Open Firmware
Copyright (c) 2004, 2017 IBM Corporation All rights reserved.
This program and the accompanying materials are made available
under the terms of the BSD License available at
http://www.opensource.org/licenses/bsd-license.php
Trying to load: -s verbose from:
/vdevice/v-scsi@7103/disk@8200: ... Successfully loaded
qemu-system-ppc64: Couldn't negotiate a suitable PVR during CAS
AIX
StarLED{814}
AIX Version 6.1
exec(/etc/init){1,0}
INIT: EXECUTING /sbin/rc.boot 1
exec(/usr/bin/sh,-c,/sbin/rc.boot 1){1114146,1}
exec(/sbin/rc.boot,/sbin/rc.boot,1){1114146,1}
+ PHASE=1
+ + bootinfo -p
exec(/usr/sbin/bootinfo,-p){1179684,1114146}
PLATFORM=chrp
+ [ ! -x /usr/lib/boot/bin/bootinfo_chrp ]
+ [ 1 -eq 1 ]
+ 1> /usr/lib/libc.a
+ init -c unlink /usr/lib/boot/bin/!(*_chrp)
exec(/etc/init,-c,unlink /usr/lib/boot/bin/!(*_chrp)){1179686,1114146}
+ chramfs -t
exec(/usr/sbin/chramfs,-t){1179688,1114146}
+ init -c unlink /usr/sbin/chramfs
+ 1> /dev/null
exec(/etc/init,-c,unlink /usr/sbin/chramfs){1179690,1114146}
+ + bootinfo -t
exec(/usr/sbin/bootinfo,-t){1179692,1114146}
BOOTYPE=3
+ [ 0 -ne 0 ]
+ [ -z 3 ]
+ unset pdev_to_ldev undolt native_netboot_cfg
+ unset disknet_odm_init config_ATM
+ /usr/lib/methods/showled 0x510 DEV CFG 1 START
exec(/usr/lib/methods/showled,0x510,DEV CFG 1 START){1179694,1114146}
+ cfgmgr -f -v
exec(/usr/sbin/cfgmgr,-f,-v){1179696,1114146}
cfgmgr is running in phase 1
Time: 0 LEDS: 0x538
Invoking top level program -- "/etc/methods/defsys"
exec(/bin/sh,-c,/etc/methods/defsys ){1245222,1179696}
exec(/etc/methods/defsys){1245222,1179696}
exec(/bin/sh,-c,/usr/lib/methods/define_rspc -n -c sys -s node -t
chrp){1310760,1245222}
exec(/usr/lib/methods/define_rspc,-n,-c,sys,-s,node,-t,chrp){1310760,1245222}
Time: 0 LEDS: 0x539
Return code = 0
* stdout *
sys0
*** no stderr
Attempting to configure device 'sys0'
Time: 0 LEDS: 0x811
Invoking /usr/lib/methods/cfgsys_chrp -1 -l sys0
exec(/bin/sh,-c,/usr/lib/methods/cfgsys_chrp -1 -l sys0){1245224,1179696}
Number of running methods: 1
exec(/usr/lib/methods/cfgsys_chrp,-1,-l,sys0){1245224,1179696}
LED{A20}
Illegal Trap Instruction Interrupt in Kernel
04151A74 tweqir0,0r0=0
KDB(0)>
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1846816/+subscriptions
[Bug 1670175] Re: qemu-system-sparc64 with tribblix-sparc-0m16.iso ends with "panic - kernel: no nucleus hblk8 to allocate"
qemu sparc64 also failed to boot Oracle Linux -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1670175 Title: qemu-system-sparc64 with tribblix-sparc-0m16.iso ends with "panic - kernel: no nucleus hblk8 to allocate" Status in QEMU: New Bug description: > qemu-system-sparc64 -m 1024 -cdrom Downloads/tribblix-sparc-0m16.iso -boot d -nographic OpenBIOS for Sparc64 Configuration device id QEMU version 1 machine id 0 kernel cmdline CPUs: 1 x SUNW,UltraSPARC-IIi UUID: ---- Welcome to OpenBIOS v1.1 built on Nov 24 2016 21:23 Type 'help' for detailed information Trying cdrom:f... Not a bootable ELF image Not a bootable a.out image Loading FCode image... Loaded 7120 bytes entry point is 0x4000 Evaluating FCode... Evaluating FCode... Ignoring failed claim for va 10a96a0 memsz 19! Ignoring failed claim for va 100 memsz d1fb6! Ignoring failed claim for va 1402000 memsz 32518! Ignoring failed claim for va 180 memsz 52ac8! SunOS Release 5.11 Version tribblix-m16 64-bit Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved. could not find debugger-vocabulary-hook>threads:interpret: exception -13 caught interpret \ ident "%Z%%M% %I% %E% SMI" \ Copyright 2005 Sun Microsystems, Inc. All rights reserved. \ Use is subject to license terms. \ \ CDDL HEADER START \ \ The contents of this file are subject to the terms of the \ Common Development and Distribution License, Version 1.0 only \ (the "License"). You may not use this file except in compliance \ with the License. \ \ You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE \ or http://www.opensolaris.org/os/licensing. \ See the License for WARNING: add_spec: No major number for sf panic - kernel: no nucleus hblk8 to allocate EXIT QEMU keeps running (CPU is on 100 % all the time), I can interact with the prompt: 0 > boot Not a Linux kernel image Not a bootable ELF image Not a bootable a.out image Loading FCode image... Unhandled Exception 0x0018 PC = 0xffd25310 NPC = 0xffd25314 Stopping execution > qemu-system-sparc64 -version QEMU emulator version 2.8.0(Virtualization:Staging / SLE_12_SP2) from https://build.opensuse.org/package/show/Virtualization:Staging/qemu on openSUSE Leap 42.2. ISO: http://pkgs.tribblix.org/iso/tribblix-sparc-0m16.iso. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1670175/+subscriptions
[Bug 1853083] Re: qemu ppc64 4.0 boot AIX5.1 hung
With
qemu-system-ppc64 -cpu power5+ -machine pseries -m 2048 -serial mon:stdio -hda
aix-hdd.qcow2 -cdrom /Download/AIX5.1/VOLUME1.iso -prom-env boot-command='boot
cdrom: -s verbose'
got:
VNC server running on ::1:5900
SLOF **
QEMU Starting
Build Date = Jul 3 2019 12:26:14
FW Version = git-ba1ab360eebe6338
Press "s" to enter Open Firmware.
Populating /vdevice methods
Populating /vdevice/vty@7100
Populating /vdevice/nvram@7101
Populating /vdevice/l-lan@7102
Populating /vdevice/v-scsi@7103
SCSI: Looking for devices
8000 DISK : "QEMU QEMU HARDDISK2.5+"
8200 CD-ROM : "QEMU QEMU CD-ROM 2.5+"
Populating /pci@8002000
00 (D) : 1234 qemu vga
00 0800 (D) : 1033 0194serial bus [ usb-xhci ]
Installing QEMU fb
Scanning USB
XHCI: Initializing
( 700 ) Program Exception [ fff ]
R0 .. R7 R8 .. R15 R16 .. R23 R24 .. R31
7dbf36f4 7e4594a8 7dc06400
7e669dc0 0100 7dc0ae70
7dc10700 7e45c000 7e466010 7e459488
7e45c000 7dc50700 7dc0b040 200081021000
7e436000 8000 200081020040
0fff f003 200081020070
7e466008 0006 0002
0118 7e66a050 7e459488
CR / XER LR / CTR SRR0 / SRR1DAR / DSISR
8408 7dbf3650 7dbf366c
8008
1 >
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1853083
Title:
qemu ppc64 4.0 boot AIX5.1 hung
Status in QEMU:
Incomplete
Bug description:
When boot AIX5.1 from cdrom device, qemu hung there, no further info
is displayed and cpu consumption is high.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1853083/+subscriptions
[Bug 1853083] Re: qemu ppc64 4.0 boot AIX5.1 hung
[root@192 emu]# qemu-system-ppc64 --version QEMU emulator version 4.1.0 Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers [root@192 emu]# -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1853083 Title: qemu ppc64 4.0 boot AIX5.1 hung Status in QEMU: Incomplete Bug description: When boot AIX5.1 from cdrom device, qemu hung there, no further info is displayed and cpu consumption is high. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1853083/+subscriptions
[Bug 1853083] Re: qemu ppc64 4.0 boot AIX5.1 hung
Tried POWER5, but got [root@192 emu]# ./aix51 qemu-system-ppc64: unable to find CPU model 'POWER5' -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1853083 Title: qemu ppc64 4.0 boot AIX5.1 hung Status in QEMU: Incomplete Bug description: When boot AIX5.1 from cdrom device, qemu hung there, no further info is displayed and cpu consumption is high. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1853083/+subscriptions
[Bug 1853083] Re: qemu ppc64 4.0 boot AIX5.1 hung
I'm running this to start the AIX5.1 installation on qemu: #!/bin/bash qemu-system-ppc64 -cpu POWER8 -machine pseries -m 2048 -serial mon:stdio -hda aix-hdd.qcow2 -cdrom /Download/AIX5.1/VOLUME1.iso -prom-env boot-command='boot cdrom: -s verbose' -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1853083 Title: qemu ppc64 4.0 boot AIX5.1 hung Status in QEMU: Incomplete Bug description: When boot AIX5.1 from cdrom device, qemu hung there, no further info is displayed and cpu consumption is high. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1853083/+subscriptions
[Bug 1853083] Re: qemu ppc64 4.0 boot AIX5.1 hung
and it got: [root@192 emu]# ./aix51 VNC server running on ::1:5900 qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-cfpc=workaround qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-sbbc=workaround qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-ibs=workaround SLOF ** QEMU Starting Build Date = Jul 3 2019 12:26:14 FW Version = git-ba1ab360eebe6338 Press "s" to enter Open Firmware. Populating /vdevice methods Populating /vdevice/vty@7100 Populating /vdevice/nvram@7101 Populating /vdevice/l-lan@7102 Populating /vdevice/v-scsi@7103 SCSI: Looking for devices 8000 DISK : "QEMU QEMU HARDDISK2.5+" 8200 CD-ROM : "QEMU QEMU CD-ROM 2.5+" Populating /pci@8002000 00 (D) : 1234 qemu vga 00 0800 (D) : 1033 0194serial bus [ usb-xhci ] Installing QEMU fb Scanning USB XHCI: Initializing USB Keyboard USB mouse No console specified using screen & keyboard Welcome to Open Firmware Copyright (c) 2004, 2017 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: -s verbose from: /vdevice/v-scsi@7103/disk@8200: ... and just hung there, took lots of CPU time, never proceed further. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1853083 Title: qemu ppc64 4.0 boot AIX5.1 hung Status in QEMU: Incomplete Bug description: When boot AIX5.1 from cdrom device, qemu hung there, no further info is displayed and cpu consumption is high. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1853083/+subscriptions
[Bug 1853083] Re: qemu ppc64 4.0 boot AIX5.1 hung
What I don't understand is ppc64 for IBM machine emulation, but qemu ppc64 can't support AIX most of the time, but can support Linux on power very well. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1853083 Title: qemu ppc64 4.0 boot AIX5.1 hung Status in QEMU: Incomplete Bug description: When boot AIX5.1 from cdrom device, qemu hung there, no further info is displayed and cpu consumption is high. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1853083/+subscriptions
[Bug 1853083] Re: qemu ppc64 4.0 boot AIX5.1 hung
No, this happened when I tried to install the AIX5.1 on qemu ppc64. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1853083 Title: qemu ppc64 4.0 boot AIX5.1 hung Status in QEMU: Incomplete Bug description: When boot AIX5.1 from cdrom device, qemu hung there, no further info is displayed and cpu consumption is high. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1853083/+subscriptions
[Bug 1853083] [NEW] qemu ppc64 4.0 boot AIX5.1 hung
Public bug reported: When boot AIX5.1 from cdrom device, qemu hung there, no further info is displayed and cpu consumption is high. ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1853083 Title: qemu ppc64 4.0 boot AIX5.1 hung Status in QEMU: New Bug description: When boot AIX5.1 from cdrom device, qemu hung there, no further info is displayed and cpu consumption is high. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1853083/+subscriptions
Re: [Qemu-devel] [Bug 1463812] Re: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption
It seems to me that no one has really looked into the matter, I can't find any comments,that this issue has been worked on. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1463812 Title: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption Status in QEMU: Incomplete Bug description: copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu 2.3.0, corrupted; copied again, run, corrupted again. Run the image on qemu 1.5.3, no problem. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1463812/+subscriptions
[Qemu-devel] [Bug 1289898] Re: qemu-system-ppc64 easily cause file corruption
After got qemu 2.3.0, I tested on CentOS6.6, the qemu-system-ppc64 also causes filesystem corruption for the big endian RHEL5.9 for power. So this should confirm the qemu for ppc has bug from at least 1.7 onward. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1289898 Title: qemu-system-ppc64 easily cause file corruption Status in QEMU: New Bug description: the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the RHEL 5.9 PPC VM, found the size is correct, but the content is corrupted from the middle of the 90+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions
[Qemu-devel] [Bug 1289898] Re: qemu-system-ppc64 easily cause file corruption
And seems no developer cares about this issue. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1289898 Title: qemu-system-ppc64 easily cause file corruption Status in QEMU: New Bug description: the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the RHEL 5.9 PPC VM, found the size is correct, but the content is corrupted from the middle of the 90+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions
[Qemu-devel] [Bug 1463812] Re: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption
I built 2.3.0 on CentOS 6.6 machine, and run the RHEL5.9 using the new qemu-system-64 ,and gets the same issue as 2.3.0 on RHEL5.3: Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda5 /: Resize inode not valid. /: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) [FAILED] As I stated before on the CentOS6.6, the qemu 1.5.3 running the RHEL5.9 for power is ok. That proves it's not because of RHEL5.3 machine that fs is corrupted, it's the newer qemu for power emulation has issue to run big-endian version of RHEL. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1463812 Title: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption Status in QEMU: New Bug description: copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu 2.3.0, corrupted; copied again, run, corrupted again. Run the image on qemu 1.5.3, no problem. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1463812/+subscriptions
Re: [Qemu-devel] [Bug 1463812] Re: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption
I already forgot the old one: I got a 2.3.0 qemu installed on the RHEL 5.3 machine, and since this machine has more disk spaces than the CentOS6.4 (now 6.6), so I copied again all emulated machine images from CentOS to RHEL machine, and started to build a new one for RHEL7.1 LE for Power on the 2.3.0, and found it's working quite well, and also other emulated machines are all working fine (mips32, mips32el, mips64el, armv7) on the 2.3.0.Then I just tried to use the RHEL5.9 Power qemu machine, but found root filesystem corrupted, copied from OS image from CentOS, start the qemu machine, again, root filesystem damaged. So, I created the bug report, didn't think about old bug report I made. So, now it's clear, it's on the RHEL5.3 machine, multiple qemu versions have issue with RHEL5.9 for power. > Date: Wed, 10 Jun 2015 16:58:40 + > From: dgilb...@redhat.com > To: w...@hotmail.com > Subject: [Bug 1463812] Re: qemu-system-ppc64 V2.30 cause RHEL5.9 disk > corruption > > and I've just seen your older bug report - > https://bugs.launchpad.net/qemu/+bug/1289898 - isn't this exactly the > same problem? Why open a new bug? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1463812 > > Title: > qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption > > Status in QEMU: > New > > Bug description: > copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu > 2.3.0, corrupted; copied again, run, corrupted again. > Run the image on qemu 1.5.3, no problem. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/qemu/+bug/1463812/+subscriptions -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1463812 Title: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption Status in QEMU: New Bug description: copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu 2.3.0, corrupted; copied again, run, corrupted again. Run the image on qemu 1.5.3, no problem. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1463812/+subscriptions
Re: [Qemu-devel] [Bug 1463812] Re: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption
Both X86_64. > Date: Wed, 10 Jun 2015 16:56:35 + > From: dgilb...@redhat.com > To: w...@hotmail.com > Subject: [Bug 1463812] Re: qemu-system-ppc64 V2.30 cause RHEL5.9 disk > corruption > > if you're running the 2.3.0 on the RHEL5.3 and the 1.53 on CentOS6.6 we can't > know if the problem > is with the qemu 2.3.0 or with running it on the older host? Please run the > two qemus on the same host > and see if the problem follows the host or the qemu version. > > Also, just checking; is that 64bit x86 host or 32 ? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1463812 > > Title: > qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption > > Status in QEMU: > New > > Bug description: > copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu > 2.3.0, corrupted; copied again, run, corrupted again. > Run the image on qemu 1.5.3, no problem. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/qemu/+bug/1463812/+subscriptions -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1463812 Title: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption Status in QEMU: New Bug description: copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu 2.3.0, corrupted; copied again, run, corrupted again. Run the image on qemu 1.5.3, no problem. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1463812/+subscriptions
Re: [Qemu-devel] [Bug 1463812] Re: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption
I'm running qemu 2.3.0 on a RHEL5.3/x86 box, 1.5.3 on a CentOS6.6/x86 box. > Date: Wed, 10 Jun 2015 12:25:22 + > From: dgilb...@redhat.com > To: w...@hotmail.com > Subject: [Bug 1463812] Re: qemu-system-ppc64 V2.30 cause RHEL5.9 disk > corruption > > Hi, > Can you add some details about your host and guest please: > 1) What's your host system? (ppc64 or x86? which os?) > 2) What's the guest disk image format - raw or qcow2? > 3) could you try some of the versions in between 2.3.0 and 1.5.3 ? > 4) Is it just the 5.9 image that has problems or is it more general? > > Dave > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1463812 > > Title: > qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption > > Status in QEMU: > New > > Bug description: > copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu > 2.3.0, corrupted; copied again, run, corrupted again. > Run the image on qemu 1.5.3, no problem. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/qemu/+bug/1463812/+subscriptions -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1463812 Title: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption Status in QEMU: New Bug description: copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu 2.3.0, corrupted; copied again, run, corrupted again. Run the image on qemu 1.5.3, no problem. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1463812/+subscriptions
Re: [Qemu-devel] [Bug 1463812] Re: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption
I'm using: qemu-system-ppc64 -hda ppcrhel5.img -cpu POWER7 -machine type=pseries,usb=off -m 768 -nographic -net nic -net tap,ifname=tap0,script=no It's on local disk. same as on qemu 1.5.3. > Date: Wed, 10 Jun 2015 12:29:56 + > From: dgilb...@redhat.com > To: w...@hotmail.com > Subject: [Bug 1463812] Re: qemu-system-ppc64 V2.30 cause RHEL5.9 disk > corruption > > Oh and: >5) What's your disk image stored on - local disk or network? >6) WHat's the command line you're using for your guest > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1463812 > > Title: > qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption > > Status in QEMU: > New > > Bug description: > copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu > 2.3.0, corrupted; copied again, run, corrupted again. > Run the image on qemu 1.5.3, no problem. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/qemu/+bug/1463812/+subscriptions -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1463812 Title: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption Status in QEMU: New Bug description: copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu 2.3.0, corrupted; copied again, run, corrupted again. Run the image on qemu 1.5.3, no problem. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1463812/+subscriptions
[Qemu-devel] [Bug 1463812] Re: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption
2.3.0 running RHEL7,1 little-endian version no problem. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1463812 Title: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption Status in QEMU: New Bug description: copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu 2.3.0, corrupted; copied again, run, corrupted again. Run the image on qemu 1.5.3, no problem. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1463812/+subscriptions
[Qemu-devel] [Bug 1463812] [NEW] qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption
Public bug reported: copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu 2.3.0, corrupted; copied again, run, corrupted again. Run the image on qemu 1.5.3, no problem. ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1463812 Title: qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption Status in QEMU: New Bug description: copied the RHEL5.9 power disk image from qemu 1.5.3, run it under qemu 2.3.0, corrupted; copied again, run, corrupted again. Run the image on qemu 1.5.3, no problem. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1463812/+subscriptions
[Qemu-devel] [Bug 1289898] Re: qemu-system-ppc64 easily cause file corruption
and lots of dependency issue . -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1289898 Title: qemu-system-ppc64 easily cause file corruption Status in QEMU: New Bug description: the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the RHEL 5.9 PPC VM, found the size is correct, but the content is corrupted from the middle of the 90+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions
Re: [Qemu-devel] [Bug 1289898] Re: qemu-system-ppc64 easily cause file corruption
On my RHEL 5.3 box, there are too many problems to get git work. And on the CentOS 6.4 it has many problem to get pixman, so I just can't test the latest qemu unless you also put the pixman in as 1.7.0 does. > Date: Mon, 10 Mar 2014 10:53:48 + > From: bonz...@gnu.org > To: w...@hotmail.com > Subject: [Bug 1289898] Re: qemu-system-ppc64 easily cause file corruption > > Also, RHEL5 does have git in the EPEL repository. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1289898 > > Title: > qemu-system-ppc64 easily cause file corruption > > Status in QEMU: > New > > Bug description: > the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. > Previously I was using QEMU 1.5.x for several months with no problem. But > after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and > QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: > > * using scp to transfer a tar.bz file from the RHEL 5.3 host to the RHEL > 5.9 PPC VM, found the size is correct, but the content is corrupted from the > middle of the 90+ MB file. re-transfer again, got a correct file. But after > untar, found some extracted files corrupted. > The extracted file corruption happened several times, and also the > filesystem in the VM had corrupted several times, had to restore the boot > image to recover. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1289898 Title: qemu-system-ppc64 easily cause file corruption Status in QEMU: New Bug description: the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the RHEL 5.9 PPC VM, found the size is correct, but the content is corrupted from the middle of the 90+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions
Re: [Qemu-devel] [Bug 1289898] Re: qemu-system-ppc64 easily cause file corruption
Yes, I tried that, but it failed due to some php component missing. > Date: Mon, 10 Mar 2014 10:45:34 + > From: peter.mayd...@linaro.org > To: w...@hotmail.com > Subject: Re: [Qemu-devel] [Bug 1289898] Re: qemu-system-ppc64 easily cause > file corruption > > On 10 March 2014 10:00, wzis wrote: > > I can't test from git: on one box with git, it failed for the pixman > > missing > > Did you try the git submodule command that configure > suggests when it can't find pixman? That will pull > in and build a local copy of pixman for QEMU. > > thanks > -- PMM > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1289898 > > Title: > qemu-system-ppc64 easily cause file corruption > > Status in QEMU: > New > > Bug description: > the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. > Previously I was using QEMU 1.5.x for several months with no problem. But > after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and > QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: > > * using scp to transfer a tar.bz file from the RHEL 5.3 host to the RHEL > 5.9 PPC VM, found the size is correct, but the content is corrupted from the > middle of the 90+ MB file. re-transfer again, got a correct file. But after > untar, found some extracted files corrupted. > The extracted file corruption happened several times, and also the > filesystem in the VM had corrupted several times, had to restore the boot > image to recover. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1289898 Title: qemu-system-ppc64 easily cause file corruption Status in QEMU: New Bug description: the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the RHEL 5.9 PPC VM, found the size is correct, but the content is corrupted from the middle of the 90+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions
[Qemu-devel] [Bug 1289898] Re: qemu-system-ppc64 easily cause file corruption
I can't test from git: on one box with git, it failed for the pixman missing. and the RHEL 5.3 doesn't have git. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1289898 Title: qemu-system-ppc64 easily cause file corruption Status in QEMU: New Bug description: the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the RHEL 5.9 PPC VM, found the size is correct, but the content is corrupted from the middle of the 90+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions
[Qemu-devel] [Bug 1289898] Re: qemu-system-ppc64 easily cause file corruption
I found a CentOS 6.4 machine which has QEMU 1.5.3, and copied the ppcrhel5.img to that machine, and tested, found it's reliable, and no such file and filesystem easy corruption issue. So, it's the 1.6.2 and 1.7.0 have the problem. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1289898 Title: qemu-system-ppc64 easily cause file corruption Status in QEMU: New Bug description: the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the RHEL 5.9 PPC VM, found the size is correct, but the content is corrupted from the middle of the 90+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions
[Qemu-devel] [Bug 1289898] Re: qemu-system-ppc64 easily cause file corruption
I used the following way to start the VM: #!/bin/bash ifconfig -a|grep tap0 >/dev/null 2>&1 || qemu-ifup tap0 qemu-system-ppc64 -hda ppcrhel5.img -cpu POWER7 -machine type=pseries,usb=off -m 768 -nographic -net nic -net tap,ifname=tap0,script=no qemu-ifdown tap0 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1289898 Title: qemu-system-ppc64 easily cause file corruption Status in QEMU: New Bug description: the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the RHEL 5.9 PPC VM, found the size is correct, but the content is corrupted from the middle of the 90+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions
[Qemu-devel] [Bug 1289898] [NEW] qemu-system-ppc64 easily cause file corruption
Public bug reported: the qemu-system-ppc64 is used to run Fedora-19 on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the Fedora-19 PPC VM, found the size is correct, but the content is corrupted from the middle of the 80+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. ** Affects: qemu Importance: Undecided Status: New ** Tags: critical -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1289898 Title: qemu-system-ppc64 easily cause file corruption Status in QEMU: New Bug description: the qemu-system-ppc64 is used to run Fedora-19 on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the Fedora-19 PPC VM, found the size is correct, but the content is corrupted from the middle of the 80+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions
[Qemu-devel] [Bug 1289898] Re: qemu-system-ppc64 easily cause file corruption
Correction, the qemu-system-ppc64 is running a VM for RHEL5.9 for PPC, not fedora-19. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1289898 Title: qemu-system-ppc64 easily cause file corruption Status in QEMU: New Bug description: the qemu-system-ppc64 is used to run Fedora-19 on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the Fedora-19 PPC VM, found the size is correct, but the content is corrupted from the middle of the 80+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions
[Qemu-devel] [Bug 1289898] Re: qemu-system-ppc64 easily cause file corruption
** Description changed: the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: - * using scp to transfer a tar.bz file from the RHEL 5.3 host to the Fedora-19 PPC VM, found the size is correct, but the content is corrupted from the middle of the 80+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. + * using scp to transfer a tar.bz file from the RHEL 5.3 host to the RHEL 5.9 PPC VM, found the size is correct, but the content is corrupted from the middle of the 90+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1289898 Title: qemu-system-ppc64 easily cause file corruption Status in QEMU: New Bug description: the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the RHEL 5.9 PPC VM, found the size is correct, but the content is corrupted from the middle of the 90+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions
[Qemu-devel] [Bug 1289898] Re: qemu-system-ppc64 easily cause file corruption
** Description changed: - the qemu-system-ppc64 is used to run Fedora-19 on RHEL 5.3. + the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the Fedora-19 PPC VM, found the size is correct, but the content is corrupted from the middle of the 80+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1289898 Title: qemu-system-ppc64 easily cause file corruption Status in QEMU: New Bug description: the qemu-system-ppc64 is used to run RHEL5.9 for IBM Power on RHEL 5.3. Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms: * using scp to transfer a tar.bz file from the RHEL 5.3 host to the RHEL 5.9 PPC VM, found the size is correct, but the content is corrupted from the middle of the 90+ MB file. re-transfer again, got a correct file. But after untar, found some extracted files corrupted. The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1289898/+subscriptions
