similar to: xvda I/O errors in linux 3.1 under XCP 1.0

Hi, how can i passthroughs HDD with sda instead of xvda ? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi all, I try to use kernel 2.6.36.1 in HVM but building the drivers xen-blkfront, xenfs, platform-pci. I used Xen 4.0.2-rc1-pre and a DomU is a ubuntu 10.04 and I try with ubuntu 10.10. In boot I receive error "Cannot find a root partition /dev/xvda2" and a prompt (initramfs) appear. In dmesg (initramfs) appear: blkfront: xvda: barriers enabled (tag) xvda: xvda1 vbd vbd-51712: 16

Hi all, I try to use kernel 2.6.36.1 in HVM but building the drivers xen-blkfront, xenfs, platform-pci. I used Xen 4.0.2-rc1-pre and a DomU is a ubuntu 10.04 and I try with ubuntu 10.10. In boot I receive error "Cannot find a root partition /dev/xvda2" and a prompt (initramfs) appear. In dmesg (initramfs) appear: blkfront: xvda: barriers enabled (tag) xvda: xvda1 vbd vbd-51712: 16

Hi, Sorry for the need of the long winded email. Looking for some answers to the following. I am setting up a xen PV domU on top of a LVM partitioned DRBD device. Everything was going just fine until I tried to test the filesystems in the domU. Here is my setup; Dom0 OS: CentOS release 5 (Final) Kernel: 2.6.18-8.1.4.el5.centos.plusxen Xen: xen-3.0.3-25.0.3.el5 DRBD:

I mounted an iso file like so: ------------------------------------------- # mount -o loop=/dev/loop0 /path/to/iso /tmp/mnt #ls /tmp/mnt cdromupgrade  dists  doc  install  isolinux  md5sum.txt  pics  pool  preseed  README.diskdefines  ubuntu ------------------------------------------- I used the following file to try to have pygrub boot the mounted iso: -------------------------------------------

Hi, I''m running Xen on a Debian Xeon E3110 using the Debian 2.6.26-2-xen kernel. As filesystem for my lvm domU partitions I choosed xfs. I get the following error in kern.log of domU when booting a domU: blkfront: sda2: write barrier op failed blkfront: sda2: barriers disabled end_request: I/O error, dev sda2, sector 0 end_request: I/O error, dev sda2, sector 0 Filesystem

Back in January there was a mail thread on this subject ( http://lists.xensource.com/archives/html/xen-devel/2005-01/msg00659.html ), however I see that blkfront still does not include ioctl support for disk geometry. So, any application that uses "sfdisk -g" to get the geometry of a partition, or disk, will fail when run in DomU. Is this a deliberate omission? Nick Logan

Hi all, I''ve got xen-4.1.1 running with linux-3.0.0-rc5 and am trying to start my first guest, f14-x86_64, which does boot on bare metal. The configs below show kernel, ramdisk, and disk assignments for the virtual machine. They also show that the virtual machine uses the target disk devices. The last section shows part of the boot sequence starting with the disk assignments,

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 guys! I installed XEN 4.0 on Debian Squeeze but I cannot get the first DomU (not an image) started. Attached you will find /etc/xen/xen1.conf and the result of "xm create -c /etc/xen/xen1.conf" in xen1.log. Can you help me? What did I wrong? Is it about the fstab in xen1 (see also attached)? Many thanks in advance! Regards Stefan

Hi, I''m just wondering if there are any speed or stability differences between running a system directly of a LVM partition versus a xvd partition? Basicly: disk = [ ''phy:/dev/LVM/root,xvda,w'', ] vs disk= [ ''phy:LVM/root,hda1,w'',] Any tips? I tried searching the archives but I didn''t find anything. Kind regards, Tarjei

Hello, I have a CentOS VM with only one disk on a Xenserver. The disk has 2 partitions: /dev/xvda1 -> /boot /dev/xvda2 -> a physical volume for LVM I added 5GB to this disk via Xencenter to extend /dev/xvda2. Usually I just have to do "pvresize /dev/xvda" to have the additional space added to the disk. But for some reason it does not work for this disk. [root ~]# pvresize

I should have added the output of pvs: [root ~]# pvs PV VG Fmt Attr PSize PFree /dev/xvda2 cl_vm731611 lvm2 a-- 9.00g 0 PFree still show 0. It should show 5g. Also: [root ~]# pvdisplay /dev/xvda2 --- Physical volume --- PV Name /dev/xvda2 VG Name cl_vm731611 PV Size 9.00 GiB / not usable 2.00 MiB Allocatable

How do you resize the partition without loosing data? gparted does not support LVM. On Wed, Feb 22, 2017 at 8:37 AM, SysAdmin <admin at s-s.network> wrote: > Hi, > > you need to resize partition /dev/xvda2, afterwards resize pv. > > Regards, > Holger > > > -----Urspr?ngliche Nachricht----- > > Von: CentOS [mailto:centos-bounces at centos.org] Im Auftrag

Are these the current functional procedures for dropping a dom0 on a jaunty 64 bit server? xen-tools: http://bderzhavets.wordpress.com/2009/08/14/attempt-of-prevu-xen-3-4-1-hypervisor-on-ubuntu-jaunty-server-64-bit/ kernel: http://bderzhavets.wordpress.com/2009/07/07/building-xenified-2-6-30-1-kernel-via-xen-patches-2-6-30-2-tar-bz2/ Regarding the patches used in the above procedure from here:

Hello everyone. I have the following problem that could help would appreciate. 1) Environment: HOST 1: xen-hypervisor-3.2-1-amd64 with all VM in LVM disk. HOST 2: XCP 0.5 2) The VM that I wish migrate is a domU in XEN and is debian lenny over LVM: ................................................................................................... # Configuration file for the Xen instance

I have a physical SLES11SP2/OES11 system that I''ve converted to a domU. It''s boots ok as an HVM, but when I try to boot as a PV it gets stuck. I have the kernel-xen packages installed and confident the menu.lst is correct. If I look at xm console for the VM I get the output below: Any ideas? Thanks James [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000]

I am running Xen 4 and want users to be able to install arbitrary HVM images. We want both PV and emulated drivers to appear. The reason for this is for compatibility with images that were prepared for Xen 3.3, which assume emulated devices exist at boot time (particularly for running the boot loader). If I do not specify on the boot line xen_emul_unplug=never, then under some guest OS''s

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, I''m the Mageia XEN packager and during QA, we stumbled into a problem. in fact, we wanted to test Mageia 3 installation on a HVM. so, we had a sparse image and a iso file: [ ''file:/opt/testhvm.img,sda,w'', ''file:/opt/mageialive.iso,hdb:cdrom,r'' ] the live booted, and was able to install to disk, but it never seemed to boot after the install...