[Bug 2060745] Re: nbd-client fails to connect when using /etc/nbdtab on Ubuntu 24.04 (Noble)

[Thiago Martins]

It seems to be an upstream issue:
https://github.com/NetworkBlockDevice/nbd/issues/156

** Bug watch added: github.com/NetworkBlockDevice/nbd/issues #156
   https://github.com/NetworkBlockDevice/nbd/issues/156

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060745

Title:
  nbd-client fails to connect when using /etc/nbdtab on Ubuntu 24.04
  (Noble)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2060745/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060745] [NEW] nbd-client fails to connect when using /etc/nbdtab on Ubuntu 24.04 (Noble)

[Thiago Martins]

Public bug reported:

[ Impact ]

NBD users who want to use /etc/nbdtab will face issues when trying to
start the NBD Client. Trying to use the `systemd` service also doesn't
work.

[ Test Plan ]

Inside a Noble VM (not a container):

# apt update
# apt install -y nbd-client nbd-server
# modprobe nbd
# truncate -s 1T /vol-0.img
# cat > /etc/nbd-server/conf.d/exports.conf << _EOF_
[vol0]
exportname = /vol-0.img
_EOF_
# systemctl restart nbd-server.service

Verify that NBD is working properly:

# nbd-client localhost /dev/nbd0 -name vol0

It should work.

To clean it up:

# nbd-client -d /dev/nbd0

Now, trigger the problem:

# cat >> /etc/nbdtab << _EOF_
nbd0 localhost vol0
_EOF_
# nbd-client nbd0

You should see the error:

# nbd-client nbd0
Error: Socket failed: Connection refused

Further attempts with `systemd` also fail:

# systemctl restart nbd@nbd0
Job for nbd@nbd0.service failed because the control process exited with error 
code.
See "systemctl status nbd@nbd0.service" and "journalctl -xeu nbd@nbd0.service" 
for details.

And the logs:

# journalctl -u nbd@nbd0.service -n 25
Apr 09 21:56:17 noble-nbd-1 systemd[1]: nbd@nbd0.service: Dependency 
Before=dev-nbd0.device ignored (.device units cannot be delayed)
Apr 09 21:56:17 noble-nbd-1 systemd[1]: Starting nbd@nbd0.service - NBD client 
connection for nbd0...
Apr 09 21:56:17 noble-nbd-1 nbd_client[5698]: Socket failed: Connection refused
Apr 09 21:56:17 noble-nbd-1 nbd-client[5698]: Error: Socket failed: Connection 
refused
Apr 09 21:56:17 noble-nbd-1 nbd_client[5698]: Exiting.
Apr 09 21:56:17 noble-nbd-1 systemd[1]: nbd@nbd0.service: Main process exited, 
code=exited, status=1/FAILURE
Apr 09 21:56:17 noble-nbd-1 systemd[1]: nbd@nbd0.service: Failed with result 
'exit-code'.
Apr 09 21:56:17 noble-nbd-1 systemd[1]: Failed to start nbd@nbd0.service - NBD 
client connection for nbd0.

** Affects: nbd (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/2060745

Title:
  nbd-client fails to connect when using /etc/nbdtab on Ubuntu 24.04
  (Noble)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2060745/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055294] Re: /usr/lib/grub/grub-multi-install fails on noble-daily

[Thiago Martins]

Hi! I was `do-release-upgrade -d` an Ubuntu 22.04 to Ubuntu 24.04 to
test and got bitten by this bug too! lol

The command `/usr/lib/grub/grub-multi-install --target=x86_64-efi`
returns 10, causing `dpkg --configure grub-efi-amd64-signed` to fail.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055294

Title:
  /usr/lib/grub/grub-multi-install fails on noble-daily

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2055294/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot

[Thiago Martins]

** Description changed:

  The `systemd` service for starting the NBD Clients on boot isn't
  working.
  
  ### Steps to Reproduce:
  
  0. Install NBD
  
  -
  apt install nbd-server nbd-client
  -
  
- 
  1. Prepare an NBD server with a disk image to share. For instance:
  
  -
  truncate -s 1T /vol-0.img
  -
  
- 
- 2. Configure the NBD server by adding the following to 
`/etc/nbd-server/conf.d/exports.conf`:
+ 2. Configure the NBD server by adding the following to `/etc/nbd-
+ server/conf.d/exports.conf`:
  
  -
  [vol0]
  exportname = /vol-0.img
  -
- 
  
  3. Configuring the client connection in `/etc/nbdtab`:
  
  Contents of `/etc/nbdtab`:
  
  -
  nbd0 localhost vol0
  -
- 
  
  4. Enable it on `systemd`:
  
  -
  systemctl enable nbd@nbd0
  -
  
  Here's what I see:
  
  -
  # systemctl enable nbd@nbd0
  Created symlink /etc/systemd/system/dev-nbd0.device.requires/nbd@nbd0.service 
→ /lib/systemd/system/nbd@.service.
  Unit /lib/systemd/system/nbd@.service is added as a dependency to a 
non-existent unit dev-nbd0.device.
  -
  
- 
  5. Add `nbd` auto-load to system'd boot:
  
  echo nbd > /etc/modules-load.d/nbd.conf
- 
  
  6. Reboot
  
  -
  sudo reboot
  -
  
- 
  7. The service not coming up on the system's boot. Look:
  
  After rebooting the system, the NBD clien for `nbd0` isn't running (but
  it's enabled on systemd).
  
  -
- root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0
+ root@demo-nbd-test:~# systemctl status nbd@nbd0
  ○ nbd@nbd0.service - NBD client connection for nbd0
   Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead)
     Docs: man:nbd-client
  
- Feb 21 22:54:22 cephao-1-ceph-osd-1 systemd[1]: nbd@nbd0.service: Dependency 
Before=dev-nbd0.device ignored (.device units cannot be delayed)
+ Feb 21 22:54:22 demo-nbd-test systemd[1]: nbd@nbd0.service: Dependency 
Before=dev-nbd0.device ignored (.device units cannot be delayed)
  -
  
  But if you try to start it again. It'll work:
  
  -
- root@cephao-1-ceph-osd-1:~# systemctl start nbd@nbd0
- root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0
+ root@demo-nbd-test:~# systemctl start nbd@nbd0
+ root@demo-nbd-test:~# systemctl status nbd@nbd0
  ● nbd@nbd0.service - NBD client connection for nbd0
   Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
   Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago
     Docs: man:nbd-client
  Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, 
status=0/SUCCESS)
     Main PID: 1096 (code=exited, status=0/SUCCESS)
  CPU: 4ms
  
- Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Starting NBD client 
connection for nbd0...
- Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Negotiation: ..size = 
3145728MB
- Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Connected /dev/nbd0
- Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Finished NBD client 
connection for nbd0.
+ Feb 21 22:57:37 demo-nbd-test systemd[1]: Starting NBD client connection for 
nbd0...
+ Feb 21 22:57:37 demo-nbd-test nbd-client[1096]: Negotiation: ..size = 
3145728MB
+ Feb 21 22:57:37 demo-nbd-test nbd-client[1096]: Connected /dev/nbd0
+ Feb 21 22:57:37 demo-nbd-test systemd[1]: Finished NBD client connection for 
nbd0.
  -
  
  So this forces me to have the following `/etc/rc.local` file as a
  workaround:
  
  -
  #!/bin/bash
  sleep 6
  systemctl start nbd@nbd0
  -
  
  Make it executable:
  
  -
  chmod +x /etc/rc.local
  -
  
  Reboot again, it'll be started on next boot!
  
  I don't think that the `/etc/rc.local` should be part of this
  procedure...  =P
  
  NOTE: Don't need to run `update-initramfs -k all -u`.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616

