similar to: Windows PV & Shutdown-Usage

Hey folks, this is my first contact to XEN-users list. So please be patient if I missed something. I''ve searched a lot before writing this email. My problem: I do have a non-VT/Pacifica box (an old IBM Laptop). There I''ve got already Xen installed (Dom0, 2.6.18-xen0). Now I''ve tried to use the newest vanilla kernel from Kernel.org (at this time: 2.6.23-rc8). As commonly

I do recieve this error when building xen-unstable tree. gcc -O2 -fomit-frame-pointer -m32 -march=i686 -DNDEBUG -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -DVMXASSIST -nostdinc -fno-builtin -fno-common -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/home/xen-unstable.hg/xen/include

Hi, I''ve recently started using the GPL PV Drivers (0.9.10) for a pair of test machines, one XP and one 2003. XP works beautifully: Thank you for the development efforts. 2003 works almost as well, with one exception. When I either xm reboot or xm shutdown and subsequently restart the virtual machine, at first login I get this dialogue: The system has restarted after an unplanned

Greetings, I would like to know how one can identify if a DomU is PV or HVM? Any docs which may indicate a way to find out? I have a CentOS 5.5 64bit DomU which might be HVM - how can this DomU can be made PV? Just stop the DomU, and then delete it using Virtual Machine Manager and the create another config file for a PV DomU and use xm new and then xm start? Let''s say I have a config

> Hello James, > > first of all thanks for your effort in writing the PV drivers for Windows. > Shame that there are at least 3 working PV drivers sets from different > vendors > but none open-source. > > I am looking for a solution of graceful shutdown of Windows domains and > found > your drivers. I''m wondering if installing the ShutdownMon service is

Hello, I''m trying to test pv-grub on existing Xen 3.3.1 installation on Debian Etch Dom0. I got the following error: Unexpected error: exceptions.OSError Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File "/usr/sbin/xm", line 10, in ? main.main(sys.argv) File "//usr/lib/python/xen/xm/main.py", line 2884, in main

Following a Xen tutorial but can''t get the VM (PV Squeeze) running. After doing: # xm create -c /etc/xen/tutorial-pv-guest.cfg The prompt just sits there. Opening another terminal: # xm list /usr/lib/python2.7/dist-packages Name ID Mem VCPUs State Time(s) Domain-0 0 7199 4 r----- 40.6

The following patch adds a section for SHUTDOWN OPTIONS for the xmdomain.cfg man page. It documents the new set of options introduced over the last few weeks. Signed-off-by: Sean Dague <sean@dague.net> Diffstat output: xmdomain.cfg.pod.5 | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 51 insertions(+) diff -r 8cc7ce549d00 docs/man/xmdomain.cfg.pod.5 ---

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19

Hi, how can I install a openSuSE 10.3 PV-guest on a LVM-drive of a openSuSE 10.3 host with Xen 3.10? On 10.2 with Xen 3.0.3 the openSuSE-YaST-module for managing VMs could install the system also on block-devices, unfortunately this is not possible anymore with OSS 10.3 :-( What I have tried: - I created two LVM-partitions, one for "/" one for swap. - Installing an OSS 10.2 PV-guest

I am having problem in guest creation for a pv-ops Dom0 kernel I compiled every thing from scratch.(Xen and 2.6.32.27 pv-ops dom0 kernel) on a Ubuntu Desktop 10.04 64 bit. Following is my config file for 2.6.32.27 http://pastebin.com/AvSVgVQE and the error I am getting trying to create a guest with virt-install is ERROR unable to connect to 'localhost:8000': Connection refused

Hi All, I sent the patch to make blktap work with PV-on-HVM. I corrected the part that had been pointed out in the Xen community. ・All xvdN disk is looked like hdN. ・All tap disks are checked.(tap:aio, tap:sync, tap:vmdk, etc.) We cannot use blktap for the volume of the system with PV-on-HVM and are embarrassed. Could you apply this patch? Or, please give the comment to me. Signed-off-by:

I''ve been trying to compare memory access speed between bare-metal, xen-pv and xen-pvhvm (hvm with pv drivers). In all 3 setups I''m running the same kernel (3.6.6), built with support for xen, on a 64 core AMD Opteron 6378. The output of xm info (relevant parts): machine : x86_64 nr_cpus : 64 nr_nodes : 8 cores_per_socket : 16

docs/man/xl.pod.1 | 6 +++++- tools/libxl/xl_cmdimpl.c | 39 ++++++++++++++++++++++++++++++++++++--- tools/libxl/xl_cmdtable.c | 3 ++- 3 files changed, 43 insertions(+), 5 deletions(-) xl: Introduce shutdown xm compatibility option -a to shutdown all domains Signed-off-by: Sander Eikelenboom <linux@eikelenboom.it> diff -r 9dc729b75595 -r 67f9ef649937 docs/man/xl.pod.1 ---

In current xend, we can not assign co-assignment devices to different guests, even for pv guests. This patch loosens the policy for pv guest: if none of the co-assignment devices have been assigned to hvm guest, we can assign the devices to different pv guests. The patch also adds a detection: if a device has been assigned to guest, we can't try to "xm pci-attach" it to the same

I have an intel 82576GB SR-IOV network card, and I''m trying to pass a function through to a PV domU. Things seem to be going right, but the function I pass through never shows up in an lspci on the domU. I''m successfully hiding the function in dom0, and it shows up in "xm pci-list-assignable-devices" I''ve tried assigning the function to my domU using both the

This patch adds the necessary KVM specific code to allow KVM to support the sleeping and CPU kicking operations needed by the queue spinlock PV code. Two KVM guests of 20 CPU cores (2 nodes) were created for performance testing. With only one KVM guest powered on (no overcommit), the disk workload of the AIM7 benchmark was run on both ext4 and xfs RAM disks at 3000 users on a 3.14-rc6 based

Hey guys, what I am trying to do is a chainload into grub2 installation in a DomU. So far I determined, PV-GRUB does not understand grub2''s grub.cfg notation. So I created a dummy menu.lst which has the needed root kernel and initrd rows and then referenced this to the DomUs config. The main intention to do this, is to be able to use kernel upgrades without touching the menu.lst for

Good Evenight I try to do working usb''s into domU xen guest, SO of xen server is Debian Squenze 6.0, into HVM guest usb works and can make use but with ParaVirtual guest PV can find this devices with lsusb or into /dev/ directory. Kernel load into xend and guest is the same and is the kernel provided by this package: ii linux-image-2.6.32-5-xen-amd64 2.6.32-35