According to comment 41, this bug has been fixed, so I'm setting the
status to "Fix released" now ... Vitalis, your problem from comment 46
sounds differently - if it still persists today, please open a new bug
ticket for this instead.
** Changed in: qemu
Status: New => Fix Released
--
Yo
Hello with bad news! I have:
virtio_ioport_write: unexpected address 0x13 value 0x1
on config:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 3072
-smp 1 -name nata_xp -uuid da607499-1d8f-e7ef
Hi Alon,
Unfortunately, qxl and virtio-serial
hang is a different 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/818673
Title:
virtio: trying to map MMIO memory
Status in QEMU:
New
Bug
I have no idea regarding Ubuntu, but you can find the new drivers
at Fedora project site
http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-0.1-22.iso
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://b
Vadim, Could this be related to the hangs during boot with qxl and
virtio-serial in a single windows vm?
Alon
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Title:
virtio: trying to map MMIO
Thanks! Where can I get ISO of new drivers pack? for Ubuntu 10.04
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Title:
virtio: trying to map MMIO memory
Status in QEMU:
New
Bug descripti
It was a long journey.
But now it seem like we've managed to fix this problem.
https://bugzilla.redhat.com/show_bug.cgi?id=771390#c45
I put new drivers here:
http://people.redhat.com/vrozenfe/vioscsi.vfd
Best regards,
Vadim.
--
You received this bug notification because you are a member of qem
Now have next config and bug still:
/usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 2048 -smp 1 -name boss_xp
-uuid 9041090d-acee-da4a-921d-238f2a43be64 -chardev
socket,id=monitor,path=/var/lib/libvirt/qemu/boss_xp.monitor,server,nowait
-monitor chardev:monitor -localtime -boot c -drive
f
well, the link in the redhat bug, comment 33, is no good apparently. I
will follow that bug, and test when I see Vadim has posted a new driver
to test.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/8
Yes, I would say it is the same bug. I will test the driver that Vadim
linked in Comment 33
(https://bugzilla.redhat.com/show_bug.cgi?id=771390#c33) and report
back.
Thanks, Mike, for posting here.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscr
Does this Bug similiar with
https://bugzilla.redhat.com/show_bug.cgi?id=771390 ?
** Bug watch added: Red Hat Bugzilla #771390
https://bugzilla.redhat.com/show_bug.cgi?id=771390
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https
I experience this on uni-processor.
On Tuesday 24 January 2012 16:48:04 Vitalis wrote:
> And more: i have too more virtual PC with WindowsXP SP3 and with one
> CPU, but them doesnt have any problems. Maybe this bug depends on 2 and
> more CPU??
--
You received this bug notification because you a
And more: i have too more virtual PC with WindowsXP SP3 and with one
CPU, but them doesnt have any problems. Maybe this bug depends on 2 and
more CPU??
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/81
And I have this bug!
Linux test-2 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 16 19:52:42 UTC 2010
x86_64 GNU/Linux
In container i have Windows XP SP3
In log:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enabl
In reply to comment #32, I encounter this problem with 1VCPU - see the original
description of the bug.
Also note that after qemu quits with the error, the subsequent execution of the
same qemu invocation will run stable.
--
You received this bug notification because you are a member of qemu-
d
Two other observations:
* The problem is also present in the latest drivers in the RHEL 6.2 virtio-win
package (both driver versions 60.62.102.3000, dates 9/12/2011).
* The problem does not seem to occur if the guest has only 1 VCPU.
So the problem only occurs when using 2 VirtIO devices with
I've been dealing with this bug for some time on Fedora. Until
recently, I was using the VirtIO drivers from RHEV 2.2, which don't
suffer from this problem. As of Fedora 16, however, that isn't an
option, because they cause the guest to blue-screen early in the boot
process.
So ... I've been doi
So I've built qemu with -enable-debug and tried running with an attached GDB,
but got nothing.
I've never tried to debug Qemu before, but I know it's not quite a simple as
debugging other apps.
I am honestly clueless about how to further debug this problem.
Should I give up on using virtio-seria
Vadim,
Did you see comment #27? Is that helpful, would you like any additional
info? Are there other things you would like for me to try?
Thanks,
-Rick
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bug
On Friday 23 September 2011 14:07:17 Alon Levy wrote:
> On Thu, Sep 22, 2011 at 02:10:04PM -0500, Rick Vernam wrote:
> > On Friday 16 September 2011 12:42:02 Rick Vernam wrote:
> > > On Friday 16 September 2011 03:52:34 hkran wrote:
> > > [snip]
> > >
> > > > I have tried many times with many rest
On Thu, Sep 22, 2011 at 02:10:04PM -0500, Rick Vernam wrote:
> On Friday 16 September 2011 12:42:02 Rick Vernam wrote:
> > On Friday 16 September 2011 03:52:34 hkran wrote:
> > [snip]
> >
> > > I have tried many times with many restarts or shutdown-and-boot xp guest
> > > but failed to meet the cr
On Friday 16 September 2011 12:42:02 Rick Vernam wrote:
> On Friday 16 September 2011 03:52:34 hkran wrote:
> [snip]
>
> > I have tried many times with many restarts or shutdown-and-boot xp guest
> > but failed to meet the crashing.
> > (I am using the virtio drivers referenced in the earlier mail
On Friday 16 September 2011 12:42:02 Rick Vernam wrote:
> On Friday 16 September 2011 03:52:34 hkran wrote:
> [snip]
>
> > I have tried many times with many restarts or shutdown-and-boot xp guest
> > but failed to meet the crashing.
> > (I am using the virtio drivers referenced in the earlier mail
On Friday 16 September 2011 03:52:34 hkran wrote:
[snip]
>
> I have tried many times with many restarts or shutdown-and-boot xp guest
> but failed to meet the crashing.
> (I am using the virtio drivers referenced in the earlier mail list.)
> my command:
>
> /home/huikai/qemu15/bin/qemu --enable-
On 09/16/2011 03:37 AM, Rick Vernam wrote:
On Thursday 15 September 2011 11:23:53 Rick Vernam wrote:
On Wednesday 14 September 2011 16:30:11 Rick Vernam wrote:
On Wednesday 14 September 2011 14:42:09 vrozenfe wrote:
Thank you, Rick.
Could you help me to narrow this problem down?
Absolutely.
On Thursday 15 September 2011 11:23:53 Rick Vernam wrote:
> On Wednesday 14 September 2011 16:30:11 Rick Vernam wrote:
> > On Wednesday 14 September 2011 14:42:09 vrozenfe wrote:
> > > Thank you, Rick.
> > >
> > > Could you help me to narrow this problem down?
> >
> > Absolutely.
> >
> > > As I
Thank you, Rick.
I will start checking virtio-serial driver tomorrow.
Best,
Vadim.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Title:
virtio: trying to map MMIO memory
Status in QEMU:
On Wednesday 14 September 2011 16:30:11 Rick Vernam wrote:
> On Wednesday 14 September 2011 14:42:09 vrozenfe wrote:
> > Thank you, Rick.
> >
> > Could you help me to narrow this problem down?
>
> Absolutely.
>
> > As I see, you have three virtio drivers installed on your system - block,
> > net
On Wednesday 14 September 2011 14:42:09 vrozenfe wrote:
> Thank you, Rick.
>
> Could you help me to narrow this problem down?
Absolutely.
>
> As I see, you have three virtio drivers installed on your system - block,
> net, and virtio serial. Technically, anyone of them can create "trying to
> ma
Thank you, Rick.
Could you help me to narrow this problem down?
As I see, you have three virtio drivers installed on your system - block, net,
and virtio serial.
Technically, anyone of them can create "trying to map MMIO memory" problem.
The best way to find a buggy driver ( or drivers) will be
sorry, scratch that last about -vga std ... it still crashed just the
same using -vga std.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Title:
virtio: trying to map MMIO memory
Status in
so if I use -vga std instead of -vga qxl (and of course take out the -spice
stuff), I don't crash.
perhaps this is spice/qxl related?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Title:
vi
Still crashes just the same.
I updated the drivers for virt net, scsi & serial from the XP and WXp folders
in the zip file that you referenced.
Then I shutdown the VM.
Because it only seems to happen every other time that Qemu is started, I
started it back up and shut it down again.
Then the VM w
I've made several unsuccessful attempts to reproduce this problem,
running VMs on top of F14 and RHEL6.2
The only one relatively close problem, reported by our QE, was
https://bugzilla.redhat.com/show_bug.cgi?id=727034
It must be fixed in our internal repository. (Public repository
is out of syn
ping...
I understand that Vadim must be very busy that he can't look at this - I can
relate.
But is there really only one person in all of Qemu and/or Spice who can be
addressed to look into this?
So that I can plan around the viability of Qemu for my users, I need to
know if the technologies I
We're affected by this bug, too. Trying to find a workaround, last
friday we changed VGA model to cirrus, and the machine is working
properly without new entries in log.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
On Thu, 2011-08-25 at 16:54 +0100, Stefan Hajnoczi wrote:
> On Thu, Aug 25, 2011 at 3:53 PM, David Rando wrote:
> > Do you know if it's something related to the virtio net driver? anyone
> > tried going to the e1000 only? i have some machines with e1000 and some
> > of them with virtio-net, but i
On Thu, Aug 25, 2011 at 3:53 PM, David Rando wrote:
> Do you know if it's something related to the virtio net driver? anyone
> tried going to the e1000 only? i have some machines with e1000 and some
> of them with virtio-net, but i have crash no matter what driver is using
> (but the virtio driver
Do you know if it's something related to the virtio net driver? anyone
tried going to the e1000 only? i have some machines with e1000 and some
of them with virtio-net, but i have crash no matter what driver is using
(but the virtio driver is installed anyway, despite i'm using the
e1000).
I was se
On Sun, Aug 14, 2011 at 7:11 AM, Rick Vernam <818...@bugs.launchpad.net> wrote:
> So that would point to virtio. This appears to be the place for virtio bugs,
> correct?
> Should I be doing anything to help usher this along?
Either we need to help Vadim reproduce this so he can take a look.
Vadi
So that would point to virtio. This appears to be the place for virtio bugs,
correct?
Should I be doing anything to help usher this along?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Title
It's something related to Windows. I have in the same machine a linux
server working with spice enabled and is rock solid. The windows
machines crash with that error randomnly.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://b
Continues with Qemu 0.15.0 and Qemu-KVM 0.15.0
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Title:
virtio: trying to map MMIO memory
Status in QEMU:
New
Bug description:
Qemu host is
Vadim,
Have you been able to reproduce this?
Do you require any additional information?
Thanks,
-Rick
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Title:
virtio: trying to map MMIO memory
Continues to occur with recently updated qxl, vdagent & virtio serial windows
binaries from spice-space.org.
Also continues with qemu-kvm-0.15.0-rc1, qemu-0.15.0-rc1 & qemu-0.15.0-rc2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
h
I have the same problem. I'm using the packages from the Sergei ppa with
spice enabled on a server with 9 windows xp machines and 1 linux (ubuntu
10.04) one. Ubuntu is rock solid and never crash, but the windows
machines do randomnly. I've updated everything i could (using the
version from spice-sp
Seems to only crash the first time qemu is started after booting the host
machine.
After the first crash, qemu will run solid for days if the host machine is not
rebooted.
If I have an opportunity, I'll test if it also crashes after first start when
kvm and/or kvm_intel modules are unloaded and
47 matches
Mail list logo
