similar to: Xen 4.0 - Support for Citrix WHQL-certified Windows PV drivers

Hello I have a Supermicro system with Intel XEON cpu with VT enabled. HVM, without Windows PV driver, works great. I am trying to use Windows PV driver from XCP 0.5, it is in the .iso file of XCP 0.5 Filename: windows-pvdrivers-xensetup.exe I have tried - XEN 3.4.3 (Linux 2.6.18.8) - XEN 4.0.1-rc6-pre (Linux 2.6.31.x and Linux 2.6.32.x from Jeremys GIT) and - XEN 4.0.1-rc6 (Linux 2.6.31.x and

Hi. I have the same problem, which described in: http://lists.xensource.com/archives/html/xen-users/2010-07/msg00241.html I''m using Debian Squeeze (2.6.32-5-xen-amd64) in Dom0, Xen 4.0.1-rc6, Windows 2008, 2003 x86_64 in domU After installing drivers from http://www.xen.org/files/XenCloud/Software/0.5/XCP-base-0.5.iso, system stops on progress bar in normal boot, but ok in safe mode. In

I have been google for a few days now trying to get the Citrix PV Drivers to work on a server 2008 R2 HVM guest. I get the machine up and running then I install the cirtix PV drivers. I have tried both making and not making the registry change. Once I reboot the server I get stuck at the boot screen. The xen log says: XENUTIL: WARNING: CloseFrontend: timed out in

Hello List, Merry Christmas to all !! Basically I''m trying to boot a Windows 2008R2 DC HVM with 90GB static max memory and 32GB static min. The node config is Dell M610 with X5660 and 96GB RAM and its running XCP 1.1 Many times the node crashes while booting HVM. Sometimes I get success. I have attached the HVM boot log of successful start. Many times the node hangs as soon as the

>>> On 2010/07/07 at 12:18, benco <benco@acid.sk> wrote: > No, I don''t like testsigning - this is the main reason why I want to use > Citrix driver. GPLPV driver works fine for me and if there would be a way > to use it without testsigning on, I would be happy with it. > Why don''t you like testsigning? -Nick -------- This e-mail may contain

When trying to use the GPL PV drivers with Windows 7 x64 (and testsigning turned on), I get a BSOD with a STOP 0x00000101 error. There''s also an error at the top that says "A clock interrupt was not received on a secondary processor within the allocated time interval." Is this STOP error related to the HPET or other timing adjustments for Xen? Any advice on things I should

+Li Jin ----- Original Message ----- > From: "Vadim Rozenfeld" <vrozenfe@redhat.com> > To: "Richard W.M. Jones" <rjones@redhat.com> > Cc: "Roman Kagan" <rkagan@virtuozzo.com>, libguestfs@redhat.com, "Amnon Ilan" <ailan@redhat.com>, "Jeff Nelson" > <jenelson@redhat.com>, "Yan Vugenfirer"

Hi Michael, On Mon, Sep 15, 2014 at 1:20 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Sun, Sep 14, 2014 at 08:29:33PM -0700, Anthony Liguori wrote: >> From: Anthony Liguori <aliguori at amazon.com> >> >> See https://issues.oasis-open.org/browse/VIRTIO-16 although it >> was prematurely closed. > > The reason it was closed is described in the

Hi Michael, On Mon, Sep 15, 2014 at 1:20 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Sun, Sep 14, 2014 at 08:29:33PM -0700, Anthony Liguori wrote: >> From: Anthony Liguori <aliguori at amazon.com> >> >> See https://issues.oasis-open.org/browse/VIRTIO-16 although it >> was prematurely closed. > > The reason it was closed is described in the

From: Anthony Liguori <aliguori at amazon.com> See https://issues.oasis-open.org/browse/VIRTIO-16 although it was prematurely closed. Red Hat has non-redistributable Windows drivers and Microsoft will not allow anyone else to WHQL certify drivers using that vendor ID. That makes it impossible to use virtio drivers with a Windows guest without changing the vendor ID. Cc: Matt Wilson

From: Anthony Liguori <aliguori at amazon.com> See https://issues.oasis-open.org/browse/VIRTIO-16 although it was prematurely closed. Red Hat has non-redistributable Windows drivers and Microsoft will not allow anyone else to WHQL certify drivers using that vendor ID. That makes it impossible to use virtio drivers with a Windows guest without changing the vendor ID. Cc: Matt Wilson

I think one - maybe final? - problem. How can I tell the difference between drivers for "client" versions of Windows (eg. Windows 7) and server versions of Windows (eg. Windows 2008 Server)? It seems in many or most cases the drivers are identical, eg: $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat

I''m now at the stage where I can think about writing some PV block drivers for Windows. I have working event channel and xen store subsystems (but they''ll probably need some more refinement once things progress), and the Windows XenPCI driver enumerates devices as they are added to xenstore. This leaves me with a few questions... 1. I assume that the qemu virtual BIOS uses the

Hello, I am just installing XCP 0.1.1 on a server with 24GB RAM Normally XCP is a 64 bits version but * *uname -a* Linux node012 2.6.27.42-0.1.1.xs0.1.1.737.1065xen #1 SMP Fri Jan 15 16:20:16 EST 2010 i686 i686 i386 GNU/Linux (not a x86_64 version !!!!) * *cat /proc/meminfo* MemTotal: 746496 kB MemFree: 384332 kB Buffers:

Hi, XCP is hanging at (or just after) "Setting Hostname" If you keep trying eventually it gets past this point. It might take 5-20 attempts to get XCP to boot. When it does boot all is stable. I have the same problem on 4 different boxes. 2 x INTEL Black Box Dual XEON server. 1 x AMD II x250 1 x Core2Duo NoteBook used for DEV. All 3 boxes are using mdadm raid 1. The

[previously posted to xen-devel@ and xen-api@ but this might be of interest to xen-users@ too] Hi, I''ve refreshed the Xen Cloud Platform (XCP) .isos on xen.org with a new development snapshot (labelled version 0.1.1). XCP is a collaborative effort to build a complete cloud infrastructure platform, complete with a powerful management stack, standards-based APIs, support for multi-tenancy

I have two systems loaded with XCP 0.1.1 and it works well. XenMotion, Live Migrations and automated installs are fantastic. I am wondering whty the field for ha-enabled is read-only... Is there any way I can change this so I can enable HA on XCP? So when a host fails the other hosts takes all the guests. What would the best way to accomplish what I need? Would XCP be the answer or straight

Hello with XEN 3.4.x antispoof=yes works on a bridge setup. I am using this line in xend-config.sxp (network-script ''network-bridge antispoof=yes'') It creates this under IPTABLES FORWARD chain: ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in peth0 Under XEN 4.0.1 it is not working, it does not create a IPTABLES rule. Customers can

XCP Users: As many of you are aware, there are several open source products available for everyone to use when working with XCP. I would like to get some feedback on the various tools to get a feeling on how people are using XCP and these tools. Here are the tools that I am aware of (please respond if you are using another tool): * OpenXenManager -

Hi, I have been using syslinux on my portable disk with success on many types of machines (both bios boot and EFI boot) I however hit a small issue recently If I use menu.c32, on some UEFI systems (HP) the menu does not appear after the vendor splash screen. The system however goes ahead and after the timeout configured in the menu system syslinux boots the kernel. I can then (after kernel