On Mon, May 24, 2021 at 05:15:25PM +0200, lizbethmutterh...@gmail.com wrote:
> I CSMd the BIOS and so I have the start partition, although every system on
> the 1TB hdd is UEFI (FreeBSD, too). I want to start the hypervisor kernel in
> advance, made a kernel and builtworld but I'm unsure what to
On Sun, May 16, 2021 at 07:17:46PM -0600, Stephen Walker-Weinshenker wrote:
> > > xen_cmdline="dom0_mem=2048M dom0_max_vcpus=1 dom0=pvh com1=115200,8n1
> > > guest_loglvl=all loglvl=all console=vga,com1"
> > Can you try adding 'watchdog' to xen_cmdline and see if that forces
> > the box to reboot
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 frame (len=1518)
>
> They
On Mon, Apr 26, 2021 at 11:41:13AM -0700, Brian Buhrow wrote:
> hello. Occasionally I see messages like the following from my
> FreeBSD-12.2/dom0 machine.
> Is this related to the issue of the NetBSD domu's seeing bursts of oversized
> packets, which I assume
> is caused by packets
On Fri, May 07, 2021 at 05:12:16AM +, Marcin Cieslak wrote:
> I have put FreeBSD-14.0-CURRENT-amd64-20210422-df456a1fcf7-246266.raw.xz
> on an zvol and tried booting it like this:
>
> builder = "hvm"
> name = "current0"
> disk = [
> '/dev/zvol/zroot/current0,raw,xvda,w'
> ]
> boot = "c"
>
On Sun, Apr 25, 2021 at 05:10:44PM -0600, Stephen Walker-Weinshenker wrote:
> On Thu, Apr 22, 2021 at 12:58 AM Roger Pau Monné
> wrote:
>
> > On Wed, Apr 21, 2021 at 08:32:18PM -0600, Stephen Walker-Weinshenker wrote:
> > > Hello Roger:
> > >
> > >
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 using for Xen hosts,
On Wed, Mar 17, 2021 at 04:13:03PM -0700, Brian Buhrow wrote:
> hello Roger. I've successfully compiled the kernel with your patch and
> installed it.
> Now, both the NetBSD-5 and NetBSD-current VM's boot with full working
> networks.
> Also, FreeBSD-12 works as a a pvh guest with full
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 crashes as Xen dom0 with
On Tue, Mar 16, 2021 at 12:06:32AM -0700, Brian Buhrow wrote:
> hello. Following up on this further, it seems there may be a timing
> issue related to this
> after all. If I bring up a NetBSD-5.2 VM, the VM comes up without a problem
> and xennet0 works
> just as it should. I can do
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.
> The documentation
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 same
Hello,
If you are not based on the main or the stable/13 branches you can
skip the email below.
There have been some bootloader changes in main and stable/13 branches
that prevented booting a FreeBSD/Xen PVH Dom0. A fix has been committed
to main and should hopefully be backported to stable/13
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 following errors. To fix
Adding freebsd-xen mailing list for reference.
On Tue, Jan 19, 2021 at 05:04:21PM +0100, Lizbeth Mutterhunt, PhD wrote:
> Op Dienstag, 19. Jänner 2021 15:06:45 CET schreef u:
> > On Fri, Jan 15, 2021 at 3:46 PM Lizbeth Mutterhunt, PhD
> >
> > wrote:
> > > Op Donnerstag, 14. Jänner 2021 09:21:09
On Fri, Jan 15, 2021 at 3:46 PM Lizbeth Mutterhunt, PhD
wrote:
>
> Op Donnerstag, 14. Jänner 2021 09:21:09 CET schreef u:
> > 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
> > >
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.
Hello,
Sorry
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 list
On Wed, Nov 18, 2020 at 11:58:27AM -0800, Brian Buhrow wrote:
> hello Roger. Sorry for the confusion. I've been running NetBSD, or
> trying to, in both PV and HVM modes. Here is a mesage I sent to the
> port-...@netbsd.org mailing list a few days ago, detailing what I found
> with running
On Thu, Nov 12, 2020 at 09:18:59PM -0800, Brian Buhrow wrote:
> hello Roger. thanks for engaging with me on this issue. I think
> I've made progress on the issue and have a better handle on what's going
> wrong. There seem to be a cascade of bugs here, which I'll try to
> enumerate.
>
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's
> post, I updated
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 will not
> boot
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 here so folks
> will
On Fri, Aug 28, 2020 at 08:47:41AM -0700, Brian Buhrow wrote:
> hello. I'm trying to configure an hvm domain with a vnc listener on
> one of the dom0's network addresses, rather than 127.0.0.1.
>
> If I use a line like:
> vfb = [ 'type=vnc,vnc=1,vnclisten=10.14.200.200' ]
type=vnc
On Fri, Feb 14, 2020 at 10:15:48AM -0800, Brian Buhrow wrote:
> hello. Ok. Perhaps I spoke too soon! the domu I was testing with,
> which is an entirely pv guest, performs fine with FreeBSD. However, if I
> take an hvm guest and run that using Intel E1000 emulation, my performance
>
On Thu, Feb 13, 2020 at 06:58:53PM -0800, Brian Buhrow wrote:
> Hello. I'm noticing that network performance on guest VN's whether
> they're pv or hvm is very slow when using FreeBSD-12.0 as dom0 as compared
> with older versions of Xen and NetBSD as dom0. For example,
> I have the
On Tue, Jan 14, 2020 at 12:47:54AM +0200, Stefan Parvu wrote:
> >>
> >> libvirtd, virt-manager: no go.
> >>
> >> * I had to rebuild libvirtd with Xen support
> >>
> >> * got occasional core dumps from libvirt
> >
> > Can you report those? (ie: send the dumps here so they can be analyzed
> >
On Mon, Jan 13, 2020 at 02:51:16PM +0100, Juergen Gotteswinter wrote:
> Am So., 12. Jan. 2020 um 20:07 Uhr schrieb Stefan Parvu <
> spa...@kronometrix.org>:
>
> > >
> > > Also a FreeBSD dom0 can only work in PVH mode, which is faster for
> > > certain operations like page table modifications, but
On Sun, Jan 12, 2020 at 09:07:32PM +0200, Stefan Parvu wrote:
> >
> > Also a FreeBSD dom0 can only work in PVH mode, which is faster for
> > certain operations like page table modifications, but it's slower for
> > others, like issuing hypercalls, when compared to a PV dom0.
> >
> > I don't have
On Sun, Jan 12, 2020 at 09:12:01PM +0200, Stefan Parvu wrote:
> >
> > Okay, so there are some options. Will have a look on virt-manager and cbsd.
>
>
> libvirtd, virt-manager: no go.
>
> * I had to rebuild libvirtd with Xen support
>
> * got occasional core dumps from libvirt
Can you report
On Mon, Jan 06, 2020 at 12:43:51PM +0200, Stefan Parvu wrote:
> Hi,
>
> How Xen hypervisor compares in terms of performance (guest) on FreeBSD vs
> Linux
> , using ZFS or UFS ?
There are several factors to take into account here.
On FreeBSD the hypervisor is built with clang, while on Linux
On Fri, Dec 06, 2019 at 09:33:44AM +0100, 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
On Fri, Nov 08, 2019 at 03:15:40PM +0200, Andriy Gapon wrote:
> On 08/11/2019 11:57, Roger Pau Monné wrote:
> > On Fri, Nov 08, 2019 at 10:19:01AM +0200, Andriy Gapon wrote:
> >>> I found this in Linux code:
> >>> HYPERVISOR_vcpu_op(VCPUOP_send_nmi, xe
On Fri, Nov 08, 2019 at 10:19:01AM +0200, Andriy Gapon wrote:
> On 08/11/2019 10:03, Andriy Gapon wrote:
> > On 07/11/2019 20:08, Andriy Gapon wrote:
> >> For CPUs that do get interrupted I see stack traces like:
> >> cpustop_handler+0x28 ipi_nmi_handler+0x44 xen_cpustophard_handler+0x9
> >>
On Wed, Oct 16, 2019 at 07:10:44PM +0300, Stefan Parvu wrote:
> >
> >> Also, IIRC X58 had some interrupt remapping issues, can you try to
> >> boot with iommu=no-intremap? (without any other iommu options)
> >
>
> here my /boot/loader.conf
>
> root@earth:~ # cat /boot/loader.conf
>
On Wed, Oct 16, 2019 at 06:59:46PM +0300, Stefan Parvu wrote:
> > Also, IIRC X58 had some interrupt remapping issues, can you try to
> > boot with iommu=no-intremap? (without any other iommu options)
>
> Let me try quickly that. No serial it is too complicated for this machine.
>
> If we can
On Wed, Oct 16, 2019 at 06:15:33PM +0300, Stefan Parvu wrote:
> > # acpidump -t|grep DMAR
> > DMAR: Length=180, Revision=1, Checksum=195,
> > OEMID=A M I, OEM Table ID=OEMDMAR, OEM Revision=0x1,
> >
>
> root@earth:~ # acpidump -t | grep DMAR
> DMAR: Length=288, Revision=1, Checksum=93,
>
On Wed, Oct 16, 2019 at 02:07:55PM +0300, Konstantin Belousov wrote:
> On Wed, Oct 16, 2019 at 11:28:23AM +0200, Roger Pau Monné wrote:
> > On Wed, Oct 16, 2019 at 12:17:20PM +0300, Stefan Parvu wrote:
> > > >
> > > > Your box doesn't seem to
On Wed, Oct 16, 2019 at 01:09:11PM +0300, Stefan Parvu wrote:
> thank you guys for tips.
>
> > Are you sure it's VT-d and not VT-x what you have enabled in the BIOS?
>
> Yes, I think the ASUS BIOS had listed VT-d. But will double check tonight.
> But it might be
> that the CPU does not support
On Wed, Oct 16, 2019 at 12:17:20PM +0300, Stefan Parvu wrote:
> >
> > Your box doesn't seem to have an iommu (aka vt-d for Intel).
>
> In BIOS I do have VT-D Enabled option. Would that be broken or not working ?
Are you sure it's VT-d and not VT-x what you have enabled in the BIOS?
Looking at
On Wed, Oct 16, 2019 at 12:07:50PM +0300, Stefan Parvu wrote:
>
> > If your box doesn't have a serial header, you can add noreboot to
> > xen_cmdline and paste a photo of the screen with the panic message,
> > it's not great but at least we would get an idea of what's wrong.
> >
>
> Im not sure
On Wed, Oct 16, 2019 at 11:49:50AM +0300, Stefan Parvu wrote:
> > Can you please provide the full boot log? I'm afraid that I'm not able
> > to provide any suggestions without knowing what went wrong.
>
> In BIOS everything regarding virtualization is turned ON.
>
> How can I provide the full
On Wed, Oct 16, 2019 at 12:12:06AM +0300, Stefan Parvu wrote:
> Hi,
>
> I have a bit of problem, cannot install FreeBSD/Xen on a bit older hardware.
> The hardware
> should support the minimal VT-D/IOMMU settings, required by Xen.
>
> CPU: Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz
On Tue, Oct 15, 2019 at 08:56:22AM -0700, Brian Buhrow wrote:
> hello Roger. Sorry, my bad. I didn't even look at the cause of the
> panic. Rebooting the system caused it to come up clean after another pass
> with fsck. With the ioapic_ack=old argument, the system comes up right
> away
On Mon, Oct 14, 2019 at 02:45:04PM -0700, Brian Buhrow wrote:
> hello. Using: ioapic_ack=old causes the dom0 to crash. Below are the
> logs.
Does the crash happen every time you boot with ioapic_ack=old?
[...]
> dev = gpt/gptroot, block = 1, fs = /
> panic: ffs_blkfree_cg: freeing free
Replying from my phone, sorry for the format.
El ds., 12 d’oct. 2019, 17:32, Brian Buhrow va escriure:
> Hello. Here are the logs with remapping enabled, plus the i, m
> and z
> xen console commands.
> Here's hoping you can provide a fix soon! Or, perhaps, a clue on how to
> fix.
>
On Fri, Oct 11, 2019 at 04:22:32PM -0700, Brian Buhrow wrote:
> hello. Following up on this issue yet again, I'm pretty sure I have
> the hardware discussed in the link below. I tried disabling interrupt
> remapping as the article suggests, but that just makes matters worse. As I
>
On Thu, Oct 10, 2019 at 04:23:10PM -0700, Brian Buhrow wrote:
> hello. I'm trying to get a FreeBSD-12 xen server up and running and
> have run into the issue that i/o seems to be very slow for the dom0, which
> is FreeBSD-12.0-stable, and Xen is xen-4.12.
> I followed the instructions
On Wed, Jul 24, 2019 at 06:49:28PM +, R0me0 *** wrote:
> Roger, I got a machine, I will perform a fresh install and try to
> reproduce the bug. If possible I will send you
I've just committed a fix to xen-kernel yesterday which I think could
solve your issue. Can you update to xen-kernel
Hello,
Could you please try to avoid top-posting.
On Tue, Jul 23, 2019 at 04:07:31PM +, R0me0 *** wrote:
> Sorry, but this host is hosted on another country which I do not have
> access to. ( Hetzner )
>
> So, I think I can't help.
Can you ask them to provide a serial console for you?
On Tue, Jul 23, 2019 at 03:45:49PM +, R0me0 *** wrote:
> Yes the DOM0, the XEN hypervisor completely hangs and the host
> automatically reboots.
You will have to setup a serial console in order to debug then. You
need to find the serial port of your box and hook a null modem [0] to it,
and
On Tue, Jul 23, 2019 at 11:51:51AM +, R0me0 *** wrote:
> I tried to boot kali linux (
> https://cdimage.kali.org/kali-2019.2/kali-linux-2019.2-amd64.iso ) as guest.
>
> The machine freezes on the same way I am using the latest xen 4.12 on
> freebsd
I think I'm confused by this sentence. When
On Mon, Jul 22, 2019 at 11:54:35PM +0900, YAMAMOTO Shigeru wrote:
>
> Hi, all,
>
> I'm using Xen Dom0 on FreeBSD/amd64.
> When following error occurs, I can not create new Xen DomU and I need
> rebooting
> Xen Dom0 to recover from error.
>
> # xl create jenkins-01.cfg
> Parsing config from
On Fri, Jun 28, 2019 at 12:02:37PM +, R0me0 *** wrote:
> Guys,
>
> I'am using FreeBSD 12.0-RELEASE-p6 FreeBSD 12.0-RELEASE-p6 GENERIC amd64
I guess this is on the host?
> When booting systemrescuecd-6.0.3.iso ( http://www.system-rescue-cd.org )
> , my system just hangs and reboot.
So you
On Thu, Jun 27, 2019 at 12:31:35PM +0200, Christian M wrote:
> Den tors 27 juni 2019 kl 12:19 skrev Roger Pau Monné :
>
> > On Thu, Jun 27, 2019 at 12:14:33PM +0200, Christian M wrote:
> > > I've installed 12.0-STABLE on two new VM's now. 172.31.16.127 and .128.
> > V
On Thu, Jun 27, 2019 at 12:14:33PM +0200, Christian M wrote:
> I've installed 12.0-STABLE on two new VM's now. 172.31.16.127 and .128. VIF
> cheksum offloading is turned off, and -txcsum for xn0 for both VM's.
>
> I feel the throughput is more consistent now, not all over the place as
> before,
There's a mistake in my reply below.
On Tue, Jun 25, 2019 at 04:56:43PM +0200, Roger Pau Monné wrote:
> On Tue, Jun 25, 2019 at 01:55:40PM +0200, Christian M wrote:
> > I've made two tests while running tcpdump on the xcp-ng host. I'm not at
> > all qualified to interpret the .
On Fri, Feb 15, 2019 at 07:43:54AM +, Eric Bautsch wrote:
> Hi All
>
>
> And one more:
>
> root@bianca # virsh -V
> Virsh command line tool of libvirt 4.10.0
> See web site at https://libvirt.org/
>
> Compiled with support for:
> Hypervisors: VMware PHYP VirtualBox ESX Bhyve Test
>
Thanks for the testing!
On Fri, Feb 08, 2019 at 07:35:04PM +, Eric Bautsch wrote:
> Hi.
>
>
> Brief abstract: I'm having ZFS/Xen interaction issues with the disks being
> declared unusable by the dom0.
>
>
> The longer bit:
>
> I'm new to FreeBSD, so my apologies for all the stupid
On Wed, Feb 06, 2019 at 09:39:47AM -0800, Rodney W. Grimes wrote:
> > Adding Benedict who wrote the Xen handbook documentation, and
> > hopefully would be able to fix it :).
> >
> > On Tue, Feb 05, 2019 at 08:18:05PM +, Marcin Cieslak wrote:
> > > On Tue, 5 Feb 2019, Eric Bautsch wrote:
> > >
On Wed, Feb 06, 2019 at 11:45:35PM +, Andrew Daugherity wrote:
> > On Feb 6, 2019, at 11:17 AM, Roger Pau Monné wrote:
> >
> > Adding Benedict who wrote the Xen handbook documentation, and
> > hopefully would be able to fix it :).
> >
> > I suggest th
Adding Benedict who wrote the Xen handbook documentation, and
hopefully would be able to fix it :).
On Tue, Feb 05, 2019 at 08:18:05PM +, Marcin Cieslak wrote:
> On Tue, 5 Feb 2019, Eric Bautsch wrote:
>
> > And yes, the qemu-dm-titania.log would have been the place to look. I feel
> >
On Tue, Feb 05, 2019 at 07:17:55AM +, Eric Bautsch wrote:
> Hi.
>
>
> I'm trying to get a Xen domU up and running.
>
> I'm running FreeBSD 12.0. System is a new install.
>
>
> I'm following the instructions here:
>
> https://www.freebsd.org/doc/handbook/virtualization-host-xen.html
>
>
On Sat, Jan 19, 2019 at 10:59:55AM +, Uni Gaia wrote:
> Does anyone know if suspend/resume works for a FreeBSD/Xen dom0 ? domU?
FreeBSD DomU does suspend and resume just fine, or else it's a bug and
should be fixed.
I think FreeBSD Dom0 suspend hasn't been tested (at least I haven't
tested
On Sat, Jan 19, 2019 at 10:59:08AM +, Uni Gaia wrote:
> In https://wiki.xenproject.org/wiki/Xen_Project_Release_Features under
> "Supported Mainline Architectures for the hypervisor (Host)" it is written
> that ARMv7+virt extensions and ARMv8 are supported by Xen.
>
> Is work ongoing in
On Mon, Sep 24, 2018 at 01:52:20PM -0300, R0me0 *** wrote:
> Hello guys,
>
> I have trying to deploy a production enviroment using FreeBSD
>
> If I try to boot Xen with more than 1 vcpu allocated to Dom0, the host
> freezes.
>
> ( also tryied compiled from ports )
>
> any direction will be
On Sat, Aug 25, 2018 at 06:54:54PM +0200, Kai Otto wrote:
> On 13/08/18 19:19, Roger Pau Monné wrote:
> > On Mon, Aug 13, 2018 at 05:24:04PM +0200, Kai Otto wrote:
> >> On 30/07/18 12:19, Roger Pau Monné wrote:
> >>> Packages for Xen 4.11 are now availabl
On Fri, Aug 31, 2018 at 11:12:30PM -0400, Steven Friedrich wrote:
> I can boot a xen kernel, but it appears it doesn't acquire a DHCP address
> from my router.
Does this mean that the box doesn't boot correctly, or just that the
network card is not working when running under Xen?
> Someone
On Sun, Aug 19, 2018 at 10:48:52PM +0200, Marko Zec wrote:
> On Sun, 19 Aug 2018 12:50:55 -0600
> Nathan Friess wrote:
>
> > Hi,
> >
> > While testing out the new PVH support in a domU (which is running
> > great!), I discovered a kernel panic related to xen and vimage
> > support when trying
On Mon, Aug 13, 2018 at 05:24:04PM +0200, Kai Otto wrote:
> On 30/07/18 12:19, Roger Pau Monné wrote:
> > Packages for Xen 4.11 are now available in pkg.
> >
> > Remember that in order to use those you need a very recent FreeBSD
> > kernel (r336475 or newer) and the Xe
On Thu, Jul 19, 2018 at 11:04:44AM +0200, Roger Pau Monné wrote:
[...]
> After introducing PVHv2 PVHv1 was deprecated and PVHv1 has been
> removed from the hypervisor in recent versions, that's why the Xen
> ports package is still stuck with Xen 4.7, because later versions
> removed P
On Sun, Jul 29, 2018 at 06:08:56PM +0530, Pratyush Yadav wrote:
> Hi,
>
> Currently, the grant table free callbacks can not work. This is
> because of a recursion on a non-recursive mutex that causes a kernel
> panic. The cause of the recursion is: check_free_callbacks() is always
> called with
On Thu, Jul 19, 2018 at 12:46:07PM +, Marcin Cieslak wrote:
> On Thu, 19 Jul 2018, Roger Pau Monné wrote:
>
> > Hello,
> >
> > Today I've merged PVHv2 support into FreeBSD, allowing FreeBSD to be
> > used as a PVHv2 DomU and Dom0. While it's not a huge set o
On Thu, Jul 19, 2018 at 02:03:00PM +0200, Miroslav Lachman wrote:
> Roger Pau Monné wrote on 2018/07/19 11:04:
> > Hello,
> >
> > Today I've merged PVHv2 support into FreeBSD, allowing FreeBSD to be
> > used as a PVHv2 DomU and Dom0. While it's not a huge set of c
On Thu, Jul 19, 2018 at 11:42:24AM +0200, Gerd Hafenbrack wrote:
> Hello,
>
> Roger Pau Monné schrieb am Do., 19. Juli 2018, 11:05:
>
> > ... Later on, we sadly discovered
> > that PVHv1 was still too similar to classic PV, and didn't allow Xen
> > to make us
Hello,
Today I've merged PVHv2 support into FreeBSD, allowing FreeBSD to be
used as a PVHv2 DomU and Dom0. While it's not a huge set of changes,
I would *really* appreciate if people could test the code starting
from r336474 (or any later changeset).
I expect there's going to be some confusion
On Mon, Jun 18, 2018 at 06:11:00PM +0530, Pratyush Yadav wrote:
> Hi everyone,
>
> I was looking at gnttab_end_foreign_access_ref() and I notice that
> while gnttab_end_foreign_access_ref() ends the foreign access, it does
> not free the grant reference.
>
> gnttab_end_foreign_access() free the
On Thu, May 24, 2018 at 08:38:30PM +0530, Pratyush Yadav wrote:
> Hi,
>
> On Thu, May 24, 2018 at 7:36 PM, Roger Pau Monné <roger@citrix.com> wrote:
> > On Thu, May 24, 2018 at 05:53:02PM +0530, Pratyush Yadav wrote:
> >> Hi everyone,
> >>
> >&
On Thu, May 24, 2018 at 05:53:02PM +0530, Pratyush Yadav wrote:
> Hi everyone,
>
> I was reading the Xen grant table code and I noticed that some code is
> wrapped in an #if 0. You can see it in sys/xen/gnttab.h:138. I have
> also attached the "commented out" part down below.
>
> Is it useful?
On Wed, May 23, 2018 at 08:27:29PM +0530, Pratyush Yadav wrote:
> Hi,
>
> On Wed, May 23, 2018 at 1:45 PM, Roger Pau Monné <roger@citrix.com> wrote:
> > It's too early for the logs to be stored anywhere. The point where you
> > get the crash is when the APs are s
On Wed, May 23, 2018 at 12:57:59PM +0530, Pratyush Yadav wrote:
> On Mon, May 21, 2018 at 2:33 PM, Roger Pau Monné <roger@citrix.com>
> wrote:
> > Please try to avoid top posting.
>
> Sorry, I didn't know. I Googled top posting just now, and realized it is
>
On Mon, May 21, 2018 at 01:51:13PM -0600, Nathan Friess wrote:
> On 2018-05-19 02:02 AM, Roger Pau Monné wrote:
> > On Thu, May 17, 2018 at 06:10:15PM -0600, Nathan Friess wrote:
> > > I tried the patch on and I my Linux domU did was not able to complete the
> > > attach
Please try to avoid top posting.
On Sat, May 19, 2018 at 03:45:41PM +0530, Pratyush Yadav wrote:
> Hi,
>
> The line is
>
> /usr/src/sys/amd64/amd64/mp_machdep.c:307
Hm, it seems like dbg_stack is not properly allocated. Can you please
try the above debug patch and paste the boot log?
---8<---
On Fri, May 18, 2018 at 05:29:06PM +0530, Pratyush Yadav wrote:
> Hi,
>
> So I have been trying to get Xen to boot on my laptop. It is getting
> stuck with the following error messages:
>
> (XEN) Scrubbing free RAM on 1 nodes using 4 CPUs
> (XEN) [VT-D] DMAR: [DMA Read} Request device
On Thu, May 17, 2018 at 06:10:15PM -0600, Nathan Friess wrote:
> On 2018-05-15 02:08 AM, Roger Pau Monné wrote:
> > On Mon, May 14, 2018 at 08:34:54PM -0600, Nathan Friess wrote:
> > >
> > > I had similar issues with Linux domUs being unable to detect their disks
>
On Tue, May 15, 2018 at 11:37:43AM +0530, Pratyush Yadav wrote:
> On Mon, May 14, 2018 at 11:25 PM, Roger Pau Monné <roger@citrix.com>
> wrote:
> > On Mon, May 14, 2018 at 10:49:43PM +0530, Pratyush Yadav wrote:
> >> I am working on the Xen grant table han
On Tue, May 15, 2018 at 07:06:49AM +, Marcin Cieslak wrote:
> On Tue, 15 May 2018, Pratyush Yadav wrote:
>
> > On Mon, May 14, 2018 at 11:25 PM, Roger Pau Monné <roger@citrix.com>
> > wrote:
> > > Yes, I think you will need to be able to run Xen + FreeB
On Mon, May 14, 2018 at 08:34:54PM -0600, Nathan Friess wrote:
> On 2018-05-14 07:04 AM, Roger Pau Monné wrote:
> > On Sun, May 13, 2018 at 07:33:03PM +0200, Kai Otto wrote:
> > > On 13/05/18 17:16, Roger Pau Monné wrote:
> > > > On Sun, May 13, 2018 at 03
On Mon, May 14, 2018 at 10:49:43PM +0530, Pratyush Yadav wrote:
> On Mon, May 14, 2018 at 10:30 PM, Roger Pau Monné <roger@citrix.com>
> wrote:
> > On Mon, May 14, 2018 at 10:25:21PM +0530, Pratyush Yadav wrote:
> >> Hi,
> >>
> >> I tried ru
On Mon, May 14, 2018 at 10:25:21PM +0530, Pratyush Yadav wrote:
> Hi,
>
> I tried running Xen in a VirtualBox guest and it errors in the boot
> process giving this error:
>
> xenoprof: Initialization failed. Intel processor family 6 model 60 is
> not supported.
> Dom0 has maximum 600 PIRQs
>
>
On Sun, May 13, 2018 at 07:33:03PM +0200, Kai Otto wrote:
> On 13/05/18 17:16, Roger Pau Monné wrote:
> > On Sun, May 13, 2018 at 03:51:36PM +0200, Kai Otto wrote:
> >> Hello,
> >>
> >> I'm trying to set up a FreeBSD 11.1 system as Xen virtualization host.
>
On Sun, May 13, 2018 at 03:51:36PM +0200, Kai Otto wrote:
> Hello,
>
> I'm trying to set up a FreeBSD 11.1 system as Xen virtualization host.
> Following a combination of handbook [1] and wiki [2], I was able to get
> get a FreeBSD dom0 in PVH mode, and FreeBSD domU in HVM mode running,
>
On Sat, Mar 31, 2018 at 07:38:28PM -0700, Rodney W. Grimes wrote:
> > On 03/31/18 18:11, Chris wrote:
> > > On 03/30/18 18:05, Rodney W. Grimes wrote:
> > >
> > >> I can affirm that a E56xx cpu should be very capable of supporting Xen.
> > >> CPU: Intel(R) Xeon(R) CPU X5675 @ 3.07GHz (3059.07-MHz
On Fri, Mar 30, 2018 at 05:43:21PM +, Chris wrote:
> On 03/30/18 12:07, Roger Pau Monné wrote:
> > On Thu, Mar 29, 2018 at 11:32:19PM +, Chris wrote:
> > > I'm having similar problems with xen on 11.1, AMD64, June 2017.
> > > The OS runs fine, but installed xen
On Thu, Mar 29, 2018 at 11:32:19PM +, Chris wrote:
> I'm having similar problems with xen on 11.1, AMD64, June 2017.
> The OS runs fine, but installed xen from package, setup exactly
> as per the handbook and get a kernel panic on two machines,
> complaining about iommu not being enabled.
On Mon, Feb 19, 2018 at 10:42:08AM +, Laurence Pawling wrote:
> >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).
> >
>
On Mon, Feb 19, 2018 at 09:58:30AM +, Laurence Pawling via freebsd-xen
wrote:
> Hi all,
>
>
>
> I’m wondering if anyone here has seen this issue before, I’ve spent the last
> couple of days troubleshooting:
>
>
>
> Platform:
>
> Host: XenServer 7.0 running on 2 x E2660-v4, 256GB RAM
On Wed, Sep 20, 2017 at 11:35:26AM +0100, Karl Pielorz wrote:
>
> Hi All,
>
> We recently experienced an "unplanned storage" fail over on our XenServer
> pool. The pool is 7.1 based (on certified HP kit), and runs a mix of FreeBSD
> (all 10.3 based except for a legacy 9.x VM) - and a few Windows
On Wed, Aug 23, 2017 at 03:49:09PM +0100, Roger Pau Monné wrote:
> On Tue, Aug 22, 2017 at 09:51:47AM -0700, James E. Pace wrote:
> > >> usbdevice=['tablet']
> > >>
> > >
> > This didn't change the behavior; mouse still does not move. Any other
> >
On Tue, Aug 22, 2017 at 09:51:47AM -0700, James E. Pace wrote:
> Thank you for the responses; I appreciate the help.
>
> On Tue, Aug 22, 2017 at 1:11 AM, Roger Pau Monné <roger@citrix.com>
> > wrote:
> >
> >> On Mon, Aug 21, 2017 at 1
1 - 100 of 323 matches
Mail list logo
