Back to Home / #xen / 2022 / 01 / Prev Day | Next Day
#xen IRC Logs for 2022-01-28

---Logopened Fri Jan 28 00:00:48 2022
00:04-!-jgross_ is now known as jgross
00:06<jgross>isodude: "extensive" is the correct attribute here. It booted as dom0 and as PVH guest. :-)
00:46<isodude>jgross: noted! well, now it boots properly with HVM/PVH/Dom0 on AMD hardware. Which by itself seems like a feat.
01:08<isodude>Ok so, anyone want to bite? Let's get suspend working on AMD Ryzen 4750U! I got two outstanding issues that I can't pin down properly. One of them is solved partly (new problem with BOs, maybe solved in drm-next) somewhere between Xen 4.15 and Xen 4.14 (, the other one seems unresolved
01:08<isodude>( Both work properly if booting the same kernel but without Xen. I was thinking that AMDGPU driver messed up MSI by not initializing it properly, was a dead end though. The other text duplication thingy is just weird.. how do you even diagnose such a thing? The response from amdgpu folks is.. nil.
01:08<isodude>Thoughs, directions?
01:09<isodude>I'm a year deep into this now soon, fun journey though :)
04:27-!-sysadmin [~sysadmin@] has joined #xen
04:27-!-sysadmin is "sysadmin" on #xen
04:28-!-sysadmin [~sysadmin@] has quit []
04:32-!-sysadmin [~sysadmin@] has joined #xen
04:32-!-sysadmin is "sysadmin" on #xen
04:32-!-sysadmin is now known as definitely5
04:33-!-definitely5 [~sysadmin@] has quit []
04:36-!-pasik [] has quit [Quit: .]
04:48-!-definitely5 [~sysadmin@] has joined #xen
04:48-!-definitely5 is "sysadmin" on #xen
04:59-!-definitely5 [~sysadmin@] has quit [Quit: definitely5]
05:14-!-cation21- [~cation21@] has quit [Ping timeout: 480 seconds]
05:30-!-definitely5 [~sysadmin@] has joined #xen
05:30-!-definitely5 is "sysadmin" on #xen
05:32-!-cation21 [~cation21@] has joined #xen
05:32-!-cation21 is "cation21" on #xen #redditprivacy #OpenBSD #Qubes_OS
05:40-!-definitely5 [~sysadmin@] has quit [Quit: definitely5]
06:05-!-definitely5 [~sysadmin@] has joined #xen
06:05-!-definitely5 is "sysadmin" on #xen
06:14-!-XCPngXOTeam [~XCPngXOTe@2a01:240:ab08::2] has quit [Read error: Network is unreachable]
06:14-!-XCPngXOTeam [~XCPngXOTe@2a01:240:ab08::2] has joined #xen
06:14-!-XCPngXOTeam is "XCPngXOTeam" on #xensummit #xen #xsxoteams
06:16-!-definitely5 [~sysadmin@] has quit [Ping timeout: 480 seconds]
11:08-!-ChmEarl [] has joined #xen
11:08-!-ChmEarl is "Mark Pryor" on #xen ##xen-packaging #mock #packaging #virt
11:58<ChmEarl>upstream binutils has a fix for broken EFI linking
11:59<andyhhp>yeah - it was reported this morning on xen-devel.
12:28<ChmEarl>Ubuntu Jammy is going with xen 4.16, qemu 6.2, & libvirt 8.0
17:35-!-ChmEarl [] has quit [Quit: Leaving]
22:44-!-jgross_ [~juergen_g@2a01:41e1:2c1c:e00:4b33:9b4:1831:7033] has joined #xen
22:44-!-jgross_ is "realname" on #xen
22:50-!-jgross [~juergen_g@2a01:41e1:2beb:4b00:5999:674f:799:9731] has quit [Ping timeout: 480 seconds]
23:15-!-genesix [~genesix@] has joined #xen
23:15-!-genesix is "purple" on #virt #llvm #ovirt #cryptoparty #xen
23:15-!-genesix [~genesix@] has quit [Remote host closed the connection]
---Logclosed Sat Jan 29 00:00:49 2022