Title:
  The systemd service for NBD Client doesn't come up on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot

[Thiago Martins]

** Description changed:

  The `systemd` service for starting the NBD Clients on boot isn't
  working.
  
  ### Steps to Reproduce:
  
  0. Install NBD
  
-```
-apt install nbd-server nbd-client
-```
+ -
+ apt install nbd-server nbd-client
+ -
+ 
  
  1. Prepare an NBD server with a disk image to share. For instance:
-```bash
-truncate -s 1T /vol-0.img
-```
+ 
+ -
+ truncate -s 1T /vol-0.img
+ -
+ 
  
  2. Configure the NBD server by adding the following to 
`/etc/nbd-server/conf.d/exports.conf`:
-```
-[vol0]
-exportname = /vol-0.img
-```
+ 
+ -
+ [vol0]
+ exportname = /vol-0.img
+ -
+ 
  
  3. Configuring the client connection in `/etc/nbdtab`:
  
  Contents of `/etc/nbdtab`:
  
-```
-nbd0 localhost vol0
-```
+ -
+ nbd0 localhost vol0
+ -
+ 
  
  4. Enable it on `systemd`:
  
-```bash
-systemctl enable nbd@nbd0
-```
+ -
+ systemctl enable nbd@nbd0
+ -
  
  Here's what I see:
  
- ```
+ -
  # systemctl enable nbd@nbd0
  Created symlink /etc/systemd/system/dev-nbd0.device.requires/nbd@nbd0.service 
→ /lib/systemd/system/nbd@.service.
  Unit /lib/systemd/system/nbd@.service is added as a dependency to a 
non-existent unit dev-nbd0.device.
- ```
+ -
+ 
  
  5. Add `nbd` auto-load to system'd boot:
  
- ```
- echo nbd > /etc/modules-load.d/nbd.conf
- ```
+ echo nbd > /etc/modules-load.d/nbd.conf
+ 
  
  6. Reboot
  
-```
-sudo reboot
-```
+ -
+ sudo reboot
+ -
+ 
  
  7. The service not coming up on the system's boot. Look:
  
  After rebooting the system, the NBD clien for `nbd0` isn't running (but
  it's enabled on systemd).
  
- ```
+ -
  root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0
  ○ nbd@nbd0.service - NBD client connection for nbd0
-  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
-  Active: inactive (dead)
-Docs: man:nbd-client
+  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
+  Active: inactive (dead)
+    Docs: man:nbd-client
  
  Feb 21 22:54:22 cephao-1-ceph-osd-1 systemd[1]: nbd@nbd0.service: Dependency 
Before=dev-nbd0.device ignored (.device units cannot be delayed)
- ```
+ -
  
  But if you try to start it again. It'll work:
  
- ```
+ -
  root@cephao-1-ceph-osd-1:~# systemctl start nbd@nbd0
  root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0
  ● nbd@nbd0.service - NBD client connection for nbd0
-  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
-  Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago
-Docs: man:nbd-client
- Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, 
status=0/SUCCESS)
-Main PID: 1096 (code=exited, status=0/SUCCESS)
- CPU: 4ms
+  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
+  Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago
+    Docs: man:nbd-client
+ Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, 
status=0/SUCCESS)
+    Main PID: 1096 (code=exited, status=0/SUCCESS)
+ CPU: 4ms
  
  Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Starting NBD client 
connection for nbd0...
  Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Negotiation: ..size = 
3145728MB
  Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Connected /dev/nbd0
  Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Finished NBD client 
connection for nbd0.
- ```
+ -
  
  So this forces me to have the following `/etc/rc.local` file as a
  workaround:
  
- ```
+ -
  #!/bin/bash
  sleep 6
  systemctl start nbd@nbd0
- ```
+ -
  
  Make it executable:
  
- ```
+ -
  chmod +x /etc/rc.local
- ```
+ -
  
  Reboot again, it'll be started on next boot!
  
  I don't think that the `/etc/rc.local` should be part of this
  procedure...  =P
  
  NOTE: Don't need to run `update-initramfs -k all -u`.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616

Title:
  The systemd service for NBD Client doesn't come up on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot

[Thiago Martins]

I've updated the description to include all the steps necessary to
reproduce the issue on Ubuntu 22.04 (Cloud Image - Server Minimal
install).

This seems to be a `systemd` thing! lol

** Description changed:

  The `systemd` service for starting the NBD Clients on boot isn't
  working.
  
  ### Steps to Reproduce:
+ 
+ 0. Install NBD
+ 
+```
+apt install nbd-server nbd-client
+```
  
  1. Prepare an NBD server with a disk image to share. For instance:
 ```bash
 truncate -s 1T /vol-0.img
 ```
  
  2. Configure the NBD server by adding the following to 
`/etc/nbd-server/conf.d/exports.conf`:
 ```
 [vol0]
 exportname = /vol-0.img
 ```
  
  3. Configuring the client connection in `/etc/nbdtab`:
  
  Contents of `/etc/nbdtab`:
  
 ```
 nbd0 localhost vol0
 ```
  
  4. Enable it on `systemd`:
  
 ```bash
 systemctl enable nbd@nbd0
 ```
  
- 5. The service not coming up on the system's boot. Look:
+ Here's what I see:
+ 
+ ```
+ # systemctl enable nbd@nbd0
+ Created symlink /etc/systemd/system/dev-nbd0.device.requires/nbd@nbd0.service 
→ /lib/systemd/system/nbd@.service.
+ Unit /lib/systemd/system/nbd@.service is added as a dependency to a 
non-existent unit dev-nbd0.device.
+ ```
+ 
+ 5. Add `nbd` auto-load to system'd boot:
+ 
+ ```
+ echo nbd > /etc/modules-load.d/nbd.conf
+ ```
+ 
+ 6. Reboot
+ 
+```
+sudo reboot
+```
+ 
+ 7. The service not coming up on the system's boot. Look:
  
  After rebooting the system, the NBD clien for `nbd0` isn't running (but
  it's enabled on systemd).
  
  ```
  root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0
  ○ nbd@nbd0.service - NBD client connection for nbd0
-  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
-  Active: inactive (dead)
-    Docs: man:nbd-client
+  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
+  Active: inactive (dead)
+Docs: man:nbd-client
  
  Feb 21 22:54:22 cephao-1-ceph-osd-1 systemd[1]: nbd@nbd0.service: Dependency 
Before=dev-nbd0.device ignored (.device units cannot be delayed)
  ```
  
- Then, after a restart, it works:
+ But if you try to start it again. It'll work:
  
  ```
- root@cephao-1-ceph-osd-1:~# systemctl restart nbd@nbd0
+ root@cephao-1-ceph-osd-1:~# systemctl start nbd@nbd0
  root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0
  ● nbd@nbd0.service - NBD client connection for nbd0
-  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
-  Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago
-    Docs: man:nbd-client
- Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, 
status=0/SUCCESS)
-    Main PID: 1096 (code=exited, status=0/SUCCESS)
- CPU: 4ms
+  Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor 
preset: enabled)
+  Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago
+Docs: man:nbd-client
+ Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, 
status=0/SUCCESS)
+Main PID: 1096 (code=exited, status=0/SUCCESS)
+ CPU: 4ms
  
  Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Starting NBD client 
connection for nbd0...
  Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Negotiation: ..size = 
3145728MB
  Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Connected /dev/nbd0
  Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Finished NBD client 
connection for nbd0.
  ```
  
  So this forces me to have the following `/etc/rc.local` file as a
  workaround:
  
  ```
  #!/bin/bash
- systemctl restart nbd@nbd0
+ sleep 6
+ systemctl start nbd@nbd0
  ```
  
