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
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
|
architecture: 0.939
performance: 0.939
graphic: 0.936
assembly: 0.936
device: 0.935
permissions: 0.932
register: 0.931
debug: 0.924
semantic: 0.923
arm: 0.922
socket: 0.912
virtual: 0.909
files: 0.906
PID: 0.906
peripherals: 0.898
user-level: 0.897
hypervisor: 0.896
kernel: 0.892
boot: 0.874
network: 0.858
KVM: 0.847
vnc: 0.828
risc-v: 0.818
VMM: 0.816
TCG: 0.805
x86: 0.797
mistranslation: 0.770
ppc: 0.770
i386: 0.649
CDROM size not updated when changing image files
I'm using qemu 13.0 with a plain Linux kernel using the ata_piix driver as the guest, and an initrd that starts a shell. When changing the image in the monitor and reading from the CDROM in the guest, the size is not updated. I'm using LInux 2.6.32.24
as the host and I've tested 2.6.32.24, 2.6.35, and 2.6.36 as guests. Both host and guest are 64-bit. Here is the command used to start the guest using the initrd:
./x86_64-softmmu/qemu-system-x86_64 -cdrom /spare2/cd1.img -kernel /sources/linux-2.6.32.24-test/arch/x86/boot/bzImage -initrd /spare2/initrd.img -append 'root=/dev/ram0 rw' -cpu core2duo
Additional info on this bug can be found here: http://marc.info/?l=kvm&m=128746013906820&w=2. Note: this is how I discovered
the bug, using 32-bit Slackware install CDs.
I'm attaching the initrd I used in my tests: I created two different-sized fake CDROM images by dd'ing from /dev/zero. In my tests,
cd1.img is smaller that cd2.img. In the monitor I executed 'change ide1-cd0 /spare2/cd2.img' to load the new image. I checked
the size by cat'ing /sys/block/sr0/size in the guest after reading the CDROM. Reading the CDROM was done by typing
'dd if=/dev/sr0 of=/dev/null bs=512 count=3'
Please note that until this bug is fixed, one cannot successfully install a guest OS from a set of CD-ROMS where the first disk image is smaller than subsequent ones.
On 10.11.2010, at 04:17, Alex Davis wrote:
> Please note that until this bug is fixed, one cannot successfully
> install a guest OS from a set of CD-ROMS where the first disk image is
> smaller than subsequent ones.
>
> --
> CDROM size not updated when changing image files
> https://bugs.launchpad.net/bugs/670769
> You received this bug notification because you are a member of qemu-
> devel-ml, which is subscribed to QEMU.
>
> Status in QEMU: New
>
> Bug description:
> I'm using qemu 13.0 with a plain Linux kernel using the ata_piix driver as the guest, and an initrd that starts a shell. When changing the image in the monitor and reading from the CDROM in the guest, the size is not updated. I'm using LInux 2.6.32.24
> as the host and I've tested 2.6.32.24, 2.6.35, and 2.6.36 as guests. Both host and guest are 64-bit. Here is the command used to start the guest using the initrd:
>
> ./x86_64-softmmu/qemu-system-x86_64 -cdrom /spare2/cd1.img -kernel /sources/linux-2.6.32.24-test/arch/x86/boot/bzImage -initrd /spare2/initrd.img -append 'root=/dev/ram0 rw' -cpu core2duo
>
> Additional info on this bug can be found here: http://marc.info/?l=kvm&m=128746013906820&w=2. Note: this is how I discovered
> the bug, using 32-bit Slackware install CDs.
>
> I'm attaching the initrd I used in my tests: I created two different-sized fake CDROM images by dd'ing from /dev/zero. In my tests,
> cd1.img is smaller that cd2.img. In the monitor I executed 'change ide1-cd0 /spare2/cd2.img' to load the new image. I checked
> the size by cat'ing /sys/block/sr0/size in the guest after reading the CDROM. Reading the CDROM was done by typing
> 'dd if=/dev/sr0 of=/dev/null bs=512 count=3'
Just to clarify, the contents of the image do change, but the reported size does not?
Alex
I code, therefore I am
--- On Tue, 11/9/10, agraf <email address hidden> wrote:
> From: agraf <email address hidden>
> Subject: Re: [Qemu-devel] [Bug 670769] Re: CDROM size not updated when changing image files
> To: <email address hidden>
> Date: Tuesday, November 9, 2010, 10:47 PM
>
> On 10.11.2010, at 04:17, Alex Davis wrote:
>
> > Please note that until this bug is fixed, one cannot
> successfully
> > install a guest OS from a set of CD-ROMS where the
> first disk image is
> > smaller than subsequent ones.
> >
> > --
> > CDROM size not updated when changing image files
> > https://bugs.launchpad.net/bugs/670769
> > You received this bug notification because you are a
> member of qemu-
> > devel-ml, which is subscribed to QEMU.
> >
> > Status in QEMU: New
> >
> > Bug description:
> > I'm using qemu 13.0 with a plain Linux kernel using
> the ata_piix driver as the guest, and an initrd that starts
> a shell. When changing the image in the monitor and reading
> from the CDROM in the guest, the size is not updated. I'm
> using LInux 2.6.32.24
> > as the host and I've tested 2.6.32.24, 2.6.35, and
> 2.6.36 as guests. Both host and guest are 64-bit. Here
> is the command used to start the guest using the initrd:
> >
> > ./x86_64-softmmu/qemu-system-x86_64 -cdrom
> /spare2/cd1.img -kernel
> /sources/linux-2.6.32.24-test/arch/x86/boot/bzImage -initrd
> /spare2/initrd.img -append 'root=/dev/ram0 rw' -cpu
> core2duo
> >
> > Additional info on this bug can be found here: http://marc.info/?l=kvm&m=128746013906820&w=2. Note:
> this is how I discovered
> > the bug, using 32-bit Slackware install CDs.
> >
> > I'm attaching the initrd I used in my tests: I created
> two different-sized fake CDROM images by dd'ing from
> /dev/zero. In my tests,
> > cd1.img is smaller that cd2.img. In the monitor I
> executed 'change ide1-cd0 /spare2/cd2.img' to load the new
> image. I checked
> > the size by cat'ing /sys/block/sr0/size in the guest
> after reading the CDROM. Reading the CDROM was done by
> typing
> > 'dd if=/dev/sr0 of=/dev/null bs=512 count=3'
>
> Just to clarify, the contents of the image do change, but
> the reported
> size does not?
Correct?
On 10.11.2010, at 13:55, Alex Davis wrote:
> --- On Tue, 11/9/10, agraf <email address hidden> wrote:
>
>> From: agraf <email address hidden>
>> Subject: Re: [Qemu-devel] [Bug 670769] Re: CDROM size not updated when changing image files
>> To: <email address hidden>
>> Date: Tuesday, November 9, 2010, 10:47 PM
>>
>> On 10.11.2010, at 04:17, Alex Davis wrote:
>>
>>> Please note that until this bug is fixed, one cannot
>> successfully
>>> install a guest OS from a set of CD-ROMS where the
>> first disk image is
>>> smaller than subsequent ones.
>>>
>>> --
>>> CDROM size not updated when changing image files
>>> https://bugs.launchpad.net/bugs/670769
>>> You received this bug notification because you are a
>> member of qemu-
>>> devel-ml, which is subscribed to QEMU.
>>>
>>> Status in QEMU: New
>>>
>>> Bug description:
>>> I'm using qemu 13.0 with a plain Linux kernel using
>> the ata_piix driver as the guest, and an initrd that starts
>> a shell. When changing the image in the monitor and reading
>> from the CDROM in the guest, the size is not updated. I'm
>> using LInux 2.6.32.24
>>> as the host and I've tested 2.6.32.24, 2.6.35, and
>> 2.6.36 as guests. Both host and guest are 64-bit. Here
>> is the command used to start the guest using the initrd:
>>>
>>> ./x86_64-softmmu/qemu-system-x86_64 -cdrom
>> /spare2/cd1.img -kernel
>> /sources/linux-2.6.32.24-test/arch/x86/boot/bzImage -initrd
>> /spare2/initrd.img -append 'root=/dev/ram0 rw' -cpu
>> core2duo
>>>
>>> Additional info on this bug can be found here: http://marc.info/?l=kvm&m=128746013906820&w=2. Note:
>> this is how I discovered
>>> the bug, using 32-bit Slackware install CDs.
>>>
>>> I'm attaching the initrd I used in my tests: I created
>> two different-sized fake CDROM images by dd'ing from
>> /dev/zero. In my tests,
>>> cd1.img is smaller that cd2.img. In the monitor I
>> executed 'change ide1-cd0 /spare2/cd2.img' to load the new
>> image. I checked
>>> the size by cat'ing /sys/block/sr0/size in the guest
>> after reading the CDROM. Reading the CDROM was done by
>> typing
>>> 'dd if=/dev/sr0 of=/dev/null bs=512 count=3'
>>
>> Just to clarify, the contents of the image do change, but
>> the reported
>> size does not?
> Correct?
Sounds like a missing change event to the guest to me.
Kevin, are you aware of this bug?
Alex
I code, therefore I am
--- On Wed, 11/10/10, agraf <email address hidden> wrote:
> From: agraf <email address hidden>
> Subject: Re: [Qemu-devel] [Bug 670769] Re: CDROM size not updated when changing image files
> To: <email address hidden>
> Date: Wednesday, November 10, 2010, 8:11 AM
>
> On 10.11.2010, at 13:55, Alex Davis wrote:
>
> > --- On Tue, 11/9/10, agraf <email address hidden>
> wrote:
> >
> >> From: agraf <email address hidden>
> >> Subject: Re: [Qemu-devel] [Bug 670769] Re: CDROM
> size not updated when changing image files
> >> To: <email address hidden>
> >> Date: Tuesday, November 9, 2010, 10:47 PM
> >>
> >> On 10.11.2010, at 04:17, Alex Davis wrote:
> >>
> >>> Please note that until this bug is fixed, one
> cannot
> >> successfully
> >>> install a guest OS from a set of CD-ROMS where
> the
> >> first disk image is
> >>> smaller than subsequent ones.
> >>>
> >>> --
> >>> CDROM size not updated when changing image
> files
> >>> https://bugs.launchpad.net/bugs/670769
> >>> You received this bug notification because you
> are a
> >> member of qemu-
> >>> devel-ml, which is subscribed to QEMU.
> >>>
> >>> Status in QEMU: New
> >>>
> >>> Bug description:
> >>> I'm using qemu 13.0 with a plain Linux kernel
> using
> >> the ata_piix driver as the guest, and an initrd
> that starts
> >> a shell. When changing the image in the monitor
> and reading
> >> from the CDROM in the guest, the size is not
> updated. I'm
> >> using LInux 2.6.32.24
> >>> as the host and I've tested 2.6.32.24, 2.6.35,
> and
> >> 2.6.36 as guests. Both host and guest are
> 64-bit. Here
> >> is the command used to start the guest using the
> initrd:
> >>>
> >>> ./x86_64-softmmu/qemu-system-x86_64 -cdrom
> >> /spare2/cd1.img -kernel
> >>
> /sources/linux-2.6.32.24-test/arch/x86/boot/bzImage -initrd
> >> /spare2/initrd.img -append 'root=/dev/ram0 rw'
> -cpu
> >> core2duo
> >>>
> >>> Additional info on this bug can be found here:
> http://marc.info/?l=kvm&m=128746013906820&w=2. Note:
> >> this is how I discovered
> >>> the bug, using 32-bit Slackware install CDs.
> >>>
> >>> I'm attaching the initrd I used in my tests: I
> created
> >> two different-sized fake CDROM images by dd'ing
> from
> >> /dev/zero. In my tests,
> >>> cd1.img is smaller that cd2.img. In the
> monitor I
> >> executed 'change ide1-cd0 /spare2/cd2.img' to load
> the new
> >> image. I checked
> >>> the size by cat'ing /sys/block/sr0/size in the
> guest
> >> after reading the CDROM. Reading the CDROM was
> done by
> >> typing
> >>> 'dd if=/dev/sr0 of=/dev/null bs=512 count=3'
> >>
> >> Just to clarify, the contents of the image do
> change, but
> >> the reported
> >> size does not?
> > Correct?
>
> Sounds like a missing change event to the guest to me.
>
> Kevin, are you aware of this bug?
>
I looks like change event is being sent, but it's being eaten by the
error recovery in the guest.
Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
[Expired for QEMU because there has been no activity for 60 days.]
|