So, as promised, here an first summary. Hardware: AMD Athlon64 X2-4600+ with Asus M2N-Mainboard. Just a short hint: By far not all memory modules work with the Asus boards! Make sure to have compatible ones... After 2 days of trial and error I got the following results: Debian "Sarge" x64: Doesn''t like the new nVidia SATA-Controller (will check today with PATA-interface) Debian "Etch" x64: Trouble with installation (setup freezes when installing more than the pure core). After this is working, I tried HVM - without much luck. After setting it up (.hvm config file) like mentioned in the manual, it just reboots the computer without any error-message. No clue why. All modules mentioned in the manual are installed... Didn''t try paravirtualization here. Debian "SID"/unstable x64: Installs with many problems. Virtual paravirtualized domains stop with the comment "can''t connect to network backend" - didn''t try HVM due to problems with mentioned trouble. So all in all no luck. But there is a question: Does AMD64''s SVM (Pacifica) work also when being in 32-Bit-mode? When thats the case I can check if the stuff is working using debian "Sarge" (thats supposed to work well) and maybe update later to AMD64 when Etch becomes stable. Anyone knowledge about that? Regards, Bigfoot29 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,> Hardware: AMD Athlon64 X2-4600+ with Asus M2N-Mainboard. > After 2 days of trial and error I got the following results:I had more or less the same (first) results some month ago with Intel Bensly-systems!> Debian "Sarge" x64: Doesn''t like the new nVidia SATA-Controller (will > check today with PATA-interface)Instead of Debian I used the Ubuntu 5.10 that accepted the SATA-HDD with the pre-compiled Xen 3.0.1-packages from Xen-source, now you can try the 6.06 with Xen 3.0.2 what should work too.> Debian "SID"/unstable x64: Installs with many problems. VirtualIs there any reason to use the x64-version of Linux? The systems I had where equipped with two Xeons (dual-core, AM64T, HT, VT) and 4GB of RAM so after several problems with the x64-verisons I decided to use the i386-version for testing which was much more stable.> So all in all no luck. But there is a question: Does AMD64''s SVM > (Pacifica) work also when being in 32-Bit-mode? When thats the case IIntel-VT does, I don''t see any reason why AMD-SVM should not. BTW: Finaly (that means with the latest Versions) I had very good results with SuSE Linux 10.1 and SLES 10 Beta and the integrated Xen 3.0.2 - at least on Intel-VT-systems. Hopefully the prices for the small systems with AM2 Athlon X2-processors will fall so I''ll get such a system for testing-purpose! -- Chau y hasta luego, Thorolf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,> Hardware: AMD Athlon64 X2-4600+ with Asus M2N-Mainboard. > After 2 days of trial and error I got the following results:I had more or less the same (first) results some month ago with Intel Bensly-systems!> Debian "Sarge" x64: Doesn''t like the new nVidia SATA-Controller (will > check today with PATA-interface)Instead of Debian I used the Ubuntu 5.10 that accepted the SATA-HDD with the pre-compiled Xen 3.0.1-packages from Xen-source, now you can try the 6.06 with Xen 3.0.2 what should work too.> Debian "SID"/unstable x64: Installs with many problems. VirtualIs there any reason to use the x64-version of Linux? The systems I had where equipped with two Xeons (dual-core, AM64T, HT, VT) and 4GB of RAM so after several problems with the x64-verisons I decided to use the i386-version for testing which was much more stable.> So all in all no luck. But there is a question: Does AMD64''s SVM > (Pacifica) work also when being in 32-Bit-mode? When thats the case IIntel-VT does, I don''t see any reason why AMD-SVM should not. BTW: Finaly (that means with the latest Versions) I had very good results with SuSE Linux 10.1 and SLES 10 Beta and the integrated Xen 3.0.2 - at least on Intel-VT-systems. Hopefully the prices for the small systems with AM2 Athlon X2-processors will fall so I''ll get such a system for testing-purpose! -- Chau y hasta luego, Thorolf ------------------------------------------------------------------ e-Mail: mailto:Thorolf@Godawa.de \|/ /''~''\ Homepage: http://www.godawa.de ( o o ) --------------------------------------------------oOOO--(_)--OOOo- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for the Info, Mr. Godawa :) I installed Debian "Etch" for i386 (486 basically, however 32 Bit.) Paravirtualized OS: Installing a paravirtualized Debian "Sarge" using debootstrap didn''t perform that well... dunno if its because of the GCC-4''ish "Etch" or whatever. The domains don''t come up that well (but they are booting to a certain point then just freeze. Will fiddle around with that later) Hardware virtualized OS (HVM): Works basically like a charm... there are a few quirks, but WinXP (without SPs) installed without _any_ special help. When using vnc its like sitting in front of it. After all Windows came up without problems. Quirks: - The mouse problem when using vnc - the problem with "Zombied" domains when shutting down or rebooting one I guess for both problems exist workarounds. Till now I haven''t had time for searching them. Next week will be the time. :) Basically I want to announce that AMD Athlon64 CPUs with Stepping F (without the Semperons) are HVM-capable. Due to the fact that all HVM-needed things are inside the CPU (not like VT - CPU and Northbridge). Can someone please add them to the list of capable CPUs? Tested with an Athlon64 X2 4600+ More within the next week. Maybe someone has one or two links for the remaining problems? :) Regards, Bigfoot29 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, > Quirks: > - The mouse problem when using vnc > - the problem with "Zombied" domains when shutting down or rebooting > one both problems I have since all 3.0-Xen-versions with several Win-installations on several different Intel-VT-systems. Unfortunately I didn''t found any solution except of using SDL only for installation, VNC maybe for remote-monitoring the boot-process and RDP for accessing the HVM-domain! -- Chau y hasta luego, Thorolf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Marco > Sent: 09 June 2006 06:39 > To: xen-users@lists.xensource.com > Subject: [Xen-users] AMD SVN and Xen3 > > So, as promised, here an first summary. > > Hardware: AMD Athlon64 X2-4600+ with Asus M2N-Mainboard. > Just a short hint: By far not all memory modules work with the Asus > boards! Make sure to have compatible ones... > > After 2 days of trial and error I got the following results: > > Debian "Sarge" x64: Doesn''t like the new nVidia SATA-Controller (will > check today with PATA-interface) > > Debian "Etch" x64: Trouble with installation (setup freezes when > installing more than the pure core). After this is working, I > tried HVM > - without much luck. After setting it up (.hvm config file) like > mentioned in the manual, it just reboots the computer without any > error-message. No clue why. All modules mentioned in the manual are > installed... Didn''t try paravirtualization here.Exactly which version of Xen are you running (copy of the output from "xm info" would help!).> > Debian "SID"/unstable x64: Installs with many problems. Virtual > paravirtualized domains stop with the comment "can''t connect > to network > backend" - didn''t try HVM due to problems with mentioned trouble. > > > So all in all no luck. But there is a question: Does AMD64''s SVM > (Pacifica) work also when being in 32-Bit-mode? When thats the case I > can check if the stuff is working using debian "Sarge" (thats supposed > to work well) and maybe update later to AMD64 when Etch > becomes stable.We test both 32- and 64-bit versions of Xen when we make our contributions to Xen-source, so it _SHOULD_ work. Of course, sometimes we''ll miss something in one direction or the other [I mostly develop on a 64-bit base, so I personally know that my changes work on 64-bit systems, but before it''s submitted to Xen-Source, all changes should be tested on 32-bit systems too], there''s certainly no INTENTIONAL differences. But since 64-bit version of Xen was a bit flaky early on, the first version of Xen to work on SVM was the 32-bit version - so since I saw that you got the 32-bit version working, perhaps you''re running an older version of Xen... Also, not so long ago, SMP-version of the Hypervisor would cause all sorts of problems, but it''s been fixed for several weeks at least... Xen changes very much from day to day... -- Mats> > Anyone knowledge about that? > > Regards, Bigfoot29 > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ok, second try - so a bit shorter :) Hi Mats. Thanks for reply. To your questions:> Exactly which version of Xen are you running (copy of the output from > "xm info" would help!).I found out a few hours after writing the message that I am running 3.0.2 instead of 3.0.2-2. I guess that was the reason for many of the bugs :/ Running 3.0.2-2 now because I have to keep the system going. So switching to an unstable/testing version isn''t that easy as long as one of the more recent versions of Xen are intended to work clean (only with some minor quirks)>> So all in all no luck. But there is a question: Does AMD64''s SVM >> (Pacifica) work also when being in 32-Bit-mode?I can answer that myself: Yep. Running AMD SVM in 32-bit-mode. :)> > We test both 32- and 64-bit versions of Xen when we make our > contributions to Xen-source, so it _SHOULD_ work. Of course, sometimes > we''ll miss something in one direction or the other [I mostly develop on > a 64-bit base, so I personally know that my changes work on 64-bit > systems, but before it''s submitted to Xen-Source, all changes should be > tested on 32-bit systems too], there''s certainly no INTENTIONAL > differences. But since 64-bit version of Xen was a bit flaky early on, > the first version of Xen to work on SVM was the 32-bit version - so > since I saw that you got the 32-bit version working, perhaps you''re > running an older version of Xen...As stated I did :/ I am running Debian ETCH with 3.0.2-2 now. As far as I can see, no trouble with paravirtualized OSes. Only remaining problems with hvm ones. Named: System crash when running more than one hvm domain. Not exactly to locate when, but randomly the complete (host)machine does die (no output of course). Installing Win2k3 crashes once while setup (can be reproduced) and then sets up/works fine (after restarting setup - without SP1). When installing SP1 it reboots as soon as you log in (actually it takes a few seconds to load some stuff - no access to the desktop). I guess its the SP1 installer that makes the hvm crash.> > Also, not so long ago, SMP-version of the Hypervisor would cause all > sorts of problems, but it''s been fixed for several weeks at least... Xen > changes very much from day to day...Thats where my next question goes to: "Testing" - does it make sense trying it on a production system for the sake of having a windows-hvm running? Or is there a 3.0.2-3 or 3.0.3 near the horizon (thats worth waiting for (reason again: stability)) ? Another big question is: Will there be support for the integrated network controller of current nVidia-powered boards? (Because the one Xen is using is far outdated. I wonder because I can''t believe that the vanilla-kernel lacks that driver... (its included in the debian kernel for example) When posting here, maybe I can ask another question: Did you change the scheduler? Several things to notice: 2.0.7: A domain could _never_ completely block the other running domains. When doing heavy work in 3.0.2-2 in dom0 it basically pauses the domUs completely. 99% CPU-load for Dom0 and nothing for DomU. Maybe you don''t notice that much on current Systems, but a small Celeron700-system became completely unresponsible when compiling a new kernel (for example). No Network (ssh), prompt after login for console (xm console vmX) took approx. 5 minutes. I never noticed that before. I am also wondering because the speed of the domUs is terribly slow. I don''t expect a P4 here, but the domU ran on a physical Celeron 433 before - and was double as fast. Another noticed thing (on an other machine) is: is it "normal", that a hvm-domain that boots up normally on CPU1 (pinned) consumes 30-70% CPU0-Load on the both-CPU-located dom0? (AMD X2 4600) This seems to be a pretty big ammount for a single domain... (196MB Ram for the domain, no graphical output) Basically the cpu load of the dom0 was higher than the load of the domU. Just wanted to get rid of these ones :) Maybe some could be answered - maybe some will stay a mystery till eternety... :D However, great work and thanks for the extensive willing to help :) Regards, Bigfoot29 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users