search for: xvdx

...noticed a weird thing. EBS Volumes attached to sd<X> are translated to xvd<Y> at the OS level. However, after a few research and IRC chat, I figured out that it's not weird, it's actually a normal and expected behavior (thanks for your help, z00dax). sdX is actually mapped to xvdX+4. There is a consistent offset of 4. Suppose you attach an ebs volume to /dev/sdf. It'll be translated to xvdj at the OS level. sdg to xvdk, sdh to xvdl and so on. Allright. After having figured the mystery out, it became easy to work on automations that deal with ebs volumes and file systems...

Hi, From cset 10921, ioemu: prefix is removed from disk config in /etc/xen/xmexample.hvm. Now HVM VBD driver is available, this thus raises a question: how would HVM domain know if one disk is a qemu-dm disk or a VBD disk? From current implementation, qemu-dm will recognize disk had, hdb, hdc, hdd, and VBD drive can recognize all disk (had~hdd, hde, hdf ...) . So the result is: qemu-dm will

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

Hello! I updated a Xen domU using linux-image-2.6.24-1-xen-686, adapted the Xen configuration (add ``extra = "console=hvc0"'' and use xvdX devices -- where is all this documented, by the way?) and it boots and I can log in via SSH, but I don't get a login session anymore on the domU's Xen console. Is this a known issue? Regards, Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: not...

Some question. Can I install Xen-3.2.1 with 2.6.18-xen kernel... to my Dom0 and without HVM, starting a debian(DomU) with kernel 2.6.25 from kernel src and compiled with all XEN port / features ? or i need to use the vmlinuz-2.6.18-xen to all my DomU ?? Thanks Crazy _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi! I tried to pcipassthrough usb-controllers to domu to use it with a memory-stick. First xen complained that the driver needs write-access to its configuration space, so I added these to pci-quirks. Since it still didn''t work I also added the device to pci-permissive but I still get an errormessage with Oops (at the end of this email) when sticking in the memory-stick. I tried

Hi! I tried to pcipassthrough usb-controllers to domu to use it with a memory-stick. First xen complained that the driver needs write-access to its configuration space, so I added these to pci-quirks. Since it still didn''t work I also added the device to pci-permissive but I still get an errormessage with Oops (at the end of this email) when sticking in the memory-stick. I tried

Hello list, I''m having a perplexing problem. I''m currently trying to install Gentoo Linux on XenServer 5.6 fp1. When I''ve compiled the kernel, I shutdown, eject CD, activate PV mode, and turn on. It worked, except for the fact that I forgot to change the entries in /etc/fstab to point to /dev/xvd?. So I shutdown, change back to HVM, and reboot into Gentoo''s

Hello! This patch fixes the xm-test restore 04 testcase: o uses ext3 instead of ext2 - which is not supported by the standard kernel config o uses xvdX instead of hdX for disks Kind regards Andreas Florath Signed-off-by: Andreas Florath <xen@flonatel.org> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi Hank, I wanted to follow up on the block device driver discussion we had at LinuxCon, based on some other input I got. What most people recommended was to make both the hv scsi and the hv ata code scsi device drivers, *not* make them standalone block drivers as I originally recommended. The main reason for this is consistent naming of the devices. We have a lot of user code that can deal

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

Hi Hank, I wanted to follow up on the block device driver discussion we had at LinuxCon, based on some other input I got. What most people recommended was to make both the hv scsi and the hv ata code scsi device drivers, *not* make them standalone block drivers as I originally recommended. The main reason for this is consistent naming of the devices. We have a lot of user code that can deal

Hi Hank, I wanted to follow up on the block device driver discussion we had at LinuxCon, based on some other input I got. What most people recommended was to make both the hv scsi and the hv ata code scsi device drivers, *not* make them standalone block drivers as I originally recommended. The main reason for this is consistent naming of the devices. We have a lot of user code that can deal

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:

...both hda and xvda, there would be two hda devices given to Qemu. >> And the image of xvda would be recover the real hda. If xvda doesn''t include >> booting system, HVM booting failed. So how about have a little modify? If >> there is a hdx device, don''t translate xvdx to related hdx. >> >> Best Regards, >> Yongkang You >> >> >>>-----Original Message----- >>>From: xen-devel-bounces@lists.xensource.com >>>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of >>>Kasai Takanori >>>Sent:...

Hello, We are planning to install a Windows 2008 DomU in one of our servers (SUSE 10/SP2, XEN 3.2). Does someone have some experience in installing 2008 ? Are they some know problems (and solutions if possible) to success in thre process. Here is the setup we will use for that DomU : ------------------------------------------------------------------- # SR3 MV9 name="SAP-IDES-ECC"

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 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

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 created an HVM type virtual machine and installed RHEL5U7 guest in it. I have assigned 7 scsi disks to the virtual machine in physical mode (using phy:), however, I see those disks are xvd and not as scsi. Is anyone aware what the problem might be ? Please let me know what kind of information do I need to post in order to narrow down to the problem. Thanks, K