- If this is not the proper way of automatically starting a `nbd0` NBD
- client, please, let me know! Perhaps documentation should be more clear.
+ Make it executable:
  
- Interesting reference:
- https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054470
+ ```
+ chmod +x /etc/rc.local
+ ```
+ 
+ Reboot again, it'll be started on next boot!
+ 
+ I don't think that the `/etc/rc.local` should be part of this
+ procedure...  =P
+ 
+ NOTE: Don't need to run `update-initramfs -k all -u`.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616

Title:
  The systemd service for NBD Client doesn't come up on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054470] Re: NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and 20.04

[Thiago Martins]

Oops, wrong bug report. Ignore my previous message.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054470

Title:
  NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and
  20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/nbd/+bug/2054470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot

[Thiago Martins]

I'm testing on Ubuntu 22.04.4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616

Title:
  The systemd service for NBD Client doesn't come up on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot

[Thiago Martins]

Hi Mitchell,

No worries at all!

I forgot to mention another step I took:

```
echo nbd > /etc/modules-load.d/nbd.conf
```

Otherwise it won't load the module on boot.

Perhaps there's also a need to `update-initramfs -k all -u`, not 100%
sure.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616

Title:
  The systemd service for NBD Client doesn't come up on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054616/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054470] Re: NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and 20.04

[Thiago Martins]

Hi Sergio,

Thank you for taking the taking to troubleshoot this!

I forgot to mention another step I took:

```
echo nbd > /etc/modules-load.d/nbd.conf
```

Perhaps there's also a need to `update-initramfs -k all -u`?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054470

Title:
  NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and
  20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/nbd/+bug/2054470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1932028] Re: missing version dependency on distro-info

[Thiago Martins]

Hi,

I also see this problem with fresh installed Xenial.

It's interesting to see that it's a bit tricky to reproduce this
problem. I have to upgrade "ubuntu-advantage-tools" shortly after
installing Xenial.

Cheers!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932028

Title:
  missing version dependency on distro-info

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1932028/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 581796] Re: grub-installer ignores grub2/linux_cmdline_default in preseed

[Thiago Martins]

I'm thinking about this.. Maybe, this is by design! Right?

The way it's today, the options used during the Packer builds, for
example, don't end up on the image! Sounds like a good idea actually.

Gonna take a look at "debian-installer/add-kernel-opts"!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/581796

Title:
  grub-installer ignores grub2/linux_cmdline_default in preseed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/581796/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 581796] Re: grub-installer ignores grub2/linux_cmdline_default in preseed

[Thiago Martins]

I was so annoyed that my "presseded" installations of Ubuntu 20.04
Legacy ISO Server with Packer were ending up with a black screen that
only "ALT + Arrow Right" was bringing the `tty1` back to life...

Then, I realized that the "Packer builds were adding" the "quiet splash"
to the /etc/default/grub file, no matter what I did to pressed regular
options, and this problem brought me to this... 11 years old bug
report!!! Wht?!

So, the workaround proposed on comment #1 worked like a charm, and
finally, my Packer builds produces awesome server images with a nice
verbose boot that goes straight to tty1!

It looks like that won't be fixed since Canonical is moving to the new
subiquity, Cloud-Init based `autoinstall`. Kinda sad. I don't like the
new "Live Server" install media, legacy is way, way better.

Thank you Mathieu!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/581796

Title:
  grub-installer ignores grub2/linux_cmdline_default in preseed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/581796/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1842417] Re: Ubiquity needs support for fscrypt

[Thiago Martins]

I do want home-based encryption but, what about the new `systemd-homed`?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842417

Title:
  Ubiquity needs support for fscrypt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1842417/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882993] Re: Package needs newer version with v2 encryption policy

[Thiago Martins]

I can't wait for it!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882993

Title:
  Package needs newer version with v2 encryption policy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1882993/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818746] Re: `ubuntu-drivers list` output doesn't bear any relation to the input to the install command

[Thiago Martins]

I totally agree with this!

The Additional Drivers doesn't work if your Netplan uses rendered:
networked.

Then, the command line is useless too... How does it work?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818746

Title:
  `ubuntu-drivers list` output doesn't bear any relation to the input to
  the install command

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1818746/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818746] Re: `ubuntu-drivers list` output doesn't bear any relation to the input to the install command

[Thiago Martins]

Never mind... Just `ubuntu-drivers install` did the trick.. LOL

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818746

Title:
  `ubuntu-drivers list` output doesn't bear any relation to the input to
  the install command

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1818746/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818749] Re: `ubuntu-drivers install --gpgpu` could have more informative error messages

[Thiago Martins]

Never mind... Just `ubuntu-drivers install` did the trick.. LOL

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818749

Title:
  `ubuntu-drivers install --gpgpu` could have more informative error
  messages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1818749/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818749] Re: `ubuntu-drivers install --gpgpu` could have more informative error messages

[Thiago Martins]

I totally agree with this!

The Additional Drivers doesn't work if your Netplan uses rendered:
networked.

Then, the command line is useless too... How does it work?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818749

Title:
  `ubuntu-drivers install --gpgpu` could have more informative error
  messages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1818749/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902293] Re: fixed_network_name still exists in drivers except heat

[Thiago Martins]

I actually changed the value os `os_distro` from just "coreos" to 
"fedora-coreos" and it worked!
I mean, I'm not seeing this error anymore.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902293

Title:
  fixed_network_name still exists in drivers except heat

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1902293/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902293] Re: fixed_network_name still exists in drivers except heat

[Thiago Martins]

I'm facing the very same problem with OpenStack Ansible, branch
`stable/ussuri`, on Ubuntu 20.04.1.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902293

Title:
  fixed_network_name still exists in drivers except heat

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1902293/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1677398] Re: Apparmor prevents using storage pools and hostdev networks

[Thiago Martins]

I found the quick "fix"...

"Double check that `security_driver = "none"` is uncommented in
`/etc/libvirt/qemu.conf` and issue `sudo systemctl restart libvirt-bin`
to restart the daemon."

https://github.com/dmacvicar/terraform-provider-libvirt/commit/22f096d9

Doesn't sound good. But it worked!  lol

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677398

Title:
  Apparmor prevents using storage pools and hostdev networks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1677398/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1677398] Re: Apparmor prevents using storage pools and hostdev networks

[Thiago Martins]

Hey guys,

I'm trying to play with Terraform and it's failing too! Ubuntu 20.04.1.

Guide:

https://fabianlee.org/2020/02/22/kvm-terraform-and-cloud-init-to-create-
local-kvm-resources/

NOTE: I'm using the latest "terraform-provider-libvirt-0.6.3" binary for
Ubuntu 20.04.

The "terraform apply" fails with:

