Re: [Xen-devel] FreeBSD PVHVM call for testing
On Wed, May 29, 2013 at 07:03:40PM +0200, Roger Pau Monné wrote: Hello, Thanks Matt and Colin for the testing and help! I've pushed yet another version, now it's branch pvhvm_v12, which I *think* should solve the issues with cpuid != acpi_id: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v12 Since I'm not able to reproduce the cpuid != acpi_id case, could you give it a try and report the results? Colin, can you build an AMI with this new kernel? [...] On 28/05/13 23:33, Colin Percival wrote: On a cc2.8xlarge EC2 instance, the lines which come after this are GEOM: new disk xbd1 GEOM: new disk xbd2 GEOM: new disk xbd3 GEOM: new disk xbd4 Trying to mount root from ufs:/dev/ad0a [rw]... start_init: trying /sbin/init and then the userland boot process; have you made any bug fixes after your pvhvm_v7 which would explain why tasting disks was hanging? I'm not sure I follow, did you found a regression from previous branches? i.e. it used to work with branch pvhvm_v6 and not pvhvm_v7? Colin was saying that his local change only moved the boot process a bit farther for cr1.8xlarge. Perhaps some of the other changes you made in the latest pvhvm_v12 branch will get the VM all the way up. --msw ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: [Xen-devel] FreeBSD PVHVM call for testing
On 05/29/13 10:45, Roger Pau Monné wrote: Oh, sure, more changes where needed in order to get it to work, like using acpi_id to map the vcpu_info and perform the cpu bindings. Ah, that explains it. I looked at timer.c for other places where that change was needed but it didn't occur to me that the same problem would exist in other parts of the tree. On 29/05/13 19:22, Matt Wilson wrote: On Wed, May 29, 2013 at 07:03:40PM +0200, Roger Pau Monné wrote: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=shortlog;h=refs/heads/pvhvm_v12 Colin, can you build an AMI with this new kernel? Done, ami-95177dfc in us-east-1. This is now booting successfully on cr1.8xlarge; are there any other instance types I should test? I don't know which Xen versions you have deployed across the entire fleet. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: [Xen-devel] FreeBSD PVHVM call for testing
On Fri, May 24, 2013 at 03:21:54PM -0700, Craig Rodrigues wrote: On Fri, May 24, 2013 at 7:14 AM, Konrad Rzeszutek Wilk konrad.w...@oracle.com wrote: On Thu, May 23, 2013 at 07:41:50PM +0200, Roger Pau Monné wrote: Hello, I've pushed a new branch, pvhvm_v10 that contains a PV IPI implementation for both amd64 and i386. I've also updated the wiki to point to the pvhvm_v10 branch: I feel a bit stupid to ask this, but how I install 'gmake'? Doing 'pkg_add -r gmake' tells me there is no package (perhaps I am using a too modern version of FreeBSD (FreeBSD-10.0-CURRENT-amd64-20130512-r250582-release.iso)? The Wiki mentions how to install git but that fails b/c it can't find gmake. For 10.0-CURRENT, not all the packages are available yet from the main FreeBSD.org ftp site. I am going through a similar setup issue with someone who has signed up for Google Summer of Code, and I need him to use close to the latest 10.0-CURRENT and have a usable system. I wrote this blog post for the student: http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gsoc-work/ Excellent! Thanks for the link. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: [Xen-devel] FreeBSD PVHVM call for testing
On 05/28/13 12:18, Matt Wilson wrote: VCPUOP_set_singleshot_timer returns -EINVAL when: 1) the specified vCPU ID is out of range (0 or MAX_VIRT_CPUS) 2) the specified vCPU ID doesn't match the running vCPU. It seems that there is a confusion between the logical vCPU ID and the local APIC physical ID. [...] (XEN) Domain 1 (vcpu#16) VCPUOP_set_singleshot_timer specified vcpuid 1 [...] APIC: CPU 1 has ACPI ID 16 Thanks Matt! Looks like we need to pass our acpi_id to the Xen hypercall instead of our cpuid. Roger, changing the line int cpu = PCPU_GET(cpuid); to int cpu = PCPU_GET(acpi_id); in xentimer_et_start and xentimer_et_stop fixes this panic and gets me slightly further; the following lines are now added to the console output prior to the system appearing to hang: ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 1 vector 48 ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 2 vector 48 ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 3 vector 48 ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 4 vector 48 ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 5 vector 48 ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 6 vector 48 ioapic0: routing intpin 28 (PCI IRQ 28) to lapic 7 vector 48 TSC timecounter discards lower 1 bit(s) Timecounter TSC-low frequency 1300024860 Hz quality -100 WARNING: WITNESS option enabled, expect reduced performance. On a cc2.8xlarge EC2 instance, the lines which come after this are GEOM: new disk xbd1 GEOM: new disk xbd2 GEOM: new disk xbd3 GEOM: new disk xbd4 Trying to mount root from ufs:/dev/ad0a [rw]... start_init: trying /sbin/init and then the userland boot process; have you made any bug fixes after your pvhvm_v7 which would explain why tasting disks was hanging? -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: [Xen-devel] FreeBSD PVHVM call for testing
On Tue, May 28, 2013 at 06:15:00PM +0200, Roger Pau Monné wrote:
On 24/05/13 12:11, Roger Pau Monné wrote:
Thanks for the test, this is what I expected. I'm a little bit out of
ideas since I'm not able to reproduce this on upstream Xen 4.2. Without
knowing what's happening inside the hypervisor it's hard to tell what's
wrong. It would be interesting to try if the same happens with a Linux
PVHVM (not PV) running on the same instance type.
Hello Matt,
Colin has found an issue on the FreeBSD PVHVM port that I haven't been
able to reproduce using open source Xen, even when using the same
version as the one reported by EC2. Is there anyway you could provide
some help debugging this? Without seeing the Xen code that causes
VCPUOP_set_singleshot_timer to return EINVAL it is quite hard to figure
out what's happening inside the hypervisor.
Hi Roger,
VCPUOP_set_singleshot_timer returns -EINVAL when:
1) the specified vCPU ID is out of range (0 or MAX_VIRT_CPUS)
2) the specified vCPU ID doesn't match the running vCPU.
It seems that there is a confusion between the logical vCPU ID and the
local APIC physical ID.
I added some debugging to case 2):
diff --git a/xen/common/domain.c b/xen/common/domain.c
index e728819..e3efb8c 100644
--- a/xen/common/domain.c
+++ b/xen/common/domain.c
@@ -901,7 +901,12 @@ long do_vcpu_op(int cmd, int vcpuid,
XEN_GUEST_HANDLE(void) arg)
struct vcpu_set_singleshot_timer set;
if ( v != current )
+{
+printk(Domain %d (vcpu#%d) VCPUOP_set_singleshot_timer specified
vcpuid %d\n,
+ d-domain_id, current-vcpu_id, vcpuid);
+
return -EINVAL;
+}
if ( copy_from_guest(set, arg, 1) )
return -EFAULT;
The output from booting ami-e75c358e on a cr1.8xlarge:
(XEN) Domain 1 (vcpu#16) VCPUOP_set_singleshot_timer specified vcpuid 1
(XEN) Domain 1 (vcpu#7) VCPUOP_set_singleshot_timer specified vcpuid 14
(XEN) Domain 1 (vcpu#23) VCPUOP_set_singleshot_timer specified vcpuid 15
(XEN) Domain 1 (vcpu#11) VCPUOP_set_singleshot_timer specified vcpuid 22
(XEN) Domain 1 (vcpu#27) VCPUOP_set_singleshot_timer specified vcpuid 23
(XEN) Domain 1 (vcpu#18) VCPUOP_set_singleshot_timer specified vcpuid 5
(XEN) Domain 1 (vcpu#2) VCPUOP_set_singleshot_timer specified vcpuid 4
(XEN) Domain 1 (vcpu#9) VCPUOP_set_singleshot_timer specified vcpuid 18
(XEN) Domain 1 (vcpu#25) VCPUOP_set_singleshot_timer specified vcpuid 19
(XEN) Domain 1 (vcpu#1) VCPUOP_set_singleshot_timer specified vcpuid 2
(XEN) Domain 1 (vcpu#6) VCPUOP_set_singleshot_timer specified vcpuid 12
(XEN) Domain 1 (vcpu#22) VCPUOP_set_singleshot_timer specified vcpuid 13
(XEN) Domain 1 (vcpu#26) VCPUOP_set_singleshot_timer specified vcpuid 21
(XEN) Domain 1 (vcpu#10) VCPUOP_set_singleshot_timer specified vcpuid 20
(XEN) Domain 1 (vcpu#14) VCPUOP_set_singleshot_timer specified vcpuid 28
(XEN) Domain 1 (vcpu#30) VCPUOP_set_singleshot_timer specified vcpuid 29
(XEN) Domain 1 (vcpu#3) VCPUOP_set_singleshot_timer specified vcpuid 6
(XEN) Domain 1 (vcpu#19) VCPUOP_set_singleshot_timer specified vcpuid 7
(XEN) Domain 1 (vcpu#12) VCPUOP_set_singleshot_timer specified vcpuid 24
(XEN) Domain 1 (vcpu#28) VCPUOP_set_singleshot_timer specified vcpuid 25
(XEN) Domain 1 (vcpu#5) VCPUOP_set_singleshot_timer specified vcpuid 10
(XEN) Domain 1 (vcpu#21) VCPUOP_set_singleshot_timer specified vcpuid 11
(XEN) Domain 1 (vcpu#24) VCPUOP_set_singleshot_timer specified vcpuid 17
(XEN) Domain 1 (vcpu#8) VCPUOP_set_singleshot_timer specified vcpuid 16
(XEN) Domain 1 (vcpu#17) VCPUOP_set_singleshot_timer specified vcpuid 3
(XEN) Domain 1 (vcpu#20) VCPUOP_set_singleshot_timer specified vcpuid 9
(XEN) Domain 1 (vcpu#4) VCPUOP_set_singleshot_timer specified vcpuid 8
(XEN) Domain 1 (vcpu#13) VCPUOP_set_singleshot_timer specified vcpuid 26
(XEN) Domain 1 (vcpu#29) VCPUOP_set_singleshot_timer specified vcpuid 27
(XEN) Domain 1 (vcpu#15) VCPUOP_set_singleshot_timer specified vcpuid 30
Note from the FreeBSD boot output:
APIC: CPU 0 has ACPI ID 0
APIC: CPU 1 has ACPI ID 16
APIC: CPU 2 has ACPI ID 1
APIC: CPU 3 has ACPI ID 17
APIC: CPU 4 has ACPI ID 2
APIC: CPU 5 has ACPI ID 18
APIC: CPU 6 has ACPI ID 3
APIC: CPU 7 has ACPI ID 19
APIC: CPU 8 has ACPI ID 4
APIC: CPU 9 has ACPI ID 20
APIC: CPU 10 has ACPI ID 5
APIC: CPU 11 has ACPI ID 21
APIC: CPU 12 has ACPI ID 6
APIC: CPU 13 has ACPI ID 22
APIC: CPU 14 has ACPI ID 7
APIC: CPU 15 has ACPI ID 23
APIC: CPU 16 has ACPI ID 8
APIC: CPU 17 has ACPI ID 24
APIC: CPU 18 has ACPI ID 9
APIC: CPU 19 has ACPI ID 25
APIC: CPU 20 has ACPI ID 10
APIC: CPU 21 has ACPI ID 26
APIC: CPU 22 has ACPI ID 11
APIC: CPU 23 has ACPI ID 27
APIC: CPU 24 has ACPI ID 12
APIC: CPU 25 has ACPI ID 28
APIC: CPU 26 has ACPI ID 13
APIC: CPU 27 has ACPI ID 29
APIC: CPU 28 has ACPI ID 14
APIC: CPU 29 has ACPI ID 30
APIC: CPU 30 has ACPI ID 15
APIC: CPU 31 has ACPI ID 31
--msw
___
Re: [Xen-devel] FreeBSD PVHVM call for testing
On Thu, May 23, 2013 at 07:41:50PM +0200, Roger Pau Monné wrote: Hello, I've pushed a new branch, pvhvm_v10 that contains a PV IPI implementation for both amd64 and i386. I've also updated the wiki to point to the pvhvm_v10 branch: I feel a bit stupid to ask this, but how I install 'gmake'? Doing 'pkg_add -r gmake' tells me there is no package (perhaps I am using a too modern version of FreeBSD (FreeBSD-10.0-CURRENT-amd64-20130512-r250582-release.iso)? The Wiki mentions how to install git but that fails b/c it can't find gmake. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: [Xen-devel] FreeBSD PVHVM call for testing
On Fri, May 24, 2013 at 10:14 AM, Konrad Rzeszutek Wilk konrad.w...@oracle.com wrote: On Thu, May 23, 2013 at 07:41:50PM +0200, Roger Pau Monné wrote: Hello, I've pushed a new branch, pvhvm_v10 that contains a PV IPI implementation for both amd64 and i386. I've also updated the wiki to point to the pvhvm_v10 branch: I feel a bit stupid to ask this, but how I install 'gmake'? Doing 'pkg_add -r gmake' tells me there is no package (perhaps I am using a too modern version of FreeBSD (FreeBSD-10.0-CURRENT-amd64-20130512-r250582-release.iso)? The Wiki mentions how to install git but that fails b/c it can't find gmake. on 10-CURRENT you need to use pkg or build from ports/devel/gmake ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: [Xen-devel] FreeBSD PVHVM call for testing
On 24/05/13 16:14, Konrad Rzeszutek Wilk wrote: On Thu, May 23, 2013 at 07:41:50PM +0200, Roger Pau Monné wrote: Hello, I've pushed a new branch, pvhvm_v10 that contains a PV IPI implementation for both amd64 and i386. I've also updated the wiki to point to the pvhvm_v10 branch: I feel a bit stupid to ask this, but how I install 'gmake'? Doing 'pkg_add -r gmake' tells me there is no package (perhaps I am using a too modern version of FreeBSD (FreeBSD-10.0-CURRENT-amd64-20130512-r250582-release.iso)? The Wiki mentions how to install git but that fails b/c it can't find gmake. Did you install the ports tree during the installation? If so I've always successfully installed git using: # whereis git # cd output of above command # make install Maybe the ISO you picked as a broken ports snapshot? ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: [Xen-devel] FreeBSD PVHVM call for testing
On 21/05/13 19:40, Konrad Rzeszutek Wilk wrote: On Mon, May 13, 2013 at 08:32:56PM +0200, Roger Pau Monné wrote: Hello, Recently Justin T Gibbs, Will Andrews and myself have been working on improving the Xen support in FreeBSD. The main goal of this was to bring full PVHVM support to FreeBSD, right now FreeBSD is only using PV interfaces for disk and network interfaces when running as a HVM guest. The main benefits of this changes are that Xen virtual interrupts (event channels) are now delivered to the guest using a vector callback injection, that is a per-cpu mechanism that allows each vCPU to have different interrupts assigned, so for example network and disk interrupts are delivered to different vCPUs in order to improve performance. With this changes FreeBSD also uses PV timers when running as an HVM guest, which should provide better time keeping and reduce the virtualization overhead, since emulated timers are no longer used. PV IPIs can also be used inside a HVM guest, but this will be implemented later. Right now the code is in a state where it can be tested by users, so we would like to encourage FreeBSD and Xen users to test it and provide feedback. The code is available in the following git repository, under the branch pvhvm_v5: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary Also, I've created a wiki page that explains how to set up a FreeBSD PVHVM for testing: http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM I tried on my Linux box to do this: HEAD is now at 9b25356... xen-netfront: fix detach of network interfaces konrad@phenom:~/git/freebsd$ make kernel-toolchain make buildkernel KERNCONF=XENHVM make installkernel KERNCONF=XENHVM Makefile:123: *** missing separator. Stop. As I thought it would compile the same way you can compile NetBSD - that is even on non-BSD distros. Is that not the case? Should I only do this under a FreeBSD guest? I have never tried to run the FreeBSD build system under something different than FreeBSD, also keep in mind that installkernel will place a bunch of FreeBSD files on your Linux box if you manage to run it. The error itself can probably be fixed by installing and using BSD make (bmake), but anyway you need a FreeBSD HVM DomU in order to test the kernel, so why not do the compilation on it? ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: [Xen-devel] FreeBSD PVHVM call for testing
On Wed, May 22, 2013 at 01:41:02PM +0200, Roger Pau Monné wrote: On 21/05/13 19:40, Konrad Rzeszutek Wilk wrote: On Mon, May 13, 2013 at 08:32:56PM +0200, Roger Pau Monné wrote: Hello, Recently Justin T Gibbs, Will Andrews and myself have been working on improving the Xen support in FreeBSD. The main goal of this was to bring full PVHVM support to FreeBSD, right now FreeBSD is only using PV interfaces for disk and network interfaces when running as a HVM guest. The main benefits of this changes are that Xen virtual interrupts (event channels) are now delivered to the guest using a vector callback injection, that is a per-cpu mechanism that allows each vCPU to have different interrupts assigned, so for example network and disk interrupts are delivered to different vCPUs in order to improve performance. With this changes FreeBSD also uses PV timers when running as an HVM guest, which should provide better time keeping and reduce the virtualization overhead, since emulated timers are no longer used. PV IPIs can also be used inside a HVM guest, but this will be implemented later. Right now the code is in a state where it can be tested by users, so we would like to encourage FreeBSD and Xen users to test it and provide feedback. The code is available in the following git repository, under the branch pvhvm_v5: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary Also, I've created a wiki page that explains how to set up a FreeBSD PVHVM for testing: http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM I tried on my Linux box to do this: HEAD is now at 9b25356... xen-netfront: fix detach of network interfaces konrad@phenom:~/git/freebsd$ make kernel-toolchain make buildkernel KERNCONF=XENHVM make installkernel KERNCONF=XENHVM Makefile:123: *** missing separator. Stop. As I thought it would compile the same way you can compile NetBSD - that is even on non-BSD distros. Is that not the case? Should I only do this under a FreeBSD guest? I have never tried to run the FreeBSD build system under something different than FreeBSD, also keep in mind that installkernel will place a bunch of FreeBSD files on your Linux box if you manage to run it. The error itself can probably be fixed by installing and using BSD make (bmake), but anyway you need a FreeBSD HVM DomU in order to test the kernel, so why not do the compilation on it? Oh, sure. Just thought that the NetBSD method (which also allows one to build the kernel and the iso) was the same on FreeBSd. Will of course install first the HVM domU and do it again. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: [Xen-devel] FreeBSD PVHVM call for testing
On Mon, May 13, 2013 at 08:32:56PM +0200, Roger Pau Monné wrote: Hello, Recently Justin T Gibbs, Will Andrews and myself have been working on improving the Xen support in FreeBSD. The main goal of this was to bring full PVHVM support to FreeBSD, right now FreeBSD is only using PV interfaces for disk and network interfaces when running as a HVM guest. The main benefits of this changes are that Xen virtual interrupts (event channels) are now delivered to the guest using a vector callback injection, that is a per-cpu mechanism that allows each vCPU to have different interrupts assigned, so for example network and disk interrupts are delivered to different vCPUs in order to improve performance. With this changes FreeBSD also uses PV timers when running as an HVM guest, which should provide better time keeping and reduce the virtualization overhead, since emulated timers are no longer used. PV IPIs can also be used inside a HVM guest, but this will be implemented later. Right now the code is in a state where it can be tested by users, so we would like to encourage FreeBSD and Xen users to test it and provide feedback. The code is available in the following git repository, under the branch pvhvm_v5: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=summary Also, I've created a wiki page that explains how to set up a FreeBSD PVHVM for testing: http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM I tried on my Linux box to do this: HEAD is now at 9b25356... xen-netfront: fix detach of network interfaces konrad@phenom:~/git/freebsd$ make kernel-toolchain make buildkernel KERNCONF=XENHVM make installkernel KERNCONF=XENHVM Makefile:123: *** missing separator. Stop. As I thought it would compile the same way you can compile NetBSD - that is even on non-BSD distros. Is that not the case? Should I only do this under a FreeBSD guest? ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: [Xen-devel] FreeBSD PVHVM call for testing
On Mon, May 13, 2013 at 7:32 PM, Roger Pau Monné roger@citrix.com wrote: Hello, Recently Justin T Gibbs, Will Andrews and myself have been working on improving the Xen support in FreeBSD. The main goal of this was to bring full PVHVM support to FreeBSD, right now FreeBSD is only using PV interfaces for disk and network interfaces when running as a HVM guest. The main benefits of this changes are that Xen virtual interrupts (event channels) are now delivered to the guest using a vector callback injection, that is a per-cpu mechanism that allows each vCPU to have different interrupts assigned, so for example network and disk interrupts are delivered to different vCPUs in order to improve performance. With this changes FreeBSD also uses PV timers when running as an HVM guest, which should provide better time keeping and reduce the virtualization overhead, since emulated timers are no longer used. PV IPIs can also be used inside a HVM guest, but this will be implemented later. Right now the code is in a state where it can be tested by users, so we would like to encourage FreeBSD and Xen users to test it and provide feedback. Is this something we should try to put on the Xen.org blog? -George ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: [Xen-devel] FreeBSD PVHVM call for testing
On mar, 2013-05-14 at 10:19 +0100, George Dunlap wrote: On Mon, May 13, 2013 at 7:32 PM, Roger Pau Monné roger@citrix.com wrote: Hello, Recently Justin T Gibbs, Will Andrews and myself have been working on improving the Xen support in FreeBSD. The main goal of this was to bring full PVHVM support to FreeBSD, right now FreeBSD is only using PV interfaces for disk and network interfaces when running as a HVM guest. [..] Right now the code is in a state where it can be tested by users, so we would like to encourage FreeBSD and Xen users to test it and provide feedback. Cool! :-) Is this something we should try to put on the Xen.org blog? I think it definitely should... Whoever is up to write a blog post about it, please, get in touch to me. Soon we'll have the new mailing lists and all the stuff, but for now, just drop me a line, and I can put the post in the pipeline. Regards, Dario -- This happens because I choose it to happen! (Raistlin Majere) - Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems RD Ltd., Cambridge (UK) signature.asc Description: This is a digitally signed message part
