Hi, I am trying to install guest system on sun xVM xen0. I am using virt install to create a hvm guest , which uses zvol as storage. The problem is i get: Starting install... libvir: Xen Daemon error : GET operation failed: libvir: Xen Daemon error : GET operation failed: Creating domain... 0 B 00:02 Domain installation still in progress. You can reconnect to the console to complete the installation process. Still domU apears to be created. bash-3.2# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1727 2 r----- 87.3 oki 1 256 1 r----- 1.6 But when i try to connect it fails. bash-3.2# xm cons oki /usr/lib/xen/bin/xenconsole: Could not read tty from store: No such file or directory Is there a way to solve it? Best regards, mjb -- [ -----< Maciej Jan Broniarz || gausus@gausus.net >------ ] | Siamo qui \ sotto la stessa luce \ sotto la sua croce \ | | cantando ad una voce \ E l''Emmanuel Emmanuel, Emmanuel, | [ ---------------< E l''Emmanuel, Emmanuel >-------------- ]
Could you,please, provide outputs :- # svcs -a|grep xvm # dladm show-dev # svccfg -s xend listprop and virt-install command line This message posted from opensolaris.org
2008/4/24 Boris Derzhavets <bderzhavets@yahoo.com>:> Could you,please, provide outputs :- > > # svcs -a|grep xvm > # dladm show-dev > # svccfg -s xend listprop > > and virt-install command lineHere they are: bash-3.2# svcs -a|grep xvm online 16:15:02 svc:/system/xvm/store:default online 16:15:16 svc:/system/xvm/xend:default online 16:15:16 svc:/system/xvm/console:default online 16:15:18 svc:/system/xvm/domains:default bash-3.2# dladm show-dev LINK STATE SPEED DUPLEX nge0 up 1000Mb full nge1 unknown 0Mb unknown bash-3.2# svccfg -s xend listprop config application config/default-nic astring config/dom0-cpus integer 0 config/dom0-min-mem integer 196 config/enable-dump boolean true config/stability astring Unstable config/xend-relocation-address astring 127.0.0.1 config/xend-relocation-hosts-allow astring ^localhost$ config/xend-relocation-server boolean true config/xend-unix-server boolean true config/vncpasswd astring MacRagge75 config/vnc-listen astring 0.0.0.0 xenstored dependency xenstored/entities fmri svc:/system/xvm/store xenstored/grouping astring require_all xenstored/restart_on astring restart xenstored/type astring service general framework general/entity_stability astring Unstable general/single_instance boolean true start method start/exec astring "/lib/svc/method/xend %m" start/timeout_seconds count 0 start/type astring method stop method stop/exec astring :kill stop/timeout_seconds count 60 stop/type astring method tm_common_name template tm_common_name/C ustring "Hypervisor Control Daemon" tm_man_xend template tm_man_xend/manpath astring /usr/share/man tm_man_xend/section astring 1M tm_man_xend/title astring xend My virt-install looks like that: virt-install --accelerate --os-type=unix -vnc -r 1024 -f /dev/zvol/dsk/tank/oki-domU --vnc --vncport=6002 --cdrom=/tank/iso/7.0-RELEASE-amd64-disc1.iso -n test I have managed to start a domU with freebsd but it fails just after starting. Screenshot is here: http://gausus.net/snv/xvm-snv87.jpg I would be thantful for any help. -- [ -----< Maciej Jan Broniarz || gausus@gausus.net >------ ] | Siamo qui \ sotto la stessa luce \ sotto la sua croce \ | | cantando ad una voce \ E l''Emmanuel Emmanuel, Emmanuel, | [ ---------------< E l''Emmanuel, Emmanuel >-------------- ]
> 2008/4/24 Boris Derzhavets <bderzhavets@yahoo.com>: > > Could you,please, provide outputs :- > > > > # svcs -a|grep xvm > > # dladm show-dev > > # svccfg -s xend listprop > > > > and virt-install command line > > Here they are: > > > bash-3.2# svcs -a|grep xvm > online 16:15:02 svc:/system/xvm/store:default > online 16:15:16 svc:/system/xvm/xend:default > online 16:15:16 > svc:/system/xvm/console:default > online 16:15:18 > svc:/system/xvm/domains:default > bash-3.2# dladm show-dev > LINK STATE SPEED DUPLEX > nge0 up 1000Mb full > nge1 unknown 0Mb unknown > bash-3.2# svccfg -s xend listprop > config application > config/default-nic astring************************ I guess you skipped:- ************************ # svccfg -s xvm/xend setprop config/default-nic="nge0" # svcadm refresh xvm/xend # svcadm restart xvm/xend> config/dom0-cpus integer 0 > config/dom0-min-mem integer 196 > config/enable-dump boolean true > config/stability astring Unstable > config/xend-relocation-address astring > 127.0.0.1 > onfig/xend-relocation-hosts-allow astring > ^localhost$ > onfig/xend-relocation-server boolean true > config/xend-unix-server boolean true > config/vncpasswd astring > MacRagge75 > onfig/vnc-listen astring 0.0.0.0 > xenstored dependency > xenstored/entities fmri > svc:/system/xvm/store > tored/grouping astring require_all > xenstored/restart_on astring restart > xenstored/type astring service > general framework > general/entity_stability astring Unstable > general/single_instance boolean true > start method > start/exec astring > "/lib/svc/method/xend %m" > tart/timeout_seconds count 0 > start/type astring method > stop method > stop/exec astring :kill > stop/timeout_seconds count 60 > stop/type astring method > tm_common_name template > tm_common_name/C ustring > "Hypervisor Control Daemon" > m_man_xend template > tm_man_xend/manpath astring > /usr/share/man > m_man_xend/section astring 1M > tm_man_xend/title astring xend > > > > My virt-install looks like that: > virt-install --accelerate --os-type=unix -vnc -r 1024 > -f /dev/zvol/dsk/tank/oki-domU --vnc --vncport=6002 > --cdrom=/tank/iso/7.0-RELEASE-amd64-disc1.iso -n testI would try to create HVM DomU as follows. ************************* Fist window session: ************************* # virt-install --os-type=unix --vnc --hvm -r 1024 \ -f /dev/zvol/dsk/tank/oki-domU \ -c /tank/iso/7.0-RELEASE-amd64-disc1.iso --name test ***************************** Second window session: ***************************** # vncviewer localhost:0> > > I have managed to start a domU with freebsd but it > fails just after starting. > Screenshot is here: > > http://gausus.net/snv/xvm-snv87.jpg > > I would be thantful for any help. > > > > -- > [ -----< Maciej Jan Broniarz || gausus@gausus.net > >------ ] > | Siamo qui \ sotto la stessa luce \ sotto la sua > croce \ | > | cantando ad una voce \ E l''Emmanuel Emmanuel, > Emmanuel, | > [ ---------------< E l''Emmanuel, Emmanuel > >-------------- ] > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.orgThis message posted from opensolaris.org
If it hangs again, i would try to add:- --debug at the end. It helped me a lot for paravirtual guests in nographics mode , HVM guest by default uses graphical console at Dom0. I would remove --vnc and try to add:- --nographics --debug Two links may be helpful:- http://www.opensolaris.org/os/community/xen/docs/virtinstall/ Search for "hvm" at the page:- http://www.opensolaris.org/os/community/xen/docs/relnotes This message posted from opensolaris.org
> ************************* > Fist window session: > *************************# virt-install --os-type=unix --vnc --hvm -r 1024 \ -f /dev/zvol/dsk/tank/oki-domU \ -c /tank/iso/7.0-RELEASE-amd64-disc1.iso --name test Sorry, i don''t remember exactly :- Vnc authorization window may come up automatically at SNV Dom0 during virt-install run. Schema described is for xm''s profiles at Linux Dom0s :- # xm create guest.hvm Guest started # ***************************** Second window session: ***************************** # vncviewer localhost:0 That''s why my intend would be to perform yours HVM install at Xen 3.2 CentOS 5.1 Dom0. Much more chance to succeed ( ofcourse in my personal opinion). This message posted from opensolaris.org
> ************************* > Fist window session: > ************************* > # virt-install --os-type=unix --vnc --hvm -r 1024 \ > -f /dev/zvol/dsk/tank/oki-domU \ > -c /tank/iso/7.0-RELEASE-amd64-disc1.iso --name testI get the following error: Starting install... libvir: Xen Daemon error : GET operation failed: libvir: Xen Daemon error : GET operation failed: Creating domain... 0 B 00:01 Traceback (most recent call last): File "/usr/bin/virt-install", line 657, in ? main() File "/usr/bin/virt-install", line 606, in main dom = guest.start_install(conscb,progresscb) File "/export/builds/xvm_87/proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 638, in start_install File "/export/builds/xvm_87/proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 682, in _do_install File "/usr/bin/virt-install", line 491, in show_console return vnc_console(dom) File "/usr/bin/virt-install", line 455, in vnc_console print >> sys.stderr, "Unable to connect to graphical console; DISPLAY is not set. Please connect to %s:%d" %(vnchost, vncport) UnboundLocalError: local variable ''vnchost'' referenced before assignment Still i can connect via vnc, but freebsd installer fails. Maybe it is some acpi-related issue? Thanks for your help gausus -- [ -----< Maciej Jan Broniarz || gausus@gausus.net >------ ] | Siamo qui \ sotto la stessa luce \ sotto la sua croce \ | | cantando ad una voce \ E l''Emmanuel Emmanuel, Emmanuel, | [ ---------------< E l''Emmanuel, Emmanuel >-------------- ]
Not sure , this is the best test:- If you have defined default-nic - "nge0", just try to start virt-install HVM SNV87 DomU at SNV87 Dom0 and see what happens. This message posted from opensolaris.org
Run also:- # ifconfig -a to find out IP at Dom0 This message posted from opensolaris.org
2008/4/25 Boris Derzhavets <bderzhavets@yahoo.com>:> Not sure , this is the best test:- > If you have defined default-nic - "nge0", > just try to start virt-install HVM SNV87 DomU at SNV87 Dom0 > and see what happens. >Ok. Trying to to that and it works pretty nice so far. gausus> > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >-- [ -----< Maciej Jan Broniarz || gausus@gausus.net >------ ] | Siamo qui \ sotto la stessa luce \ sotto la sua croce \ | | cantando ad una voce \ E l''Emmanuel Emmanuel, Emmanuel, | [ ---------------< E l''Emmanuel, Emmanuel >-------------- ]
OK. I believe, HVM FreeBSD 7.0 is going to be an issue. I will give it a try at F8 Dom0 (64-bit) via virt-install and at Xen 3.2 CentOS 5.1 Dom0 (64-bit) utilizing normal phyton profile for Xen Manager for HVM DomUs as soon as i get FreeBSD 7.0 (amd64) DVD. This message posted from opensolaris.org
Boris Derzhavets wrote:> OK. I believe, HVM FreeBSD 7.0 is going to be an issue. > I will give it a try at F8 Dom0 (64-bit) via virt-install and > at Xen 3.2 CentOS 5.1 Dom0 (64-bit) utilizing normal phyton > profile for Xen Manager for HVM DomUs as soon as i get > FreeBSD 7.0 (amd64) DVD. > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >DVD? You mean from freebsdmall cause they don''t seed DVD''s in the tubes... I guess I''ll try it, but I still am on B86. They release too often -_- I guess I''ll bfu. BFU''s contain xVM bits right? James
On 25 Apr 2008, at 1:50pm, James Cornell wrote:> I guess I''ll bfu. BFU''s contain xVM bits right?They contain the onnv-gate bits, but not the xvm-gate bits (i.e. they have the Solaris half but not the Xen half).
James, I just ordered FreeBSD 7.0 (amd64) DVD ( 3 CDs set would be a head ache ) , got a positive answer and will get it for sure in 10-12 days. No idea how it will be cooked. The cost is about $10. I would be happy to be able to order Nevada Builds even it would cost me $40-50 (if i need particular build) , but i cannot find this option at opensolaris.org. Thanks. -b. This message posted from opensolaris.org
View:- http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=622 This message posted from opensolaris.org
I am not sure how much OpenBSD 4.2 differs from FreeBSD 7.0 :-) However, some positive feeds regarding HVM OpenBSD DomUs on Xen may viewed at:- http://www.nabble.com/OpenBSD-as-Xen--domU-td15323353.html 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@lists.xensource.com. This message posted from opensolaris.org
Per http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=622 # make world vmxassist=n # make install Creates Xen 3.2 kernel , which is supposed to run HVM FreeBSD 7.0 DomU at CentOS 5.1 Dom0. This message posted from opensolaris.org
2008/4/26 Boris Derzhavets <bderzhavets@yahoo.com>:> Per >Hi> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=622 > # make world vmxassist=n > # make install > Creates Xen 3.2 kernel , which is supposed to run HVM FreeBSD 7.0 DomU > at CentOS 5.1 Dom0. > >I am trying to start snv_87 domU on ubuntu dom0 running xen3.2 root@niemiec:~# xm create elendil.sxp Using config file "/etc/xen/elendil.sxp". Error: Device 5632 (vbd) could not be connected. losetup -r /dev/loop10 /pub/sol-nv-b87-x86-dvd.iso faile the file permisions are fine, and my config looks like that: root@niemiec:~# cat /etc/xen/elendil.sxp name = "elendil" builder = "hvm" memory = "1024" disk = [''phy:/dev/vol1/elendil,ioemu:hda,w'',''file:/pub/sol-nv-b87-x86-dvd.iso,hdc:cdrom,r''] vif = [ ''type=ioemu,bridge=eth0'' ] device_model = "/usr/lib/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" vnc=1 boot="d" vcpus=1 serial = "pty" # enable serial console on_reboot = ''restart'' on_crash = ''restart'' There are no images mounting using losetup. What might be the problem? gausus> > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >-- [ -----< Maciej Jan Broniarz || gausus@gausus.net >------ ] | Siamo qui \ sotto la stessa luce \ sotto la sua croce \ | | cantando ad una voce \ E l''Emmanuel Emmanuel, Emmanuel, | [ ---------------< E l''Emmanuel, Emmanuel >-------------- ]
To respond you i have to know Ubuntu version and the way how Xen 3.2 has been installed. Same install at Xen 3.2 CentOS 5.1 Dom0 run smoothly. This message posted from opensolaris.org
Just in case, give extension name to your profile different from *.sxp. Say *.hvm. This message posted from opensolaris.org
2008/4/27 Boris Derzhavets <bderzhavets@yahoo.com>:> To respond you i have to know Ubuntu version and the way how Xen 3.2 has been > installed. Same install at Xen 3.2 CentOS 5.1 Dom0 run smoothly. > >i am using xen from ubuntu packages. All i did was apt-get install ubuntu-xen-server i have also configured it, use bridge network, instead of dummy bridge The problem that occur, is weird to me. Why it would not want to mount an iso image. btw. someting like this was in my dmesg: [ 7449.446769] (cdrom_add_media_watch() file=/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/blkback/cdrom.c, line=112) nodename:backend/vbd/5/768 [ 7449.446778] (cdrom_is_type() file=/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/xen/blkback/cdrom.c, line=97) type:0 Thanks for Your''s help gausus> > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >-- [ -----< Maciej Jan Broniarz || gausus@gausus.net >------ ] | Siamo qui \ sotto la stessa luce \ sotto la sua croce \ | | cantando ad una voce \ E l''Emmanuel Emmanuel, Emmanuel, | [ ---------------< E l''Emmanuel, Emmanuel >-------------- ]
> 2008/4/26 Boris Derzhavets <bderzhavets@yahoo.com>: > > Per > > > Hi > > > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id > =622 > > # make world vmxassist=n > > # make install > > Creates Xen 3.2 kernel , which is supposed to > run HVM FreeBSD 7.0 DomU > > at CentOS 5.1 Dom0. > > > > > I am trying to start snv_87 domU on ubuntu dom0 > running xen3.2 > > root@niemiec:~# xm create elendil.sxp > Using config file "/etc/xen/elendil.sxp". > Error: Device 5632 (vbd) could not be connected. > losetup -r /dev/loop10 /pub/sol-nv-b87-x86-dvd.iso failedJust now i ran:- # losetup -r /dev/loop7 /usr/lib/xen-solaris/snv87.iso on Ubuntu 7.10 with no problems. However, man losetup says:- FILES /dev/loop0, /dev/loop1, ... loop devices (major=7) I don''t have Ubuntu Hardy Heron installed. Check for device /dev/loop10. Does it exists on Ubuntu 8.04 ?> > the file permisions are fine, and my config looksThis message posted from opensolaris.org
If yes,then run:- # losetup -r /dev/loop10 /pub/snv87.iso See what happens ? This message posted from opensolaris.org
2008/4/27 Boris Derzhavets <bderzhavets@yahoo.com>:> If yes,then run:- > # losetup -r /dev/loop10 /pub/snv87.iso > See what happens ? >root@niemiec:/dev# losetup -r /dev/loop10 /pub/sol-nv-b87-x86-dvd.iso root@niemiec:/dev# losetup -a /dev/loop0: [fe02]:24577 (/pub/sol-nv-b87-x86-dvd.iso) /dev/loop1: [fe02]:24577 (/pub/sol-nv-b87-x86-dvd.iso) /dev/loop2: [fe02]:24577 (/pub/sol-nv-b87-x86-dvd.iso) /dev/loop10: [fe02]:24577 (/pub/sol-nv-b87-x86-dvd.iso) /dev/loop11: [fe02]:24577 (/pub/sol-nv-b87-x86-dvd.iso) /dev/loop12: [fe02]:24577 (/pub/sol-nv-b87-x86-dvd.iso)> > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >-- [ -----< Maciej Jan Broniarz || gausus@gausus.net >------ ] | Siamo qui \ sotto la stessa luce \ sotto la sua croce \ | | cantando ad una voce \ E l''Emmanuel Emmanuel, Emmanuel, | [ ---------------< E l''Emmanuel, Emmanuel >-------------- ]
It doesn''t look good for me. I would expect just one entry:- root@boris-desktop:~# losetup -a /dev/loop7: [080b]:1966915 (/usr/lib/xen-solaris/snv87.iso) This message posted from opensolaris.org
2008/4/27 Boris Derzhavets <bderzhavets@yahoo.com>:> It doesn''t look good for me. I would expect just one entry:- > root@boris-desktop:~# losetup -a > /dev/loop7: [080b]:1966915 (/usr/lib/xen-solaris/snv87.iso) >Yes, it is weird. Is there a way to debug it? It apears, that xen tries to mount an image sevral times before finaly giving up.> > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >-- [ -----< Maciej Jan Broniarz || gausus@gausus.net >------ ] | Siamo qui \ sotto la stessa luce \ sotto la sua croce \ | | cantando ad una voce \ E l''Emmanuel Emmanuel, Emmanuel, | [ ---------------< E l''Emmanuel, Emmanuel >-------------- ]
Post it on Ubuntu Forums first. It looks like OS issue. This message posted from opensolaris.org
> 2008/4/27 Boris Derzhavets <bderzhavets@yahoo.com>: > > It doesn''t look good for me. I would expect just > one entry:- > > root@boris-desktop:~# losetup -a > > /dev/loop7: [080b]:1966915 > (/usr/lib/xen-solaris/snv87.iso) > > > > Yes, it is weird. Is there a way to debug it? It > apears, that xen > tries to mount an image sevral times before finaly > giving up.It''s a bug. View:- http://ubuntuforums.org/showthread.php?t=770902> > > > > > > > > This message posted from opensolaris.org > > _______________________________________________ > > xen-discuss mailing list > > xen-discuss@opensolaris.org > > > > > > -- > [ -----< Maciej Jan Broniarz || gausus@gausus.net > >------ ] > | Siamo qui \ sotto la stessa luce \ sotto la sua > croce \ | > | cantando ad una voce \ E l''Emmanuel Emmanuel, > Emmanuel, | > [ ---------------< E l''Emmanuel, Emmanuel > >-------------- ] > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.orgThis message posted from opensolaris.org
HVM FreeBSD 7.0 (i386) DomU installed at Xen 3.2.1 CentOS 5.1 Dom0 (64-bit) with no problems. Singe DVD ISO for FreeBSD 7.0 has been used for install. SSH conections from DomU to Dom0 and vice verca have been tested OK. I''ll atach a couple of screenshots shortly. Disabling VMXASSIST in Xen 3.2.1 has been tested for :- 1. Solaris 08/07 HVM DomU (32-bit) 2. FreeBSD 7.0 HVM DomU (32-bit) However, i was not able to create 64-bit DomUs in both case. This message posted from opensolaris.org
Runtime snapshots. SSH connections: 1.Free BSD DomU to Dom0 2.Dom0 to Free BSD DomU 3.HVM S10U4 DomU to HVM FreeBSD 7 DomU This message posted from opensolaris.org
[This email is either empty or too large to be displayed at this time]
2008/4/30 Boris Derzhavets <bderzhavets@yahoo.com>:> HVM FreeBSD 7.0 (i386) DomU installed at Xen 3.2.1 CentOS 5.1 Dom0 (64-bit) > with no problems. Singe DVD ISO for FreeBSD 7.0 has been used for install. > SSH conections from DomU to Dom0 and vice verca have been tested OK. > I''ll atach a couple of screenshots shortly. > Disabling VMXASSIST in Xen 3.2.1 has been tested for :- > 1. Solaris 08/07 HVM DomU (32-bit) > 2. FreeBSD 7.0 HVM DomU (32-bit) > However, i was not able to create 64-bit DomUs in both case. >You suggest using xen built from source. Are there any problems during an upgrade. I need to deploy a rather productional enviroment. I wonder, is it possible, that some serious problems will occur while upgrading to a next xen release. gausus> This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org >-- [ -----< Maciej Jan Broniarz || gausus@gausus.net >------ ] | Siamo qui \ sotto la stessa luce \ sotto la sua croce \ | | cantando ad una voce \ E l''Emmanuel Emmanuel, Emmanuel, | [ ---------------< E l''Emmanuel, Emmanuel >-------------- ]
Maciej,
As of November 2007 RH had made a decision stop forward porting
Xen (2.6.18) to 2.6.24 (and higher) kernels and work on so called
pv_ops. At mean time F9 has it implemented only for 32-bit DomUs.
pv_ops implementation for Dom0 is scheduled for F10 (2.6.25)
In my very personal opinion, RHEL 5.1 as well as F8 provides
Enterprise Class Xen Virtualization solutions right now.
You can go another way and purchase XenServer from Citrix directly.
If you want to be safe you have to make a deal with Leading Xen vendors.
If your primery concern is FreeBSD HVM DomUs i would look for
decision from Citrix directly. I am also aware about one shop runningFreeBSD HVM
DomUs (32 and 64-bit) at Ubuntu 8.04 Dom0 (64-bit).
on AMD boxes .
I don''t have any idea, what kind of patching has been done for
this
particular "Super Ubuntu 8 Phenomen". Just remind your own experience
with Ubuntu 8.04.
I also point your attention to the fact , that Xen 3.2.1 broke backward
compatibility with Xen 3.1.2. However , Xen 3.1 doesn''t allow FreeBSD
to run in HVM Domain. Xen 3.2 allows to disable VMXASSIST and
in Xen 3.3 VMXASSIST will be disabled by default.
Have a nice time.
-b.
--- On Wed, 4/30/08, Maciej Jan Broniarz wrote:
> From: Maciej Jan Broniarz
> Subject: Re: [xen-discuss] Disabling VMXASSIST in Xen 3.2.1 tested OK.
> To: "Boris Derzhavets"
> Cc: xen-discuss@opensolaris.org
> Date: Wednesday, April 30, 2008, 7:22 AM
> 2008/4/30 Boris
Derzhavets :
> > HVM FreeBSD 7.0 (i386) DomU installed at Xen 3.2.1
> CentOS 5.1 Dom0 (64-bit)
> > with no
problems. Singe DVD ISO for FreeBSD 7.0 has
> been used for install.
> > SSH conections from DomU to Dom0 and vice verca have
> been tested OK.
> > I''ll atach a couple of screenshots shortly.
> > Disabling VMXASSIST in Xen 3.2.1 has been tested for
> :-
> > 1. Solaris 08/07 HVM DomU (32-bit)
> > 2. FreeBSD 7.0 HVM DomU (32-bit)
> > However, i was not able to create 64-bit DomUs in
> both case.
> >
>
> You suggest using xen built from source. Are there any
> problems during
> an upgrade. I need to deploy a rather productional
> enviroment. I
> wonder, is it possible, that some serious problems will
> occur while
> upgrading to a next xen release.<
br>>
> gausus
> > This message posted from opensolaris.org
> > _______________________________________________
> > xen-discuss
mailing list
> > xen-discuss@opensolaris.org
> >
>
>
>
> --
> [ -----< Maciej Jan Broniarz || gausus@gausus.net
> >------ ]
> | Siamo qui \ sotto la stessa luce \ sotto la sua
> croce \ |
> | cantando ad una voce \ E l''Emmanuel Emmanuel,
> Emmanuel, |
> [ ---------------< E l''Emmanuel, Emmanuel
> >-------------- ]
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
Boris Derzhavets wrote:> Maciej, > As of November 2007 RH had made a decision stop forward porting > Xen (2.6.18) to 2.6.24 (and higher) kernels and work on so called > pv_ops. At mean time F9 has it implemented only for 32-bit DomUs. > pv_ops implementation for Dom0 is scheduled for F10 (2.6.25) > In my very personal opinion, RHEL 5.1 as well as F8 provides > Enterprise Class Xen Virtualization solutions right now. > You can go another way and purchase XenServer from Citrix directly. > If you want to be safe you have to make a deal with Leading Xen vendors. > If your primery concern is FreeBSD HVM DomUs i would look for > decision from Citrix directly. I am also aware about one shop running > FreeBSD HVM DomUs (32 and 64-bit) at Ubuntu 8.04 Dom0 (64-bit). > on AMD boxes . > I don''t have any idea, what kind of patching has been done for this > particular "Super Ubuntu 8 Phenomen". Just remind your own experience > with Ubuntu 8.04. > I also point your attention to the fact , that Xen 3.2.1 broke > backward compatibility with Xen 3.1.2. However , Xen 3.1 doesn''t allow > FreeBSD > to run in HVM Domain. Xen 3.2 allows to disable VMXASSIST and > in Xen 3.3 VMXASSIST will be disabled by default. > Have a nice time. > -b. > > > --- On Wed, 4/30/08, Maciej Jan Broniarz <gausus@gausus.net> wrote: > > > From: Maciej Jan Broniarz <gausus@gausus.net> > > Subject: Re: [xen-discuss] Disabling VMXASSIST in Xen 3.2.1 tested OK. > > To: "Boris Derzhavets" <bderzhavets@yahoo.com> > > Cc: xen-discuss@opensolaris.org > > Date: Wednesday, April 30, 2008, 7:22 AM > > 2008/4/30 Boris Derzhavets <bderzhavets@yahoo.com>: > > > HVM FreeBSD 7.0 (i386) DomU installed at Xen 3.2.1 > > CentOS 5.1 Dom0 (64-bit) > > > with no problems. Singe DVD ISO for FreeBSD 7.0 has > > been used for install. > > > SSH conections from DomU to Dom0 and vice verca have > > been tested OK. > > > I''ll atach a couple of screenshots shortly. > > > Disabling VMXASSIST in Xen 3.2.1 has been tested for > > :- > > > 1. Solaris 08/07 HVM DomU (32-bit) > > > 2. FreeBSD 7.0 HVM DomU (32-bit) > > > However, i was not able to create 64-bit DomUs in > > both case. > > > > > > > You suggest using xen built from source. Are there any > > problems during > > an upgrade. I need to deploy a rather productional > > enviroment. I > > wonder, is it possible, that some serious problems will > > occur while > > upgrading to a next xen release. > > > > gausus > > > This message posted from opensolaris.org > > > _______________________________________________ > > > xen-discuss mailing list > > > xen-discuss@opensolaris.org > > > > > > > > > > > -- > > [ -----< Maciej Jan Broniarz || gausus@gausus.net > > >------ ] > > | Siamo qui \ sotto la stessa luce \ sotto la sua > > croce \ | > > | cantando ad una voce \ E l''Emmanuel Emmanuel, > > Emmanuel, | > > [ ---------------< E l''Emmanuel, Emmanuel > > >-------------- ] > > > ------------------------------------------------------------------------ > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try > it now. > <http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ%20> > > ------------------------------------------------------------------------ > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.orgThanks Boris. Quite annoying if you ask me. As much as I like Xen configuration wise (Extensibility and such) maybe this is why I just stick with VMware Server and equivalents. (Open)Solaris doesn''t have the luxury, and I''d rather see clients use Solaris to host their business, but if one of the needs is being able to run non-host OS'' in virtualization without using outdated Brand-Z guests, then so be it. :-( James
I see now. Similar issue as with cloning Xen 3.2 on Ubuntu 7.10 (Desktop)
Xen 3.2 needs Ubuntu Server 8.04 ( no Gnome environment).
View:-
*************************************************
http://www.osnews.com/thread?311754
*************************************************
I believe Ubuntu Server 8.04 would work for you.
FreeBSD 7.0 HVMs would run it text mode via tty console.
You might also need AMD based boxes. They are tolerant to
VMXASSIST status. Intel''s are not.
I would get it and start testing (QA) phases.
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
View:-
*************************************************
http://www.osnews.com/thread?311754
*************************************************
I believe Ubuntu Server 8.04 would work for you.
FreeBSD 7.0 HVMs would run it text mode via tty console.
You might also need AMD based boxes. They are tolerant to
VMXASSIST status. Intel''s are not.
I would get it and start testing (QA) phases.
--- On Wed, 4/30/08, Maciej Jan Broniarz wrote:
From: Maciej Jan Broniarz
S
ubject: Re: [xen-discuss] Disabling VMXASSIST in Xen 3.2.1 tested OK.
To: "Boris Derzhavets"
Cc:
xen-discuss@opensolaris.org
Date: Wednesday, April 30, 2008, 7:22 AM
2008/4/30 Boris Derzhavets :
> HVM FreeBSD 7.0 (i386) DomU installed at Xen 3.2.1 CentOS 5.1 Dom0
(64-bit)
> with no problems. Singe DVD ISO for FreeBSD 7.0 has been used for
install.
> SSH conections from DomU to Dom0 and vice verca have been tested OK.
> I''ll atach a couple of screenshots shortly.
> Disabling VMXASSIST in Xen 3.2.1 has been tested for :-
> 1. Solaris 08/07 HVM DomU (32-bit)
> 2. FreeBSD 7.0 HVM DomU (32-bit)
> However, i was not able to create 64-bit DomUs in both case.
>
You suggest using xen built from source. Are there any problems during
an upgrade. I need to deploy a rather p
roductional enviroment. I
wonder, is it possible, that some serious problems will occur while
upgrading to a next xen release.
gausus
> This message
posted from opensolaris.org
> _______________________________________________
> xen-discuss mailing list
> xen-discuss@opensolaris.org
>
--
[ -----< Maciej Jan Broniarz || gausus@gausus.net >------ ]
| Siamo qui \ sotto la stessa luce \ sotto la sua croce \ |
| cantando ad una voce \ E l''Emmanuel Emmanuel, Emmanuel, |
[ ---------------< E l''Emmanuel, Emmanuel >--------------
]
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.