Hi,
I've just successfully run FreeBSD 9.1 based guest with 'pvhvm_v8' based kernel
under Xen 3.4.4.
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
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
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
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)
)
)
)
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 r...@yurak1.vm:/usr/obj/data/freebsd/sys/XENHVM amd64
I'll also set up one (hope will have some time) under Xen 4.2.2 tomorrow.
---
Yura
On May 13, 2013, at 21: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.
>
> 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
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe, send any mail to "freebsd-xen-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"
