On 2019-12-19 02:42, Ian Jackson wrote:
Steven Haigh writes ("[PATCH] [tools/hotplug] Use ip on systems where
brctl is not available"):
Newer distros like CentOS 8 do not have brctl available. As such, we
can't use it to configure networking anymore.
This patch will fall
Newer distros like CentOS 8 do not have brctl available. As such, we
can't use it to configure networking anymore.
This patch will fall back to 'ip' or 'bridge' commands if brctl is not
available in the working PATH.
This would be a likely backport candidate to any version expected to be
built on
a series that
does nothing but cleanup - then do the brctl / ip changes on top of
that in a different patch.
I might as well do them all - and it makes sense to do nothing but
cleanup, then functional changes based on the cleaned up code.
Steven Haigh
📧 net...@crc.id.au 💻 https://www.
Signed-off-by: Steven Haigh
---
tools/hotplug/Linux/xen-network-common.sh | 144 +++---
1 file changed, 70 insertions(+), 74 deletions(-)
diff --git a/tools/hotplug/Linux/xen-network-common.sh
b/tools/hotplug/Linux/xen-network-common.sh
index 92ffa603f7..ab76827a64 100644
--- a
Signed-off-by: Steven Haigh
---
tools/hotplug/Linux/colo-proxy-setup | 30 +--
tools/hotplug/Linux/vif-bridge| 19 --
tools/hotplug/Linux/vif2 | 12 +++--
tools/hotplug/Linux/xen-network-common.sh | 15 +---
4 files
with ip / bridge commands.
This series starts cleaning up whitespace and formatting, as well
as starts adding conditionals for using brctl (if present) but using
ip if /usr/sbin/brctl is not installed.
Changes since v1
* Fixed reference to /usr/bin/brctl instead of /usr/sbin/brctl
Steven Haigh
whitespace and formatting, as well
as starts adding conditionals for using brctl (if present) but using
ip if /usr/sbin/brctl is not installed.
Changes since v1
* Fixed reference to /usr/bin/brctl instead of /usr/sbin/brctl
Steven Haigh (2):
Tidy up whitespace and formatting in file to be consistent
whitespace and formatting, as well
as starts adding conditionals for using brctl (if present) but using
ip if /usr/sbin/brctl is not installed.
Steven Haigh (2):
Tidy up whitespace and formatting in file to be consistent.
Use ip for bridge related functions where brctl is not present
tools/hotplug
Signed-off-by: Steven Haigh
---
tools/hotplug/Linux/xen-network-common.sh | 144 +++---
1 file changed, 70 insertions(+), 74 deletions(-)
diff --git a/tools/hotplug/Linux/xen-network-common.sh
b/tools/hotplug/Linux/xen-network-common.sh
index 92ffa603f7..ab76827a64 100644
--- a
Signed-off-by: Steven Haigh
---
tools/hotplug/Linux/colo-proxy-setup | 30 +--
tools/hotplug/Linux/vif-bridge| 19 --
tools/hotplug/Linux/vif2 | 12 +++--
tools/hotplug/Linux/xen-network-common.sh | 15 +---
4 files
of any patches / additions to documentation -
however maybe this is the wiki? I'll leave that for someone else to
comment on.
--
Steven Haigh
? net...@crc.id.au ? http://www.crc.id.au
? +61 (3) 9001 6090? 0412 935 897
___
Xen-devel ma
ccessfully booted.
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +613 9001 6090 📱 +614 1293 5897
On Fri, Nov 15, 2019 at 18:06, Andreas Kinzler wrote:
Hello All,
I compared the CPUID listings from Ryzen 2700X (attached as tar.xz)
to 3700X and found only very few diff
is launched - hence it
would not be applied and a guest crash would occur...
Depending on the VM's settings, this would either continue to start &
crash - or just stop again until it could be started with the ENV
variable.
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.a
Awesome - thanks Michael.
I'll try and test this out tomorrow.
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +613 9001 6090 📱 +614 1293 5897
On Sat, Oct 26, 2019 at 16:00, "YOUNG, MICHAEL A."
wrote:
On Sat, 26 Oct 2019, Steven Haigh wrote:
If /
, or just fixes the existing issues) - but we can look at
revisiting removing these workarounds from anaconda / grub2 packages in
F30 / F31 / Rawhide.
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +613 9001 6090 📱 +614 1293 5897
On Fri, Oct 25, 2019 at 22:52, &q
HVM DomU crashed.
I gzip'ed it, as its a few hundred Kb.
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +613 9001 6090 📱 +614 1293 5897
On Fri, Oct 25, 2019 at 10:28, Jan Beulich wrote:
On 25.10.2019 09:00, Steven Haigh wrote:
Further to my last, I download
error message (shown via VNC) is HAL MEMORY ALLOCATION.
On 2019-10-25 16:26, Steven Haigh wrote:
Just to make things annoying, I also get the following message in the
logs for correctly operating Linux PVH DomU's:
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x2600, fault
ad
then again they are not always to be believed.
There are some odd looking IOMMU faults in there too.
Paul
On Thu, 24 Oct 2019 at 13:01, Steven Haigh wrote:
Hi all,
I've managed to get the git master version of Xen on this affected
system and tries to boot a Windows Server 2016 system
#x27;
vnc = 2
vnclisten = "0.0.0.0"
#vncpasswd = ''
## Set the clock to localtime - not UTC...
localtime = 1
## Fix the mouse cursor for VNC usage
usbdevice = 'tablet'
## Lower CPU prio that other VMs...
cpu_weight = 128
on_poweroff = 'destroy'
on_reboot
, is there a simpler fix that could be
included before Xen 4.13 gets launched (and hopefully backported)?
I'm not sure if the proposed changes to Fedora makes this a little
simpler in fixing the entire issue.
(apologies for top posting, Geary doesn't seem to like letting me
bottom
for the same installed VM.
Any comments either here or via the BZ report above would be welcome.
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +613 9001 6090 📱 +614 1293 5897
___
Xen-devel mailing list
Xen-devel@
At the risk of sounding like a broken record, is there an progress with
investigations on the AMD Ryzen 3xxx series and Windows HVM systems?
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +613 9001 6090 📱 +614 1293 5897
On Sat, Sep 28, 2019 at 07:09, Juergen Gross
If this is helpful, I can probably provide the same from:
* Ryzen 1700x
* Ryzen 2700x
* Ryzen 3900x
I'll leave it to those in the know as to what is useful or not...
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +613 9001 6090 📱 +614 1293
On 2019-09-05 18:19, Andrew Cooper wrote:
On 05/09/2019 09:00, Lars Kurth wrote:
IMPORTANT: I had a few additions to the agenda, but do not know WHO
added these. I believe one was Juergen. Who added the items related to
MA Youngs patches?
Steven Haigh I believe.
Booting fedora guests is
On Mon, Sep 2, 2019 at 6:34 PM, Paul Durrant
wrote:
-Original Message-
From: Steven Haigh
Sent: 02 September 2019 09:32
To: Paul Durrant
Cc: Andrew Cooper ; Andreas Kinzler
; xen-
de...@lists.xenproject.org
Subject: Re: Windows HVM no longer boots with AMD Ryzen 3700X (and
On 2019-09-02 18:25, Steven Haigh wrote:
On 2019-09-02 18:20, Paul Durrant wrote:
-Original Message-
From: Steven Haigh
Sent: 02 September 2019 09:09
To: Paul Durrant
Cc: Andreas Kinzler ; Andrew Cooper
; xen-
de...@lists.xenproject.org
Subject: Re: Windows HVM no longer boots with
On 2019-09-02 18:20, Paul Durrant wrote:
-Original Message-
From: Steven Haigh
Sent: 02 September 2019 09:09
To: Paul Durrant
Cc: Andreas Kinzler ; Andrew Cooper
; xen-
de...@lists.xenproject.org
Subject: Re: Windows HVM no longer boots with AMD Ryzen 3700X (and
3900X)
On 2019-09
: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED
viridian=0
vcpus=1
Boot OK - get to Windows Server 2016 login etc
And to complete the set, how about viridian=1 vcpus=1?
Any vcpus value where viridian=1 is used creates a HAL MEMORY ALLOCATION
stopcode when trying to boot Windows.
--
Steven Haigh
? net...@crc.id.au
On 2019-09-02 11:42, Steven Haigh wrote:
On 2019-08-21 06:57, Andreas Kinzler wrote:
On 20.08.2019 22:38, Andrew Cooper wrote:
On 20/08/2019 21:36, Andreas Kinzler wrote:
On 20.08.2019 20:12, Andrew Cooper wrote:
Xen version 4.10.2. dom0 kernel 4.13.16. The BIOS version is
unchanged
from
: 4.11.2
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
Is there any further info that can be provided? Not being able to
virtualise Windows is a bit of a PITA...
--
Steven Haigh
? net...@crc.id.au ? http:
Just wanted to give this a quick followup... Did this end up
progressing?
On Fri, Aug 16, 2019 at 3:37 PM, Steven Haigh wrote:
On 2019-08-16 15:25, Steven Haigh wrote:
On 2019-08-16 05:05, YOUNG, MICHAEL A. wrote:
On Thu, 15 Aug 2019, Steven Haigh wrote:
Having a bit of a look here
On 2019-08-16 15:25, Steven Haigh wrote:
On 2019-08-16 05:05, YOUNG, MICHAEL A. wrote:
On Thu, 15 Aug 2019, Steven Haigh wrote:
Having a bit of a look here
My test system grubenv file has:
# GRUB Environment Block
saved_entry=0
kernelopts=root=UUID=5346b4d9-885f-4673-8aff-04a16bf1971a ro
On 2019-08-16 05:05, YOUNG, MICHAEL A. wrote:
On Thu, 15 Aug 2019, Steven Haigh wrote:
Having a bit of a look here
My test system grubenv file has:
# GRUB Environment Block
saved_entry=0
kernelopts=root=UUID=5346b4d9-885f-4673-8aff-04a16bf1971a ro
rootflags=subvol=root selinux=0 rhgb
-boot-directory=DIR] MENU_ENTRY
MENU_ENTRY
A number, a menu item title or a menu item identifier.
Do I have to use a name for the title to match?
I notice I still have the second option selected with saved_entry=0
--
Steven Haigh
? net...@crc.id.au ? http://www.crc.
ide an if statement in grub.cfg - as the
logic is ignored anyway. Do you still need to read the grubenv in doing
this?
I assume the read for grubenv is to get the 'saved_entry' value?
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +613 9001 6090 📱 +614 12
e decrement boot_counter
else
decrement boot_counter
fi
save_env boot_counter
fi
### END /etc/grub.d/08_fallback_counting ###
It seems pygrub sees the 'set default=1' and uses it - even though it
shouldn't be normally hit due to it being in a conditional.
Steven Haigh
📧 net...@crc.
t became default in
Fedora 30 that cause many problems - but first things first...
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +613 9001 6090 📱 +614 1293 5897
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/gr
start the discussion, with none of this currently being sent
upstream, this is a Fedora-ism. How to handle BLS enabled guests?
It also seems to be a Fedora problem with respect to kernel updates
still causing problems - but that's another issue.
Steven Haigh
📧 net...@crc.id.au 💻 http
On Tue, May 14, 2019 at 11:50 PM, Lars Kurth
wrote:
Apologies,
I mixed up some references
Lars
...
[A2] https://bugzilla.redhat.com/show_bug.cgi?id=1264103
[B1] https://bugzilla.redhat.com/show_bug.cgi?id=1703700
Bug B1 here was lodged by myself. There is also a post to xen-devel
titled
On Tue, May 14, 2019 at 11:40 PM, George Dunlap
wrote:
On Mon, May 13, 2019 at 11:25 AM Steven Haigh
wrote:
There seems to be some changes in Fedora 30 that cause the second
boot
entry in grub.cfg to be booted instead of the first.
This means that Fedora 30 systems either always boot
There seems to be some changes in Fedora 30 that cause the second boot
entry in grub.cfg to be booted instead of the first.
This means that Fedora 30 systems either always boot into an older
kernel, or in the case of systems with only one kernel installed, the
rescue image.
There also seems
(and sending to the list this time due to Geary being rather
featureless mail client)
As one of those being caught by regressions upgrading F29 to F30 under
Xen DomU's, I think this is a bad idea.
It shows that it wasn't tested, because it doesn't work. To me, this
exposes weaknesses in the
On 2018-09-19 19:38, Dario Faggioli wrote:
On Sat, 2018-09-15 at 00:21 +1000, Steven Haigh wrote:
On Friday, 14 September 2018 6:45:35 PM AEST Jan Beulich wrote:
> > > >
> And that's despite "sched=credit2 crashes system when using
> cpupools"? While I agree t
oing stuff that most
people probably wouldn't bother with - evidenced that I hadn't done it before
either.
I take peoples word on the performance +/- of a few percent here and there -
so if its easier to maintain and better code, then yeah - it makes sense to
move on
On Thursday, 13 September 2018 1:11:20 AM AEST Dario Faggioli wrote:
> On Thu, 2018-08-30 at 18:49 +1000, Steven Haigh wrote:
> > On 2018-08-30 18:33, Jan Beulich wrote:
> > > Anyway - as Jürgen says, something for the scheduler
> > > maintainers to look into.
>
0
I've updated the subject - as this isn't a NUMA issue at all.
--
Steven Haigh
? net...@crc.id.au ? http://www.crc.id.au
? +61 (3) 9001 6090? 0412 935 897
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists
On 2018-08-29 15:49, Juergen Gross wrote:
On 29/08/18 07:33, Steven Haigh wrote:
When playing with NUMA support recently, I noticed a host would always
hang
when trying to create a cpupool for the second NUMA node in the
system.
I was using the following commands:
# xl cpupool-create name
*before* attempting to
split the system and print a warning.
This would prevent a hard system freeze in this scenario.
--
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +61 (3) 9001 6090📱 0412 935 897
signature.asc
Description:
binaries exist in the make
build / make install method, and not trying to fix a test as a side effect of
having to use 'make dist'?
> > I'll note that 4.6, 4.7, and 4.10 do not fail in this fashion using almost
> > the same command set to build.
>
> I can't
ir"
(cd xen; make defconfig; sed -i 's/# CONFIG_LIVEPATCH is not set/
CONFIG_LIVEPATCH=y/g' .config; make oldconfig)
export XEN_DOMAIN=xen.crc.id.au
make %{?_smp_mflags} %{?efi_flags} dist
I'll note that 4.6, 4.7, and 4.10 do not fail in this fashion using almost the
same co
STDERR: make[6]: *** [sse2.bin] Error 1
This continues for sse4, sse-avx, sse2-avx, and sse4-avx.
Right now, the code I'm using for this build is:
git clone -n -b staging-4.9 git://xenbits.xen.org/xen.git .
git checkout %{gitid}
pushd tools
git clone -b staging-4.9 git://xenbits.xen.org/qemu-
UILDSTDERR: if ( ret )
BUILDSTDERR: ^
--
Steven Haigh
? net...@crc.id.au ? http://www.crc.id.au
? +61 (3) 9001 6090? 0412 935 897
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
On 2018-07-16 06:40, Jason Long wrote:
Hello.
If Xen Project is a type-1 Hypervisor then why it need an OS for doing
Virtualization?
A quick google search should have pointed you to this:
https://wiki.xenproject.org/wiki/Dom0
--
Steven Haigh
? net...@crc.id.au ? http://www.crc.id.au
nd 'testing' support at 6 (or
less?) months, would this help?
I guess the idea would be that the 'testing' versions are where all the rapid
features are added, which is then 'frozen' into an LTS release at some point
to only get security fixes via point releases (ala
features be more suitable and keep smaller
refinements / additions as point releases?
With a solid base via testing, there's no real reason why a weekly (or daily)
release wouldn't be technically feasible - apart from not having enough
changes to justify it ;)
--
Steven Haig
te the majority of the process?
I could imagine that with a regular release schedule, it could be refined
enough to automatically package the current git branch based on just
committing a tag.
--
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +61 (3) 90
ld probably justify a new release of
4.6, 4.7, 4.8, 4.9, and 4.10 due to the depth of XSAs contained within that
can't be patched on top of the release archive.
Its actually easier to rebuild packages often with just updating version
numbers than do patches to eternity. The kernel packages
and Fedora 28, I figure theres something more
going on here.
Does anyone have a set of recommendations or experiences of running Xen on a
Ryzen CPU?
--
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +61 (3) 9001 6090📱 0412 935 897
signature.asc
Description: This is a
On 2018-05-22 20:52, Steven Haigh wrote:
On Tuesday, 22 May 2018 8:11:38 PM AEST Jan Beulich wrote:
>>> On 18.05.18 at 19:53, wrote:
> Alternative workaround for this would be more frequent point releases by
> default (maybe with ability to delay it very few commits are queued)
ing a new build when we come across
broken patch sets for XSAs (like the current 4.9.1 vs XSAs, and prior 4.10.0
vs XSAs), then I think this part becomes irrelevant.
--
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +61 (3) 9001 6090📱 0412 935 897
signatur
d see this as fine. If it requires many more, I believe it
should trigger an out-of-cycle point release.
--
Steven Haigh
📧 net...@crc.id.au 💻 https://www.crc.id.au
📞 +61 (3) 9001 6090📱 0412 935 897
On Friday, 18 May 2018 8:13:55 PM AEST Lars Kurth wrote:
> Dear Community
On Thursday, 5 April 2018 7:19:15 PM AEST Ian Jackson wrote:
> Steven Haigh writes ("Re: Problem with Xen 4.7.5"):
> > On 2018-04-05 03:22, Ian Jackson wrote:
> > > Apologies for the inconvenience.
>
> ...
>
> > I'm wondering if the severity of th
there are quite a few user systems that have already
grabbed them.
--
Steven Haigh
? net...@crc.id.au ? http://www.crc.id.au
? +61 (3) 9001 6090? 0412 935 897
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenprojec
00 00 e9 d5 fb ff ff <0f>
0b 66 0f 1f 84 00 00 00 00 00 e9 d0 fd ff ff 90 66 2e 0f 1f
[504877.624290] ---[ end trace 62909e6ca83c56bf ]---
Has anyone seen this before or is aware of its cause?
--
Steven Haigh
📧 net...@crc.id.au 💻 http://www.crc.id.au
📞 +61 (3) 9001 6090📱 0
n XSA-255, but it looked like there is a
combination of both ARM & x86 changes in specifically the -2 patch which lead
me to the conclusion that I couldn't just remove one patch to take out the
common and x86 parts.
I figured something was missi
h/arm/mm.c
Hunk #2 FAILED at 1075.
Hunk #3 FAILED at 1090.
2 out of 3 hunks FAILED -- saving rejects to file xen/arch/arm/mm.c.rej
The patches for 4.7, 4.9 and 4.10 seem to apply successfully.
--
Steven Haigh
📧 net...@crc.id.au 💻 http://www.crc.id.au
📞 +61 (3) 9001 6090📱 0412 93
z releases -
from my not so close observations, they seem to be somewhat adhoc.
As always though - more than happy to get feedback / comments on the above.
--
Steven Haigh
📧 net...@crc.id.au 💻 http://www.crc.id.au
📞 +61 (3) 9001 6090📱 0412 935 897
si
On Tuesday, 19 December 2017 10:44:04 PM AEDT George Dunlap wrote:
> On 12/19/2017 10:42 AM, Steven Haigh wrote:
> > On Tuesday, 19 December 2017 7:47:14 PM AEDT Jan Beulich wrote:
> >>>>> On 19.12.17 at 07:58, wrote:
> >>> My proposal addresses t
I'm not sure there are really enough under-the-hood changes to justify a 6
month rapid release cycle.
It adds extra load on the security team, packagers, distro builders etc etc
which could probably be avoided with a sane release cycle.
I would think one release per year + point releases /
ndering if there is
any way without living in TEST MODE for the rest of its life to install the PV
drivers?
--
Steven Haigh
📧 net...@crc.id.au 💻 http://www.crc.id.au
📞 +61 (3) 9001 6090📱 0412 935 897
signature.asc
Description: This is a digitally signed me
DATES IN VERSION 6
>
>
> Yet another new patch, addressing another issue similar to the one
> addressed in v5.
Is there any news / information on what to patch on this for releases that
already have xsa240 included such as 4.9.1 and 4.7.4?
--
Steven Haigh
📧 net...@crc.id.au 💻
71 matches
Mail list logo
