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.
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 h
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 **
[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
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
Stat
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 y
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 requeste
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/1
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 d
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 subscri
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-
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, wh
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:
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 MA
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
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
>
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 yo
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 1
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
Bu
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 beca
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
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
> S
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 M
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 easil
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
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 notifi
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. Sympt
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
St
** 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
** 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 bot
30 matches
Mail list logo
