[Bug 1866619] Re: OverflowError when machine suspends and resumes after a longer while

2020-07-23 Thread Riccardo Pittau
any update on this? Seeing this basically every time we run dstat in the openstack CI an example: https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_8cb/725794/6/check/ipa-tempest-bios-ipmi-direct-tinyipa-src/8cb049d/job-output.txt -- You received this

[Bug 1879325] Re: Unable to remove disk metadata on vm

2020-06-05 Thread Riccardo Pittau
Hey Brian, I tested the new packages in our CI and I can confirm the original issues are both gone. This is a recent libvirt log file: https://1a06a6c5517c6a746e50-e807054499ce854694349e023b0ab289.ssl.cf5.rackcdn.com/716889/38/check/ironic-tempest-ipa-partition-uefi-pxe-grub2/a34d5b6/controller/l

[Bug 1879325] Re: Unable to remove disk metadata on vm

2020-05-27 Thread Riccardo Pittau
Hi Christian, I ran a test in our CI with the packages: 2020-05-26 16:52:02.258571 | controller | Get:1 http://ppa.launchpad.net/ci-train-ppa-service/4068/ubuntu focal/main amd64 libvirt-dev amd64 6.0.0-0ubuntu8.2~ppa1 [161 kB] 2020-05-26 16:52:02.486631 | controller | Get:2 http://ppa.launchpa

[Bug 1879325] Re: Unable to remove disk metadata on vm

2020-05-25 Thread Riccardo Pittau
Hi Christian, thank you for your patience, I just finished testing the new package in our ci and unfortunately I'm still seeing the same message about disk metadata: 2020-05-22 09:21:40.896+: 96720: error : virProcessRunInFork:1159 : internal error: child reported (status=125): 2020-05-22 09

[Bug 1879325] Re: Unable to remove disk metadata on vm

2020-05-20 Thread Riccardo Pittau
Hi Christian, thanks for the quick answer and fix, I'll test that in our CI as soon as possible. What actually worries me is the message "unable to remove disk metadata", but I guess we'll have to wait for the CI jobs to complete to see if there was an improvement on the related error that we'r

[Bug 1879325] [NEW] Unable to remove disk metadata on vm

2020-05-18 Thread Riccardo Pittau
Public bug reported: We can reproduce this 100% in our CI (upstream Openstack Ironic) using Ubuntu 20.04 LTS Focal Fossa with libvirt 6.0.0 2020-05-15 10:05:50.626+: 96089: error : virSecurityManagerMoveImageMetadata:476 : this function is not supported by the connection driver: virSecurity

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2020-02-05 Thread Riccardo Pittau
Hey Dann, thanks a lot for the thorough analysis, the reasoning makes sense. I'm just a bit sceptical because we use tinycore 9.x at the moment, with kernel 4.14, which includes the patch for the kernel panic you mentioned, it was just moved under drivers/firmware/efi/efi-bgrt.c, so I'm not sure

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2020-01-28 Thread Riccardo Pittau
Hi, just wondering if we can provide any more info or help to be able to move forward with the investigation. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf packa

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2019-11-25 Thread Riccardo Pittau
Hi Dann, I tried to narrow down where the failure happens and it seems it's between versions 0~20161202.7bbe0b3e-1 (Zesty) and 0~20170911.5dfba97c-1 (Aartful). Just to clarify, version 0~20161202.7bbe0b3e-1 (Zesty) seems working fine in my environment, while version 0~20170911.5dfba97c-1 (Aartfu

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2019-11-21 Thread Riccardo Pittau
Hi Dann, I tried to narrow down where the failure happens and it seems it's between versions 0~20161202.7bbe0b3e-1 (Zesty) and 0~20170911.5dfba97c-1 (Aartful). Just to clarify, version 0~20161202.7bbe0b3e-1 (Zesty) seems working fine in my environment, while version 0~20170911.5dfba97c-1 (Aartfu

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2019-11-20 Thread Riccardo Pittau
** Attachment added: "kernel_panic_console_log_ovmf_0~20180205.c0d9813c-2ubuntu0.1" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/530/+files/kernel_panic_console_log_ovmf_0~20180205.c0d9813c-2ubuntu0.1 ** Attachment removed: "console_log_node-0_no_ansi" https

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2019-11-20 Thread Riccardo Pittau
** Attachment added: "success_console_log_ovmf_0~20160813.de74668f-2" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/5306665/+files/success_console_log_ovmf_0~20160813.de74668f-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is s

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2019-11-20 Thread Riccardo Pittau
** Attachment added: "libvirt_xml_virtual-node-0" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/5306667/+files/libvirt_xml_virtual-node-0 ** Attachment removed: "bionic_e1000_ppa-ovmf.txt" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/526

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2019-11-20 Thread Riccardo Pittau
Hi Dann, unfortunately I was diverged to other things and couldn't test again until now. I don't see your files anymore, but I did some more testing with packages up to eoan. I can confirm that the regression is between xenial and bionic versions: 0~20160813.de74668f-2 works (tested in bionic) 0

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2019-05-20 Thread Riccardo Pittau
Hi Dann, Please find recent logs here: This is the correct output on bionic using virtio + ovmf package from xenial: http://logs.openstack.org/90/644590/8/gate/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/6232932/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-05-18-12:09:41_log.txt.

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2019-04-11 Thread Riccardo Pittau
@Dann: thanks for keep looking at this, I tested the new package both locally and in our CI, using virtio and e1000 drivers, but unfortunately I'm still seeing the issue where the vm can't load from ipxe. The only thing that we change for the test is the ovmf package, the rest of the configurati

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2019-04-01 Thread Riccardo Pittau
@Dann: what I'm saying is that I can't reproduce the kernel panic after installing a PPA build because it doesn't load from ipxe anymore. I can't confirm or deny the issue with the kernel panic is actually fixed. If you prefer I can open another bug, although it seems a regression to me, but of c

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2019-04-01 Thread Riccardo Pittau
@Dann: thanks for checking that, I did some tests and, even if I can't reproduce the kernel panic anymore, I'm seeing another issue that was also happening before with virtio, the vm is not booting on ipxe. This is the correct output on bionic using virtio + ovmf from xenial: http://logs.openstack

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2019-03-27 Thread Riccardo Pittau
console log attached ** Attachment added: "console_log_node-0_no_ansi" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/5249703/+files/console_log_node-0_no_ansi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubunt

[Bug 1821729] Re: UEFI in ovmf package causes kernel panic

2019-03-27 Thread Riccardo Pittau
libvirt xml of virtual node attached ** Attachment added: "libvirt_xml_virtual-node-0" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+attachment/5249704/+files/libvirt_xml_virtual-node-0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is sub

[Bug 1821729] [NEW] UEFI in ovmf package causes kernel panic

2019-03-26 Thread Riccardo Pittau
Public bug reported: UBUNTU info Description:Ubuntu 18.04.1 LTS Release:18.04 PACKAGE info ovmf: Installed: 0~20180205.c0d9813c-2 Candidate: 0~20180205.c0d9813c-2 Version table: *** 0~20180205.c0d9813c-2 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu bionic/univer

[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'

2018-04-29 Thread Riccardo Pittau
Same issue on a Dell XPS 9360 The issue seems to happen during or at the end of the files copying procedure as the partitions are correctly setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720