| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] AMD64 AM2 supports Windows XP?
The CPU will be fine. You will run into problems when running it using SDL
(damn slow - compare it to an KVM) but remote desktop works fast. (there
is a package available for linux/unix)
As for your SATA raid you may run into problems. Not all modules from all
distributions are supported in the Xenified kernels... ;)
For the memory: You might rin into trouble there... AM2 boards are
somewhat picky on that. Hope, that new revisions will get better. Make
sure to order these things at Alternate or kinda this and order serveral
modules from various companies (and various sizes/speeds) - send these
back that don't work...
Regards, Bigfoot29
> Message: 6
> Date: Sat, 24 Jun 2006 18:23:22 +0200
> From: Jens Gassmann <jens.gassmann@xxxxxxxxx>
> Subject: [Xen-users] AMD64 AM2 supports Windows XP?
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Message-ID: <449D66FA.7010609@xxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-15; format=flowed
>
> Hi,
>
> i consider to buy a new PC for my Desktop. Now i need Windows for do
> some work with Photoshop. I would like to buy a AMD X2 4200 with Socket
> AM2 and the new Pacifica.
>
> Supports XEN this CPU together with windows nativly? How fast Windows
> will works with SDL? Could i use 32bit color deep with SDL? I use fast
> SATA-Raid with a lot of RAM 4GB ontop of Gentoo Linux
>
> Hope someone could answer my questions,
>
> regards from germany
> Jens
>
>
>
> ------------------------------
>
> Message: 7
> Date: Sun, 25 Jun 2006 23:24:31 -0700 (PDT)
> From: Lonesome Crusader <lcrusader@xxxxxxxxx>
> Subject: [Xen-users] Xen API for custom applications
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Message-ID: <20060626062431.42453.qmail@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=iso-8859-1
>
> Hi,
>
> I have two questions related to Xen:
>
> 1. I need a way to determine the domain id of the current domain. I
> have come across GETDOMAININFO, but can this be used in my application?
>
> 2. What API's are provided to make my application Xen aware?
> Specifically, I want my application to take a particular action
> depending on whether the system has Xen installed or not.
>
> Thanks
> Ravi
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
>
> ------------------------------
>
> Message: 8
> Date: Mon, 26 Jun 2006 02:24:33 -0700
> From: Steven Brown <swbrown@xxxxxxxxxxxx>
> Subject: [Xen-users] Trouble using NAT with multiple bridges
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Message-ID: <e7o93l$43h$1@xxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I've got a network set up with xen where I have a chain of
> dom0<->domU<->domU<->etc. to simulate a multi-hop network path and
> implemented with multiple bridges (one per hop to keep them isolated).
> It works nicely locally, except that now I'm trying to have dom0 do NAT
> for that last hop out to internet and am running into problems (I've
> already fixed the ethtool/tx problem afaik). Something simple like this:
>
> iptables -t nat -A POSTROUTING -s 192.168.0.0/16 -j MASQUERADE
>
> Will result in dom0 being able to ping into the domU chain at any number
> of hops, but the domUs won't be able to ping each other. Only the first
> domU in the chain (so only traversing one bridge) can get out to
> internet through the NAT.
>
> The closest I've come to making it work is this (assumed that
> POSTROUTING is being hit by each bridge traversal):
>
> iptables -m physdev ! --physdev-is-bridged -t nat -A POSTROUTING -s
> 192.168.0.0/16 -j MASQUERADE
>
> In which case, the dom0 can ping into the domUs, the domUs can ping each
> other, but again, only the first domU in the chain can get out to
> internet through the NAT despite the other domUs having a working path
> to that working domU.
>
> I figure it's something simple I'm missing, but I'm totally out of
> clues, so hoping y'all can help. Some extra details below in case
> they're of use.
>
>
>
> (This is the route view at dom0; internet-br0 is the first bridge
> between the dom0 and chain of domUs and contains a single interface -
> that of the first domU in the chain of domUs (192.168.6.1). eth0 is the
> path out to internet. All the domUs in the chain are in the
> 192.168.0.0/16 subnet. The other bridges have two interfaces and no
> directly assigned IP, unlike this one.)
> root@fictition:~# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.6.1 0.0.0.0 255.255.255.255 UH 0 0 0
> internet-br0
> 72.130.176.0 0.0.0.0 255.255.248.0 U 0 0 0
> eth0
> 192.168.0.0 192.168.6.1 255.255.0.0 UG 0 0 0
> internet-br0
> 0.0.0.0 72.130.176.1 0.0.0.0 UG 0 0 0
> eth0
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
>
> End of Xen-users Digest, Vol 16, Issue 152
> ******************************************
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home