The fact that the sources should be mostly the same and Bionic working
while Cosmic fails leaves me puzzled - maybe after all this is like a
math library that changed.
I'll change my repro build setup to have Bionic and Cosmic builds of the
same source (will take a while) ...
--
You received
Reference: wondered while debugging for bug 1791010
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791018
Title:
self-test errors do not break the build
To manage notifications about this bug go
There was no obvious obstacle that came to our mind blocking the new
netboot image to be used on the older qemu. If working Maas could
package that as a helper for s390x until later versions (>=DD) would
provide their own one.
Next: I need to give this a try at some point to check if it is
On Thu, Sep 6, 2018 at 9:01 AM Andres Rodriguez
wrote:
> What about getting qemu 3.0 into cosmic?
>
Options:
- SRU-ing qemu 3.0 to Bionic - obviously not, not even discussing this
- It will most likely be available via Ubuntu-Cloud-Archive-Stein (based on
DD) later on next cycle.
- 3.0 in a PPA
Oh well we can.
Debugging from what I learned off the ASM I found the following TL;DR that I
put on the upstream bug:
TL;DR:
- the bug is trying to run vmtoolsd on non vmware systems
- it is stupid and ConditionVirtualization=vmware should prevent that issue
from existing
- Old versions (10.2)
Maybe it inherits the LANG settings, but the parent should be init right.
Maybe even through the restart from your ssh shell or something?
If you start an xinet process yourself (not the service).
What will its LANG be?
Please ensure your shell doing so has the ones you want.
Like:
ensure env is
We want to fix it in open-vm-tools but I also added a sytemd bug task to
get more opinions.
@systemd
As ConditionVirtualization=vmware should have prevented the issue in the first
place, is there any rumor or known issues of that not being reliable?
** Also affects: systemd (Ubuntu)
>From your log:
ago 30 21:35:42 gatzu-HP-Notebook amavis[4947]: The value of variable
$myhostname is "gatzu-HP-Notebook", but should have been
ago 30 21:35:42 gatzu-HP-Notebook amavis[4947]: a fully qualified domain
name; perhaps uname(3) did not provide such.
ago 30 21:35:42
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
Ack to the case
Ack to the analysis
Ack to the fix being better escaping so that this isn't an issue anymore
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791139
Title:
Not bad:
https://www.thezdi.com/blog/2017/8/1/pythonizing-the-vmware-backdoor
https://sites.google.com/site/chitchatvmback/backdoor
I think VMWare can reconstruct the actual call, lets add them the full
regs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Code isn't generated:
open-vm-tools/lib/backdoor/backdoorGcc64.c
Backdoor_InOut(Backdoor_proto *myBp) // IN/OUT
{
uint64 dummy;
__asm__ __volatile__(
#ifdef __APPLE__
/*
* Save %rbx on the stack because the Mac OS GCC doesn't want us to
* clobber it - it
Please ensure /etc/default/locale is valid and also the package "locales" is
correctly installed.
If using any uncommon locales you will see messages of them not being available
(to safe space).
YOu might have to run "sudo locale-gen " to regenerate these.
Overall it looks like a broken config
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
>From your log:
newaliases: fatal: file /etc/postfix/main.cf: parameter mydomain: bad parameter
value: 04.3
This config is broken, it must be a valid domain name.
It might have derived it from your hostname as other packages do as well.
Please fix the config file, then upgrades will work.
--
This bug is present in Debian too. So it would be best fixed in Debian,
and then Ubuntu will pick it up on the next merge.
Being the original reporter would you mind also filing a bug with Debian please?
If you do so report here the bug number so we can link both together.
** Tags added:
Verified by reporter, setting tags ...
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+
+ * The new version of open-vm-tools we recently SRUed had an issue
+that if started in non-VMWare environments (protected by systemd
+condition-virtualization, but people fake VMware envs) would segfault.
+
+ * It is fine to "not work there" but
** Description changed:
+ [Impact]
+
+ * Debian delta we had carried renders the udev rules of upstream
+dysfunctional.
+
+ * Drop the Debian Delta to follow upstream more closely and fix this
+ bug.
+
+ [Test Case]
+
+ * Set up a VMWare guest
+ * boot into that guest
+ * The disks
FYI - Smoser and I started to prep SRU work for this.
But once we agree on the content I'd be really happy if someone who was
affected by the upgrade issue (and therefore has a valid and "real" iscsi
setup) would test from the PPA before shoving that into the SRU queue.
I subscribed Chris
Hi Timo,
I can't reproduce this (I'm sure the bug is right, but I lack the env to do
so), but maybe you could quickly check this for me.
Could you check if reverting the following change:
-ACTION=="add", SUBSYSTEMS=="scsi", ATTRS{vendor}=="VMware*",
ATTRS{model}=="Virtual disk*",
Thanks for the quick turnaround.
That is a change that came in by Debian, which it seems we should remove
when on version 10.3 and >=Bionic.
@Oliver - I think you can abort your investigation as upstream is ok.
I have another fix for open-vm-tools in the pipe, I think I'll try to
address both
I tried backporting the upstream fix that came up in our discussion.
It fixes the crash back to how it was in Xenial (no segfault).
There still won't be much reason to run in non-VMWare envoronments, but this
isn't what this was about.
It is working just fine.
Preparing a MP to review and a
** Description changed:
[Impact]
* Service is running uselessly which is consuming a few cycles/memory as
well as rasising general concerns e.g. on minimizing attack surfcae of
a system.
- * This is also the only service in a default server install which pulls
+ * This is
2a) is an upstream decision to have better disk integrity guarantees.
There is a release notes entry since 17.10 (which is also refrenced from the
18.04 release notes)
=> https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes#qemu_2.10
2b) is I think an upstream change by the PPC devs actually.
Pre update test:
$ sudo ./test-lp1789659.sh
+ concurrency=40
+ duration=60
+ guests=4
+ uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily
arch=amd64 release=bionic label=daily
+ date +%F %T
+ starttime=2018-09-10 10:16:58
+ set +x
+ sleep 60s
uvt-kvm: error: libvirt:
Started a guest with Bionic and Kernel 4.18 - working due to the updated
apparmor profile.
We already had general regression tests on the identical PPA content, not
redoing the same.
Setting verified.
** Tags removed: verification-needed verification-needed-bionic
** Tags added:
FYI: Reported to Debian as well, linked the bug here
** Bug watch added: Debian Bug tracker #908475
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908475
** Also affects: open-vm-tools (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908475
Importance: Unknown
Full Disclosure: I never tried the latter on s390x so far
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790901
Title:
How to use s390x pxelinux style network booting from qemu 3.0 in
bionic
To
FYI:
remember
to be able to deploy that extra netboot image without conflict with the base
system.
See https://libvirt.org/formatdomain.html#elementsNICSROM
But do not derive too far from the usual paths, or you will need
apparmor rules to allow qemu accessing it.
--
You received this bug
You are the tftp/pxelinux experts more than I am.
I follow our tftp and libvirt setup as in [1]
But instead of building a complex single purpose pxelinux.0
All the new "code" youneed is actually inside that boot image.
So no need to build huge things, instead replace
Hmm,
the Debian maintainer said it works fine for him.
I OTOH finally got a VM System as well and I can confirm the 30 seconds.
$ cat /sys/block/sd[a-c]/device/timeout
30
30
30
Reverting the udev rule change helps me just as much as it helped you
Timo.
I verified and wonder where these rules
But merging we tried to follow upstream more, so we dropped
ATTRS{timeout}=="?*"
but keeping the nicer Debian style
ATTR{timeout}="180"
But while not perfect that would still work.
But the other part was about DEVTYPE which upstream has adopted.
So we exchanged Debians
Reproducing issue in Bionic as-is:
$ systemctl reload unbound
Job for unbound.service failed because a timeout was exceeded.
See "systemctl status unbound.service" and "journalctl -xe" for details.
Log:
Aug 31 05:36:18 b systemd[1]: Reloading Unbound DNS server.
Aug 31 05:36:18 b unbound[827]:
Reported upstream as https://gitlab.isc.org/isc-
projects/bind9/issues/520
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752411
Title:
bind9-host, avahi-daemon-check-dns.sh hang forever causes
@Trent - since you had the most reproducible setup could you take a look
at verifying also the Bionic upload?
Also anyone else affected with the VPN cases please give it a try.
Finally, thanks Marc D. for adding all the Data.
If it is really hanging on that epoll like forever we might want to
Hi Sopa,
the actual terminal log of DPKG was not attached so I have to guess a lot here.
I found this in your journal error log:
Mar 04 19:37:24 hostname systemd[1]: Failed to start PostgreSQL Cluster 10-main.
Mar 04 19:37:24 hostname systemd[1]: NetworkManager-wait-online.service:
Service lacks
Your assumption is right, this is from the conflict of the old and new
libmysqlclient-dev.
But then OTOH the newer should upgrade the older and just replace things.
The only thing I wonder is that you have a 14.04 version of that lib and
you install the 18.04 version which breaks.
LTS upgrades
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
us: New => Won't Fix
** Changed in: qemu (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: qemu (Ubuntu Bionic)
Assignee: Christian Ehrhardt (paelzer) => Ubuntu Security Team
(ubuntu-security)
--
You received this bug notification because you are a member of Ubu
I have made a Bionic version with the fix available for testing in [1].
I'd ask people to test this. Since it changes behavior of a default disabled
feature this call applies almost exclusively to people that have set up qemu
with "-sandbox=..." or configured libvirt to do so with
Thanks Scott for the report, we don't have 7.8 yet (Cosmic will be released
with 7.7).
But as I read the issue this already is an issue for all older SSH servers as
soon as somebodies client is new.
@cjwatson - you are usually watching over openssh, did you see this
already. How should we
no need for the kernel bot, set to confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782205
Title:
KVM SnowRidge enable
This is also the reason for all the fails in [1] which actually flags a
real issue as reported in this bug
[1]: http://autopkgtest.ubuntu.com/packages/m/makedumpfile/cosmic/s390x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For your testing here the default content of zipl.conf on a cloud-img
KVM guest
$ cat /etc/zipl.conf
# This has been modified by the cloud image build process
[defaultboot]
default=ubuntu
[ubuntu]
target = /boot
image = /boot/vmlinuz
parameters = root=LABEL=cloudimg-rootfs
ramdisk =
Ack to the report.
While I had some systems (lpar) which worked I was trivially able to confirm
that it doesn't work on KVM guests based on cloud images.
I see this on install of kdump-tools (default answers to debconf)
Setting up kdump-tools (1:1.6.4-2) ...
Using config file '/etc/zipl.conf'
Public bug reported:
Availability: PMDK is rather new (Cosmic) and builds for amd64 (main purpose)
There also is arm code in the lib, but lacking any request as well as
arm-nvdimm HW it isn't built there.
Rationale:
- There is a request to enhance qemu nvdimm support (bug 1745900) which is
Public bug reported:
Availability: GPSD is available since quite a while and builds for all
architectures
Rationale:
- The package is the de-facto way to feed GPS HW-based time info into chrony
which became the main NTP server with Bionic.
- All users using HW assisted NTP would be glad to
FYI - filed bug 1790856 for the MIR of the pmem library.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745900
Title:
[Bug][KVM][Crystal Ridge] Lack of data persistence guarantee of QEMU
writes
** Description changed:
[Impact]
* Libvirt does an overzealous check on concurrent hash usage which breaks
some automation like for example Terraform. Upstream moved the need to
lock up the stack where applicable and dropped the checks as they were
superfluous.
*
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3404
Tested and verified the proposed fix working as reported on similar
tests done before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment removed: "Helper to test and verify the issue"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1789659/+attachment/5184890/+files/test-lp1789659.sh
** Attachment added: "Helper to test and verify the issue"
*** This bug is a duplicate of bug 1745900 ***
https://bugs.launchpad.net/bugs/1745900
** This bug has been marked a duplicate of bug 1745900
[Bug][KVM][Crystal Ridge] Lack of data persistence guarantee of QEMU writes
to host PMEM
--
You received this bug notification because you are a
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745900
Title:
[Bug][KVM][Crystal Ridge] Lack of data persistence guarantee
FYI: I dupped the other bug that came up by Paul onto this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745900
Title:
[Bug][KVM][Crystal Ridge] Lack of data persistence guarantee of QEMU
I evaluated the changes here and must postpone them to Ubuntu 19.04
To some extend it is that the changes are actually noisy to backport, but that
would appear to be doable.
To some other that the info on the actual changes was made available 1 day
after feature freeze and this clearly is a
** Patch added: "suggestion to consider as debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1789841/+attachment/5182555/+files/lp-1789841-bump-timeouts.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hi,
being one of the many that hit retry on systemd autopkgtest rather often I was
checking the logs and found more than 50% of the cases dying on timeouts which
seemed to be working but slow.
I wanted to suggest bumping the timeouts to hopefully improve the
success rate
Hi Mathieu,
I know about that but taking it down to a suggest would be too much of a
regression for users of local vrtiualization with gui.
Even I not really being a UI user often enough run it on a server with X
forwarding to check bugs/features due to reports we get - so UI is used
often
I think all prep is complete, uploaded for the consideration by the SRU
team
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787208
Title:
Openvpn routing issue
To manage notifications about this
Hi Joseph,
neither me nor James have realized that this waited for a retest on our side.
The old kernel that you had linked is gone by now (together with Artful I
assume) :-/
Would you mind prepping a new test kernel of your choice (This still is
an issue in cosmic, so whatever works best for
TL;DR:
- a KVM guest with the kernel change as identified above
- works on Bionic host (kernel 4.15 / qemu 2.11 / libvirt 4.0)
- migrating on a Xenial host (kernel 4.4 / qemu 2.5 / libvirt 1.3.1) fails
VQ 0 size 0x100 Guest index 0x8101 inconsistent with Host index 0x81: delta
0x8080
error
With the insight so far we can remove the systemd task again.
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791220
Title:
increased crash rate since 10.3
Your upload seems to build fine on all architectures and checking ppc64
in particular the tests that formerly failed are good now.
The servers were restarted 167 times
Spent 1178.435 of 482 seconds executing testcases
Completed: All 768 tests were successful.
157 tests were skipped, 59 by
** Also affects: open-vm-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: open-vm-tools (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
PPA prepared at:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3412
MP:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/354695
Test of the case on the PPA is successful.
But I'll need a regression check on that before going on.
** Changed in: qemu
** Bug watch added: Red Hat Bugzilla #1623929
https://bugzilla.redhat.com/show_bug.cgi?id=1623929
** Also affects: openssh (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1623929
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Filed https://askubuntu.com/questions/1048157/libvirt-kvm-guest-failing-
due-issues-in-the-apparmorprofile/1048158#1048158 in case people search
there first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Due to translations this might be harder to maintain than it is worth
(code-wise).
Yet I created the wiki page and if it is helpful, then it will be recommended
more often and show up more in searches.
I'll consider it fix-released due to the documentation and instead of
the code change will
As discussed on IRC, this isn't important for the last week of Artful before
EOL.
But it is for the Cloud Archives longer time I'd think.
So I added a UCA task for them to take a look.
** Also affects: qemu (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: qemu
I was just about to prep an upload, but given we have approx 1-3 weeks
left until EOL and the SRU would take at least 1 week I think this makes
no sense anymore - story would be way different if Xenial would be
affected.
But on Xenial it is ok:
root@x:~# vim bad_flake8.py
root@x:~# flake8
I have built a test ppa with the fix [1].
That fixes the issue for me, I'd need a review [2] to feel confident
going forward but it LGTM.
[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3309
[2]:
** Description changed:
+ [Impact]
+
+ * Backport Debian fix for a crash in byobu due to libslang2
+
+ [Test Case]
+
+ * byobu-screen
+ * in there hit F9 or start byobu-config
+ * without the fix this crashes
+
+ [Regression Potential]
+
+ * This is changing a libs implementation and
+
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [Test
Updated the Debian bug so they are aware as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537528
Title:
byobu-config segfault with screen backend
To manage notifications about this bug go
I checked once more to be sure, artful (and later) is ok
** Changed in: slang2 (Ubuntu)
Status: New => Triaged
** Also affects: newt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: slang2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also
Since Cosmic is still open and auto-syncing I prepared that as fix [1]
for Debian to sync it in.
[1]: https://salsa.debian.org/ssh-team/openssh/merge_requests/2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Steps to reproduce
uvt-simplestreams-libvirt --verbose sync --source
http://cloud-images.ubuntu.com/daily arch=amd64 release=xenial label=daily
uvt-kvm create --password ubuntu x-freeze arch=amd64 release=xenial label=daily
Add this to the guest definition and restart it
>From the
** Changed in: qemu (Ubuntu Xenial)
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/1587065
Title:
btrfs qemu-ga - multiple mounts block fsfreeze
To manage
** Also affects: slang2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1537528
Title:
byobu-config segfault with screen backend
To manage
>From upstream a few fair questions, this goes on at
https://www.spinics.net/lists/linux-rdma/msg69992.html but the archive
updates slowly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794825
Summarizing Upstream feedback:
#1
# apt install ibacm
[...]
ibacm.service failed
Question: why does it even start it is meant to be socket activated
That is correct, it should be - but it only uses dh_installinit which
will start it as it doesn#t know about service/sockets.
I need to experiment
A full set of regression tests completed on the PPA and the MP got a
check for silly mistakes - both are good. Also the Dep8 tests completed
on the Bileto ticket and completed all but the known flaky i36 systemd
test.
I think we are ready to push this to Bionic.
Uploading it for the review of the
That was the last bit missing, thereby MIR approved for mecab
Since the changes that pull it in are (currently) not in the archive the state
is "in progress" [1], please go on pulling it in with your early merges for
19.04.
[1]: https://wiki.ubuntu.com/MIRTeam#Process_states
** Changed in:
Discussion upstream continues, the suggested approach with the Checkpath isn't
helping.
I have crated some debug code for the discussion and replied to the ML thread
once more.
- https://gist.github.com/cpaelzer/fc3abd28f81eda55ffb317bb4091bf48
-
Added an SRU Template and did a test build in [1]
LGTM, opening up the MP [2] for review towards extra confidence.
[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3478/+packages
[2]:
https://code.launchpad.net/~paelzer/ubuntu/+source/virt-manager/+git/virt-manager/+merge/356647
As Ryan I can not reproduce locally - hrm.
The crash in your log is the root-fs mount.
[ 22.524541] VFS: Cannot open root device
"squash:http://172.16.99.2:5248/images/ubuntu/amd64/generic/bion; or
unknown-block(0,0): error -6
[ 22.575588] Please append a correct "root=" boot option; here
After DHCP is up it works just fine.
(initramfs) wget http://192.168.122.1:80/squashfs
Connecting to 192.168.122.1:80 (192.168.122.1:80)
squashfs 100% |***| 174M 0:00:00 ETA
(initramfs) mount -t squashfs squashfs /root
(initramfs) mount
rootfs on / type
Hi Jürgen,
well lets take a look at your network that is associated to the guest.
Your guest XML representation will have a network definition with a source.
Like this:
Check `virsh dumpxml ` to get that.
Once you know the name check the network - in my case "default".
$ virsh net-info
Working on this I found by accident that I actually can reproduce:
VFS: Cannot open root device "squash:http://192.168.122.1:80/squashfs; or
unknown-block(0,0): error -6
But the way I got there lets assume some more potential reasons.
I got there by breaking my initramfs :-)
After realizing
Repro crash with the case - still triggering
Installed 32bit Test kernel
It boots this one:
Linux 4.15.0-36-generic #40 SMP Fri Oct 12 00:17:54 UTC 2018
Seems to have no "special" version suffix to identify it other than #40 and
build time.
But #40 and the build time indicate this is the
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
I hope the general hints above help you to resolve your situation, but as-is
there isn't enough to help you or fix anything.
Since there isn't enough information in your report to differentiate
between a local
Ok,
at lvl1 definition Openstack came up with it's cpu modelling which in this case
is actually:
cpu mode='host-passthrough
+ a bunch of required features
That is what gives your LVL1 the invpcid feature (so far so good).
At lvl2 we have
Nova:
vs uvtool
Thanks for the data
MP approved and made available to the SRU team in Bionic-unapproved.
** Changed in: virt-manager (Ubuntu Bionic)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Jochen, is that in
https://salsa.debian.org/debian/libpam-mount/commits/master ?
I didn't see it there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404599
Title:
libpam-mount installs
Thanks for the update Alex.
In general the package seems rather different than upstream in terms of systemd
integration.
We will have to take a wider look at this than just this line.
** Tags added: server-next
** Changed in: rabbitmq-server (Ubuntu)
Importance: Undecided => Medium
--
You
Hi Juan,
>From your logfiles:
2017-04-19T11:52:27.511052Z 0 [ERROR] InnoDB: The Auto-extending innodb_system
data file './ibdata1' is of a different size 640 pages (rounded down to MB)
than specified in the .cnf file: initial 768 pages, max 0 (relevant if
non-zero) pages!
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Yes this change (the Debian version of it, not yours) is in since 3.3.1-3
Thanks a lot Mark! for the ping on this forgotten bug also for the
documentation of the config in regard to BackupZeroFilesIsFatal if previously
set to 1.
(And also thanks for your upstreaming work on this)
** Also
1001 - 1100 of 10013 matches
Mail list logo
