Domain Birth Time

2024-05-10 Thread James Dingwall
Hi, We've added a feature to Xen 4.15 such that `xl uptime -b` reports the birth time of the domain (i.e. a value preserved across migrations). If this would be of wider interest I can try porting this to a more recent release and submitting it for review. Regards, James

Re: XSA-446 relevance on Intel

2024-01-05 Thread James Dingwall
On Tue, Dec 12, 2023 at 10:56:48AM +, Andrew Cooper wrote: > On 12/12/2023 9:43 am, James Dingwall wrote: > > Hi, > > > > We were experiencing a crash during PV domU boot on several different models > > of hardware but all with Intel CPUs. The Xen version wa

XSA-446 relevance on Intel

2023-12-12 Thread James Dingwall
Hi, We were experiencing a crash during PV domU boot on several different models of hardware but all with Intel CPUs. The Xen version was based on stable-4.15 at 4a4daf6bddbe8a741329df5cc8768f7dec664aed (XSA-444) with some local patches. Since updating the branch to

Re: xen 4.15.5: msr_relaxed required for MSR 0x1a2

2023-11-29 Thread James Dingwall
On Mon, Nov 20, 2023 at 10:24:05AM +0100, Roger Pau Monné wrote: > On Mon, Nov 20, 2023 at 08:27:36AM +0000, James Dingwall wrote: > > On Fri, Nov 17, 2023 at 10:56:30AM +0100, Jan Beulich wrote: > > > On 17.11.2023 10:18, James Dingwall wrote: > > > > On Thu, No

Re: xen 4.15.5: msr_relaxed required for MSR 0x1a2

2023-11-20 Thread James Dingwall
On Fri, Nov 17, 2023 at 11:17:46AM +0100, Roger Pau Monné wrote: > On Fri, Nov 17, 2023 at 09:18:39AM +0000, James Dingwall wrote: > > On Thu, Nov 16, 2023 at 04:32:47PM +, Andrew Cooper wrote: > > > On 16/11/2023 4:15 pm, James Dingwall wrote: > > > > Hi, >

Re: xen 4.15.5: msr_relaxed required for MSR 0x1a2

2023-11-20 Thread James Dingwall
On Fri, Nov 17, 2023 at 10:56:30AM +0100, Jan Beulich wrote: > On 17.11.2023 10:18, James Dingwall wrote: > > On Thu, Nov 16, 2023 at 04:32:47PM +, Andrew Cooper wrote: > >> On 16/11/2023 4:15 pm, James Dingwall wrote: > >>> Hi, > >>&g

Re: xen 4.15.5: msr_relaxed required for MSR 0x1a2

2023-11-17 Thread James Dingwall
On Thu, Nov 16, 2023 at 04:32:47PM +, Andrew Cooper wrote: > On 16/11/2023 4:15 pm, James Dingwall wrote: > > Hi, > > > > Per the msr_relaxed documentation: > > > >"If using this option is necessary to fix an issue, please report a bug." > >

xen 4.15.5: msr_relaxed required for MSR 0x1a2

