similar to: [PATCH] stubdom: add example config file

stubdom: rename the ioemu-dm domain config file to domainname-dm, which is shorter, makes more sense, and sorts better. diff -r c9b516a77927 stubdom/README --- a/stubdom/README Mon Aug 04 11:29:45 2008 +0100 +++ b/stubdom/README Mon Aug 04 12:51:31 2008 +0100 @@ -10,6 +10,9 @@ of video memory for the HVM domain, you of video memory for the HVM domain, you need to avoid the need for ballooning,

Hello I have trouble with Quard Core Opteron and windows 2008(x86). By the way Windows device manager show 4 processors, BUT task manager show only one core. I found that my problem is not new. But solutions, provided by those people did not helped me. By the way, my windows is enterprise version, and as far as I know, it allows up to 8 processor sockets, so the trouble is not, that windows

Hi, I have been trying to get Hyperthreading to work in a Windows HVM on Xen 4.1.2 as described in ''xmexample.hvm''. I think I have set it up correctly, but I can''t seem to get it to work. There is not much documentation on it and most topics are from years ago. I''m curious to know to whether this functionality is still supposed to work. I''m aware that

I am updating this patch to use the tools/ioemu-dir symlink as qemu source directory in case CONFIG_QEMU != ioemu. Before we were trying to figure out where is the actual qemu source dir again. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> --- diff -r f5e72cbfbb17 stubdom/Makefile --- a/stubdom/Makefile Wed Sep 10 11:26:16 2008 +0100 +++ b/stubdom/Makefile Thu Sep

Having fs-backend running in background, tried to start:- root@ServerXen331:/etc/xen# cat f10.hvm-stubdom kernel = "/usr/lib/xen/boot/hvmloader" builder="hvm" memory = 1024 name = "f10.hvm" disk = [ ''phy:/dev/sdb11,hda,w'', ''phy:/dev/loop0,hdc:cdrom,r'' ] vif = [ ''type=ioemu, bridge=eth0'' ] device_model =

yes, the cause of BSOD 0x101 is that watchdog time interrupt was not received by the vcpu in a certain timeout in Windows kernel . this is taken place especially in vista kernel. Generally speaking, we have some ways to fix this, one is that we an write a programme whitch can intercept the trigger of BSOD 0x101, on the other word, we make kernel don''t care the watchdog time interrrupt.

Hello, I don''t have a Vt-x machine on which I can test and see; I have a question regarding running qemu on Vt-x xen machines. xen-unstable has a config file example: dist/install/etc/xen/xmexample.hvm In this file we have the follwoing line: device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' The use manual says about the device_model:

Hi all, I recently upgraded my Xen 3.2.1 to 3.3.1 on Centos 5.2. Everything seems to have gone pretty smoothly except I have a few issues. My system specs are: 4GB RAM Q6600 quad core Intel CPU P5E-VM DO Q35 Intel mobo (VT-d enabled) Skystar2 DVB PCI card passed through to HVM DomU HVM Windows XP SP3 DomU 1. When I restart my DomU, it shuts down and turns into Domain-Unnamed but

I test stubdom in xen-3.3.1, when I start it, just see the message bellow using "xm li" . It seems stubdom haven''t start. Name ID Mem VCPUs State Time(s) Domain-0 0 964 2 r----- 34.8 hvmachine 1 1024 1 ------ 0.0 the two config

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: 1. I use default vnclisten. Does it matter? 2. Seems qemu

parent: 24691:3432abcf9380 tip Fix x86_32 build branch: default commit: 4 modified, 1439 unknown update: (current) /usr/src/xen-4.2/stubdom/ioemu/block-vbd.c: In function âqemu_aio_waitâ: /usr/src/xen-4.2/stubdom/ioemu/block-vbd.c:147:20: error: macro "remove_waiter" requires 2 arguments, but only 1 given /usr/src/xen-4.2/stubdom/ioemu/block-vbd.c:147:5: error: âremove_waiterâ

stubdom: fix build dependency newlib now depends on mini-os header links diff -r 4c2d9a4d11f2 stubdom/Makefile --- a/stubdom/Makefile Fri Jul 18 13:58:29 2008 +0100 +++ b/stubdom/Makefile Fri Jul 18 14:19:52 2008 +0100 @@ -86,7 +86,7 @@ NEWLIB_STAMPFILE=$(CROSS_ROOT)/$(GNU_TARGET_ARCH)-xen-elf/lib/libc.a .PHONY: cross-newlib cross-newlib: $(NEWLIB_STAMPFILE) -$(NEWLIB_STAMPFILE):

stubdom: do not build tapdisk as it it not supposed to build and we don''t need it Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 4024164e7572 stubdom/Makefile --- a/stubdom/Makefile Tue Jul 08 16:11:49 2008 +0100 +++ b/stubdom/Makefile Tue Jul 08 17:12:38 2008 +0100 @@ -190,7 +190,7 @@ [ -f ioemu/config-host.mak ] || \ ( cd ioemu ; \

Hi, all I am new to xen, and just try to use the HVM feature of xen3.1. two issues i met: 1. fedora 7 guest can not boot grub is displaying the boot menu, but hang there. and from "xm top", seems the guest exhauses all the cpu. 2. sdl doesn''t work, i always need to use vnc client to connect to the console here are some info about my system. * cat /proc/cpuinfo * cat xm.hvm (my

stubdom: prevent newlib from emiting cli/sti in longjmp Also fix build dependencies and cleanup. Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r b320cfe1f10f stubdom/Makefile --- a/stubdom/Makefile Thu Jun 05 13:04:07 2008 +0100 +++ b/stubdom/Makefile Fri Jun 06 16:00:35 2008 +0100 @@ -23,9 +23,11 @@ ifeq ($(GNU_TARGET_ARCH), i686) TARGET_CFLAGS=

Hi there, Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2. My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,

Hi there, Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2. My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,

Signed-off-by: Matthew Fioravante <matthew.fioravante@jhuapl.edu> --- stubdom/configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/stubdom/configure.ac b/stubdom/configure.ac index db44d4a..384a94a 100644 --- a/stubdom/configure.ac +++ b/stubdom/configure.ac @@ -18,7 +18,7 @@ m4_include([../m4/depends.m4]) # Enable/disable stub domains

Hi folks, i have a problem to boot an Ubuntu CD in a hvm-enabled machine. I get a black screen when connecting via vnc to the virtual machine. When i change the line cdrom= to some other CD (grml Live CD, Windows CD, other ones) it runs fine. But any Ubuntu CD (kubuntu alternative, ubuntu server, ubuntu desktop) i get the mentioned error. I tried using sdl (no window opens) and with