similar to: xvda vs lvm

Hi All, The following is my domU''s cfg file. # ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ kernel = ''/usr/local/src/xen/vmlinuz'' ramdisk = ''/usr/local/src/xen/initrd.img'' memory = ''256'' name = ''centos5.2'' vif0 = [ ''bridge=xenbr1'' ] disk = [ ''phy:/dev/server/cbox,xvda,w'' ] on_reboot =

Hi! Say I export an LVM logical volume from dom0 as /dev/xvda to the domU: disk = [ ''phy:xenimages/stan,xvda,w'' ] No I can lvresize xenimages/stan in dom0, but the domU stays ignorant of this change. How could I propagate the resize to the domU without rebooting or temporarily breaking its connection to /dev/xvda? Sort of a SCSI rescan, perhaps? -- Thanks, Feri.

centos-virt, I'm trying to create/install domU guests all in "one" step, following Daniel's wiki page (I've found these pages really helpful, BTW): http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU I have a few questions about this process: (1) How would it be modified (w/respect to defining the disk in the domain configuration file) to use a disk layout where dom0

I realize this might be one of those religious topics, but is there any good rule of thumb as to how to setup storage for a Xen domU? Without really knowing any better, I''m basically going to make a disk image of the OS and the create a ''data'' partition on my raid 5 volume for each virtual machine. This is for use at home, so in reality it probably doesn''t

I''ve been using lvm under centos to create the backing store for domUs and although the performance seems acceptable it has some shortcomings. The biggest of which is the LVM bug which prevents me from removing an lv (it says it is still mounted and it definitely isnt). I thought this was just a centos bug but it appears to be evident in debian and ubuntu too and I really can''t

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

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,

You get these if you install Debian Wheezy as HVM and then try to convert to PV. This is Debian bug #603391. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Tested-by: Tril <tril@metapipe.net> --- tools/pygrub/examples/debian-wheezy-hvm.grub2 | 104 +++++++++++++++++++++++++ tools/pygrub/src/GrubConf.py | 6 +- 2 files changed, 109 insertions(+), 1

Hi experts, First I post my log root@intel_5500_server:/> ifconfig eth0 Link encap:Ethernet HWaddr 00:15:17:BB:5E:88 inet addr:128.224.165.205 Bcast:128.224.165.255 Mask:255.255.255.0 inet6 addr: fe80::215:17ff:febb:5e88/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2375 errors:0 dropped:0 overruns:0 frame:0

Hi,All, I installed a guest os with full-virtualization and a local volume as the disk, now becuase of poor performance, I want to change the full-virtualization guest to para-virtualization, so I just changed the config file to boot the guest os with para-virtualization, but it fails to boot. but how can I convert the full-virtualization guest to para-virtualization without reinstall the os,on

Hi all, a newbie question. I''m trying to install lenny guest image (in an img file) on my lenny Dom0 by following the http://wiki.debian.org/Xen: xm create -c xm-debian.cfg install=true install-mirror=ftp://ftp.XX.debian.org/debian i created the xen-lenny-image.img using dd, format is ext3. disk is defined as (cfg file): disk =

Hello, I''m currently trying to understand some problems I had in the past with mixing look-back with blktap(2) for HV and PV domains. I''m stuck reading the source code, so I''d like to get some help from the list. Interrupt me if I got something fundamentally wrong in my understanding so far: 1. With pure-HV the domU gets an emulated IDE (or whatever) disk. The

Hello list. My server: Gentoo 2.6.21-xen dom0 xen-tools 3.2.1 lvm 2.02.28-r2 udev-115-r1 Symptoms: normally I run 4 domUs. About once a week I have a need to restart a domU. Sometimes it works just fine, but other times it does not and I''ll get a message back saying "Error: Device 0 (vif) could not be connected. Hotplug scripts not working". The domU config file has not

Hello all, I''ve been searching through the archives and the internet for a while now, and can''t seem to find anything that helps me out. I hope you don''t my posting this to both xen-users and linux-lvm simultaneously, but i figured it''d help keep the solution in one place... even though it''ll be the same across two places... Anyways: My setup is this:

I''m trying to do what I think would be relatively simple but can''t seem to make it work. Essentially I want to create several domU''s running CentOS each with it''s own LVM partition for increased performance over image files. Initially I did a test with image files and everything went fine, I booted the supplied initrd and vmlinuz images installed CentOS from

Mats, Thanks for your trial; following your mail I tried it with hda; it is the same, it does not work - "fdisk -l" does not show hda. Regards, Ian On 4/2/07, Petersson, Mats <Mats.Petersson@amd.com> wrote: > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ian Brown

Good morning everybody, I get a: Error: Adding extent to vbd failed: device (vbd (uname file:/xen/slackware-linux-10/linu.img) (dev hda1) (mode w)), error 8 What is "error 8"? Where are those error-codes listed? My linux.conf: kernel="/xen/slackware-linux-10/vmlinuz-install" # <- the one from Xen memory=64 name="Linux" # <- is it right that this cannot have

I''ve been running any number of CentOS 4 based Xen hosts and guests using CentOS 4.4, and the Xen RPM''s from www.xensource.com, and various hand-built OS images using jailtime and my own own OS images. I like the jailtime approach: One partition for / on the DomU, /dev/sda1, built as a local file or local LVM partition One partiton for swap on the DomU, /dev/sda2,

Dear Xen users! In case you were struggling with recent version of th gplpv drivers, I''ve possibly found an LVM related bug in it, and reported to James Harper. Thats''s the point: I''ve tested the mentioned version of your driver on top of 32bit xen-3.2.1 32bit xen-3.3.0 and 64bit xen xen-3.3.0 hypervisors, dom0 was always an appropriate version of a 32bit PAE kernel,