similar to: blkback in DomU

How should I be detecting a block-configure operation done in Dom0 in a HVM DomU? Under Debian Lenny''s Xen 3.2.1, when I execute such a command, Dom0 writes to the backend values ''params'' and ''type'', twice, but doesn''t update the ''sectors'' value to match the new device, or initiate a state change. Given that, the best I can

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

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

On Sun, Jun 8, 2008 at 3:28 PM, James Harper <james.harper@bendigoit.com.au> wrote: > I''ve just uploaded 0.9.8 to http://www.meadowcourt.org/downloads > > As a reminder, the wiki page is > http://wiki.xensource.com/xenwiki/XenWindowsGplPv > > This release fixes a bug which could be hit under high disk load (high > number of outstanding requests with fragmented

I am rewriting the TX path in the GPLPV drivers and in its current form I am readily able to crash the system (eg Dom0 and everything else running) from DomU. xen is 3.3.1, linux is at most a week behind the 3.3.1 release date. My Windows DomU boots up, fails to get an IP address (yes, the TX path is broken), and then a short time later the system has rebooted. I don''t know exactly

hi,         I am  an engineer of Intel , on cloud and virtalization. thanks for you great updates of vTPM.Could you share your experience on how to build vTPM with xen 4.3?  I failed to boot up  2.6.18.8 kernel which is from               # make linux-2.6-xen-build              # make linux-2.6-xen-install                   I want to integerate  vTPM to OpenAttestation.OpenAttestation project is

Just reporting some iperf results. In each case, Dom0 is iperf server, DomU is iperf client: (1) Dom0: Intel Core2 3.16 GHz, CentOS 5.2, xen 3.0.3. DomU: Windows XP SP3, GPLPV 0.9.12-pre13, file based. Iperf: 1.17 Gbits/sec (2) Dom0: Intel Core2 2.33 GHz, CentOS 5.2, xen 3.0.3. DomU: Windows XP SP3, GPLPV 0.9.12-pre13, file based. Iperf: 725 Mbits/sec (3) Dom0: Intel Core2 2.33 GHz,

Hi there. I have been dealing with a conundrum off and on with a VPS of mine. Windows 2003 Standard 32 bit on a Xen HVM instance. Been trying to get the GPLPV drivers working to help boost performance but always seem to run into one major issue: The PV network device looks like it works but actual connectivity is non-existant. Everything else in the GPLPV driver suite works fine. What I want to

Hi everyone. I´m having this problem with Red Hat 5.4 running on a HP ProLiant BL460c G6. I have two windows 2k3 x64, but network performance is extremely bad without PV drivers, i mean, it takes a lot of time to access any location and if the path has many folders it can´t conect. Redhat provides some PV dirvers. I´ve installed them, but with no improvements. I tested another DomU, with the

1. Shouldn''t the GPLPV drivers take care of the (bad) clock drift I''m experiencing in my Windows XP HVM? Or is there some other way around this problem that I haven''t been able to find on Google? How can I tell if the GPLPV drivers are active? I''ve added the /gplpv switch to the boot.ini file and the virtual NIC is definitely using the GPLPV version but other

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

Hello! after update of GPLPV drivers from 0.9.12-pre13 to 0.10.0.86 on windows 2008 server domU I cant use xm shutdown <domU> in dom0 (nothing happens exactly for this domU, other domU with old drivers shutdowns normally), how to fix? opensuse11.1x64 xen 3.3.1 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

My target is virtualized SBS2003 on dell PE T410 Now I test xen on my desktop. Centos 6 as dom0 - kernel: 2.6.32-131.12.1.el6.xendom0.x86_64 from http://xenbits.xen.org/people/mayoung/testing/x86_64/ hypervisor 4.1.1.3 from http://xenbits.xen.org/people/mayoung/EL6.xen/x86_64/ One NIC simple bridge-network configuration dom0 uses static IP with ISP router as gateway domU have also static IP

Hi all, Thought I''d share my success with VT-d. I picked up an Asus P5E-VM DO motherboard as it was relatively cheap and had an extra PCI slot compared to the Intel Q35 board. The people on #xen IRC were very helpful. I wasted 2 days trying to get things working on Ubuntu and OpenSUSE with forward patched versions of Xen for newer kernels. Ended up using CentOS 5.1 which has the requred

I''ve just put up the latest release of the GPLPV drivers for Windows. This release involved a fairly big rewrite of the stuff that talks to Windows as I changed from WDF to WDM. WDF is a newer framework from Microsoft which makes it easier to write drivers as a lot of the state management stuff is done for you. It also means shipping a great big dll around with the drivers (note the

I''ve just put up the latest release of the GPLPV drivers for Windows. This release involved a fairly big rewrite of the stuff that talks to Windows as I changed from WDF to WDM. WDF is a newer framework from Microsoft which makes it easier to write drivers as a lot of the state management stuff is done for you. It also means shipping a great big dll around with the drivers (note the

Hi, I just installed gplpv drive for my windows 2003 domU, but not sure if it works right, in my device manager, there is a unknown pci device, do you know what''s that? Thanks. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello, I have a big problem: Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the only thing is that I give 3 nics to the domU so I use a modified network script (which has worked since january... since fedora 6): " #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1

Hi all, After loading the GplPV drivers for Windows Server 2008, I wanted to get rid of the annoying F8 option when rebooting each time. I looked at Ready Driver Plus, which seemed to work, but was only a workaround. It also seemed to kill my terminal connection from Dom0. After some research, I found another way: http://www.ngohq.com/home.php?page=dseo Which will disable driver