[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] can't boot guests on Debian/Buster with 4.19.0-6-rt-amd64 and Xen 4.11
Hi, Looks like it's still the case! I booted from 4.19.0-6-amd64 (non-RT) with Xen 4.11 and I can't reproduce the errors I was getting before... thanks! jf * Chuck Ritola <cjritola@xxxxxxxxx> [20191102 13:59]: > It's been a number of years, but I remember RT kernels having trouble > starting in Xen. Any success with non-RT? > > On Fri, Nov 1, 2019 at 12:43 PM Jean-Francois Malouin < > Jean-Francois.Malouin@xxxxxxxxxxxxxxxxx> wrote: > > > Hi, > > > > On a stock Debian GNU/Linux 10 (buster) running kernel 4.19.0-6-rt-amd64 > > #1 SMP PREEMPT RT Debian 4.19.67-2+deb10u1 (2019-09-20) > > with Xen 4.11... > > > > I keep getting the errors below when trying to boot guests, related to > > xen_evtchn it seems. > > > > They usually don't boot, even though sometimes they do but very rarely. > > Can > > someone shed some light? I've tried the next kernel available for Buster, > > 5.2.0-0.bpo.3-rt-amd64, but I get with exactly the same issues... > > > > Thanks, > > jf > > > > -- > > xl info: > > > > host : puck > > release : 4.19.0-6-rt-amd64 > > version : #1 SMP PREEMPT RT Debian 4.19.67-2+deb10u1 > > (2019-09-20) > > machine : x86_64 > > nr_cpus : 8 > > max_cpu_id : 23 > > nr_nodes : 2 > > cores_per_socket : 4 > > threads_per_core : 1 > > cpu_mhz : 2000.091 > > hw_caps : > > bfebfbff:009ce3bd:28100800:00000001:00000000:00000000:00000000:00000100 > > virt_caps : hvm > > total_memory : 12279 > > free_memory : 35 > > sharing_freed_memory : 0 > > sharing_used_memory : 0 > > outstanding_claims : 0 > > free_cpus : 0 > > xen_major : 4 > > xen_minor : 11 > > xen_extra : .2-pre > > xen_version : 4.11.2-pre > > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > > hvm-3.0-x86_32p hvm-3.0-x86_64 > > xen_scheduler : credit > > xen_pagesize : 4096 > > platform_params : virt_start=0xffff800000000000 > > xen_changeset : > > xen_commandline : placeholder > > cc_compiler : gcc (Debian 8.3.0-7) 8.3.0 > > cc_compile_by : pkg-xen-devel > > cc_compile_domain : lists.alioth.debian.org > > cc_compile_date : Mon Jun 24 10:10:11 UTC 2019 > > build_id : a2c4043244b6d32b05873fcfae7635cd823bf0bb > > xend_config_format : 4 > > > > > > > > > > Nov 1 12:20:48 puck root: /etc/xen/scripts/block: add > > XENBUS_PATH=backend/vbd/6/51714 > > Nov 1 12:20:48 puck root: /etc/xen/scripts/block: add > > XENBUS_PATH=backend/vbd/6/51713 > > Nov 1 12:20:49 puck root: /etc/xen/scripts/block: Writing > > backend/vbd/6/51714/physical-device fd:4 to xenstore. > > Nov 1 12:20:49 puck root: /etc/xen/scripts/block: Writing > > backend/vbd/6/51714/physical-device-path /dev/dm-4 to xenstore. > > Nov 1 12:20:49 puck root: /etc/xen/scripts/block: Writing > > backend/vbd/6/51714/hotplug-status connected to xenstore. > > Nov 1 12:20:50 puck root: /etc/xen/scripts/block: Writing > > backend/vbd/6/51713/physical-device fd:3 to xenstore. > > Nov 1 12:20:50 puck root: /etc/xen/scripts/block: Writing > > backend/vbd/6/51713/physical-device-path /dev/dm-3 to xenstore. > > Nov 1 12:20:50 puck root: /etc/xen/scripts/block: Writing > > backend/vbd/6/51713/hotplug-status connected to xenstore. > > Nov 1 12:20:50 puck systemd-udevd[15181]: Using default interface naming > > scheme 'v240'. > > Nov 1 12:20:50 puck systemd-udevd[15181]: link_config: autonegotiation is > > unset or enabled, the speed and duplex are not writable. > > Nov 1 12:20:50 puck root: /etc/xen/scripts/vif-bridge: online type_if=vif > > XENBUS_PATH=backend/vif/6/0 > > Nov 1 12:20:50 puck kernel: [70698.477679] xenbr0: port 3(vif6.0) entered > > blocking state > > Nov 1 12:20:50 puck kernel: [70698.477684] xenbr0: port 3(vif6.0) entered > > disabled state > > Nov 1 12:20:50 puck kernel: [70698.477829] device vif6.0 entered > > promiscuous mode > > Nov 1 12:20:50 puck kernel: [70698.485422] IPv6: ADDRCONF(NETDEV_UP): > > vif6.0: link is not ready > > Nov 1 12:20:50 puck root: /etc/xen/scripts/vif-bridge: Successful > > vif-bridge online for vif6.0, bridge xenbr0. > > Nov 1 12:20:50 puck root: /etc/xen/scripts/vif-bridge: Writing > > backend/vif/6/0/hotplug-status connected to xenstore. > > Nov 1 12:20:53 puck kernel: [70700.870856] ------------[ cut here > > ]------------ > > Nov 1 12:20:53 puck kernel: [70700.870864] Interrupt for port 99, but > > apparently not enabled; per-user 00000000b68b6469 > > Nov 1 12:20:53 puck kernel: [70700.870912] WARNING: CPU: 0 PID: 15559 at > > drivers/xen/evtchn.c:167 evtchn_interrupt+0xc1/0xd0 [xen_evtchn] > > Nov 1 12:20:53 puck kernel: [70700.870913] Modules linked in: xen_netback > > xen_blkback sctp rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache nft_l > > imit xt_limit nft_counter xt_state xt_conntrack nf_conntrack > > nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_compat nf_tables nfnetlink > > xen_gntdev x > > en_evtchn xenfs xen_privcmd bridge stp llc snd_hda_intel mgag200 evdev > > intel_powerclamp snd_hda_codec ttm snd_hda_core ipmi_si ipmi_devintf snd_ > > hwdep serio_raw ipmi_msghandler pcspkr drm_kms_helper sg snd_pcm snd_timer > > iTCO_wdt iTCO_vendor_support drm snd i2c_algo_bit soundcore ioatdma b > > utton i7core_edac i5500_temp dca nfsd drbd lru_cache auth_rpcgss nfs_acl > > dm_mod lockd parport_pc grace ppdev sunrpc lp parport ip_tables x_table > > s autofs4 ext4 crc16 mbcache jbd2 fscrypto ecb crypto_simd cryptd > > glue_helper aes_x86_64 raid10 raid456 async_raid6_recov > > Nov 1 12:20:53 puck kernel: [70700.870969] async_memcpy async_pq > > async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid0 multipath > > line > > ar raid1 md_mod sd_mod hid_generic usbhid hid ahci libahci uhci_hcd > > ehci_pci crc32c_intel psmouse ehci_hcd libata usbcore e1000e scsi_mod i2c_i8 > > 01 lpc_ich usb_common > > Nov 1 12:20:53 puck kernel: [70700.870994] CPU: 0 PID: 15559 Comm: > > irq/138-evtchn: Tainted: G W 4.19.0-6-rt-amd64 #1 Debian 4.19 > > .67-2+deb10u1 > > Nov 1 12:20:53 puck kernel: [70700.870995] Hardware name: Supermicro > > X8DTL/X8DTL, BIOS 2.0c 01/05/11 > > Nov 1 12:20:53 puck kernel: [70700.870999] RIP: > > e030:evtchn_interrupt+0xc1/0xd0 [xen_evtchn] > > Nov 1 12:20:53 puck kernel: [70700.871001] Code: ba 01 00 00 00 be 1d 00 > > 00 00 48 8d bb e8 00 00 00 e8 73 eb d3 c0 eb b5 8b 76 20 48 89 da 48 c7 c7 > > e8 81 54 c0 e8 d9 b2 b3 c0 <0f> 0b e9 55 ff ff ff 0f 1f 84 00 00 00 00 00 > > 66 66 66 66 90 41 57 > > Nov 1 12:20:53 puck kernel: [70700.871002] RSP: e02b:ffffc90046c77e80 > > EFLAGS: 00010282 > > Nov 1 12:20:53 puck kernel: [70700.871004] RAX: 0000000000000000 RBX: > > ffff888322716700 RCX: 0000000000000000 > > Nov 1 12:20:53 puck kernel: [70700.871006] RDX: 0000000000000001 RSI: > > ffffffff81e8828b RDI: 00000000ffffffff > > Nov 1 12:20:53 puck kernel: [70700.871014] RBP: ffff88832256f740 R08: > > 0000000000000001 R09: 0000000000000000 > > Nov 1 12:20:53 puck kernel: [70700.871015] R10: 0000000000000004 R11: > > 0000000000000000 R12: 000000000000008a > > Nov 1 12:20:53 puck kernel: [70700.871017] R13: ffffffff810ef3c0 R14: > > ffff8881cb19fd20 R15: ffff888327ff1e00 > > Nov 1 12:20:53 puck kernel: [70700.871032] FS: 00007fd05ce0b700(0000) > > GS:ffff88832ee00000(0000) knlGS:0000000000000000 > > Nov 1 12:20:53 puck kernel: [70700.871034] CS: e033 DS: 0000 ES: 0000 > > CR0: 0000000080050033 > > Nov 1 12:20:53 puck kernel: [70700.871035] CR2: 0000560600680000 CR3: > > 0000000306b04000 CR4: 0000000000000660 > > Nov 1 12:20:53 puck kernel: [70700.871042] Call Trace: > > Nov 1 12:20:53 puck kernel: [70700.871059] irq_forced_thread_fn+0x24/0x80 > > Nov 1 12:20:53 puck kernel: [70700.871062] irq_thread+0xdd/0x180 > > Nov 1 12:20:53 puck kernel: [70700.871066] ? wake_threads_waitq+0x30/0x30 > > Nov 1 12:20:53 puck kernel: [70700.871068] ? > > irq_thread_check_affinity+0xc0/0xc0 > > Nov 1 12:20:53 puck kernel: [70700.871074] kthread+0x112/0x130 > > Nov 1 12:20:53 puck kernel: [70700.871077] ? > > kthread_create_worker_on_cpu+0x70/0x70 > > Nov 1 12:20:53 puck kernel: [70700.871083] ret_from_fork+0x35/0x40 > > Nov 1 12:20:53 puck kernel: [70700.871087] ---[ end trace > > 000000000000001d ]--- > > Nov 1 12:20:53 puck kernel: [70700.871104] ------------[ cut here > > ]------------ > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@xxxxxxxxxxxxxxxxxxxx > > https://lists.xenproject.org/mailman/listinfo/xen-users _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |