Hi Christian,
as stated above, found other bugs but as you said they seem to not to be
related to this one so please feel free to close it.
Thanks,
Rolando.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Thank you all very much guys!
I'm on a business travel but will install update it as soon as I get
back home.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1684239
Title:
vvfat core dump when enabl
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.13
---
qemu (1:2.5+dfsg-5ubuntu10.13) xenial; urgency=medium
* debian/patches/ubuntu/vvfat-fix-volume-name-assertion.patch:
Fix the volume name assertion in vvfat rw mode (LP: #1684239)
qemu (1:2.5+dfsg-5ubuntu10.12)
Hi Christian,
Ok, understood. And, yes, you are correct: basically I create a qcow image file
and then:
- Bering works fine when passing qemu the qcow image file to be used as the HDD
- Bering doesn't work when mounting the same qcow image file and then launching
qemu to access those same files
Hi Rolando,
we really should stick to here verify the issue that we fixed (the vvfat rw
fail) and after you gave me a 50%-heartache :-) I verified proposed on my own
now.
It just works via
1. echo "deb http://archive.ubuntu.com/ubuntu/ xenial-proposed restricted main
multiverse universe" >> /et
Hi Rolando,
there are further changes in this build - we need to exclude that you are
seeing this just due to only downloading the .deb file instead of enabling
proposed to gain all required dependencies.
You can instead of an full "apt upgrade" also run rather selective upgrades.
I'd recommend
Just in case, this the output of a "dmesg" command:
firewall# dmesg
[0.00] Linux version 4.4.61-x86_64 (kapeka@stalker) (gcc version 5.3.0
(GCC) ) #1 SMP Thu Apr 13 19:03:07 CEST 2017
[0.00] Command line: rw root=/dev/ram0 console=ttyS0,115200n8 VERBOSE=1
PKGPATH=/dev/sda1:vfat
I meant "I'll be glad to help to have this solved" :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1684239
Title:
vvfat core dump when enabling RW
To manage notifications about this bug go to:
h
Hi guys,
unfortunatelly, I hit an issue with this patched version: there seems to
be some issues, at least for LEAF (Linux Embedded Appliance Framework -
https://sourceforge.net/projects/leaf).
Previous steps to reproduce (LEAF image creation):
# This download is ~110M:
wget
http
Hi guys,
sorry, my bad! Downloaded the wrong file, the correct one is:
>>> http://launchpadlibrarian.net/318154621/qemu-system-x86_2.5+dfsg-5ubuntu10.13_amd64.deb
So, I checked it and, yes, it works fine!
I got this errors but I think they are correct as I'm just pointing to the new
binary inst
Hi Robie,
I think something is wrong with the build you mention.
Still can't install it by means of:
>>> apt-get -s install qemu-system-x86/xenial-proposed
>>> apt-get -s install qemu-system/xenial-proposed
or
>>> apt-get -s install qemu-kvm/xenial-proposed
but issuing a:
>>> wget
>>> https://la
Hello Rolando, or anyone else affected,
Accepted qemu into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-
5ubuntu10.13 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Subscribing Marc so he can easily track once this SRU passes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1684239
Title:
vvfat core dump when enabling RW
To manage notifications about this bug go
Sure, no problem Christian!
BTW, I just updated my system and got this qemu version:
>>> QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.11), Copyright (c)
>>> 2003-2008 Fabrice Bellard
but the issue is still there:
>>> qemu-system-x86_64: /build/qemu-iZpOAh/qemu-2.5+dfsg/block/vvfat.c:2
Hi,
I haven't touched on anything that would bring much more features to the vvfat
code.
In general it is a helper to sync data, but it is brittle I'd not even so much
like to see a bootsector support there. That I don't find anything doesn't mean
there is nothing, if you know an upstream commit
Added SRU Template and tested 1:2.5+dfsg-5ubuntu10.13 from the bileto
ppa.
Bug is fixed, content can be written from the guest and is re-readable
from there as well as on the Host.
That said pushed to the SRU unapproved queue.
** Changed in: qemu (Ubuntu Xenial)
Status: Triaged => Fix Com
** Description changed:
+ [Impact]
+
+ * enabling vvfat with rw set breaks qemu once it writes something
+
+ * Fix is a backport of a small upstream fix
+
+ [Test Case]
+
+ * 1. get a guest that works (via uvtoools-libvirt or whatever you prever)
+ * 2. get the qemu commandline that it is
Gah obviously for vvfat it isn't an image to be created at all.
So I thought steps to reproduce are:
1. get a guest that works (via uvtoools-libvirt or whatever you prever)
2. get the qemu commandline that it is started with, in my case:
$ sudo kvm -m 1024 -drive
file=/dev/sdb,format=raw,cache
If there are no blockers uncovered on the way I will merge this with the
ongoing qemu SRU.
That means that a test builds will soon be available in
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2697
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Thank you Rolando for your report!
I think the issue is valid and a backport as SRU [1] possible.
I don't think you need to upload further Data, yet there is more you can help
with.
For the SRU and testing it we will need some simplified steps to reproduce (and
verify the fix).
Also see the Sect
That means it is fixed in Yakkety and later, and not Broken in Trusty
yet as the feature is not in.
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New => Fix Released
** Changed in: qemu (Ubuntu Xenial)
Importance:
The mentioned commit is:
commit ebb72c9f066e5f85259e1541a6d3fb5bfd6e73ff
Author: Kevin Wolf
Date: Wed Apr 27 14:11:38 2016 +0200
vvfat: Fix volume name assertion
Commit d5941dd made the volume name configurable, but it didn't consider
that the rw code compares the volume name stri
Moving to QEMU-Ubuntu since you're not using upstream QEMU (and the bug
should have been fixed there as pointed out by Hervé on the qemu-devel
mailing list).
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
23 matches
Mail list logo