Error: Error creating libvirt domain: virError(Code=1, Domain=10,
Message='internal error: process exited while connecting to monitor:
2020-11-17T01:55:34.375538Z qemu-system-x86_64: -blockdev
{"driver":"file","filename":"/var/lib/libvirt/images/simple-os_image
","node-name":"libvirt-2-storage","auto-read-
only":true,"discard":"unmap"}: Could not open '/var/lib/libvirt/images
/simple-os_image': Permission denied')

The generated XML looks just like the one from comment #39!

As you guys can see, the path is "normal". The file permissions are
accessible to Libvirt users/groups. The QEMU host is working normally
with virt-manager.

Any quick fix!?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677398

Title:
  Apparmor prevents using storage pools and hostdev networks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1677398/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868587] Re: Module 'pg_autoscaler' has failed: division by zero

[Thiago Martins]

I'm seeing this on the latest Ubuntu 20.04.1, fully upgraded.

Ceph version 15.2.3-0ubuntu0.20.04.2.

The `ceph status` is "HEALTH_ERR", Module 'pg_autoscaler' has failed:
division by zero, 1 daemons have recently crashed.

:-(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868587

Title:
  Module 'pg_autoscaler' has failed: division by zero

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1868587/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878674] Re: apt purge snapd fails in LXD (on amd64)

[Thiago Martins]

Never mind! Found it at https://images.linuxcontainers.org! No more
snapd!! Wheee!!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878674

Title:
  apt purge snapd fails in LXD (on amd64)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878674] Re: apt purge snapd fails in LXD (on amd64)

[Thiago Martins]

Thanks Johan! But this procedure failed too.

I'll try the images without snapd!

But, currently, I'm using an image called just "focal", which comes with
this creepy snapd. I can't find an image called "ubuntu/focal/cloud"...

Which source are you using for your images? I'm using "https://cloud-
images.ubuntu.com/releases" simplestreams.

Thanks again!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878674

Title:
  apt purge snapd fails in LXD (on amd64)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly

[Thiago Martins]

Any news about this?!

The vim is still very bad on Ubuntu 20.04.

