search for: stubdomain

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 http://wiki.xen.org/wiki/Device_Model_Stub_Domains I am able to activate a stubdomain for a normal domain but this domain is so basic in it''s resources (e.g. 32MB RAM) that the normal gue...

Hello all, I have question about the configuration of stubdomains. I read the Wiki articles about that theme and I am able to tell a domain to use stubdomains but this stubdomains are so basically (e.g. 32MB RAM) that the guest isn''t usable. How can I tell the domain/stubdomain which configuration should be used for the stubdomain? And should I use...

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1323432076 0 # Node ID 9c1b223e152eaaa3861f9b6132590de0b4f6cb7e # Parent d8c390192ad1147d7202cf04be090478f1810a5d libxl: fix cold plugged PCI devices with stubdomains Since 23565:72eafe80ebc1 the xenstore entries for the stubdomain''s PCI were never created and therefore the stubdom ends up waiting forever for the devices which it has been asked to insert to show up. Since the stubdomain is already running when we call the libxl_device_pci_add loop in...

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1341397625 -3600 # Node ID 167f013324e854a28fc7637cbb7211fa266dcbc5 # Parent 12011fcfd5cce2a831da3558c59f2c3622e71250 libxl: rename stubdomain when renaming domain. Otherwise after a localhost migrate of an HVM domain with a stubdomain we end up with domains called "FOO" and "FOO--incoming-dm". This because we initially create the domains as "FOO--incoming" and then rename to "FOO" inorder to maint...

Dear all, Firstly I apologise for what may be a fairly simple question, but after spending a few days on this I really need the help of an expert. I''m developing a stubdomain based on Mini-OS and I''m trying to convert the virtual address of a shared memory page to a machine frame number. I would have thought this requires an #include <xen/page.h> library, but it is not available however. I have found instances of page.h in architecture specific directorie...

