1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
|
socket: 0.867
graphic: 0.861
instruction: 0.854
device: 0.848
assembly: 0.840
semantic: 0.837
vnc: 0.831
KVM: 0.828
boot: 0.807
other: 0.789
network: 0.786
mistranslation: 0.724
qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption
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.
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
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
2.3.0 running RHEL7,1 little-endian version no problem.
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 +0000
> From: <email address hidden>
> To: <email address hidden>
> 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
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 +0000
> From: <email address hidden>
> To: <email address hidden>
> 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
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 ?
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?
Both X86_64.
> Date: Wed, 10 Jun 2015 16:56:35 +0000
> From: <email address hidden>
> To: <email address hidden>
> 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
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 +0000
> From: <email address hidden>
> To: <email address hidden>
> 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
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.
Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
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.
[Expired for QEMU because there has been no activity for 60 days.]
|