Monday, 2026-07-06

opendevreviewBhavana proposed openstack/nova-specs master: Add spec for minimal-displacement MIG repartitioning  https://review.opendev.org/c/openstack/nova-specs/+/99605505:35
opendevreviewBhavana proposed openstack/nova master: Add Minimal Displacement Solver for MIG GPU Repartitioning  https://review.opendev.org/c/openstack/nova/+/99605806:54
opendevreviewThibaut Démaret proposed openstack/nova master: libvirt: add disk rotation_rate support for local disks  https://review.opendev.org/c/openstack/nova/+/97969307:12
opendevreviewAshish Gupta proposed openstack/nova master: tests: file-backed SQLite with WAL in threading mode for Database and CellDatabases Fixtures  https://review.opendev.org/c/openstack/nova/+/98858307:35
UgglaHi gibi and bauzas, I will be on PTO for the next 3 weeks. Would you be able to run the upstream meeting on my behalf?08:28
bauzasI can do it08:41
bauzasmaybe not on July 13th tho, I'll probably take the day off08:41
bauzasbut that's something we can discuss08:41
gibiI can take July 13th if you take the others :)08:45
bauzasheh, looks like we have a plan ;)08:45
gibiOK08:45
*** ykarel_ is now known as ykarel08:59
Ugglagibi, bauzas thanks I'll update the agenda accordingly.09:05
opendevreviewsean mooney proposed openstack/nova master: Add vTPM startup validation reproducer  https://review.opendev.org/c/openstack/nova/+/99055109:32
opendevreviewsean mooney proposed openstack/nova master: Limit startup instance processing to libvirt  https://review.opendev.org/c/openstack/nova/+/99055209:32
opendevreviewsean mooney proposed openstack/nova master: Reduce ProviderTree copy cost for Ironic  https://review.opendev.org/c/openstack/nova/+/98067609:32
opendevreviewsean mooney proposed openstack/nova master: Parallelize per-node resource updates  https://review.opendev.org/c/openstack/nova/+/98067909:32
opendevreviewsean mooney proposed openstack/nova master: perf: add ironic startup performance simulator  https://review.opendev.org/c/openstack/nova/+/98064109:32
opendevreviewsean mooney proposed openstack/nova master: docs: add Ironic startup performance measurements  https://review.opendev.org/c/openstack/nova/+/98068009:32
opendevreviewTakashi Kajinami proposed openstack/nova master: Update documentations for AMD SEV-SNP support  https://review.opendev.org/c/openstack/nova/+/99509009:46
opendevreviewTakashi Kajinami proposed openstack/nova master: Remove [libvirt] num_memory_encrypted_guests  https://review.opendev.org/c/openstack/nova/+/99512009:46
opendevreviewTakashi Kajinami proposed openstack/nova master: Fix wrong comment in test  https://review.opendev.org/c/openstack/nova/+/99607009:49
opendevreviewAshish Gupta proposed openstack/nova master: tests: use file-backed Placement SQLite in functional threading  https://review.opendev.org/c/openstack/nova/+/99258109:51
opendevreviewBhavana proposed openstack/nova master: Add Minimal Displacement Solver for MIG GPU Repartitioning  https://review.opendev.org/c/openstack/nova/+/99605810:30
opendevreviewAshish Gupta proposed openstack/nova master: tests: Use per-database write locks instead of global lock  https://review.opendev.org/c/openstack/nova/+/99286210:39
*** chandank` is now known as chandankumar11:21
tkajinamgibi, thanks a lot for reviews and tests !11:58
gibitkajinam: thanks for the patches. I'm happy that we made a quick progress on SNP12:01
tkajinamyeah :-D12:01
tkajinamthough it has been a long way for me, though, because SEV-SNP support has been the ultimate goal for me since I touched my initial work to support SEV-ES12:02
tkajinambut finally we are close to complete that long journey, hopefully12:03
sean-k-mooneytkajinam: we were talking about locked memory last week, i remembered at the weekend why we limited it to hugepages12:20
sean-k-mooneytkajinam: locked memory cannot be swapped12:20
sean-k-mooneytkajinam: so we limited it to hugepages becasuse hugepages cannot be overcommited12:20
sean-k-mooneyif you use locked memory with out hugepageas and you memory allocation ration is > 1.012:20
sean-k-mooneythen you will have OOM events12:20
sean-k-mooneyso while it can work for non hugepage memory i.e hw:mem_page_size=small we require you to enabel the numa aware memory trackign which disables oversubsction to use it to prevent OOM events12:21
sean-k-mooneyso it could work wiht annoumus memory but its not safe to use it that way unless you acount for it via ram allcoation ratio12:22
sean-k-mooneythat was why that limitation exits today12:22
sean-k-mooneytkajinam: anyway that should not impact th sev-snp work just the background context the current design choice12:23
sean-k-mooneygmaan: as an fyi i somethime see test_cold_migration_dest_compute_graceful_shutdown fila in the the functional/coverage tests12:40
sean-k-mooneyhttps://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_dc2/openstack/dc227da7383b4f62ab0731d251d86e2f/testr_results.html12:41
sean-k-mooneyso that may be unstable in some caes12:41
opendevreviewsean mooney proposed openstack/nova master: Parallelize per-node resource updates  https://review.opendev.org/c/openstack/nova/+/98067912:50
opendevreviewsean mooney proposed openstack/nova master: perf: add ironic startup performance simulator  https://review.opendev.org/c/openstack/nova/+/98064112:50
opendevreviewsean mooney proposed openstack/nova master: docs: add Ironic startup performance measurements  https://review.opendev.org/c/openstack/nova/+/98068012:50
*** haleyb|out is now known as haleyb13:07
tkajinamsean-k-mooney, ah ok. thanks for sharing that context.13:08
gibigmaan: bauzas: could one of take a look at this eventlet config patch https://review.opendev.org/c/openstack/nova/+/993760 this would be a helpful addition to our downstream performance testing efforts 14:03
gibialso, do you think it would make sense / possible to backport this to Gazpacho? (not super important as it seems downstream folks are building from master directly, so I'm just curious what you think):14:05
tkajinamsean-k-mooney, I'm now reading your comment in https://review.opendev.org/c/openstack/nova/+/995835 ... I was thinking of rejecting usage of hw_firmware_stateles for bios boot because bios does support stateless/stateful concept and it's always stateless and am wondering what you think about it.14:15
sean-k-mooneyi dont thin that is a good idea14:16
sean-k-mooneyi think we shoudl only look at it if its uefi14:16
sean-k-mooneybecuase if anywon has set both today we dont want to break them when they upgrae14:17
sean-k-mooneywe have not been enforcing that restiction before correct? so enforcing it now would have an upgrade impact14:17
sean-k-mooneyif we had enforced it when we intoduced it it woudl have been fine14:18
sean-k-mooneyand perhaps correct14:18
sean-k-mooneybut unless we fix the existign instance on nova-compute startup that going to be problematic i think14:19
sean-k-mooneyif we enfoce it now then if you have an image with bios and stateless configured to any value then resize will fail14:19
sean-k-mooneyand either an operator will need to fix it with nova-manage or you will need to rebuild14:20
sean-k-mooneyso the best i think we can do is log a warning14:20
tkajinamthat's correct, though the existing instance may have only bios boot with firmware_stateless=False which is incorrect14:20
tkajinamok14:20
tkajinamI'll drop the validation and then add a warning message there14:20
opendevreviewAshish Gupta proposed openstack/nova master: tests: file-backed SQLite with WAL in threading mode for Database and CellDatabases Fixtures  https://review.opendev.org/c/openstack/nova/+/98858314:52
opendevreviewAshish Gupta proposed openstack/nova master: tests: use file-backed Placement SQLite in functional threading  https://review.opendev.org/c/openstack/nova/+/99258114:56
UgglaReminder: upstream meeting in ~ 1h14:58
opendevreviewAshish Gupta proposed openstack/nova master: tests: Use per-database write locks instead of global lock  https://review.opendev.org/c/openstack/nova/+/99286215:04
opendevreviewTakashi Kajinami proposed openstack/nova master: Accept hw_firmware_stateless=True for BIOS firmware type  https://review.opendev.org/c/openstack/nova/+/99583515:25
mhentkajinam: I won't be able to attend today's meeting but I'll see if I can do some tinkering with my SEV-SNP node tomorrow regarding my comment in https://review.opendev.org/c/openstack/nova/+/994930 and report back15:26
tkajinammhen, thanks15:27
tkajinammhen, if libvirt isn't able to correct the correct rom firmware then I suspect something is still wrong in libvirt firmware detection or descriptor file15:28
tkajinamthe selection logic was updated to treat type: rom as stateless so stateless=true should trigger usage of type: rom (unless nothing else is selected)15:28
tkajinamI suspect there is still a legacy descriptor file with sev-snp I have to check which firmware is actually selected and how its descriptor looks like15:29
opendevreviewTakashi Kajinami proposed openstack/nova master: compute: Validate SEV/SEV-ES support at start up  https://review.opendev.org/c/openstack/nova/+/99434215:30
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Ignore SEV-ES when SEV-SNP is detected  https://review.opendev.org/c/openstack/nova/+/99434315:31
opendevreviewMerged openstack/nova master: Return 400 for invalid properties for locked memory  https://review.opendev.org/c/openstack/nova/+/99581315:43
Uggla#startmeeting nova16:00
opendevmeetMeeting started Mon Jul  6 16:00:45 2026 UTC and is due to finish in 60 minutes.  The chair is Uggla. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
opendevmeetThe meeting name has been set to 'nova'16:00
UgglaHello everyone16:00
fwieselo/16:01
tkajinamo/16:01
* gibi is distracted16:01
samborko/16:02
UgglaLet's start16:02
Uggla#topic Bugs (stuck/critical) 16:02
Uggla#info No Critical bug16:02
Uggla#topic Gate status 16:03
Uggla#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:03
Uggla#link https://etherpad.opendev.org/p/nova-ci-failures-minimal16:03
Uggla#link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&branch=stable%2F*&branch=master&pipeline=periodic-weekly&skip=0 Nova&Placement periodic jobs status16:03
Uggla#info Please look at the gate failures and file a bug report with the gate-failure tag.16:03
Uggla#info Please try to provide a meaningful comment when you recheck16:03
UgglaLooking quickly at the gate, that looks ok. Please tell me if I'm wrong.16:04
Uggla#topic Release Planning 16:05
Uggla#link https://releases.openstack.org/hibiscus/schedule.html16:05
Uggla#info Nova deadlines are set in the above schedule16:05
Uggla         #info PTG etherpad for 2026.2 is available: https://etherpad.opendev.org/p/nova-2026.2-ptg16:05
bauzaso/16:05
UgglaNothing special on planning, we are ~5 weeks before Nova implementation review day16:06
Uggla#topic Review priorities16:06
Uggla#link New file for Hibiscus https://etherpad.opendev.org/p/nova-2026.2-status16:06
Uggla#info I have updated Launchpad and the above doc. Please ping me if you spot something missing.16:06
Uggla#info Starting: https://etherpad.opendev.org/p/nova-2026.2-status#L16 interesting bugs to review.16:06
UgglaSkipping Elod points because he is on pto16:07
Uggla#topic vmwareapi 3rd-party CI efforts Highlights16:07
Ugglafwiesel something you'd like to share.16:07
fwieselHi16:07
fwieselI'm investigating recent failures in the pipeline.16:07
fwieselI haven't gotten quite hold of the root cause yet16:07
fwieselBear with me, i hope I'll get it fixed tomorrow 16:08
fwieselThat's from my side16:08
Ugglafwiesel 👍16:08
Ugglathx16:09
sean-k-mooneyo/16:09
Uggla#topic Kamil's news about eventlet removal16:09
* Uggla giving the mic to sambork or gibi16:09
samborkSo today we almost landed changes that add a config option to run with eventlet/threading mode. As a segue from that, we should have data from the performance run with logs in the next few days. The first run indicates a probable degradation in the rally tests. Other than that, Ashish made progress with the unit testing patches (https://review.opendev.org/c/openstack/nova/+/992862, https://review.opendev.org/c/openstack/nova/+/992581, 16:10
samborkhttps://review.opendev.org/c/openstack/nova/+/988583, https://review.opendev.org/c/openstack/placement/+/993106)16:10
samborkI think thats i,t we didn't progress with anything else, and I give mic back (or maybe gibi have something to add)16:11
gibiI started looking at the functional test series from Ashish again today but I will need more time to have comments there16:11
gibinothing else16:11
Ugglathanks sambork and gibi16:12
Ugglaskipping Layos topic16:12
Uggla#topic Ironic review priorities16:12
Ugglacardoe do you have something ot share with us ?16:13
cardoeWe've rebased the startup-time series at https://review.opendev.org/q/topic:%22startup-time%2216:13
cardoeThe spec for trunk ports in the metadata is still ready to go as well as are the patches.16:14
cardoeBut that's all I've got.16:14
Ugglathanks cardoe16:14
Uggla#topic Confidential computing, status of SNP and TDX features16:14
* Uggla giving the mic to tkajinam and antia16:15
Ugglaand gibi16:15
antiaResuming development this week, was on PTO last week16:15
gibiantia: welcome back :)16:16
tkajinamThe implementations for SEV-SNP are still up for review. gibi already provided review many feedbacks and also completed the end to end testing (thanks a lot !!)16:16
Uggla👍16:17
gibiyeah for me that series looks good16:17
tkajinamgibi, just fyi. there is a problem pointed by sean in one of the base changes. I fixed it but I have to rebase the other changes later.16:18
bauzasyeah I started to look at the series16:18
tkajinamthere are a few more feedbacks by sean-k-mooney I still have to check. I'm afraid it might be quite tricky to address these cleanly soon, and might need some more discussions to find out a good balance.16:18
bauzasthanks tkajinam I'll continue to review then16:18
tkajinambauzas, thanks !16:18
sean-k-mooneytkajinam: libvirt has the snp cpaablity in domain caps16:19
sean-k-mooneyill post an xml dump of that shortly16:19
gibitkajinam: ack, I can do a quick re-test tomorrow. But then I have to give the HW back16:19
tkajinamsean-k-mooney, no it does not reflect actual cpu feature.16:19
tkajinamsean-k-mooney, it only shows whether libvirt supports it.16:19
sean-k-mooneyok but chekcing kernel option or proc is not ok 16:19
tkajinamwe should detect snp is enabled in bios, then appears in cpu flag16:19
sean-k-mooneyso if we cant trust libvirt when it reports it16:20
sean-k-mooneythen 1 that is a bug that shoudl be fixed in libvirt16:20
sean-k-mooneyand 2 we woudl need a config option in nova16:20
sean-k-mooneyit repots 16:20
sean-k-mooney    <launchSecurity supported='yes'>16:20
sean-k-mooney      <enum name='sectype'>16:20
sean-k-mooney        <value>sev</value>16:20
sean-k-mooney        <value>sev-snp</value>16:20
sean-k-mooney      </enum>16:20
sean-k-mooney    </launchSecurity>16:20
sean-k-mooney<value>sev-snp</value> should not be there if the host is not configure for snp16:20
tkajinamthe tricky point is that we should catch the case that sev-snp is enabled in firmware, but is not in kernel/qemu/libvirt16:21
sean-k-mooneynot in nova16:21
tkajinambecause enabling sev-snp in firmware immediately prohibits sev-es16:21
sean-k-mooneythat is what libvirt is ment to be doing with that api16:21
tkajinambut kernel still reports sev_es is available which is annoying16:21
gibi(I like the CVE :)16:21
sean-k-mooneysure but libvirt does not16:22
bauzasfwiw we discussed that in the spec16:22
sean-k-mooneywell it reqport generic sev which i guess we might be proxiting16:22
sean-k-mooneybauzas: we have rejected parsinc /proc before 16:22
sean-k-mooneyso i dont knwo why we woudl allow it now16:22
bauzaswe said that the BIOS option is the difference between whether we support SNP or ES16:23
bauzasso, if the operator modified the bios option, then the system supports SNP and that's it16:23
sean-k-mooneyok so then nova does not need to check for this right16:23
bauzascorrect16:23
bauzasthat's what we agreed on the spec at least16:24
sean-k-mooneyso if livbirt has sev-snp in the lauch capabliteis16:24
sean-k-mooneywe should just report the trait16:24
bauzaswe don't need to look at the firmware, because even if the firmware can support SNP, the host won't use this until the BIOS is modified16:24
sean-k-mooneyand if the operator has not enabeld snp but did create snp flavors16:24
sean-k-mooneythen we expect the vm boot to fail16:24
gibiit is about the fact the ES support disappears after that specific firmware upgrade and you can still have ES VMs on thehost16:25
bauzaslibvirt provides SNP capabilities only once the BIOS option is modified16:25
gibithe complication is not about SNP, but the disappearence of ES16:25
sean-k-mooneybauzas: ack in that case then we jsut need to look at the libvirt output16:25
bauzasgibi: AFAICU, the ES support continues until the BIOS option is modified, that's my point16:25
bauzastkajinam: am I right?16:26
gibiif you had a host with both ES and SNP enabled, and then update the firmware, ES disappears without BIOS changes16:26
gibi* BIOS config changes16:26
bauzasbecause you enabled SNP16:26
tkajinambauzas, the problem is that /proc/cpuinfo is only the feasible way I could find to detect "the BIOS option is modified"16:26
sean-k-mooneywell the sev section has16:26
sean-k-mooney    <sev supported='yes'>16:26
sean-k-mooney      <cbitpos>51</cbitpos>16:26
gibibauzas: because you updated the firmware to fix a CVE16:26
sean-k-mooney      <reducedPhysBits>1</reducedPhysBits>16:26
sean-k-mooney      <maxGuests>500</maxGuests>16:26
sean-k-mooney      <maxESGuests>9</maxESGuests>16:26
sean-k-mooney      <cpu0Id>LlF/9YPV8hnqsGNCBpLJeRUbm9y/yr5uNhgTaW96/ZVoYXjZRRuIfEwSMFWWd9882pcNDLW6LW3E3tytpU7/2g==</cpu0Id>16:26
sean-k-mooney    </sev>16:26
sean-k-mooneythe max es gust is still reproted in snp mode16:26
sean-k-mooneybut i think we need to look at the combidntion fo the lauchsecurit section and the sev section16:27
gibibeacuse the same set of ASIDs are used for ES and SNP16:27
gibibut a different set used for pure SEV16:27
gibibtw that CVE fix is actually good for us as we don't have to share resources between ES and SNP16:28
bauzasgibi: well, that's another concern, if the operator enabled SNP in the BIOS and then upgraded the firmware due to the CVE, they should know that ES is then disabled automatically16:28
gibibauzas:16:28
bauzasthat's unrelated to nova, right?16:28
gibibut nova has ES VMs on the host :):16:28
gibiso we cannot ignore it16:28
tkajinambauzas, yes and that's why /proc/cpuflag is checked, because at that point sev-snp is not yet enabled in kvm ( so nova assumes sev-snp is not ready )16:29
bauzasI think I wrote a spec comment saying about when we restart the compute16:29
sean-k-mooneygibi: do you happen to know if the host you are testing on has the firmware patch16:29
bauzaswe can look at the instances and stop the service if we find ES-used instances16:29
gibiit has. It is not possible to boot ES VMs on it16:29
gibiqemu fails16:29
tkajinamhttps://review.opendev.org/c/openstack/nova/+/99434316:30
sean-k-mooneyok and does it work with snp disabled16:30
tkajinamthis is the actual change where this is being discussed16:30
gibisean-k-mooney: I don't know that16:30
sean-k-mooneyi dont think this is an upgrede concern for nova yet16:30
sean-k-mooneysince nova didnt supprot snp before this firmware change16:30
gibibut it did support ES16:30
sean-k-mooneyso we just need to document that operator can use oen of the other16:30
sean-k-mooneygibi: right if they flat out broke es with the cve fix16:30
tkajinamso reading actual implementation may give clearer view about the topic.16:31
sean-k-mooneythat woudl be a problem but if it works just not when snp is enabeld in teh bios its not an upgrade probvlem16:31
gibithey actaully disabled ES on purpose as when SNP is enabled ES becomes voulnerable16:31
bauzashttps://review.opendev.org/c/openstack/nova-specs/+/983376/20..21/specs/2026.2/approved/amd-sev-snp-libvirt-support.rst#b6216:31
sean-k-mooneysure but as long as you can choose between the two its fine16:31
bauzasso the concern is that we need to look at /proc/cpuinfo ?16:31
sean-k-mooneyfrom a nova point of view we just need to docuemnt that es and snp are mutally exclisive16:31
sean-k-mooneybauzas: yep16:32
sean-k-mooneybauzas: i dont think bypsassing libvirt to look at /proc/cpuinfo is ok16:32
bauzasand there are no other ways to detect a SNP-supported OS ?16:32
sean-k-mooneybauzas: i think that is reported in the launchSecurity section16:32
sean-k-mooneybut we woudl have to disabel snp in the bios to confirm16:33
sean-k-mooneyand im hesitent to ask gibi to do that16:33
bauzasyeah16:33
tkajinamsean-k-mooney, no launchSecurity does not fully match with sev_snp cpu flag16:33
gibiwe agreed in the spec that if we have ES VMs on a host the nova-compute is restarted and sees that no ES capability is available any more due to SNP enabled then nova-compute will fail to start and let the deployer know that there is a mixup of configuration and ask for draining the ES VMs before enabling SNP16:33
sean-k-mooneyso its list there whewn its disabeld in the bios16:33
tkajinamsean-k-mooney, for example if you are using an older libvirt then it doesn't have that option but you can enable snp in firmware16:33
sean-k-mooney?16:33
sean-k-mooneytkajinam: that fine16:33
sean-k-mooneyold libivrt is handled by a min version check16:33
tkajinambut that still disables sev-es16:33
tkajinamin hardware level16:34
sean-k-mooneygibi: yep that is the corect behvior16:34
sean-k-mooneyits not enfocning that that i object too16:34
sean-k-mooneyits how we are determinign that that is problematic16:35
bauzasdon't we already look at the cpu capabilities other than using libvirt ?16:35
sean-k-mooneycorect we do not16:35
bauzashmmm16:36
antiadoes the kernel report sev-es support after firmware update?16:36
sean-k-mooneybauzas: to be clear i was told to go modify libvirt to get feature flags to report in the past more then once16:36
tkajinambauzas, sean-k-mooney is correct and there is no other logic reading /proc/cpuinfo now16:36
bauzasantia: that depends on the BIOS option AFAICU16:36
tkajinamantia, yes. sev_es cpu flag is still reported, and kvm_amd module still reports sev_es capability16:36
bauzastkajinam: if the operator didn't set the BIOS SNP option, right ?16:37
sean-k-mooneytkajinam: do you have a host that you are developing this on with the patch16:37
tkajinambauzas, no, regardless of BIOS setting16:37
sean-k-mooney*with the patched firmware16:37
bauzasI see, of course16:38
bauzasif you set SNP in the BIOS, you will have *both* flags (sev_snp and sev_es)16:38
tkajinamI don't have the one with the said firmware update yet. I'm trying to get full machine time for it but it takes a bit more time.16:38
tkajinamI spent some time looking into kernel and actually sev_es flag is required when sev_snp flag is enabled in kvm_amd16:39
tkajinamso I don't think this behavior (es still reported after snp is enabled in bios) may change quite soon.16:39
gibiso what if we file a bug somewhere in the virt stack, and keep the /proc/cpuinfo check for a while?16:40
bauzaswfm16:40
bauzaswith a big TODO/FIXME16:40
Ugglawfm16:40
sean-k-mooneyim honestly borderline -2 on /proc/cpuinfo16:41
sean-k-mooneyunless we replace usign libvirt for that in generla16:41
sean-k-mooneyi really dont think that is correct16:41
gibibut as far as I see we don't have an alternative at the moment16:42
tkajinamthere is still an option not to detect partial sev-snp configuration, and just fail only when sev-snp is flly configured16:42
sean-k-mooneywe have at leat one check to do which is detemin if the lauch securit section chagnes in reponce to the bios chagne16:42
sean-k-mooneyand we can have a config option for it16:42
tkajinamI mean, compute may not fail only when snp is enabled in BIOS, but then fails if operators try to enable snp fully.16:42
gibitkajinam: but ES VM still fail16:43
sean-k-mooneythe same way we had a config option for the number of sev isntance that can be coreated16:43
gibiin the partial config16:43
sean-k-mooney*created16:43
tkajinamgibi, yes16:43
sean-k-mooneyuntil we fixed libvirt16:43
gibiI rather keep that ~10 lines of code in nova than partially detect the a failure16:43
gibithe config option route does not apply in my mind as the deployer probably don't know that snp disables es in the hardware otherwise he would drain the ES VMs already16:44
gibiso config is unreliable16:44
sean-k-mooneybut the operator should know that16:44
gibithen we don't need the nova-compute startup check at all16:45
gibias operator knows and drains :)16:45
sean-k-mooneyright 16:45
sean-k-mooneyi also dont think we need that16:45
sean-k-mooneybut that a seprate issue16:45
sean-k-mooneyi want to make sure we are reporting the trait16:45
sean-k-mooneywhen a host supprot it or not for schduling16:45
gibias far as I understand we need the /proc/cpuinfo because we would like to have a startup check16:45
sean-k-mooneyand we shoudl do that based on what libvirt reports16:45
gibisean-k-mooney: even if libvirt reports it wrongly?16:46
sean-k-mooneyyes16:46
gibiI don't like that16:46
sean-k-mooneyi dont think nova shoudl be secondguessing libvirt16:46
sean-k-mooneyalso we have not fully confirmed libvirt reports it incorrectly16:46
sean-k-mooneyit repoce 2 diffent things16:46
sean-k-mooneyit reporst the sev capastiy16:46
sean-k-mooneyand seperate it reprot what modes can be used for sev to lauch a vm16:47
sean-k-mooneythere wre 3 modes of sev sofar16:47
sean-k-mooneysev, sev-es and sev-snp16:47
sean-k-mooneyin the lauch security section it only has sev and sev-snp16:47
sean-k-mooneynot sev-es16:48
sean-k-mooneyso i think libvirt is correctly reporting that sev-es cant be used16:48
tkajinamthat's basically because they use same enum (sev) for sev and sev-es16:48
tkajinamsev-snp is there because they introduced a different enum (for different scheme)16:48
sean-k-mooneyi see16:49
tkajinamI agree it's not quite ideal and doesn't show full items we want to know16:49
sean-k-mooneycan we defer this and come back to it16:49
sean-k-mooneyi.e. next week16:49
sean-k-mooneyi really dont like this16:49
tkajinamI at least add large TODO there and consider how we can improve libvirt to get rid of that hack16:50
sean-k-mooneyto be clear this hack is enouch to punt the feature until libvirt is fixed in my view16:50
sean-k-mooneyim trying to come aroudn to a diffent approch16:50
tkajinambut if people can spend some time reviewing it and give some more feedback about this topic that would be appreciated16:50
sean-k-mooneybut i have been toold by nova cores to go fix libvirt for similar issue multipel times16:50
gibisean-k-mooney: I'm totally not OK punting a working feature just because we need self contained workaround for a libvirt / amd complication16:51
gibiI'm OK to wait a week and reasses16:51
bauzastkajinam: as said I'll definitely review your series16:51
tkajinambauzas, thanks16:51
bauzasand yeah we can revisit that next week16:52
Ugglaguys I think that's the conclusion for today.16:52
tkajinamwe also might need some discussion about how we implement the startup check but that would be less prioritized. the discussion can be found in the series so I appreciate any thoughts about it, too.16:52
bauzas(at least personnally I'll appreciate it to have more context :D )16:52
tkajinamyup16:52
Ugglathanks tkajinam, antia and gibi16:53
* Uggla moving to next topics as we are reaching the top of the hour16:53
sean-k-mooneytkajinam: i htink we need my change to add the new driver fuction or you need to do it in the libvirt drivers init host but sure we can disucss in gerrit16:53
Uggla#topic Bug scrubbing 16:54
Uggla#info up to 91 (-3)16:54
Uggla#link https://etherpad.opendev.org/p/nova-bug-triage-roster16:54
Uggla#link https://truc.uggla.fr/ to follow the trend.16:54
tkajinamsean-k-mooney, thanks. yeah I just opened your change and will check it soon.16:54
UgglaNext meeting (this week): [public] Upstream bug triage. Wednesday, July 8th · 15:30 – 16:00 UTC. Video call link: meet.google.com/zjr-rxus-hzj16:54
Uggla#topic Open discussion16:54
UgglaUggla: PTO next 3 weeks. gibi will host the meeting next week then bauzas will host the next 2 ones.16:55
gibiyepp16:55
Ugglasomething you'd like to quickly share in the lastest 5 mn16:55
gibi-16:56
Ugglaif not I guess we are done for today.16:56
UgglaThanks for joining this meeting. Have a nice day/evening.16:56
Uggla#endmeeting16:56
opendevmeetMeeting ended Mon Jul  6 16:56:55 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:56
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2026/nova.2026-07-06-16.00.html16:56
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2026/nova.2026-07-06-16.00.txt16:56
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2026/nova.2026-07-06-16.00.log.html16:56
gibithanks folks16:56
tkajinamthanks !16:57
antiathanks :)16:57
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Detect AMD SEV-SNP support  https://review.opendev.org/c/openstack/nova/+/99476417:06
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Support launchSecurity element for SEV-SNP  https://review.opendev.org/c/openstack/nova/+/99492017:06
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Omit optional fields for SEV/SEV-ES  https://review.opendev.org/c/openstack/nova/+/99492117:07
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Drop sev capability check in launch instance flow  https://review.opendev.org/c/openstack/nova/+/99492917:07
opendevreviewTakashi Kajinami proposed openstack/nova master: AMD SEV: omit iommu='on' for virtio devices  https://review.opendev.org/c/openstack/nova/+/90963517:07
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Launch instances with SEV-SNP memory encryption  https://review.opendev.org/c/openstack/nova/+/99493017:09
opendevreviewTakashi Kajinami proposed openstack/nova master: Update documentations for AMD SEV-SNP support  https://review.opendev.org/c/openstack/nova/+/99509017:09
opendevreviewTakashi Kajinami proposed openstack/nova master: Remove [libvirt] num_memory_encrypted_guests  https://review.opendev.org/c/openstack/nova/+/99512017:09
opendevreviewMerged openstack/nova master: Add concurrency_backend config option for Nova services  https://review.opendev.org/c/openstack/nova/+/99376017:17
opendevreviewTakashi Kajinami proposed openstack/nova master: Fix wrong comment in test  https://review.opendev.org/c/openstack/nova/+/99607018:30

Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!