...effertt posted some patches (http://lists.xensource.com/archives/html/xen-devel/2009-04/msg00696.html) to add this functionallity, but they weren''t applied. So.. having xenstore in separate domain can have other advantages (performance?). Is it (or will be) possible run oxenstroed in stubdomain? -- Łukasz Oleś _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Build stubxenstore only when building stubdomain. Fixes build failure on platforms w/o stubdomain support. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85689 Dornach b. Muenchen Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd Sitz:...

...to a buffer overflow attack. IMPACT ====== A guest which has access to an emulated floppy device can exploit this vulnerability to take over the qemu process elevating its privilege to that of the qemu process. VULNERABLE SYSTEMS ================== All Xen systems running x86 HVM guests without stubdomains are vulnerable to this depending on the specific guest configuration. The default configuration is vulnerable. Guests using either the traditional "qemu-xen" or upstream qemu device models are vulnerable. Guests using a qemu-dm stubdomain to run the device model are only vulnerable to...

Hi, I''m using a custom block script in my xen setup and when started, it creates a new device node pointing to some network resources. Now I noticed that the script is called twice for the root block, the first time for pygrub most likely, but is only stopped once ... I don''t mind creating two devices node, but then I need to destroy both ... Is this a known issue ? Cheers,

...() { kill %1 ( [ -n "$vncpid" ] && kill -9 $vncpid - xm destroy stubdom-$domname + xm destroy $domname-dm xm destroy $domname ) & # We need to exit immediately so as to let xend do the commands above @@ -67,12 +67,12 @@ trap term SIGHUP ############ # stubdomain # Wait for any previous stubdom to terminate -while xm list | grep stubdom-$domname +while xm list | grep $domname-dm do sleep 1 done -creation="xm create -c stubdom-$domname target=$domid memory=32 extra=\"$extra\"" +creation="xm create -c $domname-dm target=$domid...

...be used instead: # virsh start --paused <name> # virsh domid <name> For a domain $DOMID the following command will recursively correct the permissions for the primary PV console: # xenstore-chmod -r /local/domain/$DOMID/console n0 r$DOMID If the domain uses a device model stubdomain then it will also be necessary to fix the permissions for the stubdomain. The stubdomain is named "<name>-dm". Assuming its domain ID is $DMDOM: # xenstore-chmod -r /local/domain/$DMDOM/console n0 r$DMDOM In addition a stub domain has three secondary PV consoles which must be...

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1341839122 -7200 # Node ID 2dd50c201ca0d3542f3589942ae9e51d33ec7509 # Parent 42f76d536b116d2ebad1b6705ae51ecd171d2581 stubdom: fix errors in newlib rpmlint found a few code bugs in newlib, and marks them as errors after rpm build. Add another newlib patch and apply it during stubdom build. I: A function uses a

...s RFC at http://lists.xen.org/archives/html/xen-devel/2012-09/msg00943.html To use it set vif.default.script="vif-openvswitch" in /etc/xen/xl.conf or use script=vif-openvswitch in the vif configuration. Appears to do the right thing for PV and HVM guests (including tap devices) and with stubdomains. In order to support VLAN tagging and trunking the "bridge" specified in the configuration can have a special syntax, that is: BRIDGE_NAME[.VLAN][:TRUNK,TRUNK] e.g. - xenbr0.99 add the VIF to VLAN99 on xenbr0 - xenbr0:99,100,101 add the VIF to xenbr0 as a trunk port receivi...

This patch enables PCI passthrough with stub domain. PCI passthrough with stub domain has failed in the past. The primary reason is that hypercalls from qemu in stub domain are rejected. This patch allows qemu in stub domain to call the hypercalls which is needed for PCI passthrough. For security, if target domain of hypercall is different from that of stub domain, it rejects hypercall. To use

samuel, I have a try with HVM stubdomain on r17062, but failed to make on 32b platform. Attached patch can fix it, but don''t know if okay. After installation, I failed to start stubdom. So I created it manually and got following debug mesg(both HVMdomain and stubdom are created) Can you give some lights on following questions:...

...tches that enable this domain and also add significant stability improvements to the entire vTPM subsystem, including the original method of using vtpmd as a process. Summary of changes: -Major stability fixes to vtpm manager -#define VTPM_STUBDOM for vtpm_managerd to allow it to work with vtpm stubdomains. -hotplug system stability fixes -add #defines to mini-os to disable drivers like pci and net if you don''t want to use them. -generic tpm frontend and backend devices for mini-os -libgmp, polarssl, and tpm_emulator 0.6.1 ported to mini-os using the stubdom makefile structure -vtpm stubd...

...nios, libxenctrl, libxenguest, libxenstore, all built out of the xen tree, - patched grub, - patched newlib and - a libz. - ioemu/dom0 userspace The upstream build uses a clone of the qemu repository with several patches on top. This should be buildable out of the qemu source. - ioemu/stubdomain This also needs several parts: - minios and the libs, - patched qemu, - patched newlib and - patched libpci. Some notes: - Xen upstream hacked newlib to allow (some) libs built against the glibc to work with it. This is used for the unpatched libz. Sure, this is an easy way, but I...

...9;', arch): + arch_libdir = ''lib64'' +else: + arch_libdir = ''lib'' + +kernel = "/usr/" + arch_libdir + "/xen/boot/ioemu-stubdom.gz" + +# Must be the same as in xmexample.hvm-stubdom, with a prepended vif for TCP/IP +# networking in the stubdomain itself, here just '''' +vif = [ '''', ''type=ioemu, bridge=xenbr0'' ] + +# Set here instead of in xmexample.hvm-stubdom +disk = [ ''file:/var/images/min-el3-i386.img,hda,w'', '',hdc:cdrom,r'' ] + +# Actual output via PV...

After syncing to the latest xen-unstable sources, I am getting following compilation error : make[3]: *** No rule to make target `/data/xen-sources/xen-unstable.hg/stubdom/ioemu/i386-stubdom/qemu.a'', needed by `/data/xen-sources/xen-unstable.hg/stubdom/mini-os-x86_32-ioemu/mini-os_app.o''. Stop. make[3]: Leaving directory

...> distro might want to natively ship binary Rumprun images, as opposed to > just the toolchain and components. One concrete example of what I want is a Debian package in the Debian archive which the xen-tools.deb can depend on which provides a qemu rumpkernel binary such that users can use stubdomain functionality for their HVM guests. Debian are (most likely) not going to accept a second copy of the QEMU source in the archive and likewise they wouldn't want a big source package which was "qemu + all its build dependencies" or anything like that, especially when "all its bui...