Date: Sat, 4 Aug 2012 08:50:00 +0800 From: Wei Xu <wei.xu.prc@gmail.com> To: Sean Bruno <seanbru@yahoo-inc.com> Cc: "freebsd-xen@freebsd.org" <freebsd-xen@freebsd.org> Subject: Re: Compiling error for amd64 on FreeBSD9.0 with XENHVM when include xen console driver. Message-ID: <CAH=9XOaqFF9UgB=tkdgUfjotuc1BL_9wovRpFDL_Vd-u0sRCxg@mail.gmail.com> In-Reply-To: <1344010924.2552.7.camel@powernoodle.corp.yahoo.com> References: <CAH=9XOZBUxnChw9fUc92j7YqCaPaz2emvGHmsaA7TJWyjo1eZQ@mail.gmail.com> <1343844148.5229.1.camel@powernoodle.corp.yahoo.com> <CAH=9XOaZQx7tNmD6juGTThuYzodzdVnjM1iCm1EiNh1YneFYKA@mail.gmail.com> <1343929221.2573.5.camel@powernoodle.corp.yahoo.com> <CAH=9XOYN_jzK9jEngZWOcnX6oN1BfC3kycdDDYAAkabWvLvviw@mail.gmail.com> <1344010924.2552.7.camel@powernoodle.corp.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sean=EF=BC=8C Thanks=EF=BC=8Ci'll try it. On Saturday, August 4, 2012, Sean Bruno wrote: > > > > On Thu, 2012-08-02 at 19:21 -0700, Wei Xu wrote: > > My Dom0 is Oracle Linux(64bit too), Xen version is 4.0.2, I installed > > FreeBSD with the official iso image, that's > > "FreeBSD-9.0-RELEASE-i386-dvd1.iso", I'm not sure if it was started as > > HVM by default, how can i check it? > > > > If the VM started up at all, it had to be running via full hardware > virtualization. :-) > > > > How to convert it to PV support, i just compiled and installed the src > > with the "XEN" config in the source tree, I think that will include PV > > support, since "XEN" is defined in the options, right? > > > > Correct. You compile your i386 kernel with the XEN kernel config, then > you need to copy that kernel into your Dom0 and reconfigure the VM to be > PV and boot with no HVM options. I'm not sure how to do that with the > tools that you have access to, but I did this by editing the xen domU > config file for the virtual machine. Here's an example of my DomU > config for your reference. Of course, this is a Xen 3 hypervisor, so > your changes might have to be different( xl create vs xm create). > > > #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D > # Python configuration setup for 'xm create'. > # This script sets the parameters used when a domain is created using > 'xm create'. > # You use a separate script for each domain you want to create, or > # you can set the parameters for the domain on the xm command line. > > #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D > > > #------------------------------------------------------------------------= ---- > # Kernel image file. > #kernel =3D "/usr/lib/xen/boot/hvmloader" > kernel =3D "/var/virt/freebsd-9.current-i386-domu-kernel" > > > #------------------------------------------------------------------------= ---- > # device model to use: only qemu-dm available for now > #device_model =3D '/usr/lib64/xen/bin/qemu-dm' > > #builder=3D'hvm' > > # Initial memory allocation (in megabytes) for the new domain. > memory =3D 2048 > > # number of CPUS > vcpus =3D 1 > > # A name for your domain. All domains must have different names. > name =3D "ref9-xen32" > arch =3D "i386" > > #Network interface. By default emules a realtek 8139. For a NetBSD guest > you > # have to disable re(4) and let rtk attach to use it. > # ne2k_pci emulates a pci ne2000 clone; this his cpu-hungry in dom0 > # pcnet emulates a AMD PCnet-PCI controller; but it corrupts packets > with > # pcn(4) under NetBSD. > #vif =3D [ 'mac=3D00:16:3e:00:00:03, bridge=3Dxenbr0, type=3Dioemu' ] > vif =3D [ 'mac=3D00:16:3e:00:00:03, bridge=3Dxenbr0, type=3Dvbd' ] > > # Define the disk devices you want the domain to have access to, and > # what you want them accessible as. > # Each disk entry is of the form phy:UNAME,DEV,MODE > # where UNAME is the device, DEV is the device name the domain will see, > # and MODE is r for read-only, w for read-write. > # For hvm domains you can only use hda to hdd. You can set extra types > # (e.g. cdrom) > > disk =3D [ > 'file:/var/virt/ref9-xen32.bin,hda,w', > 'file:/var/virt/ref9-xen32_scratch.bin,hdb,w' > ] > # floppy images; this doesn't seem to work currently. Use a iso image > instead. > #fda =3D '/home/domains/boot1.fs' > > extra =3D "vfs.root.mountfrom=3Dufs:/dev/ad0p2,kern.hz=3D100" > > # boot device: a =3D floppy, c=3D hard drive, d=3D cdrom (with the disk e= ntry > # before) > # > # boot CDROM image > #boot=3D'd' > # boot from DISK file > #boot=3D'c' > # boot from DHCP/PXE then DISK file > boot=3D'nc' > > # By default, 'xm create' will try to open an X window on the current > display > # for the virtal framebuffer. You can have the virtal framebuffer in vnc > # instead, and connect using a vnc client (using localhost:$vncdisplay) > # If vncunused is set to 1 (this is the default value), vncdisplay > # will be set to the first unused port; so it's recommended to > #vnc =3D 1 > #vncdisplay =3D 3 > #vncunused =3D 1 > #vncpasswd=3D'' > > #Xen emulates a PS/2 mouse, but the pointer in the guest has > difficulties > # tracking the absolute position. Xen can emulate a USB tablet in > addition > # to the mouse which will report the absolute position of the pointer, > # and make the mouse much easier to use. > # > usb=3D1 > usbdevice=3D'tablet' > #usbdevice=3D'mouse' > > acpi =3D 1 > serial=3D'pty' > on_reboot=3D'restart' > > #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D > > > > > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAH=9XOaqFF9UgB=tkdgUfjotuc1BL_9wovRpFDL_Vd-u0sRCxg>