(errors/warnings, but, still, could/should be fixed).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841457
Title:
QEMU Eoan FTBS in my machine (gcc9 + amd related ?)
To manage notifications about
** Changed in: qemu (Ubuntu Bionic)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: qemu (Ubuntu Disco)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: qemu (Ubuntu Bionic)
Status: Triaged => In Progress
** C
** Changed in: libvirt (Ubuntu Disco)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: libvirt (Ubuntu Bionic)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: qemu (Ubuntu Disco)
Assignee: Rafael David Tinoco (rafaeld
# BISECT LOG
git bisect start
# bad: [0adb32858b0bddf4ada5f364a84ed60b196dbcda] Linux 4.16
git bisect bad 0adb32858b0bddf4ada5f364a84ed60b196dbcda
# good: [d8a5b80568a9cb66810e75b182018e9edb68e8ff] Linux 4.15
git bisect good d8a5b80568a9cb66810e75b182018e9edb68e8ff
# good: [c14376de3a1befa70d9811c
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834522
Title:
Bionic QEMU with Bionic Kernel hangs in AMD FX-8350 with cpu
I've included patch above into Bionic tree:
commit 9bff5f095923aab04411cf4e9135b975b70e3ead (tag: Ubuntu-4.15.0-58.64,
origin/master, origin/HEAD)
Author: Stefan Bader
Date: Tue Aug 6 10:45:37 2019
UBUNTU: Ubuntu-4.15.0-58.64
And it, indeed, fixed the issue.
--
You received this bug no
Also needed:
commit 35be0aded76b54a24dc8aa678a71bca22273e8d8
Author: Sean Christopherson
Date: Thu Aug 23 17:56:47 2018
KVM: x86: SVM: Set EMULTYPE_NO_REEXECUTE for RSM emulation
Re-execution after an emulation decode failure is only intended to
handle a case where two or vCPUs ra
Sent out to kernel team:
https://lists.ubuntu.com/archives/kernel-team/2019-August/103470.html
https://lists.ubuntu.com/archives/kernel-team/2019-August/103471.html
** Description changed:
[Impact]
- * QEMU does not work in some AMD hardware when using host-passthrough as
cpu-mode (usuall
Waiting kernel team sponsorship. Thx.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834522
Title:
Bionic QEMU with Bionic Kernel hangs in AMD FX-8350 with cpu-host as
passthrough
To manage notif
fects: crmsh (Ubuntu)
Importance: High
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Changed in: crmsh (Ubuntu)
Status: New => Confirmed
** Changed in: crmsh (Ubuntu)
Importance: Undecided => High
** Changed in: crmsh (Ubuntu)
Assignee: (u
** Changed in: ocfs2-tools (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ocfs2-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840958
I'm verifying Disco SRU and will provide feedback here very soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722201
Title:
CTDB port is not aware of Ubuntu-specific NFS Settings
To manage notifi
Marking verification-done according to:
https://bugs.launchpad.net/debian/+source/samba/+bug/722201/comments/53
** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco
--
You received this bug notification because you are a member
Marking verification-done according to:
https://bugs.launchpad.net/debian/+source/samba/+bug/722201/comments/53
** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco
--
You received this bug notification because you are a member
Marking Disco SRU as verified.
** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722
Following https://discourse.ubuntu.com/t/ctdb-create-a-3-node-nfs-ha-
backed-by-a-clustered-filesystem/11608:
(c)inaddy@ctdb01:~$ cat /etc/ctdb/public_addresses
192.168.0.1/24 fakeinternal01
192.168.0.2/24 fakeinternal01
192.168.0.3/24 fakeinternal01
(c)inaddy@ctdb01:~$ cat /etc/ctdb/nodes
172.16
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: qemu (Ubuntu Xenial)
Status: New => Confirmed
** Summary changed:
- qemu-user-static fails to install in WSL
+ qemu-user-st
Frank, based on your previous comment I'm also flagging disco as Fix
Released. Please fix this if it makes no sense (just to be accurate).
Thx!
** Also affects: qemu (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
St
** Changed in: subiquity (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: probert (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: probert (Ubuntu)
Status: Confirmed => Triaged
** Changed in: subiquity (Ubuntu)
Status: Confirmed => Triaged
** Changed in
** Changed in: linux (Ubuntu Disco)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788098
Title:
Avoid migration issues with aligned 2MB THB
To manage notificatio
** Changed in: sg3-utils (Ubuntu)
Status: New => Incomplete
** Changed in: sg3-utils (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: sg3-utils (Ubuntu)
Importance: Undecided => High
** Changed in: sg3-utils (Ubuntu)
Assignee: (unassigned) => Rafael
Hello Simon,
The fix for the current release can be made, but, in order for that to
happen, we need an exact way how to make the error to happen, and what
was your use case. Reading Debian bug and this bug, it appears that
you've enabled cgroupv2, correct ?
You likely enabled:
systemd.unified_cg
Hello peterzay,
IF you are facing something like:
https://unix.stackexchange.com/questions/85993/why-rsync-attempts-to-
copy-file-that-is-already-up-to-date
Then I would recommend reading the 1st answer to that question, which
explains why and when rsync would try to re-sync everything again.
I
Hello Pawel,
I'm currently seeing Build-Depends for both versions (Xenial, 18.04,
version 1:13.18.3~dfsg-1ubuntu4) and current (Eoan, 19.04, version
1:16.2.1~dfsg-2build2) and both include:
libopencore-amrnb-dev,
libopencore-amrwb-dev,
in debian/control file for the package generation.
Descri
Mitsuya Shibata San,
I've changed flag back to In Progress. Fix Committed will be done
automatically once the package lands into -proposed repository, it
depends on the merge request being accepted by a reviewer and uploaded
to the -proposed repo by someone with proper rights.
I see your MR solve
Looks like there was an issue during GAState channel initialization...
as the channel was used (by run_agent() ?) before it was fully
initialized (by initialize_agent()), so the assert:
static int send_response(GAState *s, const QDict *rsp)
{
const char *buf;
QString *payload_qstr, *respon
** Changed in: byobu (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843729
Title:
byobu ftbfs in eoan
To manage notifications about this bug go to:
@Patricia,
I'll concentrate efforts into the sg3-utils issue with disco for now.
For Eoan, based on the console output you attached to the bug, it seems
that one of the services listed as "getty@ttyAMA0.service" dependencies
did not start before timeout occurred. You can check systemd output
after
@Rhyan, thanks for the quick pointers, helped a lot =), I think I found
out what is going on.
Linux mylab 5.0.0-30-generic #32-Ubuntu SMP Wed Sep 18 00:24:43 UTC 2019
aarch64 aarch64 aarch64 GNU/Linux
Using a memstick in an aarch64 server:
$ sudo sg_inq -d /dev/sdb
standard INQUIRY:
PQual=0
This also happens in amd64 (and likely other architectures), only when
having "sg3-utils-udev" package installed.
Command "udevadm settle" only returns after the initial "sg_inq" command
also returns, raising the question:
(1) Would call "udevmadm settle" before "udevadm info" be enough to get
A
BTW, you got:
15 the utility is unable to open, close or use the given
DEVICE or some other file. The given file name could be incorrect or
there may be permission problems. Adding the '-v' option may give more
information.
And this is likely because USB devices don't have VPD, so sysf
I meant "for USB devices and that would be "enough"" in previous
comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833618
Title:
failing to deploy Ubuntu Disco
To manage notifications about t
Well, checking udev rules, its exactly what you said.
I guess we could change sg3 udev rules not to execute sg_inq --export
--inhex to /sys/block/$kernel/device/vpd_pg83 for SCSI devices and
that would be "enough" for this issue.
--inhex=FN|-I FNread ASCII hex from file FN instead of
Adding:
# Ignore USB block devices as they don't contain VPD 0x80 and 0x83
# and their SERIAL is calculated from usb_id in persistent-storage rules
DEVPATH=="*usb*", GOTO="sg3_utils_id_end"
before
#SCSI EVPD page 0x80 values
in 55-scsi-sg3_id.rules file fixes the issue.
--
You received this
Alright, I'll change the udev rules from sg3-utils-udev package to
ignore USB devices. From the initial ACTION (add) event, I only get
simple data from udev:
S: disk/by-id/usb-Corsair_Voyager_Mini_3.0_070851D0E490C776-0:0
S: disk/by-path/pci-:00:14.0-usb-0:2:1.0-scsi-0:0:0:0
S: disk/by-label/U
ance: High
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Also affects: sg3-utils (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: curtin
Status: Confirmed => Invalid
** Changed in: curtin
Importance: High => Undecided
** Ch
I have asked upstream to consider the following merge:
https://salsa.debian.org/linux-blocks-team/sg3-utils/merge_requests/2
** Changed in: sg3-utils (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: sg3-utils (Ubuntu Disco)
Status: Confirmed => In Progress
** Change
Summary:
Merge Requests (to be reviewed):
# Debian
MR: https://salsa.debian.org/linux-blocks-team/sg3-utils/merge_requests/2
# Eoan
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/sg3-utils/+git/sg3-utils/+merge/373438
# Disco
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/sg3
Note:
I have to re-submit Disco MR and a new PPA package, as the compiler in
Disco is likely more recent and treating lots of "new warnings" as
errors (-Wimplicit-fallthrough, etc...). I'll do it tomorrow!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Disco PPA package (and MR) is good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833618
Title:
failing to deploy Ubuntu Disco
To manage notifications about this bug go to:
https://bugs.launchpad.
Based on stack trace:
[ 1692.658756] Call Trace:
[ 1692.658762] [c00020739ba9b970] [24008842] 0x24008842 (unreliable)
[ 1692.658769] [c00020739ba9bb48] [c001c270] __switch_to+0x2a0/0x4d0
[ 1692.658774] [c00020739ba9bba8] [c0d048a4] __schedule+0x2a4/0xb00
[ 1692.658777] [c00
Thanks a lot for those 2 files, I compared side by side and it called my
attention:
https://pastebin.ubuntu.com/p/VJXrJHsqRB/
this difference:
+ partmap /dev/vda1 | + partmap /dev/sda
Error: /dev/vda1: unrecognised disk label<
Which Im currently investigating (and
After Andreas and I compared side by side the 2 "set -x" outputs, we
discovered what is happening.
https://pastebin.ubuntu.com/p/WyvnChrqBQ/
And "/dev/vda1" is being caught instead of "/dev/vda", as it happens to
"/dev/sda" (instead of getting "/dev/sda1"). This logic comes a bit
above that execu
17:45 cyphermox: I tried with a serial number for vda, it failed in
the same way
17:46 andreas: not necessarily a serial
17:46 isn't the serial what allows the by-id symlink to be created?
17:46 andreas: that was my previous summary
17:46 in the case
17:46 (about the dbconfig variable)
17:46
Excluding installer issue on ordering, which would be harder to fix AS code
base is highly dependent on assumptions, etc... checking only LVM for previous
releases:
(k)inaddy@kdisco:~$ sudo ls -lah -1 /dev/disk/by-id
total 0
drwxr-xr-x 2 root root 100 Oct 2 13:57 .
drwxr-xr-x 7 root root 1
SUMMARY Of the problem (or a HUGE TL;DR):
- Installer depends on "grub-mkdevice --no-floppy -m -" command to get bootable
devices ordering.
- grub-mkdevice was dropped upstream and it is included in grub2 by a quilt
patch.
- grub-mkdevice orders everything that is in /dev/disk/by-id/* excluding,
Now we will dig into:
lvm2: /lib/udev/rules.d/69-lvm-metad.rules
and check if that udev rule is really needed (what for ?) and then we'll
know what to fix: the installer (grub-mkdevicemap logic) or lvm2 itself
(udev rules).
--
You received this bug notification because you are a member of Ubunt
xenial - does not ask device to grub-install, finds /dev/vda correctly
~ # pvs
PV VGFmt Attr PSize PFree
/dev/vda5 ubuntu-vg lvm2 a-- 29.28g 40.00m
~ # vgs
VG#PV #LV #SN Attr VSize VFree
ubuntu-vg 1 2 0 wz--n- 29.28g 40.00m
~ # lvs
LV VG
Hey Dann, nope, the file changed is Debian related only. I'm glad it
worked, I'll ask server team review and merge then! Tks for testing it!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833618
Titl
On 02/10/19 16:58, Torvald Riegel wrote:
> This example looks like Dekker synchronization (if I get the intent right).
It is the same pattern. However, one of the two synchronized variables
is a counter rather than just a flag.
> Two possible implementations of this are either (1) with all memor
On Wed, 2019-10-02 at 15:20 +0200, Paolo Bonzini wrote:
> On 02/10/19 13:05, Jan Glauber wrote:
>> The arm64 code generated for the
>> atomic_[add|sub] accesses of ctx->notify_me doesn't contain any
>> memory barriers. It is just plain ldaxr/stlxr.
>>
>> From my understanding this is not sufficient
Documenting this here as bug# was dropped from the mail thread:
On 02/10/19 13:05, Jan Glauber wrote:
> The arm64 code generated for the
> atomic_[add|sub] accesses of ctx->notify_me doesn't contain any
> memory barriers. It is just plain ldaxr/stlxr.
>
> From my understanding this is not sufficie
staller (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: grub-installer (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: lvm2 (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Als
No no, you are definitely right, I totally missed upstream change, I did
"on my own", not sure why I thought upstream didn't have any change/fix
(too many bugs in my head perhaps). I'll reply you in the MR, but, we
should go with whatever upstream has done, so delta is reduced. I might
re-do the MR
Possible related bugs:
https://bugs.launchpad.net/ubuntu/eoan/+source/libvirt/+bug/1828495
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1841066
TODOs being worked in there:
LP: #1828495 - [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES
https://bugs.launchpad.net/ubuntu/eoan/+source/li
Thanks for confirming that!
On the other hand, patch seems to be good, even for upstream.
>From the merge request comment:
"""
ACTUALLY, it made little difference because the new rules:
Oct 04 09:34:46 macbook systemd-udevd[30592]: Process '/usr/bin/sg_inq --export
--inhex=/sys/class/scsi_devic
This it the upstream pull request:
https://github.com/hreinecke/sg3_utils/pull/47
And I have updated Debian pull request as well:
https://salsa.debian.org/linux-blocks-
team/sg3-utils/merge_requests/2/commits
I'm preparing updates for Eoan, Disco and Bionic fixes.
--
You received this bug not
* Changed in: sg3-utils (Debian)
Remote watch: Debian Bug tracker #1833618 => None
** Package changed: sg3-utils (Debian) => maas
** Changed in: maas
Status: New => Invalid
** Changed in: maas
Status: Invalid => In Progress
** Changed in: maas
Assignee: (unassi
The following commit:
commit 417e52c13a8156b11c25c411d44bda8b32bf87e4
Author: Peter Rajnoha
Date: Tue Feb 18 07:27:21 2014
udev: create /dev/disk/by-id/lvm-pv-uuid- symlink for a PV
We already have /dev/disk/by-id/dm-uuid-... (which encompasses the
VG UUID and LV UUID in case
16:47 sp.. 60-persistent-storage.rules sets the ID_SERIAL for
USB devices
16:47 it checks first for ATA then ATAPI (with ata_id command)
16:47 if it does not work, it falls back to usb_id (from USB
device descriptor)
16:48 IF you install sg3-utils, it does not check if it is USB
or not, it s
Merge request was done here:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/grub2/+git/grub2/+merge/373792
And the following PPA is available:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1838525
** Description changed:
+ [Impact]
+
+ * Any Eoan installation that depends
Verifying the fix from the PPA:
(k)rafaeldtinoco@keoan:~$ ls /dev/disk/by-id
ls: cannot access '/dev/disk/by-id': No such file or directory
(k)rafaeldtinoco@keoan:~$ sudo grub-mkdevicemap --no-floppy -m -
(hd0) /dev/vda
(hd1) /dev/vdb
This is the expected behavior (by installer).
(k)rafaeld
** Changed in: debian-installer (Ubuntu)
Status: In Progress => Invalid
** Changed in: lvm2 (Ubuntu)
Status: In Progress => Invalid
** Changed in: debian-installer (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: lvm
Alright, I found a much better solution for this:
# SCSI EVPD page 0x80 values
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SCSI}=="1", IMPORT{program}="/usr/bin/sg_inq
--export --inhex=/sys/block/$kernel/device/vpd_pg80 --raw", ENV{ID_SCSI_SN}="1"
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SCSI_SN}!="1" GOTO="sg3_utils
Output from udevtest rules in a USB drive supporting VPDs and SCSI
protocol:
Starting '/usr/bin/sg_inq --export /dev/sdb'
'/usr/bin/sg_inq --export /dev/sdb'(out) 'SCSI_TPGS=0'
'/usr/bin/sg_inq --export /dev/sdb'(out) 'SCSI_TYPE=disk'
'/usr/bin/sg_inq --export /dev/sdb'(out) 'SCSI_VENDOR=Seag
Okay, so I discovered the upstream version is doing something "similar"
to what I just proposed, but in a different and more complete way (not
suitable for a SRU for example). I explained it here:
https://github.com/hreinecke/sg3_utils/pull/47#issuecomment-539545275
And, because of that, I'll pro
o test this,
next merge though).
** Changed in: sg3-utils (Ubuntu Ff-series)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: sg3-utils (Ubuntu Ff-series)
Importance: Undecided => High
** Changed in: sg3-utils (Ubuntu Ff-series)
Status: New
From, at least, commit:
commit b6e681fea79d3d9b479acca1806f32310199053a
Author: Doug Gilbert
Date: Mon Sep 18 16:15:01 2017
https://github.com/hreinecke/sg3_utils branch sles15 synced
20170914; change sg_ll_*() function's 'int noisy' to bool
and beyond we haven't updated sg3-tools. This c
Manoj,
This is a soft lockup in schedule() - a task is waiting I/O completion -
inside a KVM guest.
The guest kernel has a completion that will be awaken, re-scheduling the
task back to a CPU run queue, as soon as the I/O is finished (the I/O
usually contains a handle that, as soon as I/O is conf
ager_Mini_3.0_070851D0E490C776-0:0
ID_SERIAL_SHORT=070851D0E490C776
ID_INSTANCE=0:0
...
Installing the version: 1.44-1ubuntu1 in Disco fixes the ID_SERIAL issue
(enough for now).
** Changed in: sg3-utils (Ubuntu Ff-series)
Status: Confirmed => Fix Released
** Changed in: sg3-utils (Ubunt
Will provide SRU proposal (Disco and Bionic) later today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833618
Title:
MAAS can't deploy Ubuntu if ID_SERIAL of any block device is broken
(USB pend
Provided a fix for Ubuntu Disco at the PPA and pushed changes into the
merge request.
---
# Ubuntu Disco (showing the problem)
kernel: usb 2-6: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
kernel: usb 2-6: New USB device found, idVendor=1b1c, idProduct=1a0c,
bcdDevice= 1.00
@rharper: feel free to review the MR for Disco and Bionic (they're
basically the same).
server-hwe team: feel free to test version from the PPA:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1833618
I think this is it, if no bad feedback, SRU is good to go in my POV.
--
You received th
IIRC the unique symlink for the multipathed device will be named:
/dev/disk/by-id/dm-uuid-mpath-36006016095b03a00a8b3bc647644e711
this will guarantee mount wont round-robin through same UUIDs for
multiple devices.
Been there already :(
--
You received this bug notification because you are a me
NOTE for myself (for the future merge w/ upstream):
BTW, I got feedback from upstream developer saying that my logic of
skipping VPD 0x83, if VPD 0x80 is not there - to avoid the big delay for
the device addiction - can't be done. In his own words:
"""
SPC devices are a different can of worms, an
@ed,
I just finished the backport to Eoan it was straightforward, I'll finish
tests tomorrow with HA related software and networkd enabled HA
clusters. After that I'll give you a better estimation about Disco and
Bionic.
This is the total size of changes (systemd-networkd-tests.py is not so
great
s'
[0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes,
using 'standard' format.
...
** Affects: qemu (Ubuntu)
Importance: Undecided
Assignee: Rafael David Tinoco (inaddy)
Upstream discussion regarding the topic can be found here:
http://lists.nongnu.org/archive/html/qemu-devel/2016-04/msg02597.html
And it is well documented in the .patch inside debdiff.
Thank you for considering this fix.
Best,
Rafael
--
You received this bug notification because you are a mem
** Patch added: "qemu_2.5+dfsg-5ubuntu10.38.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1828288/+attachment/5262436/+files/qemu_2.5+dfsg-5ubuntu10.38.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Hey Christian,
sorry for missing the SRU template, I was in hurry to create a package
for myself and some local needs. I'll do it right now, feel free to SRU
it whenever is good for you based on other fixes I know you usually take
care off.
Thanks a lot!
--
You received this bug notification be
** Description changed:
+ [Impact]
+
+ * QEMU does not work in some AMD hardware when using host-passthrough
+ as cpu-mode (usually to allow nested KVM to work).
+
+ [Test Case]
+
+ * to use Xenial qemu (1:2.5+dfsg-5ubuntu10.36 ou 1:2.5+dfsg-5ubuntu10.37)
+ * to use the following XML file: h
** Changed in: qemu (Ubuntu Xenial)
Status: New => In Progress
** Changed in: qemu (Ubuntu)
Status: In Progress => Fix Released
** Changed in: qemu (Ubuntu Xenial)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification be
I received an e-mail ~2 hours ago telling me:
"""
from: shahul hameed <1828...@bugs.launchpad.net> via canonical.com
** Patch removed: "qemu_2.5+dfsg-5ubuntu10.38.debdiff"
https://bugs.launchpad.net/ubuntu/xenial/+source/qemu/+bug/1828288/+attachment/5262436/+files/qemu_2.5+dfsg-5ubuntu10.
** Patch added: "qemu_2.5+dfsg-5ubuntu10.38.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1828288/+attachment/5264449/+files/qemu_2.5+dfsg-5ubuntu10.38.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Changed in: linux (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439872
Title:
kernel panic involving drbd
To man
** Changed in: linux (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: linux (Ubuntu Precise)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Changed in: tightvnc (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626758
Title:
tightvncserver doesn't work
** Changed in: linux (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389787
Title:
3.11 and 3.13 EXT4 race condit
** Changed in: linux (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496942
Title:
Infiniband (mellanox) SR-IOV
** Changed in: linux (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: linux (Ubuntu Precise)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Changed in: linux (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447763
Title:
HP Proliant Servers suffer from cpuf
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member
> > sudo perf record -a -F $((250*100)) -e cycles:u --
> > /usr/bin/qemu-system-x86_64 -name guest="guest"
>
> I instead attached perf to the qemu process after it was spawned by
> libvirt so I didn't have to worry about producing a working qemu
> cmdline. I let it run for several seconds whil
Attached file is already the stdio, sorry for prev message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838575
Title:
passthrough devices cause >17min boot delay
To manage notifications about th
Sorry Robie,
I missed the template. Now its good to go I believe.
** Description changed:
+ [Impact]
+
+ * DEP8 race condition for ppc64el (LP: #1836593): intermittent
+ migration regressions.
+
+ * growpart: fix bug when file image ends in a digit (LP: #1835124):
+ image files can't end i
** Changed in: chrony (Ubuntu Disco)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836929
Title:
chrony has migration regressions from autopkgtests (disco
** Changed in: chrony (Ubuntu Disco)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836882
Title:
autopkgtest due to other packages changing
To manage not
Chrony issue was solved in here:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1836929
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831775
Title:
ss seems broken when using multiple filte
** Description changed:
- With the default installation on Ubuntu 19.04 ctdb does not start as it
- cannot create its PID file:
+ [Impact]
+
+ * LP: #722201 - SAMBA CTDB cluster suite does not work for High Available
NFS setups
+ * LP: #1821775 - ctdb cannot create PID file
+ * LP: #1828799 -
** Description changed:
+ [Impact]
+
+ * LP: #722201 - SAMBA CTDB cluster suite does not work for High Available
NFS setups
+ * LP: #1821775 - ctdb cannot create PID file
+ * LP: #1828799 - Package ctdb does not create directories in /var/lib/ctdb
+
+ [Test Case]
+
+ * Installing CTDB and
401 - 500 of 2815 matches
Mail list logo