2023-11-16 Thread James Dingwall
Hi, Per the msr_relaxed documentation: "If using this option is necessary to fix an issue, please report a bug." After recently upgrading an environment from Xen 4.14.5 to Xen 4.15.5 we started experiencing a BSOD at boot with one of our Windows guests. We found that enabling `msr_relaxed =

Re: live migration fails: qemu placing pci devices at different locations

2023-11-01 Thread James Dingwall
On Tue, Oct 31, 2023 at 10:07:29AM +, James Dingwall wrote: > Hi, > > I'm having a bit of trouble performing live migration between hvm guests. The > sending side is xen 4.14.5 (qemu 5.0), receiving 4.15.5 (qemu 5.1). The error > message recorded in qemu-dm---incoming.log: &

live migration fails: qemu placing pci devices at different locations

2023-10-31 Thread James Dingwall
Hi, I'm having a bit of trouble performing live migration between hvm guests. The sending side is xen 4.14.5 (qemu 5.0), receiving 4.15.5 (qemu 5.1). The error message recorded in qemu-dm---incoming.log: qemu-system-i386: Unknown savevm section or instance ':00:04.0/vga' 0. Make sure that

Re: [PATCH] fix invalid frontend path for set_mtu

2022-04-27 Thread James Dingwall
On 2022-04-27 10:17, Anthony PERARD wrote: On Tue, Apr 19, 2022 at 01:04:18PM +0100, James Dingwall wrote: Thank you for your feedback. I've updated the patch as suggested. I've also incorporated two other changes, one is a simple style change for consistency, the other is to change

Re: [PATCH] fix invalid frontend path for set_mtu

2022-04-19 Thread James Dingwall
Hi Anthony, On Tue, Apr 12, 2022 at 02:03:17PM +0100, Anthony PERARD wrote: > Hi James, > > On Tue, Mar 01, 2022 at 09:35:13AM +0000, James Dingwall wrote: > > The set_mtu() function of xen-network-common.sh currently has this code: > > > >

[PATCH] fix invalid frontend path for set_mtu

2022-03-01 Thread James Dingwall
Hi, The set_mtu() function of xen-network-common.sh currently has this code: if [ ${type_if} = vif ] then local dev_=${dev#vif} local domid=${dev_%.*} local devid=${dev_#*.} local

Re: [RFC] kernel: xenfs parameter to hide deprecated files

2022-03-01 Thread James Dingwall
Hi Juergen, On Fri, Feb 25, 2022 at 03:09:05PM +0100, Juergen Gross wrote: > On 23.02.22 19:08, James Dingwall wrote: > > Hi, > > > > I have been investigating a very intermittent issue we have with xenstore > > access hanging. Typically it seems to happen when all do

[RFC] kernel: xenfs parameter to hide deprecated files

2022-02-23 Thread James Dingwall
/drivers/xen/xenfs/super.c index d7d64235010d..d02c451f6a4d 100644 --- a/drivers/xen/xenfs/super.c +++ b/drivers/xen/xenfs/super.c @@ -3,6 +3,11 @@ * xenfs.c - a filesystem for passing info between the a domain and * the hypervisor. * + * 2022-02-12 James Dingwall Introduce hide_deprecated

tools: propogate MTU to vif frontends (backporting)

2022-02-14 Thread James Dingwall
Hi, I've been backporting this series to xen 4.14 and everything relating to the backend seems to be working well. For the frontend I can see the mtu value published to xenstore but it does't appear to be consumed to set the matching mtu in the guest.

Re: possible kernel/libxl race with xl network-attach

2022-01-24 Thread James Dingwall
On Mon, Jan 24, 2022 at 10:07:54AM +0100, Roger Pau Monné wrote: > On Fri, Jan 21, 2022 at 03:05:07PM +0000, James Dingwall wrote: > > On Fri, Jan 21, 2022 at 03:00:29PM +0100, Roger Pau Monné wrote: > > > On Fri, Jan 21, 2022 at 01:34:54PM +0000, James Dingwall wrote: > >

Re: possible kernel/libxl race with xl network-attach

2022-01-21 Thread James Dingwall
On Fri, Jan 21, 2022 at 03:00:29PM +0100, Roger Pau Monné wrote: > On Fri, Jan 21, 2022 at 01:34:54PM +0000, James Dingwall wrote: > > On 2022-01-13 16:11, Roger Pau Monné wrote: > > > On Thu, Jan 13, 2022 at 11:19:46AM +0000, James Dingwall wrote: > > > > >

Re: possible kernel/libxl race with xl network-attach

2022-01-21 Thread James Dingwall
On 2022-01-13 16:11, Roger Pau Monné wrote: On Thu, Jan 13, 2022 at 11:19:46AM +, James Dingwall wrote: I have been trying to debug a problem where a vif with the backend in a driver domain is added to dom0. Intermittently the hotplug script is not invoked by libxl (running as xl devd

possible kernel/libxl race with xl network-attach

2022-01-13 Thread James Dingwall
Hi, I have been trying to debug a problem where a vif with the backend in a driver domain is added to dom0. Intermittently the hotplug script is not invoked by libxl (running as xl devd) in the driver domain. By enabling some debug for the driver domain kernel and libxl I have these

Re: xen 4.14.3 incorrect (~3x) cpu frequency reported

2022-01-07 Thread James Dingwall
On Fri, Jan 07, 2022 at 12:39:04PM +0100, Jan Beulich wrote: > On 06.01.2022 16:08, James Dingwall wrote: > >>> On Wed, Jul 21, 2021 at 12:59:11PM +0200, Jan Beulich wrote: > >>> > &

Re: xen 4.14.3 incorrect (~3x) cpu frequency reported

2022-01-06 Thread James Dingwall
Hi Jan, > > On Wed, Jul 21, 2021 at 12:59:11PM +0200, Jan Beulich wrote: > > > >> On 21.07.2021 11:29,

Re: xen 4.11.4 incorrect (~3x) cpu frequency reported

2021-11-05 Thread James Dingwall
Hi Jan, On Fri, Nov 05, 2021 at 01:50:04PM +0100, Jan Beulich wrote: > On 26.07.2021 14:33, James Dingwall wrote: > > Hi Jan, > > > > Thank you for taking the time to reply. > > > > On Wed, Jul 21, 2021 at 12:59:11PM +0200, Jan Beulich wrote: > >>

domain never exits after using 'xl save'

2021-09-23 Thread James Dingwall
Hi, This is an issue that was observed on 4.11.3 but I have reproduced on 4.14.3. After using the `xl save` command the associated `xl create` process exits which later results in the domain not being cleaned up when the guest is shutdown. e.g.: # xl list -v | grep

Re: xen 4.11.4 incorrect (~3x) cpu frequency reported

2021-07-26 Thread James Dingwall
Hi Jan, Thank you for taking the time to reply. On Wed, Jul 21, 2021 at 12:59:11PM +0200, Jan Beulich wrote: > On 21.07.2021 11:29, James Dingwall wrote: > > We have a system which intermittently starts up and reports an incorrect > > cpu frequency: > > > > # gr

xen 4.11.4 incorrect (~3x) cpu frequency reported

2021-07-21 Thread James Dingwall
Hi, We have a system which intermittently starts up and reports an incorrect cpu frequency: # grep -i mhz /var/log/kern.log Jul 14 17:47:47 dom0 kernel: [0.000475] tsc: Detected 2194.846 MHz processor Jul 14 22:03:37 dom0 kernel: [0.000476] tsc: Detected 2194.878 MHz processor Jul 14

Re: [PATCH for-4.12 and older] x86/msr: fix handling of MSR_IA32_PERF_{STATUS/CTL} (again)

2021-02-04 Thread James Dingwall
Hi Jan, On Thu, Feb 04, 2021 at 10:36:06AM +0100, Jan Beulich wrote: > X86_VENDOR_* aren't bit masks in the older trees. > > Reported-by: James Dingwall > Signed-off-by: Jan Beulich > > --- a/xen/arch/x86/msr.c > +++ b/xen/arch/x86/msr.c > @@ -226,7 +226,8 @@ int guest

Re: VIRIDIAN CRASH: 3b c0000096 75b12c5 9e7f1580 0

2021-02-04 Thread James Dingwall
Hi Jan, Thank you for your reply. On Wed, Feb 03, 2021 at 03:55:07PM +0100, Jan Beulich wrote: > On 01.02.2021 16:26, James Dingwall wrote: > > I am building the xen 4.11 branch at > > 310ab79875cb705cc2c7daddff412b5a4899f8c9 which includes commit > > 3b5de119f0399cbe745

VIRIDIAN CRASH: 3b c0000096 75b12c5 9e7f1580 0

2021-02-01 Thread James Dingwall
Hi, I am building the xen 4.11 branch at 310ab79875cb705cc2c7daddff412b5a4899f8c9 which includes commit 3b5de119f0399cbe745502cb6ebd5e6633cc139c "86/msr: fix handling of MSR_IA32_PERF_{STATUS/CTL}". I think this should address this error recorded in xen's dmesg: (XEN) d11v0 VIRIDIAN CRASH:

Re: [Xen-devel] [PATCH] xen/xenbus: fix self-deadlock after killing user process

2019-10-21 Thread James Dingwall
0 > [ 2551.528665] kthread+0x121/0x140 > [ 2551.528667] ? xb_read+0x1d0/0x1d0 > [ 2551.528670] ? kthread_park+0x90/0x90 > [ 2551.528673] ret_from_fork+0x35/0x40 > > Fix this by doing the cleanup via a workqueue instead. > > Reported-by: James Dingwall > Fixes: fd8aa9095a9

Re: [Xen-devel] [PATCH] xen/xenbus: fix self-deadlock after killing user process

2019-10-07 Thread James Dingwall
2551.528654] xenbus_dev_queue_reply+0xc4/0x220 > > [ 2551.528657] xenbus_thread+0x7de/0x880 > > [ 2551.528660] ? wait_woken+0x80/0x80 > > [ 2551.528665] kthread+0x121/0x140 > > [ 2551.528667] ? xb_read+0x1d0/0x1d0 > > [ 2551.528670] ? kthread_park+0x90/0x90 > >

[Xen-devel] failed to launch qemu when running de-privileged (xen 4.8)

2018-08-02 Thread James Dingwall
Hi, I had a bit of a head scratcher while writing a patch for 4.8 which allows the qemu-dm process for a stubdom to be executed as an unprivileged user. After a liberal sprinkling of log messages I found that my problem was related to the check of the return code from getpwnam_r. In 4.11