search for: device_model_stubdomain_overrid

Hello all, I hope that it now works and there is no longer problems with my mailsystem. It could be that it already worked but it doesn''t look like because the mail don''t came back from the list. I am trying to setup stubdomains for my running domains on Xen 4.2. I read this wiki articles: http://wiki.xen.org/wiki/StubDom

...ntly set to 256 Block device 252:0 .... --------------------------DomU configuration file------------------------ name = "winxp" #kernel = "/usr/lib/xen/boot/hvmloader" firmware_override = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' #device_model_stubdomain_override = 1 #device_model=''qemu-dm'' #device_model=''stubdom'' #device_model=''stubdom-dm'' #device_model=''qemu-xen'' memory = 3096 vcpus=4 boot=''cd'' disk = [ ''phy:/dev/SSDagility/win_xp,sda,rw'', '&...

The following series flushes my documentation queue and replaces previous postings of those patches. The main difference is that the xl cfg file is now formatted using POD instead of markdown and presented as a manpage. I have setup a cron job to build docs/html and publish it at http://xenbits.xen.org/docs/unstable/ (it''s a bit bare right now). The motivation for some of these patches

This patch set adds XSM security labels to useful debugging output locations, and fixes some assumptions that all interrupts behaved like GSI interrupts (which had useful non-dynamic IDs). It also cleans up the policy build process and adds an example of how to use the user field in the security context. Debug output: [PATCH 01/10] xsm: Add security labels to event-channel dump [PATCH 02/10] xsm: