similar to: HVM direct boot broken in xen-unstable

Before, in my "Hard Problem" email I was trying to communicate a design issue were trying to solve with Xen. This is what we need to do: 1) Deploy 24 Windows XP VMs in parallel. 2) Boot them from a shared Windows XP C: drive. 3) Since this is a read-only shared image we obviously can''t have multiple VM''s writing to it. 4) All writes to the boot image for logging,

Before, in my "Hard Problem" email I was trying to communicate a design issue were trying to solve with Xen. This is what we need to do: 1) Deploy 24 Windows XP VMs in parallel. 2) Boot them from a shared Windows XP C: drive. 3) Since this is a read-only shared image we obviously can''t have multiple VM''s writing to it. 4) All writes to the boot image for logging,

I''ve been doing some merge work between tools/ioemu and qemu upstream. I came across this commit: changeset: 11209:9bb6c1c1890a07885265bbc59f4dbb660312974e date: Sun Aug 20 23:59:34 2006 +0100 files: [...] description: [qemu] hdparm tunable IDE write cache for HVM qemu 0.8.2 has a flush callback to the storage backends, so now it is possible to implement

ioemu-remote: The device model needs to write in the ACPI tables when it wakes up from S3 state. Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com> -- Jean Guyader _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, Attached patch tells the linker where to find libxenctrl.so.3.2, libxenguest.so.3.2 and libxenstore.so.3.0 when launching qemu-dm. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Geschäftsanschrift): Wilschdorfer Landstr.

hi, I just tried the tip of the xen-unstable branch. It looks that the Xen supports 64bit BARs now? Thanks, Neo -- I would remember that if researchers were not ambitious probably today we haven''t the technology we are using! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

As many of us are all too painfully aware we have completely different VNC server implementations for paravirt vs fullyvirt Xen guests. The former based on libvncserver, the latter integrated into QEMU. There are many new and interesting ideas being tried out in the VNC server space in particular wrt to virtualization and having to implement them all twice is not very desirable. Also

I am seeing a problem with the Xen emulated serial console. When running a Linux 2.6.20 HVM guest that has CONFIG_HOTPLUG_CPU=n, the guest blocks on output to the console until it receives input keypresses from `xm console`. This prevents the guest from booting up without banging on some keys, and makes interactive use of the console difficult. By bisecting Linux kernel commits, I found that

# HG changeset patch # User john.levon@sun.com # Date 1196969481 28800 # Node ID 2c28ac4db1f7542220b1472821e8631b79b6a23a # Parent 4a98d4b6e4daccd610175e3c0f8cab49b056c649 Fix ioemu compile serial.c was including another Linux-specific header. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/ioemu/hw/serial.c b/tools/ioemu/hw/serial.c --- a/tools/ioemu/hw/serial.c +++

Hello, it''s not the first time but ... Who know? Well, I use xen in HVM. All works fine, my keyboard in Dom0 is AZERTY, but this keyboard become QWERTY when i enter in VM, it''s not useful to type password. How can i keep my keyboard AZERTY in my VM and in Dom0? -- Benjamin HENRION Elève de 4eme année de l'' EXIA (Nancy) Ecole supérieure d''informatique Spé

The attached patch changes the logfile name generated by qemu-dm to use the pattern qemu-dm-[NAME].log instead of qemu-dm-[PID].log. This makes it easier for the adminsitrator to figure out which log corresponds to which guest (particularly after a crash where you no long know what PID the qemu-dm process for your guest had). It also prevents the number of log files from growing unbounded.

Hi there, i have trouble with Win NT 4 and WIN98 in XEN DomU when i will install. WinNT says on Hardware detect: # i can find graficadapter, install fails, please reboot ... And Win98 starts in shell an says: # no valid cdrom drivers selected .... My install Disks are ISO Files, my Config: disk = [ ''file:/path/windisk.img,ioemu:hda,w'',

Hi Ian, There have been a lot of interest on gfx passthru recently. This patch enables ATI VBIOS in passthru mode. The guest VM system BIOS (including Windows boot logo) can now show in passthru screen. We have tested with various Windows and Linux guest VMs. Please help review it. We are also looking forward to comments and suggestions from Xen community users. Signed-off-by: Wei Huang

The series "HVM firmware passthrough" series in Jan 2013 from Ross Philipson cause two regressions for HVM guests which sadly found their way into the Xen 4.3 release. The first regression causes an incorrect count of tables to be placed in the main header, and can be seen by running dmidecode in any applicable HVM domain. The second regression found its way into the public ABI, making

I have a self built system using an Intel D 920 processor and a MB that supports VT. I''m able to run HVM domains fine, but have trouble getting multiple VCPUs for these domains. Here is an example of one of my configs. # -*- mode: python; -*- #============================================================================ # Python configuration setup for ''xm create''. #

changeset: 9226:7d8efd4f1ac7 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Tue Mar 14 08:18:35 2006 +0100 summary: Initialise blkfront_info to zeroes after allocating it. Hardware: x460 ******************** x86_32(no PAE): *************************** * dom0: SLES9 SP2 * dom0 boots fine * xend starts without problem --- Linux HVM domain status: --- ISSUES: *

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

> Thanks all point about security, I''ll do as follows. > I thought that the point was the following two. > > > 1. Storage place of encrypted password > Should I store it in /etc/xen/passwd ? > Or, should I wait for DB of Xen that will be released in > the future? The xend life cycle management patches were posted by Alistair a couple of months back.

Package: xen-hypervisor-3.0-unstable-1-amd64 Version: 3.0-unstable+hg11561-1 Severity: important The HVM domU won't start. The following is the config (comments stripped). --------------------begin-------------------- import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' kernel =

In spite of reading howtos and this mailing list now for several weeks, I am still not able to get the network of my winXP guest connected to the host (opensuse 10.2) or the external network. There are some network interfaces missing on my host (peth0, vif0.0). ifconfig: eth0 Protokoll:Ethernet Hardware Adresse 00:18:8B:B3:1A:AC inet Adresse:192.168.0.66 Bcast:192.168.0.255