Because of the problem I am having I think I must be missing something basic, but it eludes me. I''m attempting to install hvm guests on SXDE (v79) Windows XP and OpenBSD went on easily, but when I try FreeBSD, Fedora or Debian I get the same problem. Using virt-install the installation creates the disk file, creates the domain, asks for the vnc password and pops up the vnc window. This displays Plex86/Bochs BIOS header, detects ata0 and ata1 and then hangs with no further action (apart from 100% cpu usage as indicated by xm top) The command I''m using is virt-install -n OpenBSD --hvm -r 768 -s 10 --vnc -f /export/disks/OpenBSD.img -m 52:54:00:12:72:AB -l /dev/dsk/c1t0d0s2 --noacpi -d obviously with the name and disk image name being changed between OSes. It asks for the virtual CD, which I give as /dev/dsk/c1t0d0s2 and for XP and OpenBSD away it goes happily. My thoughts are along the lines that the installers are trying to do some clever GUI stuff (OpenBSD is blessedly CLI based) but thoughts/comments greatly appreciated. John -- John Landamore School of Mathematics & Computer Science University of Leicester University Road, LEICESTER, LE1 7RH J.Landamore@mcs.le.ac.uk Phone: +44 (0)116 2523410 Fax: +44 (0)116 2523604
> Because of the problem I am having I think I must be > missing something > basic, but it eludes me. > > I''m attempting to install hvm guests on SXDE (v79) > Windows XP and > penBSD went on easily, but when I try FreeBSD, Fedora > or Debian I get the > same problem.Check it:- http://opensolaris.org/os/community/xen/docs/relnotes/ I believe you will find several CRs concerning HVM DomUs at Solaris Dom0.> > Using virt-install the installation creates the disk > file, creates the > domain, asks for the vnc password and pops up the vnc > window. This > displays Plex86/Bochs BIOS header, detects ata0 and > ata1 and then hangs > with no further action (apart from 100% cpu usage as > indicated by xm top) > > The command I''m using is > > virt-install -n OpenBSD --hvm -r 768 -s 10 --vnc -f > /export/disks/OpenBSD.img -m 52:54:00:12:72:AB -l > /dev/dsk/c1t0d0s2 > --noacpi -d > > obviously with the name and disk image name being > changed between OSes. > It asks for the virtual CD, which I give as > /dev/dsk/c1t0d0s2 and for XP > and OpenBSD away it goes happily. > > My thoughts are along the lines that the installers > are trying to do some > clever GUI stuff (OpenBSD is blessedly CLI based) but > thoughts/comments > greatly appreciated. > > John > > -- > John Landamore > > School of Mathematics & Computer Science > University of Leicester > University Road, LEICESTER, LE1 7RH > J.Landamore@mcs.le.ac.uk > Phone: +44 (0)116 2523410 Fax: +44 (0)116 > 2523604 > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.orgThis message posted from opensolaris.org
On Wed, Apr 16, 2008 at 03:16:04PM +0100, J. A. Landamore wrote:> virt-install -n OpenBSD --hvm -r 768 -s 10 --vnc -f > /export/disks/OpenBSD.img -m 52:54:00:12:72:AB -l /dev/dsk/c1t0d0s2 > --noacpi -dI doubt this will help, but you shouldn''t use -l for HVM guests. Just replace it with -c regards john
View:- http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=622 This message posted from opensolaris.org
To succeed with HVM FreeBSD 7.0 DomU install you will have to move to Xen 3.2 Linux Dom0. I''ve received positive feeds regarding mentioned install for Xen 3.2 Ubuntu Hardy Heron Dom0 (kernel 2.6.24) at xen-users at lists dot xensource dot com. This message posted from opensolaris.org