[Bug 1882774] Re: issues with secondary VMX execution controls
Thanks to everyone who contributed to this fix. I confirm that it works for me in testing with Ussuri and Ubuntu Bionic on vmx-enabled GCP VMs; with fixed qemu packages coming from cloud-archive:ussuri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882774 Title: issues with secondary VMX execution controls To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1882774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851552] Re: since ubuntu 18 bionic release and latest, the ubuntu18 cloud image is unable to boot up on openstack instance
I don't believe this is to do with networking-calico, so will mark as Invalid for networking-calico. ** Changed in: networking-calico Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851552 Title: since ubuntu 18 bionic release and latest, the ubuntu18 cloud image is unable to boot up on openstack instance To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1851552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856485] Re: ERROR neutron.manager [-] Plugin 'calico' not found.
Python 3 support was added in Calico v3.15 https://docs.projectcalico.org/release-notes/#v3150 The master networking-calico code now supports Python 3, and no longer Python 2. There is a 'release-v3.15-python2' branch that still supports Python 2, but we are hoping that maintenance of that branch can now be short-lived. ** Changed in: networking-calico Status: New => 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/1856485 Title: ERROR neutron.manager [-] Plugin 'calico' not found. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-calico/+bug/1856485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882774] Re: issues with secondary VMX execution controls
Christian, would it be easy for you to build this for Bionic as well? I run tests with GCP instances as the OpenStack hypervisors, and have hit this bug, so am keen to test your fix. (http://lists.openstack.org/pipermail/openstack- discuss/2020-June/015343.html) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882774 Title: issues with secondary VMX execution controls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1882774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856485] Re: ERROR neutron.manager [-] Plugin 'calico' not found.
Thanks Bence. FYI, in Neutron I believe https://review.opendev.org/#/c/691874/ has already broken Python 2, so the ship has now sailed for almost all new OpenStack deployments (excepting any that are Swift-only, or still using nova-net if that is possible). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856485 Title: ERROR neutron.manager [-] Plugin 'calico' not found. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-calico/+bug/1856485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856485] Re: ERROR neutron.manager [-] Plugin 'calico' not found.
Vasili, I completely agree with you, and I am trying to schedule time for the work needed for it. BTW, you can see the work that I have started, at https://github.com/neiljerram/networking-calico/commits/ci- fixups. (The next class of problems is where the test code expects normal strings and gets b"..." strings instead.) Regarding the PyPI declaration - yes, I'm sorry, this is wrong. I did previously think that our code was already Python 3 compatible, but I'm afraid I misunderstood the situation. I will try to fix the PyPI declaration for the next release... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856485 Title: ERROR neutron.manager [-] Plugin 'calico' not found. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-calico/+bug/1856485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530667] Re: Loading pylint.elc causes emacs24 to hang for a VERY LONG TIME at startup
I would guess that this is because pylint.el includes: (require 'tramp) and that this is more a problem with Tramp startup, than with pylint. I've had slow Tramp startup problems in other contexts unrelated to python. Possibly relevant references: https://magit.vc/manual/magit/Emacs-245-hangs-when-loading- Magit.html#Emacs-245-hangs-when-loading-Magit, which includes: > You can work around the problem by setting tramp-ssh-controlmaster- options. Changing your DNS server (e.g. to Google’s 8.8.8.8) may also be sufficient to work around the issue. https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20015 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530667 Title: Loading pylint.elc causes emacs24 to hang for a VERY LONG TIME at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pylint/+bug/1530667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665698] Re: /etc/qemu-ifup not allowed by apparmor
@Christian: what does the default /etc/qemu-ifup do? Although I'm inclined to accept your argument that my recent change to Nova was a step in the wrong direction, I'm wondering why it seems to work (at least in my testing) in practice. Also, if there was now a change in libvirt to interpret '' as "do nothing", is there something straightforward we could put in the Nova code to detect when libvirt has that fix - and so set '' - and when it doesn't - in which case best to set None. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665698 Title: /etc/qemu-ifup not allowed by apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1665698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572094] Re: Upgrade from 5.0.16-dfsg-2 to 5.0.16-dfsg-3 broke X startup on my Xenial guest
Thanks. After upgrading just the Ubuntu virtualbox packages to 5.0.18 -dfsg-2build1, and rebooting: X starts up. Only wrinkle is that display is not resized (to my monitor) when showing the lightdm login screen. The display _is_ resized correctly when I log in and my normal X session starts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572094 Title: Upgrade from 5.0.16-dfsg-2 to 5.0.16-dfsg-3 broke X startup on my Xenial guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1572094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572094] Re: Upgrade from 5.0.16-dfsg-2 to 5.0.16-dfsg-3 broke X startup on my Xenial guest
I see that that version is now available, so happy in principle to try this. Do I at the same time need to upgrade my Virtualbox install (on Windows) to 5.0.18? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572094 Title: Upgrade from 5.0.16-dfsg-2 to 5.0.16-dfsg-3 broke X startup on my Xenial guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1572094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572094] [NEW] Upgrade from 5.0.16-dfsg-2 to 5.0.16-dfsg-3 broke X startup on my Xenial guest
Public bug reported:
I run Ubuntu Xenial as a virtualbox guest on a Windows 10 host. This
morning, after rebooting the guest, I found that X was failing to start
up. (Rebooted several times to confirm this.) I reviewed the packages
that changed yesterday and found that they included upgrading
virtualbox-guest-{dkms,utils,x11} from 5.0.16-dfsg-2 to 5.0.16-dfsg-3.
So then I manually downloaded the .debs for 5.0.16-dfsg-2, and installed
those using 'dpkg -i'. Then rebooted, and X starts correctly again.
Apparent conclusion: X start up was broken by the the upgrade from
5.0.16-dfsg-2 to 5.0.16-dfsg-3.
** Affects: virtualbox (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/1572094
Title:
Upgrade from 5.0.16-dfsg-2 to 5.0.16-dfsg-3 broke X startup on my
Xenial guest
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1572094/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