Any recommendation for a better /etc/vim/* ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767314

Title:
  Ubuntu Bionic vi/vim not working correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1767314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878674] Re: apt purge snapd fails in LXD (on amd64)

[Thiago Martins]

I can also confirm this too! Here is a list of problems that I'm seeing
with snap inside LXD containers:

https://askubuntu.com/questions/1288779/the-snapd-package-fails-to-
upgrade-inside-of-ubuntu-20-04-lxd-container

At first, "apt update ; apt full-upgrade" fails... Then, I thought,
let's remove this `snapd` thing. Nop, doesn't work either!

Here is the error when I try `apt remove --purge snapd` inside of an LXD
Container:

https://pastebin.com/TTj4Z4Jp

Johan, do you mind sharing how are you removing snapd out from your
containers?

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878674

Title:
  apt purge snapd fails in LXD (on amd64)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873103] [NEW] The hugepages package isn't available on Focal repos anymore

[Thiago Martins]

Public bug reported:

Hello,

 Since a few weeks ago, the hugepages packages isn't available from
Focal repositories anymore!


---
root@focal-1:~# apt install hugepages
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package hugepages
---

 This was working before! It looks like that it must be recompiled
against libhugetlbfs0-2.22-1!

Thanks!
Thiago

** Affects: libhugetlbfs (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/1873103

Title:
  The hugepages package isn't available on Focal repos anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libhugetlbfs/+bug/1873103/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

[Thiago Martins]

Maybe related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857 ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820063

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

[Thiago Martins]

This is also happening on bare-metal machines as well!

It starts to happen after installing the "linux-cloud-tools-generic-
hwe-18.04" package.

Also, Ubuntu 20.04 has the same problem.


20.04 slow boot stops for 1:30 min heree:
---
A start job is running for /sys/dev…misc/vmbus!hv_kvp (13s / 1min 30s) 
---

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820063

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

[Thiago Martins]

Terry,

 Ubuntu 18.04.4 with Kernel 5.3.0-40-generic, running on QEMU, takes
more than 1:30 minutes to boot, it stops here for a while:

---
[ *] A start job is running for sys-devi…\x21hv_kvp.device (51s / 1min 30s)
---

 I'm using the following image to build my QEMU VMs:

http://uec-images.ubuntu.com/releases/18.04/release/ubuntu-18.04-server-
cloudimg-amd64.img

Cheers!
Thiago

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820063

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

[Thiago Martins]

I'm seeing this problem with Ubuntu 18.04.4 with HWE Kernel, fully
upgraded.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820063

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1847228] Re: Installer crashes at partitioning stage

[Thiago Martins]

The ZFS option crashed the installer, I'll try again today!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847228

Title:
  Installer crashes at partitioning stage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1847228/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813662] Re: Cannot build VM

[Thiago Martins]

I'm creating a file:

/etc/kernel/postinst.d/fix-damn-bug-759725 with:

---
#/bin/sh

# https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725

set -e
version="$1"
if [ -z "$version" ]; then
exit 0
fi
exec dpkg-statoverride --update --add root root 0644 "/boot/vmlinuz-${version}"
---

As a workaround to BUG 759725 that MUST be fixed by Ubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813662

Title:
  Cannot build VM

To manage notifications about this bug go to:
https://bugs.launchpad.net/libguestfs/+bug/1813662/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813662] Re: Cannot build VM

[Thiago Martins]

BUG https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725 is
super, ultra annoying and useless!

:-@

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813662

Title:
  Cannot build VM

To manage notifications about this bug go to:
https://bugs.launchpad.net/libguestfs/+bug/1813662/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 759725] Re: The kernel is no longer readable by non-root users

[Thiago Martins]

ROLL BACK THIS DAMN CHANGE!!!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/759725

Title:
  The kernel is no longer readable by non-root users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1540692] Re: Enable the VirtIO GPU 3D (Virgil)

[Thiago Martins]

Hey guys!

This is an awesome version of QEMU and I can use Virgil 3D (vGPU within
QEMU Guests works ok) with the native Linux `radeon` driver.

However, if I try to install the AMDGPU-19.03 drivers, it completely
breaks QEMU!

AMDGPU-19.30:

https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-navi-
linux

It breaks QEMU on Ubuntu 18.04.2 + Stein UCA Repo!!!

I also tried the previous AMDGPU versions, same results.

Here is the error after installing amdgpu:

https://paste.ubuntu.com/p/35Mtqrsd3n/

How to repeat:

Here is what I do:

1- Install Ubuntu 18.04.2 (with HWE for Kernel and XOrg);
2- Enable UCA with `sudo add-apt-repository cloud-archive:stein`;
3- Install `qemu-vkm`, `virt-manager`, and etc;
4- You'll be able to create a QEMU Guest using Virgil 3D using the Linux 
`radeon` module! It's awesome.
5- Install AMDGPU-19.30 (or any other previous version), for an even more 
awesome QEMU? Let's see!
6- No deal, after installing AMDGPU drivers, no more QEMU!


Any idea about how to fix this? Is this an amdgpu limitation? Any idea if QMEU 
with Virgil 3D with it someday (or this isn't in the master plan)?

Cheers!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540692

Title:
  Enable the VirtIO GPU 3D (Virgil)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1540692/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1540692] Re: Enable the VirtIO GPU 3D (Virgil)

[Thiago Martins]

Unfortunately, the text console is just black.

But both Ubuntu desktops are working! The regular one, and the one based
on "Wayland".

Which is huge anyway!

Any idea about how to fix the text-only black console?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540692

Title:
  Enable the VirtIO GPU 3D (Virgil)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1540692/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1540692] Re: Enable the VirtIO GPU 3D (Virgil)

[Thiago Martins]

YAY! This is finally ready on Ubuntu 18.04 with Ubuntu Cloud Archive
Stein!   :-D

Just do:

sudo add-apt-repository cloud-archive:stein
sudo apt update
sudo apt full-upgrade

And enjoy a 3D Enabled QEMU 3.1 on Ubuntu 18.04!

It's AWESOME!

Likely that it's also enabled by default on Ubuntu 19.04 but, I didn't
test it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540692

Title:
  Enable the VirtIO GPU 3D (Virgil)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1540692/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1817225] Re: 18.04.2 breaks xrdp

[Thiago Martins]

I'll maintain the following repo:

https://launchpad.net/~martinx/+archive/ubuntu/xrdp-hwe-18.04

...until Ubuntu fixes it in an LTS version, maybe 20.04? That's okay...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817225

Title:
  18.04.2 breaks xrdp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1817225] Re: 18.04.2 breaks xrdp

[Thiago Martins]

And here is the xrdp-0.9.9 and xorgxrdp-0.2.9 for Bionic HWE!

https://launchpad.net/~martinx/+archive/ubuntu/xrdp-next

Awesome Friday night! LOL

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817225

Title:
  18.04.2 breaks xrdp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1817225] Re: 18.04.2 breaks xrdp

[Thiago Martins]

So, there is a need to rebuild xrdp against HWE 18.04.

Maybe Ubuntu should provide a new binary package, let's say "xrdp-
hwe-18.04"

For now, I've recompiled the same xrdp from Ubuntu 18.04, on Ubuntu
18.04.2 and uploaded to my "XRP PPA", here:

https://launchpad.net/~martinx/+archive/ubuntu/xrdp-hwe-18.04

To enjoy xrdp on Ubuntu 18.04 with HWE, just do:

sudo add-apt-repository ppa:martinx/xrdp-hwe-18.04
sudo apt install xrdp xorgxrdp

;-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817225

Title:
  18.04.2 breaks xrdp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Thiago Martins]

Ryan,

 If I remove the UEFI line (back to BIOS), the machine enters in Kernel
Panic during the boot / commissioning.

 That was actually, the very test that I executed in first place (add
UEFI to see)! Then, I came with this UEFI workaround, which is even
better for me.

Cheers!
Thiago

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Thiago Martins]

@Ryan,

 The working XML file is attached here, with 2048 MB of RAM.

 NOTE: This XML was created using Virt-Manager, then, MaaS took it over
after being "refreshed".

Cheers!
Thiago

** Attachment added: "vunft-1.xml"
   
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5229030/+files/vunft-1.xml

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Thiago Martins]

I'm also facing this problem.

My workaround is to compose VMs using Virt-Manager, Firmware = UEFI for
the VM and then, refreshing the MaaS Pod.

There is a need to install ovmf

sudo apt install ovmf

On MaaS Pod.

Then, no more Kernel Panic!

Details:

https://discourse.maas.io/t/maas-2-5-bionic-pod-composing-guests-kernel-
panic-no-init/302

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797581

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] Re: Missing "/sys/module/dummy/parameters/" subdir on dummy module

[Thiago Martins]

After chatting on IRC, #systemd channel, damjan explained this:

https://github.com/systemd/systemd/blob/master/NEWS#L845

So, actually, the following file:

cat /lib/modprobe.d/systemd.conf

disables "extra" dummies, as follows:

--
options bonding max_bonds=0
options dummy numdummies=0
--

Forcing us to explicitly create the dummy devices per demand (I believe,
and I'll try it soon). I guess that it's really time to say goodbye to
"ifupdown / /etc/network/interfaces" approach...

Just for testing, after disabling the dummy line out from that file and
rebooting it, I have the 12 dummies without my ugly workaround via
/etc/rc.local!

See, Jan-Dirk? I thought that I could blame systemd and I got my answer
there!

NOTE: I actually like systemd, okay? :-P

It's just a new way of doing this (Netplan? systemd-networkd directly?),
Jan, you can safely move to Ubuntu!  ^_^

Cheers!

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] Re: Missing "/sys/module/dummy/parameters/" subdir on dummy module

[Thiago Martins]

Any news about this problem?!

** 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/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1226855] Re: Cannot use open-iscsi inside LXC container

[Thiago Martins]

Is this still a problem on Ubuntu 18.04?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1226855

Title:
  Cannot use open-iscsi inside LXC container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1746992] Re: gnocchi-api in Bionic uses python3, and libapache2-mod-wsgi-py3 conflicts with the python 2 version

[Thiago Martins]

What about making "gnocchi-api" to depends on "python-gnocchi", instead
of "python3-gnocchi"?

I just installed it (python-gnocchi) here! But I didn't tested it yet
(missing correct config files).

So, if Gnocchi _only_ works with Python 3, why there is this "python-
gnocchi" that is based on Python 2?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746992

Title:
  gnocchi-api in Bionic uses python3, and libapache2-mod-wsgi-py3
  conflicts with the python 2 version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnocchi/+bug/1746992/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1746992] Re: gnocchi-api in Bionic uses python3, and libapache2-mod-wsgi-py3 conflicts with the python 2 version

[Thiago Martins]

Same problem here!   :-/

The gnocchi-api package looks bad.

It doesn't even contain the "/usr/bin/gnocchi-api"! Only an apache
config file...

Looks trivial to fix this problem.

No idea why the "/usr/bin/gnocchi-api" comes from "python-gnocchi"
package...

What's happening to Debian/Ubuntu?!   :-O

Or is it Gnocchi that it is "crazy"...  lol

:-P

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746992

Title:
  gnocchi-api in Bionic uses python3, and libapache2-mod-wsgi-py3
  conflicts with the python 2 version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnocchi/+bug/1746992/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] WifiSyslog.txt

[Thiago Martins]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1774731/+attachment/5147764/+files/WifiSyslog.txt

** 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/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] UdevDb.txt

[Thiago Martins]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1774731/+attachment/5147763/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] ProcInterrupts.txt

[Thiago Martins]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1774731/+attachment/5147761/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] Re: Missing "/sys/module/dummy/parameters/" subdir on dummy module

[Thiago Martins]

apport information

** Tags added: apport-collected bionic uec-images

** Description changed:

  Hello,
  
   On Ubuntu 18.04 (fully updated), the following configuration does not
  work:
  
   File /etc/modprobe.d/dummy.conf with:
  
  
   options dummy numdummies=12
  
  
   File /etc/modules
  
  
   dummy
  
  
   The module "dummy" is loaded but, there is no 12 dummies NIC cards!
  
   The manual workaround is:
  
  ---
  rmmod dummy
  modprobe dummy numdummies=12
  ---
  
   I talked on IRC and someone pointed that the dummy module is missing
  its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug
  report now.
  
  Cheers!
+ --- 
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.9-0ubuntu7.1
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
+ Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
+ Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
+ DistroRelease: Ubuntu 18.04
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
+ Lsusb:
+  Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=screen
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 qxldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro
+ ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-22-generic N/A
+  linux-backports-modules-4.15.0-22-generic  N/A
+  linux-firmware 1.173.1
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
+ Tags:  bionic uec-images
+ Uname: Linux 4.15.0-22-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 04/01/2014
+ dmi.bios.vendor: SeaBIOS
+ dmi.bios.version: 1.10.2-1ubuntu1
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: QEMU
+ dmi.chassis.version: pc-i440fx-bionic
+ dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
+ dmi.product.name: Standard PC (i440FX + PIIX, 1996)
+ dmi.product.version: pc-i440fx-bionic
+ dmi.sys.vendor: QEMU

** Attachment added: "AlsaDevices.txt"
   
https://bugs.launchpad.net/bugs/1774731/+attachment/5147753/+files/AlsaDevices.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] PciMultimedia.txt

[Thiago Martins]

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1774731/+attachment/5147758/+files/PciMultimedia.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] ProcModules.txt

[Thiago Martins]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1774731/+attachment/5147762/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] ProcCpuinfo.txt

[Thiago Martins]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1774731/+attachment/5147759/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] ProcCpuinfoMinimal.txt

[Thiago Martins]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1774731/+attachment/5147760/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] Card0.Codecs.codec.0.txt

[Thiago Martins]

apport information

** Attachment added: "Card0.Codecs.codec.0.txt"
   
https://bugs.launchpad.net/bugs/1774731/+attachment/5147755/+files/Card0.Codecs.codec.0.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] CRDA.txt

[Thiago Martins]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1774731/+attachment/5147754/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] CurrentDmesg.txt

[Thiago Martins]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1774731/+attachment/5147756/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] Lspci.txt

[Thiago Martins]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1774731/+attachment/5147757/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] [NEW] Missing "/sys/module/dummy/parameters/" subdir on dummy module

[Thiago Martins]

Public bug reported:

Hello,

 On Ubuntu 18.04 (fully updated), the following configuration does not
work:

 File /etc/modprobe.d/dummy.conf with:


 options dummy numdummies=12


 File /etc/modules


 dummy


 The module "dummy" is loaded but, there is no 12 dummies NIC cards!

 The manual workaround is:

---
rmmod dummy
modprobe dummy numdummies=12
---

 I talked on IRC and someone pointed that the dummy module is missing
its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug
report now.

Cheers!

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774731] Re: Missing "/sys/module/dummy/parameters/" subdir on dummy module

[Thiago Martins]

I also asked a question about this here:

https://askubuntu.com/questions/1042452/file-etc-modprobe-d-dummy-conf-
ignored-on-ubuntu-18-04

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774731

Title:
  Missing "/sys/module/dummy/parameters/" subdir on dummy module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly

[Thiago Martins]

Thanks! vim on Ubuntu 18.04 is so annoying!  lol

The workaround 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/1767314

Title:
  Ubuntu Bionic vi/vim not working correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1767314/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1761995] Re: Error Formatting luks device

[Thiago Martins]

Same problem here! Any workarounds?

Time to go fscrypt instead?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761995

Title:
  Error Formatting luks device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1761995/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1756600] Re: Ubuntu 18.04 beta install DVD cannot encrypt home

[Thiago Martins]

What about fscrypt from ext4?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756600

Title:
  Ubuntu 18.04 beta install DVD cannot encrypt home

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1756600/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1540692] Re: Enable the VirtIO GPU 3D (Virgil)

[Thiago Martins]

Looks like that the bug report on Debian was fixed:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839695

I'll also try the Ernstp's PPA.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540692

Title:
  Enable the VirtIO GPU 3D (Virgil)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1540692/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Thiago Martins]

Is it possible to reproduce this problem with upstart or sysvinit-core?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1540692] Re: Enable the VirtIO GPU 3D (Virgil)

[Thiago Martins]

Aaah... That's sad... Maybe for Ubuntu 18.04!   :-D

On 23 May 2017 at 15:09, ChristianEhrhardt <1540...@bugs.launchpad.net>
wrote:

> Hi - just my two cents trying to clarify a few things.
>
> FYI there are two and a half road-blockers on the way to get this done.
>
> #1 We don't need/want to divert from Debian for that, but there due to a
> lot of issues with virgl and being too late for the current release
>   * Revert "enable virtio gpu (virglrenderer) and opengl support"
> Revert "switch from sdl1 to gtk3"
> Revert other gtk2/drm/vte/virgl-related changes
> Reopens: #813658, #839695
> The change were too close to stretch release and too large,
> bringing too much graphics stuff for headless servers,
> will re-think this for stretch+1.
> sdl1 back: Closes: #851509
> virtio-3d bugs: Closes: #849798, #852119
>
> #2 most of the needed extra dependencies are not in main, so they will
> need to pass the MIR process [1]
>
> #3 (the half one) at least recently virgl had a lot of security issues
> spiking the maintenance effort around it, so it seems not safe/mature
> enough yet. At least that will affect/deleay a positive security review.
>
> What one could do right now is identifying the exact list of extra
> dependencies that this will create on qemu, check which are not in main yet
> and add them as [MIR] bug tasks here.
> That as a prep for when Debian makes the switch, otherwise we will have to
> opt out of that until all dependencies are in main.
>
> [1]: https://wiki.ubuntu.com/MainInclusionProcess
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1540692
>
> Title:
>   Enable the VirtIO GPU 3D (Virgil)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1540692/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540692

Title:
  Enable the VirtIO GPU 3D (Virgil)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1540692/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

[Thiago Martins]

I'm also expecting this on Xenial ASAP!

I'm using OpenStack with OVN, and the OpenFlow rules does not work with
Kernel 4.4! And MTU does not work with 4.8!

Very bad situation...   :-(

Also expecting the fix for:

https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1685742

...in one shot!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49, xenial-hwe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1614837] Re: ovn:Multi nodes devstack, controller node losts ovs port when computer node starts

[Thiago Martins]

BTW, I'm running Ocata on Ubuntu 16.04 via Cloud Archive, Kernel 4.4.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614837

Title:
  ovn:Multi nodes devstack, controller node losts ovs port when computer
  node starts

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-ovn/+bug/1614837/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1614837] Re: ovn:Multi nodes devstack, controller node losts ovs port when computer node starts

[Thiago Martins]

I just saw this problem in my Ocata with Networking OVN...

Rebooted a Compute Node, instance lost connectivity.

/var/log/openvswitch/ovs-vswitchd.log:

---
2017-05-09T14:32:53.558Z|00092|dpif|WARN|system@ovs-system: failed to query 
port 
patch-lrp-dtsp-99913e36-94b1-463f-a95b-9c3ff840b07b-to-dtsp-99913e36-94b1-463f-a95b-9c3ff840b07b:
 Invalid argument
---

Any idea?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614837

Title:
  ovn:Multi nodes devstack, controller node losts ovs port when computer
  node starts

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-ovn/+bug/1614837/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

[Thiago Martins]

Nice goldyfruit, thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49, xenial-hwe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)

[Thiago Martins]

@goldyfruit, can you confirm if it also fixes the BUG:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1685742 ?

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49, xenial-hwe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1685742] Re: MTU 9000 not possible on openvswitch bridge

[Thiago Martins]

Any chance to include patch #5 on Xenial?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685742

Title:
  MTU 9000 not possible on openvswitch bridge

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1685742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1384109] Re: Mechanism driver 'l2population' failed in update_port_postcommit

[Thiago Martins]

Ubuntu 16.04 + Ocata from Cloud Archive.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384109

Title:
  Mechanism driver 'l2population' failed in update_port_postcommit

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1384109/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1384109] Re: Mechanism driver 'l2population' failed in update_port_postcommit

[Thiago Martins]

I'm seeing this error message when with Networking OVN.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384109

Title:
  Mechanism driver 'l2population' failed in update_port_postcommit

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1384109/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1685742] Re: MTU 9000 not possible on openvswitch bridge

[Thiago Martins]

Ralf, that might be also needed!

I'm trying to run jumbo frames on top of Neutron with Networking OVN and
it is not working.

I just saw that the commit you posted, comes from someone from @ovn.org!
So, go figure... lol

Hope to see this fixed ASAP!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685742

Title:
  MTU 9000 not possible on openvswitch bridge

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1685742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

[Thiago Martins]

I also have a production environment running into network issues...
Planning to downgrade the kernel to 4.4 series...=(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

[Thiago Martins]

I was experiencing issues with OpenStack deployed with Networking OVN
and just saw this message in my dmesg:


---
[   12.241706] 8021q: adding VLAN 0 to HW filter on device eno2
[   15.077293] eno2: Invalid MTU 9000 requested, hw max 68
---

And the IP of my eno2.600 VLAN is gone! So, the Instances can't ping
each other because that is where my data path (GENEVE / VXLAN) tunnels
are created on!

How a bug like this ended up into an LTS release?   :-(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1540692] Re: Enable the VirtIO GPU 3D (Virgil)

[Thiago Martins]

Mesa on Ubuntu 17.04 have VirGL!

---
user@ubuntu-1:~/sources/mesa/mesa-17.0.3/debian$ grep virgl . -r
./changelog:  * Enable support for virgl (Closes: #807774).
./rules:GALLIUM_DRIVERS += nouveau svga virgl
---

Maybe there is a need to double check GPU drivers?

Let me know if it works for you!

Cheers!
Thiago


On 13 April 2017 at 18:28, GizmoChicken  wrote:

> I've updated from 16.10, and my host is now running Ubuntu 17.04 with
> all packages up-to-date, including the following:
>
>  qemu (2.8+dfsg-3ubuntu2)
>  libvirglrenderer0 (0.5.0-2)
>
> As mentioned in comment #7, my QEMU commands include the following:
>
> -vga virtio \
> -display gtk,gl=on \
>
> And when I try to start my VM using commands including the above, I
> still get:
>
>  qemu-system-x86_64: -display gtk,gl=on: GTK support is disabled
>
> I'm not certain, but I think that, for the VirtIO GPU 3D (Virgil) to
> work, mesa must be compiled using the "--with-gallium-drivers=virgl"
> option.  See https://wiki.archlinux.org/index.php/QEMU#virtio
>
> So maybe the problem isn't with qemu, but instead with mesa being
> compiled without the "--with-gallium-drivers=virgl" option being set.
> Any thoughts?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1540692
>
> Title:
>   Enable the VirtIO GPU 3D (Virgil)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1540692/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540692

Title:
  Enable the VirtIO GPU 3D (Virgil)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1540692/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1524737] Re: systemd presents hugetblfs at /dev/hugepages

[Thiago Martins]

I'm seeing this problem while trying to launch an Instance on OpenStack
Ocata on Ubuntu 16.04, here is the error message on nova-compute.log:

---
2017-04-07 20:13:18.504 3996 ERROR nova.compute.manager [instance: 
fbbb7bde-763e-40d3-8987-fb3a6c568ad8] libvirtError: internal error: process 
exited while connecting to monitor: 2017-04-07T20:13:17.764939Z 
qemu-system-x86_64: -object 
memory-backend-file,id=ram-node0,prealloc=yes,mem-path=/dev/hugepages-1048576/libvirt/qemu,share=yes,size=4294967296,host-nodes=0,policy=bind:
 can't open backing store /dev/hugepages-1048576/libvirt/qemu for guest RAM: 
Permission denied
---

At syslog:

---
Apr  7 20:13:17 expert-jennet kernel: [ 1535.437956] audit: type=1400 
audit(1491595997.759:23): apparmor="DENIED" operation="mknod" 
profile="libvirt-fbbb7bde-763e-40d3-8987-fb3a6c568ad8" 
name="/dev/hugepages-1048576/libvirt/qemu/qemu_back_mem._objects_ram-node0.BFNx2W"
 pid=8341 comm="qemu-system-x86" requested_mask="c" denied_mask="c" fsuid=64055 
ouid=64055
---

Any idea about how to fix it?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1524737

Title:
  systemd presents hugetblfs at /dev/hugepages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1524737/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...

[Thiago Martins]

Guys?!:-P

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475078

Title:
  VirtIO (and probably other modules as well) is built-in, make it
  modular...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1653967] Re: nova raises ConfigFileValueError for URLs with dashes

[Thiago Martins]

Guys,

Why is taking so long for python-rfc3986 package to leave the Proposed
repo, into main?

https://launchpad.net/ubuntu/+source/python-
rfc3986/0.2.2-0ubuntu0.16.04.1

It was uploaded on 2016-10-27!

Cheers!
Thiago

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653967

Title:
  nova raises ConfigFileValueError for URLs with dashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-requirements/+bug/1653967/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1556301] Re: Missing Virt-Manager Menu (File, Edit, etc)

[Thiago Martins]

I am unable to reproduce this problem on Ubuntu 16.10.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556301

Title:
  Missing Virt-Manager Menu (File, Edit, etc)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1556301/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1577088] Re: OVS+DPDK segfault at the host, after running "ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4" within a KVM Guest

[Thiago Martins]

This is still a bug on Xenial with OpenvSwitch-2.6 and DPDK-16.07, from
Ubuntu Cloud Archive.

I just crashed the OVS+DPDK running at the host, right after trying to
enable multiqueue inside of a KVM Guest, also running OVS+DPDK.

NOTE: Multiqueue was enabled at the host in advance, on both OVS and
Libvirt VM XML.

I also noted that right after enabling 2 queues at the host, the speed
improved inside of the running guest! Without doing anything with it.
But, then, after trying to enable multiqueue at the KVM guest, on its
OVS+DPDK on top of VirtIO, host crashed.

After running on the KVM Guest:

---
root@ubuntu-ovs-dpdk-vm-1:~# ovs-vsctl set interface dpdk0 options:n_rxq=2 ; 
ovs-vsctl set interface dpdk1 options:n_rxq=2
---

At the host, ovs-vswitchd crashed:

---
root@ubuntu-ovs-dpdk-kvm-1:~# tail -F /var/log/openvswitch/ovs-vswitchd.log
..
2016-12-02T04:11:28.578Z|00127|dpdk(vhost_thread2)|INFO|State of queue 0 ( 
tx_qid 0 ) of vhost device '/var/run/openvswitch/vhost-user1'changed to 
'enabled'
2016-12-02T04:11:28.578Z|00128|dpdk(vhost_thread2)|INFO|State of queue 2 ( 
tx_qid 1 ) of vhost device '/var/run/openvswitch/vhost-user1'changed to 
'enabled'
2016-12-02T04:11:28.956Z|2|daemon_unix(monitor)|ERR|1 crashes: pid 3841 
died, killed (Segmentation fault), core dumped, restarting
---

I REALLY want to be able to use DPDK Apps, on top of OVS+DPDK at the
host but, it still looks unstable to me.

:-(

** Summary changed:

- OVS+DPDK segfault at the host, after running "ovs-vsctl set Open_vSwitch . 
other_config:n-dpdk-rxqs=4" within a KVM Guest
+ OVS+DPDK segfault at the host, after running "ovs-vsctl set interface dpdk0 
options:n_rxq=2 " within a KVM Guest

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577088

Title:
  OVS+DPDK segfault at the host, after running "ovs-vsctl set interface
  dpdk0 options:n_rxq=2 " within a KVM Guest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1577088/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1500475] Re: adding index_var to AutoScalingGroup

[Thiago Martins]

If I remember well, AutoScaling on Amazon EC2 works very well with
index.

Why OpenStack can't do it?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500475

Title:
  adding index_var to AutoScalingGroup

To manage notifications about this bug go to:
https://bugs.launchpad.net/heat/+bug/1500475/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1632538] Re: Using generate_service_certificate and undercloud_public_vip in undercloud.conf breaks nova

[Thiago Martins]

It is working now!

python-rfc3986 from xenial-proposed fixes the problem, move it to main!
:-D

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632538

Title:
  Using generate_service_certificate and undercloud_public_vip in
  undercloud.conf breaks nova

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1632538/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1632538] Re: Using generate_service_certificate and undercloud_public_vip in undercloud.conf breaks nova

[Thiago Martins]

Oh! There is a new python-rfc3986 verison on xenial-proposed! Trying
that...   :-P

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632538

Title:
  Using generate_service_certificate and undercloud_public_vip in
  undercloud.conf breaks nova

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1632538/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1632538] Re: Using generate_service_certificate and undercloud_public_vip in undercloud.conf breaks nova

[Thiago Martins]

Mmmm... Nova, from OpenStack Newton for Xenial, com UCA, doesn't work...
I'm seeing at my Nova logs:

* nova-api.log:

https://paste.ubuntu.com/23472691/


* nova-consoleauth.log:

ERROR nova ConfigFileValueError: Value for option url is not valid:
invalid URI:


* nova-conductor:

ERROR nova ConfigFileValueError: Value for option url is not valid:
invalid URI:

* nova-compute:

Timed out waiting for nova-conductor.  Is it running? Or did this
service start before nova-conductor?  Reattempting establishment of
nova-conductor connection...

I have:

---
Package: python-rfc3986
Version: 0.2.0-2
---

I'll try to manually backport it from Debian, since it is 0.3.1 there:

https://tracker.debian.org/pkg/python-rfc3986


So, Newton doesn't work no Xenial... H...   ;-(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632538

Title:
  Using generate_service_certificate and undercloud_public_vip in
  undercloud.conf breaks nova

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1632538/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1389077] Re: [HP ProBook 4530s] Intel Powerclamp is Slowing CPU

[Thiago Martins]

I'm seeing this problem on Ubuntu 16.10. Not too frequent.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389077

Title:
  [HP ProBook 4530s] Intel Powerclamp is Slowing CPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389077/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...

[Thiago Martins]

Guys,

 I'm marking this as "New", because this bug/improvement was not fixed
on "4.8.0-11.12".

 Look:

---
tmartins@blade:~$ lsb_release -ra
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename:   yakkety

tmartins@blade:~$ grep VIRTIO /boot/config-4.8.0-26-generic 
CONFIG_VIRTIO_VSOCKETS=m
CONFIG_VIRTIO_VSOCKETS_COMMON=m
CONFIG_NET_9P_VIRTIO=m
CONFIG_VIRTIO_BLK=y
CONFIG_SCSI_VIRTIO=m
CONFIG_VIRTIO_NET=y
CONFIG_CAIF_VIRTIO=m
CONFIG_VIRTIO_CONSOLE=y
CONFIG_HW_RANDOM_VIRTIO=m
CONFIG_DRM_VIRTIO_GPU=m
CONFIG_VIRTIO=y
CONFIG_VIRTIO_PCI=y
CONFIG_VIRTIO_PCI_LEGACY=y
CONFIG_VIRTIO_BALLOON=y
CONFIG_VIRTIO_INPUT=m
CONFIG_VIRTIO_MMIO=y
CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
---

 See it? "CONFIG_VIRTIO_NET=y" and few others... Still not as modules...

Cheers!
Thiago

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Confirmed

** Changed in: linux (Ubuntu)
   Status: Fix Released => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475078

Title:
  VirtIO (and probably other modules as well) is built-in, make it
  modular...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...

[Thiago Martins]

I installed Linux 4.8 from "Ubuntu Kernel Team PPA" (ppa:canonical-
kernel-team/ppa) on my Xenial, here is the result:

--
grep VIRTIO /boot/config-4.8.0-25-generic 
CONFIG_VIRTIO_VSOCKETS=m
CONFIG_VIRTIO_VSOCKETS_COMMON=m
CONFIG_NET_9P_VIRTIO=m
CONFIG_VIRTIO_BLK=y
CONFIG_SCSI_VIRTIO=m
CONFIG_VIRTIO_NET=y
CONFIG_CAIF_VIRTIO=m
CONFIG_VIRTIO_CONSOLE=y
CONFIG_HW_RANDOM_VIRTIO=m
CONFIG_DRM_VIRTIO_GPU=m
CONFIG_VIRTIO=y
CONFIG_VIRTIO_PCI=y
CONFIG_VIRTIO_PCI_LEGACY=y
CONFIG_VIRTIO_BALLOON=y
CONFIG_VIRTIO_INPUT=m
CONFIG_VIRTIO_MMIO=y
CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
--

 Still not modular...   :-(

 Any plans to make this available to Xenial via "linux-image-generic-
lts-yakkety" ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475078

Title:
  VirtIO (and probably other modules as well) is built-in, make it
  modular...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1500475] Re: adding index_var to AutoScalingGroup

[Thiago Martins]

Is it available on Newton? If yes, any chances to backport it to Mitaka?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500475

Title:
  adding index_var to AutoScalingGroup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heat/+bug/1500475/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

[Thiago Martins]

You guys can ignore my latest message (#96).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572801

Title:
  Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

[Thiago Martins]

Right after booting my 16.04 (now 16.10), before even logging into
Unity, I go to text console and log there...

32G of RAM being used! htop shows nothing...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572801

Title:
  Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1577256] Re: The OVS+DPDK dpdkvhostuser socket bridge, only works as expected, if the KVM Guest also have DPDK drivers loaded

[Thiago Martins]

Hey guys,

Looks like that this bug is now fixed on Ubuntu 16.10.

Also, the new OpenvSwitch 2.6 and DPDK 16.07 packages are available to
Xenial via Newton Cloud Archive.

Cheers!

** Changed in: openvswitch (Ubuntu)
   Status: Expired => Fix Released

** Changed in: dpdk (Ubuntu)
   Status: Expired => 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/1577256

Title:
  The OVS+DPDK dpdkvhostuser socket bridge, only works as expected, if
  the KVM Guest also have DPDK drivers loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1577256/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)

[Thiago Martins]

Anmar,

I am 100% sure that it is not the browser, please guys, watch this:

https://www.youtube.com/watch?v=BC287yYPfTA

This BUG is not fixed. Or maybe, what I'm seeing here is a different
bug.

On Ubuntu 16.10, things looks a little bit better but, Chrome still
flickers.

Ubuntu 14.04 is fine. While 16.04 and 16.10 are just terrible.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554613

Title:
  Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs