similar to: Mounting filesystems with blktap2

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

Hey Roger, I am seeing this weird behavior when using #linux-next + stable/for-jens-3.8 tree. Basically I can do ''pvscan'' on xvd* disk and quite often I get checksum errors: # pvscan /dev/xvdf PV /dev/xvdf2 VG VolGroup00 lvm2 [18.88 GiB / 0 free] PV /dev/dm-14 VG vg_x86_64-pvhvm lvm2 [4.00 GiB / 68.00 MiB free] PV /dev/dm-12 VG vg_i386-pvhvm lvm2

Hello, I just installed Xen 4.0.1 on Ubuntu 10.04 dom0. After this i had Ubuntu 11.04 as Para domU. I tried to attach file based disk to the this domU. My command is: # xm block-attach Ubuntu-11 file:/root/ubunut-natty/Extra /dev/xvdb w there is no error on this. But inside the DomU i cannot see any disk xvdb. xend.log shows : [2011-10-25 16:27:32 14794] DEBUG

Hi, I have a Xen server running OpenSuSE 10.2, with Xen version 3.0.3_11774. It''s happily hosting two DomU''s running the same OS / kernel. Now I tried to create a new DomU running a newer OS - OpenSuSE 11.1. It comes with Xen version 3.3.1_18494_03. Unfortunately for me, it doesn''t work - this is what I get: > xen1:/etc/xen/vm # xm create NEW > Using config file

I tried to use cdrom in domU linux pv (Linux Mint 11 based on Natty). With ''/mnt/vm/iso/test.iso,raw,xvdb,ro,cdrom'', Mint sees it as internal disk (not cdrom) and only administrators can mount it. I tried also ''/dev/scd0,raw,xvdb,ro,cdrom'' does the same thing. Is possible use cdrom on linux domU pv full working where also normal user can mount it without

I followed the book called "Professional Xen Virtualization" written by William von Hagen,and published by Wiley Publishing,Inc. Here are some configuration files: #cat /xen/ubuntu/ubuntu.xen3.cfg kernel = "/boot/vmlinuz-2.6.18-128.1.16.el5xen" ramdisk = "/boot/initrd-2.6.18-128.1.16.el5xen-no-scsi.img" memory = "512" name = "Ubuntu804" vif =

Hi, I''ve been touring XCP and making my way around it for the last few days, and am having problems with some reasonably straightforward actions. I''ve poured a several hours into different ways of resolving the issue, but am coming up short. Here''s the main issue. The following command (plugging in a VBD to the dom0 VM), when, run, hangs for several minutes, and then

Hello everyone, I just put together a brand new system, and I''m getting the following when I try to start a domU: > [ 1902.049066] xend[12924]: segfault at b9ff6cd8 ip 00007f36c474afe1 sp 00007f36b9ff6af8 error 4 in libxenguest.so.4.0.0[7f36c4730000+24000] This is on an AMD CPU with the AVX instructions, and I already have this in my grub.cfg: > multiboot /xen-4.1.2.gz

Hi, for hours now, I am trying to upgrade a paravirtualized Opensuse 10.3 to 11.0. I turned it into a hvm machine, set boot="d", but I cannot get it to work. file:/os-images/opensuse_11.0_32bit.iso,xvdb:cdrom,r results in Booting from CD-Rom... CDROM boot failure code : 0002 Boot from CD-Rom failed: could not read the boot disk FATAL: No bootable device. If I change xvdb to hdc,

I am trying to write a script to handle setup of domains using virtual block devices for their root FS and have been unable to get the virtual devices to work with any sort of consistency. This is using xen-1.1.bk on Redhat 7.3 (I had to rebuild all the tool binaries to run on 7.3). Anyway, I would first like to make sure I am using the vd/vbd stuff correctly. Here is an example of the problem I

Distro: debian unstable Xen version: 4.0.0-2 This is the config: #HVM #still no qemu-dm in debian #kernel = "/usr/lib/xen-4.0/boot/hvmloader" #builder = ''hvm'' #memory = 2048 #name = "webserver" #vif = [''bridge=eth0''] #disk = [''tap:tapdisk:aio:/srv/xen/webserver.img,xvda,w'',''phy:/dev/cdrom,xvdb:cdrom,r'']

Hello, Maybe someone can help me.... I have a guest XEN image that ran well until today. I use an LVM partition to host the guest and today on Dom0 I added another LVM to be available to this domU. This were all the commands I issued : On hypervisor lvcreate -n lintra02data -L 30G rootvg vi /etc/xen/lintra02 and add volume to file like this : disk = [

Hello, CentOS 5.0 on x86_64 I'm trying to set up Xen paravirt guests with access to 2 block devices: One for / and one for swap. The block devices are LVM LVs, but that shouldn't matter. When I create the guest using either virt-manager or virt-install, I get asked which device to use for xvda. But I want more block devices: xvdb for swap. I know how to add this as an option to the

I''m using xen 4.3 with gentoo as dom0. the kernel and ramdisk file is taken from http://ftp.jaist.ac.jp/pub/Linux/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/xen/ the pv domU config file (according to the ubuntu xen documentation https://help.ubuntu.com/community/Xen) precise.cfg name = "precise" kernel = "/xen/kernels/precise/vmlinuz"

Package: xen-utils-4.0 Version: 4.0.0-2 Severity: normal This is the config: #HVM #still no qemu-dm #kernel = "/usr/lib/xen-4.0/boot/hvmloader" #builder = 'hvm' #memory = 2048 #name = "webserver" #vif = ['bridge=eth0'] #disk = ['tap:tapdisk:aio:/srv/xen/webserver.img,xvda,w','phy:/dev/cdrom,xvdb:cdrom,r'] #device-model =

There are a number of flaws in the blktap userspace daemon when dealing with I/O errors. - The backends which use AIO check the io_events.res member to determine if an I/O error occurred. Which is good. But when calling the callback to signal completion of the I/O, they pass the io_events.res2 member Now this seems fine at first glance[1] "res is the usual result of an I/O

All, Is is possible for xm create foo.cfg to traverse a symlink to access the foo.img. Here''s an example config and the resulting error.. --- name = "jim" memory = "512" disk = [ ''phy:/dev/VolGroup00/foo,xvda,r'', ''tap:aio:/home/fred/local/jim/build/foo_swap.img,xvdd,w'',

Yesterday, I had a PV OpenSolaris DomU stop responding. I looked on my xen machine and it was in a paused state. I ended up destroying it and then doing xm create to bring it back up. It won''t boot, and I think PyGrub is hanging. Not sure how to resolve this, there aren''t any errors being presented in xen/xm itself. If I try ''xm create config.conf'' it just

Just moving a chunk of files from one filesysstem on xvba to another on xvdb, and was monitoring with xentop as it was taking longer than expected. The VBD_RD and VBD_WR counters were both clocking-up as expected, as was the VBD_RSECT counter, but the VBD_WSECT counter was stuck on zero, I toggled on the individual VBD device counters and these showed the same (with the RD and WR counters

Just moving a chunk of files from one filesysstem on xvba to another on xvdb, and was monitoring with xentop as it was taking longer than expected. The VBD_RD and VBD_WR counters were both clocking-up as expected, as was the VBD_RSECT counter, but the VBD_WSECT counter was stuck on zero, I toggled on the individual VBD device counters and these showed the same (with the RD and WR counters