Date: Fri, 24 May 2013 11:34:10 +0300 From: Yuriy Kohut <ykohut@onapp.com> To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com> Cc: "freebsd-xen@freebsd.org" <freebsd-xen@freebsd.org>, xen-devel <xen-devel@lists.xen.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>, "xen-users@lists.xen.org" <xen-users@lists.xen.org> Subject: Re: FreeBSD PVHVM call for testing Message-ID: <F18A7066-4A1C-4A2A-A034-9A2A46985565@onapp.com> In-Reply-To: <7C420745-BAC0-4BD0-AB60-E3BC7F8BA2A7@onapp.com> References: <519131D8.9010307@citrix.com> <7C420745-BAC0-4BD0-AB60-E3BC7F8BA2A7@onapp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
I've just successfully run FreeBSD 9.1 based guest with 'pvhvm_v8' based =
kernel under Xen 4.2.2.
So I couldn't confirm any issue with the kernel both on Xen 3.4.4 and =
4.2.2.
Nice Job.
Hypervisor details:
# xm info
host : ********
release : 3.8.7-1.el6xen
version : #1 SMP Tue Apr 16 13:14:14 EEST 2013
machine : x86_64
nr_cpus : 4
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 1995
hw_caps : =
bfebfbff:28100800:00000000:00003b40:009ce3bd:00000000:00000001:00000000
virt_caps : hvm
total_memory : 16374
free_memory : 7194
free_cpus : 0
xen_major : 4
xen_minor : 2
xen_extra : .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=20
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=3D0xffff800000000000
xen_changeset : unavailable
xen_commandline : dom0_mem=3D409600
cc_compiler : gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3)
cc_compile_by : mockbuild
cc_compile_domain : ********
cc_compile_date : Tue May 7 19:26:49 EST 2013
xend_config_format : 4
DomU details:
# xm list --long f2tbrxodmgk9ng
(domain
(domid 146)
(cpu_weight 400)
(cpu_cap 0)
(pool_name Pool-0)
(bootloader '')
(vcpus 4)
(cpus (() () () ()))
(on_poweroff destroy)
(description '')
(on_crash restart)
(uuid 355cfb26-4793-f85a-e330-7b6bfcae49b5)
(bootloader_args '')
(name f2tbrxodmgk9ng)
(on_reboot restart)
(maxmem 1024)
(memory 1024)
(shadow_memory 12)
(features '')
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1369384081.34)
(cpu_time 59.956655605)
(online_vcpus 4)
(image
(hvm
(kernel '')
(superpages 0)
(videoram 4)
(hpet 0)
(stdvga 0)
(loader /usr/lib/xen/boot/hvmloader)
(xen_platform_pci 1)
(nestedhvm 0)
(rtc_timeoffset 10801)
(pci ())
(hap 1)
(localtime 0)
(timer_mode 1)
(pci_msitranslate 1)
(oos 1)
(apic 1)
(usbdevice tablet)
(vpt_align 1)
(vncunused 1)
(boot cd)
(pae 1)
(viridian 0)
(acpi 1)
(vnc 1)
(nographic 0)
(nomigrate 0)
(usb 0)
(tsc_mode 0)
(guest_os_type default)
(device_model /usr/lib64/xen/bin/qemu-dm)
(pci_power_mgmt 0)
(xauthority /root/.Xauthority)
(isa 0)
(notes (SUSPEND_CANCEL 1))
)
)
(status 2)
(state -b----)
(store_mfn 1044476)
(device
(vif
(bridge nnl9l2z5l3q3d8)
(uuid daeabd68-05a0-f25b-ba65-394627505b50)
(script /etc/xen/scripts/vif-bridge)
(ip 109.123.91.166)
(mac 00:16:3e:e8:88:49)
(vifname qgdvmt5h6d2l9s)
(backend 0)
)
)
(device
(console
(protocol vt100)
(location 7)
(uuid c670a71d-4c3b-1fcb-974a-587f17740a6c)
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 9067929c-9b48-99c6-5526-e771d43f427c)
(bootable 1)
(dev hda:disk)
(uname phy:/dev/fv4zl7t2h5wbeq/o76ciuubu0r986)
(mode w)
(backend 0)
(VDI '')
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 2ae3630e-0e8e-04e4-8caf-ac4d1e9fd402)
(bootable 0)
(dev hdb:disk)
(uname phy:/dev/fv4zl7t2h5wbeq/xi0nw7u4zo0bu9)
(mode w)
(backend 0)
(VDI '')
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 33d3e25c-0c1c-ced6-c8b6-5a706ab0d403)
(bootable 0)
(dev hdc:cdrom)
(uname file:/tools/freebsd/boot-freebsd-generic.iso)
(mode r)
(backend 0)
(VDI '')
)
)
(device
(vfb
(vncunused 1)
(vnc 1)
(uuid 438a2ffd-bec7-1e54-bb0b-4fdd400517cf)
(location 0.0.0.0:5908)
)
)
)
DomU from "inside":
# uname -a
FreeBSD yurak2.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r+03cdadc: Thu =
May 23 18:55:33 AST 2013 root@yurak2.vm:/usr/obj/freebsd/sys/XENHVM =
amd64
---
Yura
On May 22, 2013, at 18:27 PM, Yuriy Kohut <ykohut@onapp.com> wrote:
> Hi,
>=20
> I've just successfully run FreeBSD 9.1 based guest with 'pvhvm_v8' =
based kernel under Xen 3.4.4.
>=20
> Hypervisor details:
> # xm info
> host : *******
> release : 2.6.18-348.2.1.el5xen
> version : #1 SMP Tue Mar 5 17:05:33 EST 2013
> machine : x86_64
> nr_cpus : 4
> nr_nodes : 1
> cores_per_socket : 4
> threads_per_core : 1
> cpu_mhz : 2128
> hw_caps : =
bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000
> virt_caps : hvm
> total_memory : 6135
> free_memory : 262
> node_to_cpu : node0:0-3
> node_to_memory : node0:262
> xen_major : 3
> xen_minor : 4
> xen_extra : .4
> 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=20
> xen_scheduler : credit
> xen_pagesize : 4096
> platform_params : virt_start=3D0xffff800000000000
> xen_changeset : unavailable
> cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)
> cc_compile_by : root
> cc_compile_domain : ******
> cc_compile_date : Wed Sep 5 18:01:10 EEST 2012
> xend_config_format : 4
>=20
>=20
> DomU details:
> # xm list --long h283bpm53f9rnx
> (domain
> (domid 61)
> (on_crash restart)
> (uuid a2cbcba9-1d66-87ce-6d2f-412e70eab051)
> (bootloader_args )
> (vcpus 2)
> (name h283bpm53f9rnx)
> (on_poweroff destroy)
> (on_reboot restart)
> (cpus (() ()))
> (bootloader )
> (maxmem 1024)
> (memory 1024)
> (shadow_memory 10)
> (features )
> (on_xend_start ignore)
> (on_xend_stop ignore)
> (start_time 1369235607.92)
> (cpu_time 31.914003553)
> (online_vcpus 2)
> (image
> (hvm
> (kernel )
> (videoram 4)
> (hpet 0)
> (stdvga 0)
> (loader /usr/lib/xen/boot/hvmloader)
> (vncunused 1)
> (xen_platform_pci 1)
> (boot cd)
> (rtc_timeoffset 7202)
> (pci ())
> (pae 1)
> (vpt_align 1)
> (hap 1)
> (viridian 0)
> (acpi 1)
> (localtime 0)
> (timer_mode 1)
> (vnc 1)
> (nographic 0)
> (guest_os_type default)
> (pci_msitranslate 1)
> (apic 1)
> (monitor 0)
> (usbdevice tablet)
> (device_model /usr/lib64/xen/bin/qemu-dm)
> (pci_power_mgmt 0)
> (usb 0)
> (xauthority /root/.Xauthority)
> (isa 0)
> (notes (SUSPEND_CANCEL 1))
> )
> )
> (status 2)
> (state -b----)
> (store_mfn 1044476)
> (device
> (vif
> (bridge xnh5getjoj54ke)
> (uuid 6133c146-48ea-b7a5-0263-fda98e1a30fe)
> (script /etc/xen/scripts/vif-bridge)
> (ip 83.170.81.183)
> (mac 00:16:3e:a4:02:5a)
> (vifname t2vd5w22msrv5d)
> (backend 0)
> )
> )
> (device
> (vbd
> (protocol x86_64-abi)
> (uuid dd857cd1-2a4c-ea21-a5a5-e95d811f607a)
> (bootable 1)
> (dev hda:disk)
> (uname phy:/dev/9yblt1m70pdtdp/ddfhogyred6bby)
> (mode w)
> (backend 0)
> (bootable 1)
> (VDI )
> )
> )
> (device
> (vbd
> (protocol x86_64-abi)
> (uuid 19cae15c-354d-77cb-57ec-dc313f1d05ba)
> (bootable 0)
> (dev hdb:disk)
> (uname phy:/dev/9yblt1m70pdtdp/dhnnwhs6jh9kdd)
> (mode w)
> (backend 0)
> (bootable 0)
> (VDI )
> )
> )
> (device
> (vbd
> (protocol x86_64-abi)
> (uuid 2b97ec8c-0cc5-7197-f510-63c272449680)
> (bootable 0)
> (dev hdc:disk)
> (uname phy:/dev/9yblt1m70pdtdp/d1jilc7s7jxsaq)
> (mode w)
> (backend 0)
> (bootable 0)
> (VDI )
> )
> )
> (device
> (vbd
> (protocol x86_64-abi)
> (uuid 1b472270-1ef3-2f49-81f1-031cc00c0eb7)
> (bootable 0)
> (dev hdd:cdrom)
> (uname file:/tools/freebsd/boot-freebsd-generic.iso)
> (mode r)
> (backend 0)
> (bootable 0)
> (VDI )
> )
> )
> (device
> (vfb
> (vncunused 1)
> (vnc 1)
> (uuid b3defeea-4acc-1408-9b22-71547a64e705)
> (location 0.0.0.0:5900)
> )
> )
> (device
> (console
> (protocol vt100)
> (location 4)
> (uuid 58a089ce-a4d0-037e-23e8-9df37b2bd5da)
> )
> )
> )
>=20
>=20
> DomU from "inside":
> # uname -a
> FreeBSD yurak1.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r+03cdadc: Wed =
May 22 17:47:40 EEST 2013 =
root@yurak1.vm:/usr/obj/data/freebsd/sys/XENHVM amd64
>=20
>=20
> I'll also set up one (hope will have some time) under Xen 4.2.2 =
tomorrow.
> ---
> Yura
>=20
> On May 13, 2013, at 21:32 PM, Roger Pau Monn=E9 <roger.pau@citrix.com> =
wrote:
>=20
>> Hello,
>>=20
>> 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.
>>=20
>> 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.
>>=20
>> The code is available in the following git repository, under the =
branch
>> pvhvm_v5:
>>=20
>> http://xenbits.xen.org/gitweb/?p=3Dpeople/royger/freebsd.git;a=3Dsummar=
y
>>=20
>> Also, I've created a wiki page that explains how to set up a FreeBSD
>> PVHVM for testing:
>>=20
>> http://wiki.xen.org/wiki/Testing_FreeBSD_PVHVM
>> _______________________________________________
>> freebsd-xen@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
>> To unsubscribe, send any mail to =
"freebsd-xen-unsubscribe@freebsd.org"
>=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F18A7066-4A1C-4A2A-A034-9A2A46985565>