Hi,
my current build (r188436M) ignores external xm commands (on Xen 3.3.1), such as
# xm reboot
# xm shutdown
# xm dump-core -L bsd8
Dumping core of domain: bsd8 ...
Error: Failed to dump core: (1, 'Internal error', 'p2m_size < nr_pages -1 (0 <
3')
# xm save (
irq137: xn)
[thread pid 12 tid 100025 ]
Stopped at xlvbd_add+0x2f70: movl0x900(%edx,%eax,4),%edx
Second System (AMD64, CentOS5.2, Xen 3.3.1):
thru: 0.000ms atinfGB/s ( 598.1kB/s avg) 82.9MB
thru: 0.000ms atinfGB/s ( 599.0kB/s avg) 83.0MB
Fatal trap 12: page f
Hi,
We're playing with FBSD8 (paravirt) for some time now, with these results:
- current CentOS 5.2+ (64bit) with Xen 3.3.1 installed via this XEN repo
(remove CentOS Xen first):
http://www.gitco.de/linux/x86_64/centos/5/rpms/
- self made kernel available from
http://kai.freshx.de/k
usy at the moment, and there are some issues in HEAD related to Xen that I
would like to fix before pushing anything new.
In any case, I see that you are sending the patches using Thunderbird, which is
not ideal (MUAs tend to mangle patches). The preferred way for sending patches
is using "
rate a little bit more on the commit message here? What issues are
you seeing without this patch applied? What is the result after applying the
patch?
Commit messages are very important in order to know why a change is needed,
specially when you look at them in for example 3 years time.
> ---
>
s should I look at? You have sent two emails with patches attached,
and I'm confused about which ones should I review:
https://lists.freebsd.org/pipermail/freebsd-xen/2017-February/002952.html
https://lists.freebsd.org/pipermail/freebsd-xen/2017-February/002957.html
Can you also fix your email
On 2019-12-06 09:33, davidheinrichplanner wrote:
Hi Royger,
i want to inform you by freshports page but i forgett my pw and reset
doesnt work :(.
first one i don't know which one must be informed about this problem
(you or direct xen project, xen team by freebsd?). I have a amd
Hi Royger,
i want to inform you by freshports page but i forgett my pw and reset
doesnt work :(.
first one i don't know which one must be informed about this problem
(you or direct xen project, xen team by freebsd?). I have a amd epyc
system with two cpus. And xen tell me its a unsupp
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
ed to reproduce this at home on Xen 4.4 with Linux 4.7 with small 256M
memory VMs and found while running "periodic daily & periodic weekly":
- With file-backed Swap: behaviour like above
- With block-backed Swap: behaviour like expected (heavy swapping, eventual
success)
- Without S
tic one, for xn0 (and potentially for both ixv and ena, if you
support EC2 Enhanced Networking) was more work that we wanted to undertake
for this.
Jeremiah Lott
Avere Systems
_______
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/
ow.
Unsubscribe here:
https://www.linkedin.com/e/v2?e=mcbmkn-j6ov5319-jk&t=lun&midToken=AQFmrFVhGEd36Q&ek=invite_guest&loid=AQEGfc8BqHpXlgAAAV4OlrQmkzpeIaC0meCMdj-OlDC9QsaSZ2GaBXP7ITQAsqygLF5LqZ4i7YDhx93zuf0Uy5IurpubSUSKmiGRBMflYw&eid=mcbmkn-j6ov5319-jk
This email was sent
st anecdotal. Also, the problem seems by far the most prevalent when
communicating between two VMs on the same host, in the same VLAN. Xen still
sends packets via the switch rather than bridging internally between the
interfaces.
Note that we have not had a chance to investigate the effect of differ
>When using >1 vCPUs can you set hw.xn.num_queues=1 on
>/boot/loader.conf and try to reproduce the issue?
>
>I'm afraid this is rather related to multiqueue (which is only used
>if >1 vCPUs).
>
>Thanks, Roger.
Roger - thanks for your quick reply, this is confirmed. Sett
sharing_freed_memory : 0
sharing_used_memory : 0
outstanding_claims : 0
free_cpus : 0
xen_major : 4
xen_minor : 10
xen_extra : .3_04-lp150.2.1
xen_version : 4.10.3_04-lp150.2.1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p
__
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Am Samstag, 4. Januar 2020, 18:32:26 CET schrieb Stefan Parvu:
> We got a new server, where we plan to install FreeBSD 12.1 amd64 and use
> Xen. Is there anything we could use as GUI management tools for Xen on
> FreeBSD ?
>
> Im looking for some graphical user interface managem
Full equipment invoice #14864
Password for this document: 709384
Best regards,
Christianson Fitzwater
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-uns
Invoicing terminable statement #84691
Regards,
Coffield Iglesias
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
versatility (suitable for all skin types) combined with an affordable price
means that customers make an informed choice of a product among others
available on the market.
Are you interested in cooperation?
William Jones
___
freebsd-xen@freebsd.org mailing list
rozważeniem naszej propozycji, proszę o
informację zwrotną.
Z pozdrowieniami
Aleksandra Musiał
Project Manager
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebs
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
option). It might be useful if you post the full
xl.cfg maybe.
>
> A google search suggests this is somewhat of a known problem, but I
> don't see a patch in the upstream version of xen-tools that addresses it.
> Is there an easy fix for this issue, or perhaps I need to do w
On Fri, Aug 28, 2020 at 02:11:07PM -0700, Brian Buhrow wrote:
> hello Roger. thanks for the quick reply. I think, after a careful
> read of the xl.cfg man page plus a careful reading of the xen-tools source
> code, I've figured out the issue. I'm sending the solution h
along to
> you and this list. If you think it helps, then it could be submitted as an
> upstream patch.
Sure, I would certainly aim to have this upstream, as I don't carry
patches to the Xen packages unless they are backports from upstream
commits.
If you can provide the adjuste
On Sun, Nov 08, 2020 at 11:46:34PM -0800, Brian Buhrow wrote:
> hello. I'm trying to get an installation of FreeBSD-12.1 / xen 4.12
> running an Intel DQ67SW motherboard with 4 8TB disks attached to it up and
> running. Everything seems to work fine, except that the BIOS w
On Wed, Nov 11, 2020 at 01:13:18AM -0800, Brian Buhrow wrote:
> hello. Following up on my own message, I believe I've run into a
> serious problem that exists on FreeBSD-xen with FreeBSD-12.1P10 and
> Xen-4.14.0. Just in case I was running into an old bug with yesterday'
h this behavior, in fact, NetBSD until May
> of 2020, doesn't play well with this behavior
> See:
> http://mail-index.NetBSD.org/source-changes/2020/05/24/msg117668.html
Oh great, so it's something specific to NetBSD. This means you are
running NetBSD in HVM mode?
> 2. Th
> with running NetBSD in any mode under Xen as a domu. Unfortunately, I
> don't think I can provide a trace of a crash to the xen server when the
OK, I'm not really able to reproduce this myself, so if you get those
crashes again can you please make sure you have a serial attac
On Tue, Jan 12, 2021 at 11:12:15AM -0800, Kevin G. Eliuk wrote:
It's kind of hard to tell what's going on without you providing almost
any info, but are you maybe booting using UEFI?
Roger.
___
freebsd-xen@freebsd.org mailing
On Sun, Dec 13, 2020 at 12:11:40AM +0100, lizbethmutterh...@gmail.com wrote:
> to make a long story short: either I get a lock (hard to avoid, not to be
> unlimited with ulimit -l unlimited) or a boot of xen and a blank screen with
> reboot after a 10 seconds with vga=current.
Hell
On Thu, Jan 28, 2021 at 05:11:04PM -0800, Brian Buhrow wrote:
> hello. Recently One of my FreeBSD-xen servers went down hard due to a
> power failure.
> When it came back up, one of the domus' came up, but with no network
> interface. Dmesg
> messages show the follo
Hello,
Since commit 97527e9c4fd37140 on main branch FreeBSD should be able to
boot and work as a Xen dom0 from UEFI.
Booting from UEFI also requires the usage of xen-kernel 4.14.1_1,
previous versions of xen-kernel won't boot correctly under UEFI.
The way to setup the system is exactly the
On Sun, Mar 14, 2021 at 11:30:33PM +0300, Oleg Ginzburg wrote:
> Hi,
>
> I recently tried to use the Xen dom0 through UEFI loader and, finally, it
> worked! (Thanks to Roger).
>
> Now I try to use UEFI boot method in the guest and for some reason, the
> domain does not start
r kernel
sources, recompile and test?
The above fix changes the behavior of FreeBSD netback to only try to
fetch the data when the frontend switches to the Connected state, this
seems to be inline with what Linux netback does, so in any case I
think it's a change worth making.
Thanks, Roger
On Fri, Mar 19, 2021 at 11:59:49PM +, Marcin Cieslak wrote:
> Hello,
>
> I have just upgrade my machine that used to ran 11.x with Xen 4.7.2_9
> as dom0 for a long time.
>
> After upgrade to 12.2-STABLE r369477, runs GENERIC kernel just fine.
>
> Unfortunately it
o look at your other issue also.
Roger.
_______
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
On Wed, Apr 21, 2021 at 08:32:18PM -0600, Stephen Walker-Weinshenker wrote:
> Hello Roger:
>
> Thank you for your work on this. I am new to Xen and FreeBSD but am willing
> to help test this and get it in a release version.
>
> I have 3 Intel NUC 8v5PNK that I am planning on u
ank you for your work on this. I am new to Xen and FreeBSD but am
> > willing
> > > to help test this and get it in a release version.
> > >
> > > I have 3 Intel NUC 8v5PNK that I am planning on using for Xen hosts, but
> > > they can only boot in UEFI mode (
it solves the issue in the domU:
https://cgit.freebsd.org/src/commit/?id=5d8fd932e418f03e98b3469c4088a36f0ef34ffe
I don't think there's any snapshot image with this yet.
> I tried to collect some info but now an attempt to start it seems to bog down
> my Xen h
is caused by packets getting sent from the dom0 to the domu in batches rather
> than one at a
> time, each with an interrupt signal, or, the xen equivalent?
>
> On the domu's I see:
> xennet0: discarding oversize frame (len=1518)
>
> I see the following messages on the dom0,
On Wed, Mar 17, 2021 at 01:23:46AM -0700, Brian Buhrow wrote:
> hello. I've noticed that on my Xen server, running
> FreeBSD-12.2/Xen-4.14.0, I see a lot
> of messages like the following from my NetBSD-5 and NetBSD-current domu's:
> xennet0: discarding oversize fram
r Pau Monné
> > > wrote:
> > >
> > > > On Wed, Apr 21, 2021 at 08:32:18PM -0600, Stephen Walker-Weinshenker
> > wrote:
> > > > > Hello Roger:
> > > > >
> > > > > Thank you for your work on this. I am new to Xen and FreeBSD but am
and see if that forces
> > the box to reboot after it goes black?
> >
> > If Xen is able to boot, and the problem is with FreeBSD dom0 you might
> > try also adding vga=keep to xen_cmdline, that way we might get some
> > output from dom0 (if that's indeed where t
unsure what to do now?
I'm afraid I'm not sure I understand what you want to achieve.
Please note that FreeBSD HEAD supports booting Xen from UEFI now also,
so you are no longer tied to using legacy BIOS.
If you want to boot Xen you need to install the xen-kernel package and
add the xe
46 matches
Mail list logo
