Hey, Folks, I know I''ve posted this question before and have not really received a response, but I''m continuing to experience some problems with graphics pass through related to the amount of memory assigned to a domU. I have an HVM domU, running Windows 7. My physical platform is a Dell Optiplex 790 with 8GB and 16GB of RAM. I''ve also experienced similar issues on the Dell Optiplex 780 with 8GB of RAM. At this point I''ve determined that the limit of the memory I can assign to the domU with graphics pass-through is 3266 MB. If I assign any more than that - 3267, 3270, 4096, and up - I start to see problems. In earlier versions of Xen the domU will not start at all. In the version I''m running, now, 4.1.2, the domU will start but Windows blue-screens with a variety of errors, from service problems to attempts to write to read-only memory. I''m wondering if anyone can shed any light on why I would be running into a problem at 3267MB of RAM and any possible things to try to get around that. I''ve played with the videoram and shadow_memory settings, to no avail. Thanks! -Nick -------- 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.
Hi Nick, Is your Dom0 64bit? Is your Windows7-DomU 64bit? Do you create your DomU via xm or (better!) with xl? How many CPUs do you give this DomU? Does your DomU work ok with <=3266, including GPU support? Or are there problems even with fewer than 3266MB Ram? Sorry, i have no definite answer to your problem, but i recall similar Problems with xm-created HVM guests and 64/32bit mixes , especially with older Xen Versions. Greetings Tobias Am Mittwoch, 15. Februar 2012, 01:00:02 schrieb Nick Couchman:> Hey, Folks, > I know I''ve posted this question before and have not really received a > response, but I''m continuing to experience some problems with graphics > pass through related to the amount of memory assigned to a domU. I have > an HVM domU, running Windows 7. My physical platform is a Dell Optiplex > 790 with 8GB and 16GB of RAM. I''ve also experienced similar issues on > the Dell Optiplex 780 with 8GB of RAM. > > At this point I''ve determined that the limit of the memory I can assign > to the domU with graphics pass-through is 3266 MB. If I assign any more > than that - 3267, 3270, 4096, and up - I start to see problems. In > earlier versions of Xen the domU will not start at all. In the version > I''m running, now, 4.1.2, the domU will start but Windows blue-screens > with a variety of errors, from service problems to attempts to write to > read-only memory. > > I''m wondering if anyone can shed any light on why I would be running > into a problem at 3267MB of RAM and any possible things to try to get > around that. I''ve played with the videoram and shadow_memory settings, > to no avail. > > Thanks! > -Nick > > > > -------- > 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 > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users
On Wed, 2012-02-15 at 17:19 +0100, Tobias Geiger wrote:> Hi Nick, > > Is your Dom0 64bit? Is your Windows7-DomU 64bit? > Do you create your DomU via xm or (better!) with xl?dom0 is 64 bit and Windows 7 HVM is also 64 bit. I used virt-manager (libvirt) to create the domU - definitely not xl, but I''m not sure how closely libvirt is associated with xm.> > How many CPUs do you give this DomU?2 - physical machine has a total of 4 cores on a single chip (Intel Core i5).> > Does your DomU work ok with <=3266, including GPU support? Or are there > problems even with fewer than 3266MB Ram?Yes, domU graphics pass-through works with anything less than or equal to 3266MB of RAM. Anything greater than 3266 causes Windows to crash with one of several BSODs.> > Sorry, i have no definite answer to your problem, but i recall similar Problems > with xm-created HVM guests and 64/32bit mixes , especially with older Xen > Versions. >No worries, I appreciate any help at all tracking this issue down. It''s very strange, and I''m sure is related to some combination of interactions between memory, the VGA BIOS, and the graphics card driver in the Windows HVM. I''m hoping someone can help track it down on this list - if not, I''ll post to the devel list and see if anyone there has anything I can try. -Nick -------- 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.