similar to: [PATCH] Support for official xvd major number

This is the patch from Amos Waterland for the xenconsole to use /dev/xvc0 instead of taking over ttys. I''ve fixed a few places which needed to check for XVC mode in addition to serial mode. Also, until LANANA responds with an official minor, I''ve adjusted it to use char 250/187 (in the experimental range) as opposed to 204/187 Signed-off-by: Jeremy Katz

This is the patch from Amos Waterland for the xenconsole to use /dev/xvc0 instead of taking over ttys. I''ve fixed a few places which needed to check for XVC mode in addition to serial mode. Also, until LANANA responds with an official minor, I''ve adjusted it to use char 250/187 (in the experimental range) as opposed to 204/187. (Should be identical to this patch from last

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

Package: xen-utils-common Version: 4.1.3-6 Severity: minor Dear Maintainer, I am trying to run the following command on a dom0 Debian server in order to mount a vmware vmdk. I don't want to use kpartx or losetup as they have poor write performance and I'm hoping blktap will provide better performance. xm block-attach 0 tap:vmdk:/mnt/backup/3MSYDDP01/3MSYDDP01_2-flat.vmdk /dev/xvda1 w 0

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.

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream Normally (in 'iso-based' XCP) is possible to attach VDI to dom0. That operation usually looks like: xe vbd-create vdi-uuid=... vm-uuid=(dom0 uuid) device=N xe vbd-plug I done those steps in xcp-xapi and got success (no error), but no xvd* device found. Here operations log: # xe vbd-create

Hi have 4 dom0 with debian lenny running xen. When I run ps axf|grep xvd I see it''s different on diferent dom0s. dom0-A 15677 ? S< 0:00 \_ [blkback.139.xvd] 15678 ? S< 0:38 \_ [blkback.139.xvd] 17015 ? S< 0:00 \_ [blkback.140.xvd] 17016 ? S< 2:34 \_ [blkback.140.xvd] 21309 ? S< 0:00 \_ [blkback.142.xvd] 21310 ?

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

We recently added a disk to our Coraid SAN. We''ve used tons of devices off of this SAN with Xen before, but this time we experienced some weird behavior. I configured a DomU to have the device directly offered as a disk (i.e. ''phy/dev/etherd/e1.1,sdb1,rw''). When I tried to boot it, an xvd process showed up as usual. However, it consumed 100% processor

Hello List, i am trying to boot a 2.6.28 vanilla kernel as a DomU. This is some of my config: ---------------------------------------------- root = ''/dev/xvda2 ro'' disk = [ ''drbd:pgone,xvda2,w'', ''phy:/dev/vg/pgone-swap,xvda1,w'',

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 list! (resending, it seems the previous mail didn''t make it to the list) At some point Xen supported block-reconfigure to resize domU disks on the fly.. This is not working atm/anymore? Discussion about the subject.. (in the end of the thread): http://lists.xensource.com/archives/html/xen-users/2008-04/msg00246.html Support for online resizing Linux SCSI disks was accepted

Hola: Con esto del R me da la impresión que avanzo un paso y retrocedo dos! El caso es que tengo una "cascada de funciones", para realizar un análisis descriptivo "automático" en función del tipo de variable. Y en los resultados, en lugar de aparecer el nombre de la variable, aparece el nombre del argumento. Esto ocurre tanto si utilizo o no la función get(). Un ejemplo

Hola Carlos: Te adjunto un ejemplo de aplicación: las funciones (he borrado los path de las funciones y las ordenes "source()" que las carga ) y un ejemplo para ejecutarlas para las opciones que tengo implementadas con la tabla de datos birthwt del paquete"MASS": - Descriptiva de todas las variables de una tabla. - Análisis univariado de todas las variables de una tabla

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

I''m using scriptaculous'' SlideUp and SlideDown effects to animate a menu. Specifically, I SlideUp, make some CSS changes, and SlideDown. All works well, except that for a split second in between, the element''s display becomes ''none'' and the other menu item jump into the space. I haven''t been able to find any way to force an element to retain

H. Peter Anvin wrote: > On the subject of virtualization; there are a number of devices which > keep being invented and reinvented by just about every virtualization > vendor for no really good reason. > > I personally recently pointed out that a proper virtualization > solution should handle entropy collection at the lowest level (where > the physical hardware drivers are)

H. Peter Anvin wrote: > On the subject of virtualization; there are a number of devices which > keep being invented and reinvented by just about every virtualization > vendor for no really good reason. > > I personally recently pointed out that a proper virtualization > solution should handle entropy collection at the lowest level (where > the physical hardware drivers are)

Now I''m sure that the following configuration can destroy a PostgreSQL 8.3.5 database: * Linux host (dom0) with XEN, XFS filesystem with "nobarrier", RAID controller with battery backed cache. * XEN vm (domU) with XFS filesystem with "nobarrier" with postgresql * my daughter with 3.5 years switching off the power supply of the server, just behind the UPS Seems XEN

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