search for: xen_init_pv

...g exactly that. First of all I''ve copied tools/xenfb/xenfb.c into the qemu/hw/xenfb.c file. Next I added a qemu/hw/xen.c file to provide the implementation of the QEMU machine type - called ''xenpv''. All the interesting code (all 100 lines of it) is in hw/xen.c in the xen_init_pv method - which is called when using the ''-M xenpv'' command line arg. The first thing this does is get the domain ID - to avoid touching QEMU''s command line args, I just use an environ variable XEN_DOMID to pass this in. The main_loop() in qemu/vl.c assumes there is alw...

...nctions. Then the compiler helped me locate the local variables that are unused, so they could be removed. --- Changes v3 -> v4: - Rebase against latest qemu.git master, solved conflicts at hw/xilinx_zynq.c Changes v2 -> v3: - Fix typo (missing dot) on main() - Fix another mistake on xen_init_pv() Changes v1 -> v2: - Fix mistake on the conversion of pc_xen_hvm_init() and xen_init_pv() hw/alpha_dp264.c | 12 ++-- hw/an5206.c | 8 +-- hw/axis_dev88.c | 9 +-- hw/boards.h | 16 +++-- hw/collie.c |...

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and

When I submitted the qcow2 patch for blktap, suggestions came up that the qemu block drivers should be used also for blktap to eliminate the current code duplication in ioemu and blktap. The attached patch adds support for a tap:ioemu pseudo driver. Devices using this driver won''t use tapdisk (containing the code duplication) any more, but will connect to the qemu-dm of the domain. In