All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingmar Schraub <is@eseco.de>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: [ANNOUNCE] qemu-kvm-0.12.1
Date: Mon, 21 Dec 2009 09:41:10 +0100	[thread overview]
Message-ID: <4B2F34A6.5020407@eseco.de> (raw)
In-Reply-To: <4B2F2E55.6050501@eseco.de>

Apparently it doesn't matter what type of VM (Windows or Linux) you
start, the same problem happens.

For the time being, I reverted back to qemu-kvm-0.12.0-rc2

But of course I would like to move forward to the new version. So any
suggestions are welcome.

Thanks, Ingmar

Ingmar Schraub wrote:
> Hi,
> 
> after upgrading from qemu-kvm-0.12.0-rc2 to qemu-kvm-0.12.1 I cannot
> start my Windows 7 (64Bit) VM any more. I get the following error on
> start-up:
> 
> rom: requested regions overlap (rom vapic.bin. free=0x0000000000000600,
> addr=0x0000000000000000)
> rom loading failed
> 
> I used to run it with this command line:
> 
> qemu-system-x86_64 -k de -enable-kvm -usb -drive
> file=/home/ingmar/kvm/windows7.qcow2,if=ide,boot=on,cache=none -net
> nic,macaddr=DE:AD:BE:EF:28:26,vlan=1,model=e1000 -net
> tap,script=/etc/kvm/qemu-ifup,vlan=1 -m 1024 -vnc :3 -boot c
> 
> Any idea what is wrong here? It worked fine with all previous qemu-kvm
> versions.
> 
> Thanks and regards,
> 
> Ingmar
> 
> 
> Avi Kivity wrote:
>> qemu-kvm-0.12.1 is now available.  This release is is based on the
>> upstream qemu 0.12.1, plus kvm-specific enhancements.  Please see the
>> original qemu 0.12.1 release announcement for details.
>>
>> This release can be used with the kvm kernel modules provided by your
>> distribution kernel, or by the modules in the kvm-kmod package, such as
>> kvm-kmod-2.6.32.
>>
>> Changes from qemu-kvm-0.11.1
>> - merge qemu 0.12.1
>>   - many changes, including:
>>     - s390 support
>>     - live migration: support migration with non shared storage
>>     - live migration: make save/restore data driven (VMState)
>>     - monitor: introduce machine-protocol (QMP)
>>     - qdev: convert many devices, support reading config from file
>>     - pci: infrastructure to support 64-bit busses
>>     - net: introduce -netdev to support point-to-point networking
>>     - net: add support for GSO and checksum offload
>>     - tons of bug fixes throughout the code base
>> - many kvm-specific bug fixes
>>
>> http://www.linux-kvm.org
>>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-12-21  8:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-20 16:40 [ANNOUNCE] qemu-kvm-0.12.1 Avi Kivity
2009-12-20 16:57 ` Nikola Ciprich
2009-12-20 22:06   ` Alexander Graf
2009-12-21  6:33     ` Nikola Ciprich
2009-12-21 12:19       ` Avi Kivity
2009-12-21 12:33   ` Avi Kivity
2009-12-21 13:17     ` Nikola Ciprich
2009-12-21  5:58 ` John Wong
2009-12-21 14:43   ` Thomas Mueller
2009-12-21 15:44     ` John Wong
2009-12-21 16:46       ` FinnTux
2009-12-21  8:14 ` Ingmar Schraub
2009-12-21  8:41   ` Ingmar Schraub [this message]
2009-12-21  9:43   ` Thomas Mueller
2009-12-21  9:58     ` Ingmar Schraub
2009-12-21 14:48     ` Avi Kivity
2009-12-21 15:39       ` Ingmar Schraub

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B2F34A6.5020407@eseco.de \
    --to=is@eseco.de \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.