Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=434978.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2008-02-26T17:31:49+00:00 Jan wrote:

Description of problem:
After the recent upgrade my Fedora 8 image could no longer boot.

Version-Release number of selected component (if applicable):
kvm-60-2.fc8.x86_64 (broken)
kvm-60-1.fc8.x86_64 (OK)

How reproducible:
Tried once.  (I no longer have the appropriate image now.)

Steps to Reproduce:
1. Install F8 GA into kvm-60-1.fc8.
2. `yum update kernel' in this F8 GA.
3. Shutdown kvm.
4. Upgrade kvm to: kvm-60-2.fc8
5. Start kvm.

Actual results:
/1 primary superblock features different from backup, check forced.
Restarting system.
---> KVM restart
/1 primary superblock features different from backup, check forced.
Restarting system.
---> ad infinitum

Expected results:
/1 primary superblock features different from backup, check forced.
Restarting system.
---> KVM restart
/1: clean, ...

Additional info:
Downgrade to kvm-60-1.fc8.x86_64 really fixed the problem.

Expecting an off-by-one bug in the fix of the Bug 433560:
* Sat Feb 23 2008 Daniel P. Berrange <[email protected]> - 60-2.fc8
- Fix block device extents check (rhbz #433560)

The message:
  /1 primary superblock features different from backup, check forced.
is right as it happened during the recent F8 kernel update.
But it should happen only once.
Expecting some ext3 superblock backup near the end of the media got ignored.

Used disk image layout:
The partition is aligned to the physical end of the media but it does not 
exceed it!
in KVM:
/dev/sda:
 geometry      = 509/255/63, sectors = 8192000, start = 0

Disk /dev/sda: 4194 MB, 4194304000 bytes
255 heads, 63 sectors/track, 509 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000d71ca

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         509     4088511   83  Linux

Disk /dev/sda: 255 heads, 63 sectors, 509 cylinders

Nr AF  Hd Sec  Cyl  Hd Sec  Cyl     Start      Size ID
 1 80   1   1    0 254  63  508         63    8177022 83
 2 00   0   0    0   0   0    0          0          0 00
 3 00   0   0    0   0   0    0          0          0 00
 4 00   0   0    0   0   0    0          0          0 00

qemu-img:
file format: qcow2
virtual size: 3.9G (4194304000 bytes)


Expecting this Bug should get cloned across all the Fs/RHELs and for QEMU.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/213570/comments/0

------------------------------------------------------------------------
On 2008-02-26T17:31:49+00:00 Jan wrote:

Created attachment 295958
Forever-restarting Fedora 8 screenshot.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/213570/comments/1

------------------------------------------------------------------------
On 2008-02-26T17:33:31+00:00 Jan wrote:

Created attachment 295960
Finally updated Fedora 8 screenshot on kvm-60-1.fc8.x86_64.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/213570/comments/2

------------------------------------------------------------------------
On 2008-02-26T18:01:32+00:00 Daniel wrote:

Hmm, I think this could be related to use of QCow files instead of raw.

Can you convert your disk image to raw format using 'qemu-img' and see if the
problem still occurrs.


Reply at: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/213570/comments/3

------------------------------------------------------------------------
On 2008-02-26T19:31:59+00:00 Daniel wrote:

Ok, I have reproduced this problem. It impacts  QCow2 disks at least - probably
impacts the other Cow related formats too. Raw is not impacted.

In my tests it causes complete & unrecoverable data loss on the guest disk in
question :-(

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/213570/comments/4

------------------------------------------------------------------------
On 2008-02-26T19:38:05+00:00 Jan wrote:

Thanks for reproducing it (->no NEEDINFO).


Reply at: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/213570/comments/5

------------------------------------------------------------------------
On 2008-02-27T00:05:40+00:00 Daniel wrote:

Created attachment 296004
A revised block range checking patch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/213570/comments/6

------------------------------------------------------------------------
On 2008-02-28T01:03:30+00:00 Fedora wrote:

kvm-60-3.fc8 has been submitted as an update for Fedora 8

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/213570/comments/7

------------------------------------------------------------------------
On 2008-02-28T21:40:21+00:00 Fedora wrote:

kvm-60-3.fc8 has been pushed to the Fedora 8 stable repository.  If
problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/213570/comments/8


** Changed in: kvm (Fedora)
   Importance: Unknown => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/213570

Title:
  kvm vulnerable to several CVEs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/213570/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to