I certainly saw the issue with the non-APIC HAL, but I don't see any performance or CPU issues with the APIC MP HAL.|
From: Venefax <venefax@xxxxxxxxx>
To: 'James Harper' <james.harper@xxxxxxxxxxxxxxxx>, 'Oliver Wilcock' <oliver@xxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Xen GPL PV and undesirable requirement for APIC (irq >15)
Date: Tue, 25 Nov 2008 10:03:48 -0500
I concur on seeing the issue. I changed the HAL to Standard PC (Non-apic)
and the Xennet driver strangely got an IP address from the DHCP, but could
not communicate after that. The regular APIC Multiprocessor HAL works fine
with the drivers, but a few machines kill the server. In fact, the idle
usage is 0.9% and if you add more virtual cpus it shoots up to 3.5%, making
impossible to use.
Looking at in perspective, if we are forced to use a single VCPU windows
machine, then Virtual Box gives a substantial advantage in performance, and
you may run many more machines. They don't support SMP, but it seems that
XEN does not either.
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of James Harper
Sent: Tuesday, November 25, 2008 4:18 AM
To: Oliver Wilcock; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Xen GPL PV and undesirable requirement for APIC
> Hi James,
> Thanks for all the hard work on the GPL PV project.
> I've been having trouble with the more recent builds and then saw
> > Making Windows do the right thing with IRQ's etc was really hard, I
> tried quite a few different approaches and this was the best one I
> come up with. It is a pity that it doesn't work with apic=0, but I
> think that there is a valid reason these days why you would set
> Previously (xen 3.0.x) it was required to make some versions of
> > James
> The APIC problems haven't gone away, as far as I'm aware...
> Like a number of people I run my Windows HVMs with apic=0 (or rather
> the "Standard PC" hal.dll or halacpi.dll) to avoid performance
> Earlier releases of the GPL PV drivers worked well with "Standard PC"
> Windows XP halacpi.dll , but in the last few weeks they have been
> I just wanted to express my concern about the idea that the xennet
> should crash if used with a non APIC HAL. The xennet driver should
> with any HAL, just like the xenvbd driver.
> It would be nice if the apic problems were fixed, too. Any idea why
> APIC related problem? I think the pre-requisites for the symptoms are
> CPU and 64 bit hypervisor and 32 bit Windows HVM.
I reversed the bit that made it fail when it couldn't find an IRQ > 16.
I had incorrectly assumed that all IRQ's < 16 were ISA anyway. I think I
just need to detect the type of IRQ (ISA or PCI) and act
I will revisit this when I've gotten the pvscsi working again (I
desperately need that for internal testing, but it involves quite a few
Xen-users mailing list
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.
Xen-users mailing list