wddm dod 0.17 version released which fixes the issue guest side.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1635339
Title:
qxl_pre_save assertion failure on vm "save"
Status in QEMU:
Confirme
Similar issue, seems not caused by save/restore/migration but is still
detecting offset problems with resource deallocation.
See https://lists.freedesktop.org/archives/spice-devel/2017-April/037248.html.
Still working on some updates for the driver.
--
You received this bug notification because
Next version of the driver will solve the problem (already fixed in
master).
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1635339
Title:
qxl_pre_save assertion failure on vm "save"
Status in QEMU
Will be fixed in the windows driver, yes.
But throwing core dumps isn't exactly nice, even in case the guest is
buggy, thats why the qemu workaround, so we simply refuse to live-
migrate instead of crashing.
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Did I miss something or this is a bug in the windows qxl driver and
should be fixed there?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1635339
Title:
qxl_pre_save assertion failure on vm "save"
On Mo, 2017-04-10 at 11:56 +, Frediano Ziglio wrote:
> Is this problem limited to commands or also to data attached to the commands?
Everything which contains QXLReleaseInfo and is released via release
ring.
> To me looks like a limitation Qemu should remove on the long run.
That is an optio
Is this problem limited to commands or also to data attached to the commands?
To me looks like a limitation Qemu should remove on the long run.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1635339
T
Your approach works ok Gerd with a migration blocker. Are you going to
send a patch?
I am afraid we would have to make this code permanent though, since
there has been several releases of this driver already, and it's much
nicer to block migration than to crash a VM.
I have reached out to wddm dr
Not sure we want a failure mode for pre_save().
If we go for option (a) (from comment 9), I'd add a check when reading
the commands from the ring, not at migration time, so we don't run enter
a state where pre_save() can fail in the first place. Because that will
break the windows drivers we migh
An untested hack that might fail cleaner might be:
error_report("Broken driver . migration failed");
qemu_file_set_error(migrate_get_current()->to_dst_file, -EINVAL);
(untested, probably needs checking it works with savevm).
I must go around and add a return value to pre_save().
We prob
Well. qxl commands are expected to live in bar 0 (same bar where the
rings are too). vram bar was added as surface storage.
Now the windows drivers started to us vram for qxl commands. Problem is
we simply can't live-migrate such a guest. At least not without
changing the vmstate format. Whic
** Changed in: qemu
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1635339
Title:
qxl_pre_save assertion failure on vm "save"
Status in QEMU:
Confirmed
B
damn launchpad, wrong bug and I can't change it back. Please someone
move it back to New/Confirmed
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs
Crash reproduced immediately after setting up a win10 VM with qxl driver
10.0.0.15000.
Gerd, are you looking into fixing it? Is it acceptable to crash qemu if
the driver is faulty?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
http
I put my money on that one:
https://cgit.freedesktop.org/spice/win32/qxl-wddm-
dod/commit/?id=f6e099db39e7d0787f294d5fd0dce328b5210faa
commit f6e099db39e7d0787f294d5fd0dce328b5210faa
Author: Sameeh Jubran
Date: Sun Sep 11 16:05:24 2016 +0300
Use the second bar (VRAM) for qxl command buffe
I can see a bunch of similar looking failures in Fedora's automatic
backtrace stats system
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1635339
Title:
qxl_pre_save assertion failure on vm "save"
I'm running into this issue as well:
Arch Linux
Qemu 2.8.0
spice guest tools: 0.132
QXL driver version (as reported by Windows Device Manager): 10.0.0.15000
Everything else works great. It would save me a lot of rebooting if this could
get fixed.
If there is anything I can do or try, I'll be glad
I tried other QXL drivers: 22.33.46.473.
These work (but have a older date: 2015-07-28.
17.54.59.923 have the date 2016-04-21.
I got them from this package:
http://depot.flexvdi.com/guest-tools/flexvdi-guest-tools-2.2.11.iso
Those provide something, which lets my window resize freely.
--
You r
QXL driver version is 17.54.59.923
Commandline (git compiled today) is:
/usr/sbin/qemu-system-x86_64 -name guest=dc,debug-threads=on -S -object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-dc
/master-key.aes -machine pc-i440fx-2.7,accel=kvm,usb=off,vmport=off
,dump-guest-co
Hmm docmax on #qemu just complained about a similar error; although
they were on win2016, and using qemu-2.7 and the latest git versions,
and that assert has been in there for years.
Can you please add the full qemu command line you're using, and the
version of the spice/qxl drivers you're using
20 matches
Mail list logo
