similar to: detecting a ''block-configure'' via xenbus

Hi Is it true that the GPLPV drivers is incompatible with QCOW images? The Windows DomU works fine with raw standard "file:/" images, and paravirtualized Linux DomU works fine with QCOW and raw images. If i use QCOW images with my Windows DomU''s i get a stop error: 0x00000007b (inaccessible boot device). It looks like the blkback.3.hda process, that normally starts with

I''ve recently noticed that my windows crash dumps fail at around 40-50% under GPLPV. ''xm dmesg'' shows the following: (XEN) grant_table.c:350:d0 Iomem mapping not permitted ffffffffffffffff (domain 865) At first I thought that the cause was just a bug in my grant ref code but it just occurred to me that this could be happening when Windows tries to write out the

I''ve just made my first ever attempt at an Nullsoft installer, so if you want to try it download "Xen PV Drivers 0.9.5.exe" from http://www.meadowcourt.org/downloads/ The installer should detect the version of windows you are running and install the drivers. At the moment you''ll need to install the shutdown monitor service manually, but you can do that from the start

I''ve just made my first ever attempt at an Nullsoft installer, so if you want to try it download "Xen PV Drivers 0.9.5.exe" from http://www.meadowcourt.org/downloads/ The installer should detect the version of windows you are running and install the drivers. At the moment you''ll need to install the shutdown monitor service manually, but you can do that from the start

A user has pointed out a problem with GPLPV under Xen 4.2 when using PoD. I''m using the difference between XENMEM_maximum_reservation and XENMEM_current_reservation to tell me how much I should balloon down to account for PoD, but when the user has ballooned down to 1G (from 4Gb or 8GB), GPLPV logs the following: 13005008825593: XenPCI XENMEM_maximum_reservation = 262400

I just about have my PV block device drivers booting, except just before the login screen appears I get a message that the registry couldn''t be written out. I''m pretty sure that this is because some data from the int13 interface provided by the qemu intel ide driver that has been written, hasn''t actually made it to the block device (lvm volume in my case). I''ve

I accidentally realized today that any domU''s using the paravirt disk driver potentially suffer from poor performance when they get handed in a physical volume and partitioning is done inside the guest. The physical volume passed in has to be one that has the compat 512 logical sector size but hints its real sector size (eg. 4096) as physical sector size. In dom0 handling is correct and

I''m trying to compile pvscsi out-of-tree, and I''m getting an error that set_phys_to_machine is not defined when I try to load the module (with the warning to that effect at compile time too). This used to work fine in pvops. It seems that netfront uses that symbol in a module so I''m confused as to why pvscsi can''t... any suggestions? Is it one of the virtues of

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

Can the XenStore database be accessed by domU''s? If so, could it be used to pass small amounts of data back and forth between dom0 and domU''s using XenStore key entries? If this is possible, it would seem that this could eliminate the need to create a "device" driver for a simple communication path. Also, what type of Guest Fedora Kernel would be needed to

Hi All, I am working on creating storage driver domain with xen-4.3.0 . I am referring this - http://wiki.xen.org/wiki?title=Storage_driver_domains&oldid=9371 I have created Storage domain with xl utility of xen, then followed above wiki for rest of the steps, additionally I did install blktap-dkms package also- Following xen processes are running on Domain 0:

Hi All, I am working on creating storage driver domain with xen-4.3.0 . I am referring this - http://wiki.xen.org/wiki?title=Storage_driver_domains&oldid=9371 I have created Storage domain with xl utility of xen, then followed above wiki for rest of the steps, additionally I did install blktap-dkms package also- Following xen processes are running on Domain 0:

Hello List, I have a small problem with the ring when transferring blocks the id on the response is different from the request. This is the boot up read, count 0. The guest requests block 0, it has to be located at 7c00. I go ahead and create a REQUEST with this data: ring_req = RING_GET_REQUEST(priv,priv->req_prod_pvt); ring_req->id = 9; ring_req->nr_segments=1; ring_req->operation

''xm block-attach'' doesn''t let me assign the same backend device anymore, even if I use ''r!'' or ''w!''. I think this has changed since 3.1.1 (or maybe since 3.1.0). Is this the way it is supposed to work? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi James. I go through the patch, since all its changes happens inside __xen_evtchn_do_upcall(), so I apply the patch into my 2.6.31.kernel by manual. (I was failed to merge a usable, 2.6.38dom0, since quite a lot branch needed, such as blkback, netback) But still, the blue screen shows up. Log attached. Is the timeout better than before? Beside, I think I need find some to examine my

I''ve just uploaded 0.9.11-pre12 of the GPL PV drivers for Windows. Since -pre10 (and -pre11) I''ve fixed a heap of crashes that were plaguing xennet under load, and also rewritten the interrupt/event distribution logic to improve performance. Under windows 2003 I can now get network speeds of 1-2Gbit/second TX and 600Gbit/second RX, which is considerably better than I was

I''ve just uploaded 0.9.11-pre12 of the GPL PV drivers for Windows. Since -pre10 (and -pre11) I''ve fixed a heap of crashes that were plaguing xennet under load, and also rewritten the interrupt/event distribution logic to improve performance. Under windows 2003 I can now get network speeds of 1-2Gbit/second TX and 600Gbit/second RX, which is considerably better than I was

Hi, I''ve been working on getting a working blktap driver allowing to access ceph RBD block devices without relying on the RBD kernel driver and it finally got to a point where, it works and is testable. Some of the advantages are: - Easier to update to newer RBD version - Allows functionality only available in the userspace RBD library (write cache, layering, ...) - Less issue when

Hi all, I add a blkback QoS patch. You can config(dynamic/static) different I/O speed for different VM disk by this patch. ---------------------------------------------------------------------------- diff -urNp blkback/blkback.c blkback-qos/blkback.c --- blkback/blkback.c 2011-06-22 07:54:19.000000000 +0800 +++ blkback-qos/blkback.c 2011-06-22 07:53:18.000000000 +0800 @@ -44,6 +44,11 @@

Hi all, I add a blkback QoS patch. You can config(dynamic/static) different I/O speed for different VM disk by this patch. ---------------------------------------------------------------------------- diff -urNp blkback/blkback.c blkback-qos/blkback.c --- blkback/blkback.c 2011-06-22 07:54:19.000000000 +0800 +++ blkback-qos/blkback.c 2011-06-22 07:53:18.000000000 +0800 @@ -44,6 +44,11 @@