similar to: [PATCH 0 of 2] Parse image elfnotes, write them to xenstore, save and load via image sxpr

Hi, just upgraded my testsystem to 3.0.4 (using the provided source rpm, xen-3.0.4.1-1.src.rpm, rebuilt it to run on non-PXE but no changes besides that, and it doesn''t look like the 3.0.4-testing HG has major differences so far?) and I have two problems with rebooting domains (xm reboot, or reboot from inside the domain). 1) the kernel-commandline keeps growing. On the first boot

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. The first patch modifies creation of the hvmloader key in xenstore and adds creation of a new read/write hvmloader/generation-id-addr key. The second patch changes hvmloader to use the new key (as

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. The vast majority of the code is in second patch. The first patch merely changes the xenstore key name used by hvmloader to store the buffer address.

To allow xenguest consumers to also make use of the extra protection added as a result of xsa-25. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> diff -r 5af4f2ab06f3 -r daec50a41570 tools/libxc/xenguest.h --- a/tools/libxc/xenguest.h +++ b/tools/libxc/xenguest.h @@ -177,6 +177,13 @@ int xc_dom_linux_build(xc_interface *xch unsigned int console_evtchn, unsigned

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. Patch 1 modifies the guest ro and rw node creation to an open coding style and cleans up some extraneous node creation. Patch 2 modifies creation of the hvmloader key in xenstore and adds

On a 8 Core system only dom0 can set cap > 100 and vcpus > 1. On a domU ''xm sched-credit -d <domU> -c 200'' says "Error: cap is out of range". Vcpu cannot be set higher than 1 - regardless of boot/config/command line. Low performance is equivalent to the cap setting. See ''xm list --long'': (domain (domid 0) (uuid

Hello, I''m trying to get a freebsd virtual machine running following : http://www.yuanjue.net/xen/howto.html But I get : # xm create freebsd_xen_INSTALL -c Using config file "./freebsd_xen_INSTALL". Error: (14, ''Bad address'') Am I missing something? I am using xen 3.0.4. Thanks and regards, Sergi .... log output from xend.log: [2007-02-27 12:46:59

I have built a dom 0 using a Gentoo Linux kernel. All is up and running with no errors. I downloaded a Centos 4.4 image from the web and when I rum xm I get an error 22. Does anyone know what I am doing wrong and/or where I can find more documentation on running unmodified VMX guest domains. The Xen 3.0 Users Manual is out of date. Here is the control file: sun temp # cat

Hi everyone, I generated my own DomU guest using opensuse''s yast dirinstall and stored it on a seperate iscsi target. I created it as a DomU on my Domain0 (2.6.25.16-0.1-xen kernel) successfully, using the following configuration: name = "vm01-opensuse11-base-LAMP" memory = 256 kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root =

The following is a revised patch series to add support for a VM generation ID virtual device for HVM guests. The basic requirements of this device are as follows: - It must be exposed somewhere in ACPI namespace with a _CID of "VM_Gen_Counter". - It must also include a _DDN of "VM_Gen_Counter". - It must contain a _HID object but no particular value is required. - It must

I got latest (13601) yesterday evening. This doesn''t seem to work to do Restore (at least of the Windows test-image that I''ve been using for testing previously). The VM restores reasonably OK, but it jumps to an invalid address shortly after restoring, giving a D1 blue-screen error (DRIVER_IRQL_LESS_OR_EQUAL), which turns out to be "page-fault in driver" after I

Hello, I am trying to see if the hypervisor can be used to detect deadlocks in the guest VMs. My goal is to detect if a guest OS is deadlocked, and if it is, then create a clone of the deadlocked OS without the locking condition, and letting the clone run. While the clone runs I am hoping to generate some hints that could tell me what caused the deadlock. I simulated a deadlock/hang

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -

Hello again, now my xen works. But a strange thing: Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 2514 4 r----- 76.2 vx1 1 256 1 -b---- 6.1 vx2 2 256 1 -b---- 5.8 vx3 3 256 1 -b---- 5.3 vx4

Hi there I get the following error message when i try to "xm create <domid>" Error: Error creating domain: (22, ''Invalid argument'') I have included everything i can think of Thanks The DomU config is kernel = "/boot/vmlinuz-2.6.12-xenU" ramdisk = "/boot/initrd-2.6.12.6-xenU.img" memory = 128 name = "xen01" nics=1 disk = [

Hi, I've just committed ELF notes support to Xen unstable. It should become public once changeset 11239:58b5141c8309 passes through regression testing and into the public tree. The patches which follow update the paravirt tree to define the notes. Some of them should be merged with existing patches others are completely new. I've made a note in the intro to the individual patches. There

There are a bunch of issues with defining elf notes using assembler macros, as described here: http://marc.theaimsgroup.com/?l=linux-kernel&m=115633393226158&w=2 Therefore I replaced it with a pre-processor macro. This is a new patch, it should fit into the series anywhere after the -mm patch. It's been submitted to Andrew M so hopefully it'll get picked up for next -mm.

This patch introduces support for two new parameters in libxl: smbios_firmware=<path_to_smbios_structures_file> acpi_firmware=<path_to_acpi_tables_file> The changes are primarily in the domain building code where the firmware files are read and passed to libxc for loading into the new guest. After the domain building call to libxc, the addresses for the loaded blobs are returned and

Hi folks I deploy a two Dell PowerEdge T300 to test Virtualization with kvm+drbd+heartbaet. The KVM drbd and heartbeat work properly. However, I have doubt!! When the primary node has down, the secondary node start the VM that has original running on primary node... So, this required a full stop of hole system... This is not we wish here... Is there something way to live migrate VM from

Hi all, I have recently installed FC5 along with xen via yum. I''ve successfully rebooted using the dom0 (2.6.16-1.2133_FC5) kernel, started xend, and trying to start my first domU after following the instructions in the user guide. However, I keep receiving a kernel panic and an error about XENBUS timeout. Any help greatly appreciated as I am stumped. Should I be using the provided