On 11/10/2020 10:43, Sander Eikelenboom wrote: > On 11/10/2020 02:06, Igor Druzhinin wrote: >> On 10/10/2020 18:51, Sander Eikelenboom wrote: >>> Hi Igor/Jan, >>> >>> I tried to update my AMD machine to current xen-unstable, but >>> unfortunately the HVM guests don't boot after that. The guest keeps >>> using CPU-cycles but I don't get to a command prompt (or any output at >>> all). PVH guests run fine. >>> >>> Bisection leads to commit: >>> >>> 8efa46516c5f4cf185c8df179812c185d3c27eb6 >>> hvmloader: indicate ACPI tables with "ACPI data" type in e820 >>> >>> I tried xen-unstable with this commit reverted and with that everything >>> works fine. >>> >>> I attached the xl-dmesg output. >> >> What guests are you using? > Not sure I understand what you ask for, but: > dom0 PV > guest HVM (qemu-xen) > >> Could you get serial output from the guest? > Not getting any, it seems to be stuck in very early boot. > >> Is it AMD specific? > Can't tell, this is the only machine I test xen-unstable on. > It's a AMD phenom X6. > Both dom0 and guest kernel are 5.9-rc8. > > Tested with guest config: > kernel = '/boot/vmlinuz-xen-guest' > ramdisk = '/boot/initrd.img-xen-guest' > > cmdline = 'root=UUID=7cc4a90d-d6b0-4958-bb7d-50497aa29f18 ro > nomodeset console=tty1 console=ttyS0 console=hvc0 earlyprintk=xen' > > type='hvm' > > device_model_version = 'qemu-xen' > > cpus = "2-5" > vcpus = 2 > > memory = '512' > > disk = [ > 'phy:/dev/xen_vms_ssd/media,xvda,w' > ] > > name = 'guest' > > vif = [ 'bridge=xen_bridge,ip=192.168.1.10,mac=00:16:3E:DC:0A:F1' ] > > on_poweroff = 'destroy' > on_reboot = 'restart' > on_crash = 'preserve' > > vnc=0 > > >> If it's a Linux guest could you get a stacktrace from >> the guest using xenctx? > > It is, here are few subsequent runs: > > ~# /usr/local/lib/xen/bin/xenctx -s > /boot/System.map-5.9.0-rc8-20201010-doflr-mac80211debug+ -f -a -C 4 > vcpu0: > cs:eip: ca80:00000256
Ok, it's stuck in linuxboot.bin option ROM. That's not something we test in Citrix - we don't use fw_cfg. It could be something with caching (given it's moving but slowly) or a bug uncovered by memory map changes. I'll try to get a repro on Monday. It could be AMD specific if it's caching related and that's why osstest didn't pick it up. Igor
