Regarding your xen/windows xp setup, I have successfully installed win2k3. The "trick" is the cdrom drive and making it accessible, so you need to do something like:
name = "windoze" builder = "hvm" memory = "512" disk = [ 'phy:/dev/VolGroup00/windoze,had,w', 'file:/root/win2k3std.iso,hdc:cdrom,r' ] vif = ... uuid = ... device_model = "/usr/lib64/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" vnc=1 apic=1 acpi=1 pae=1 vcpus=2 serial = "pty" on_reboot = 'restart' on_crash = 'restart' boot='d' assuming above file was called /etc/xen/windows you can start it with xm create windoze and use virt-manager from there on. The disk line above is one line, which is what is causing your install not to see the cd. The boot='d' will prompt to boot from cd. Sometimes it helps to do xm create windoze && xm pause windows so that you can boot from cd. Vif and uuid lines should be generated by virt manager already for you... Pritam -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, December 12, 2006 10:48 AM To: [email protected] Subject: rhelv5-beta-list Digest, Vol 5, Issue 14 Send rhelv5-beta-list mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://www.redhat.com/mailman/listinfo/rhelv5-beta-list or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of rhelv5-beta-list digest..." Today's Topics: 1. Re: Dell 690n (Subhendu Ghosh) 2. Xen DomUs (Jeffrey D Lane) 3. Re: Xen DomUs (Jan Mark Holzer) 4. Xen, ParaVirt and PAE Extensions (Brian Long) 5. Re: Xen DomUs (Paolo D.) 6. Re: Xen, ParaVirt and PAE Extensions (Jan Mark Holzer) 7. Re: Xen, ParaVirt and PAE Extensions (Brian Long) ---------------------------------------------------------------------- Message: 1 Date: Mon, 11 Dec 2006 16:50:49 -0500 (EST) From: Subhendu Ghosh <[EMAIL PROTECTED]> Subject: Re: [rhelv5-beta-list] Dell 690n To: "Red Hat Enterprise Linux 5 (Tikanga) Beta releases discussion mailing-list" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 10 Dec 2006, Joakim Karlsson wrote: > > > > Anyone has success installing Beta2 on Dell 690n ? > > > > > > -- > > -sg > > Yes, we have a pair of Dell 690:s running rhel5 beta2, but I think we > didn't do a fresh install on them but uppgraded them from beta1. > > We got some dwarf-errors from the beta1 kernel on the 690:s, but beta2 > runs without any problems. > > /Joakim > Silly me - anaconda was writing GRUB to /dev/hda and only disk installed was /dev/sda .. (Had to change BIOS boot order SAS before SATA) -- -sg ------------------------------ Message: 2 Date: Tue, 12 Dec 2006 10:00:37 -0500 From: Jeffrey D Lane <[EMAIL PROTECTED]> Subject: [rhelv5-beta-list] Xen DomUs To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" Just for my own edification, has anyone managed to install a fully virtualized DomU with WinXP or Windows 2003?? I cant seem to get one to install completely which is quite frustrating. I can get virt-manager to create the DomU, and it does begin installing from CD, but after the Windows installer copies all its files, it reboots to load the full installer and at that point it fails because it can no longer see the CD. I have tried adding a cdrom line that points to /dev/hdc and then tried one that pointed to /media/cdrom after mounting the cdrom to that mt. point, but no joy. So anyone try this, or am I just insane? Of course, my network installed RHEL5 DomUs work perfectly. I haven't tried any other OSs yet. Is there a list of supported OSs available anywhere on Red Hat.com yet?? Cheers Jeff Jeffrey Lane <--> W4KDH Software Engineer IBM eServer xSeries Research Triangle Park, NC 27709 -------------- next part -------------- An HTML attachment was scrubbed... URL: https://www.redhat.com/archives/rhelv5-beta-list/attachments/20061212/31 579502/attachment.html ------------------------------ Message: 3 Date: Tue, 12 Dec 2006 10:19:57 -0500 From: Jan Mark Holzer <[EMAIL PROTECTED]> Subject: Re: [rhelv5-beta-list] Xen DomUs To: "Red Hat Enterprise Linux 5 (Tikanga) Beta releases discussion mailing-list" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" An HTML attachment was scrubbed... URL: https://www.redhat.com/archives/rhelv5-beta-list/attachments/20061212/f5 0d262a/attachment.html ------------------------------ Message: 4 Date: Tue, 12 Dec 2006 10:28:50 -0500 From: Brian Long <[EMAIL PROTECTED]> Subject: [rhelv5-beta-list] Xen, ParaVirt and PAE Extensions To: Red Hat "Enterprise Linux 5 (Tikanga) Beta releases discussion mailing-list" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain Can someone more familiar with Xen development help me understand why PAE extensions are now required? I remember running FC rawhide Xen on my IBM Thinkpad 42P (Intel Pentium M w/o PAE) and I got paravirt working (6-9 months ago, I believe). Now it seems PAE is hard-coded in the RHEL 5 and FC6 kernels so I'm SOL. Thanks. /Brian/ -- Brian Long | | IT Infrastructure . | | | . | | | . Data Center Systems ' ' Cisco Enterprise Linux C I S C O ------------------------------ Message: 5 Date: Tue, 12 Dec 2006 16:25:07 +0100 From: "Paolo D." <[EMAIL PROTECTED]> Subject: Re: [rhelv5-beta-list] Xen DomUs To: "Red Hat Enterprise Linux 5 (Tikanga) Beta releases discussion mailing-list" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" Sorry, Jeffrey, can I ask you how were you able and install virt-manager on Tikanga? Paolo ----- Original Message ----- From: Jeffrey D Lane To: [email protected] Sent: Tuesday, December 12, 2006 4:00 PM Subject: [rhelv5-beta-list] Xen DomUs Just for my own edification, has anyone managed to install a fully virtualized DomU with WinXP or Windows 2003?? I cant seem to get one to install completely which is quite frustrating. I can get virt-manager to create the DomU, and it does begin installing from CD, but after the Windows installer copies all its files, it reboots to load the full installer and at that point it fails because it can no longer see the CD. I have tried adding a cdrom line that points to /dev/hdc and then tried one that pointed to /media/cdrom after mounting the cdrom to that mt. point, but no joy. So anyone try this, or am I just insane? Of course, my network installed RHEL5 DomUs work perfectly. I haven't tried any other OSs yet. Is there a list of supported OSs available anywhere on Red Hat.com yet?? Cheers Jeff Jeffrey Lane <--> W4KDH Software Engineer IBM eServer xSeries Research Triangle Park, NC 27709 ------------------------------------------------------------------------ ------ _______________________________________________ rhelv5-beta-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-beta-list -------------- next part -------------- An HTML attachment was scrubbed... URL: https://www.redhat.com/archives/rhelv5-beta-list/attachments/20061212/63 594a0e/attachment.html ------------------------------ Message: 6 Date: Tue, 12 Dec 2006 10:39:20 -0500 From: Jan Mark Holzer <[EMAIL PROTECTED]> Subject: Re: [rhelv5-beta-list] Xen, ParaVirt and PAE Extensions To: "Red Hat Enterprise Linux 5 (Tikanga) Beta releases discussion mailing-list" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi Brian, the decision to only support PAE capable hosts was made at the end of the FC5 cycle. The majority (if not all) of server in customer datacenters/environments are PAE capable today and the only edge case for non-PAE support would have been "older" laptops which do not yet have PAE capable processors. It also would have been an additional burden for QA/QE to test/certify older non-PAE capable servers. As the use case for Xen is certainly geared towards servers and not laptops this made a lot of sense. However there are quite a number of folks with laptops which do not support PAE and at this time you have two options. either get a PAE capable laptop :) or you could build your own customer kernel-xen/Xen packages/RPMs and disable PAE for them. However the use case for a non-PAE installation is pretty limited as you'd also have to build your own installation tree with a non-PAE PV guest etc.... Hth, Jan Brian Long wrote: > Can someone more familiar with Xen development help me understand why > PAE extensions are now required? I remember running FC rawhide Xen on > my IBM Thinkpad 42P (Intel Pentium M w/o PAE) and I got paravirt working > (6-9 months ago, I believe). Now it seems PAE is hard-coded in the RHEL > 5 and FC6 kernels so I'm SOL. > > Thanks. > > /Brian/ > ------------------------------ Message: 7 Date: Tue, 12 Dec 2006 10:47:42 -0500 From: Brian Long <[EMAIL PROTECTED]> Subject: Re: [rhelv5-beta-list] Xen, ParaVirt and PAE Extensions To: [EMAIL PROTECTED], Red Hat "Enterprise Linux 5 (Tikanga) Beta releases discussion mailing-list" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain Thanks for the quick response Jan. You may want to check your mail client's word-wrap settings. :) I understand the PAE decision and appreciate the reasoning. /Brian/ On Tue, 2006-12-12 at 10:39 -0500, Jan Mark Holzer wrote: > Hi Brian, > > the decision to only support PAE capable hosts was made at the end > of the FC5 cycle. The majority (if not all) > of server in customer datacenters/environments are PAE capable today > and the only edge case for non-PAE > support would have been "older" laptops which do not yet have PAE > capable processors. > It also would have been an additional burden for QA/QE to > test/certify older non-PAE capable servers. > As the use case for Xen is certainly geared towards servers and not > laptops this made a lot of sense. > However there are quite a number of folks with laptops which do not > support PAE and at this time you > have two options. either get a PAE capable laptop :) or you could > build your own customer kernel-xen/Xen > packages/RPMs and disable PAE for them. > However the use case for a non-PAE installation is pretty limited as > you'd also have to build your > own installation tree with a non-PAE PV guest etc.... > > Hth, > > Jan > > Brian Long wrote: > > Can someone more familiar with Xen development help me understand why > > PAE extensions are now required? I remember running FC rawhide Xen on > > my IBM Thinkpad 42P (Intel Pentium M w/o PAE) and I got paravirt working > > (6-9 months ago, I believe). Now it seems PAE is hard-coded in the RHEL > > 5 and FC6 kernels so I'm SOL. > > > > Thanks. > > > > /Brian/ > > > > _______________________________________________ > rhelv5-beta-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/rhelv5-beta-list -- Brian Long | | IT Infrastructure . | | | . | | | . Data Center Systems ' ' Cisco Enterprise Linux C I S C O ------------------------------ _______________________________________________ rhelv5-beta-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-beta-list End of rhelv5-beta-list Digest, Vol 5, Issue 14 *********************************************** ********************************************************* THIS ELECTRONIC MAIL MESSAGE AND ANY ATTACHMENT IS CONFIDENTIAL AND MAY CONTAIN LEGALLY PRIVILEGED INFORMATION INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR INDIVIDUALS NAMED ABOVE. If the reader is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the sender to notify us of the error and delete the original message. Thank You. ********************************************************* _______________________________________________ rhelv5-beta-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-beta-list
