I''m unable to create a centos domU on Opensolaris 2009.6. I had no
problem following the instructions to make Solaris a dom0. The same
process worked just fine with the GUI virtual machine manager under
OpenSUSE 11.1. For a number of reasons I''d prefer to use Opensolaris
as my Dom0, but not if it going to be a battle to get everything to
work. Is Xen actually a production-quality system on Opensolaris?
with virtual machine manager
machine name: centos
paravirtualized
initial memory 1024 MB
Maximum memory 1024 MB
Virtual CPUs: 1
installation source http://.../MYDVD
which is the centos installation dvd
disk image: /rpool/vms/centosx
disk size: 9120 MB
network: shared physical device e1000g0
Unable to complete install ''libvirt.libvirtError virDomainCreateLinux()
failed POST operation failed: (xend.err "Error creating domain: (2,
''Invalid kernel'', ''xc_dom_parse_elf_kernel: ELF image
has no shstrtab\\n'')")
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/create.py", line 699, in
do_install
dom = guest.start_install(False, meter = meter)
File
"/export/builds/xvm_111a///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 923, in start_install
File
"/export/builds/xvm_111a///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 944, in _do_install
File "libvirt.py", line 585, in createLinux
if ret is None:raise libvirtError(''virDomainCreateLinux()
failed'', conn=self)
libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err
"Error creating domain: (2, ''Invalid kernel'',
''xc_dom_parse_elf_kernel: ELF image has no
shstrtab\\n'')")
attempt at manual creation:
virt-install --paravirt --name centos --ram 2038 --vnc --os-type=linux
--os-variant=rhel5 --network bridge --file /rpool/vms/centos --file-size=20
--location http://heidelberg.rutgers.edu/MYDVD/
Starting install...
Retrieving file .treeinfo 100% |=========================| 417 B 00:00
Retrieving file .treeinfo 100% |=========================| 417 B 00:00
Retrieving file .treeinfo 100% |=========================| 417 B 00:00
Retrieving file vmlinuz.. 100% |=========================| 1.9 MB 00:00
Retrieving file initrd.im 100% |=========================| 6.3 MB 00:00
virDomainCreateLinux() failed POST operation failed: (xend.err ''Device
0 (vkbd) could not be connected. Hotplug scripts not working.'')
Domain installation may not have been
successful. If it was, you can restart your domain
by running ''virsh start centos''; otherwise, please
restart your installation.
Fri, 12 Jun 2009 19:54:56 ERROR virDomainCreateLinux() failed POST operation
failed: (xend.err ''Device 0 (vkbd) could not be connected. Hotplug
scripts not working.'')
Traceback (most recent call last):
File "/usr/bin/virt-install", line 511, in ?
main()
File "/usr/bin/virt-install", line 471, in main
dom = guest.start_install(conscb,progresscb)
File
"/export/builds/xvm_111a///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 923, in start_install
File
"/export/builds/xvm_111a///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
line 944, in _do_install
File "libvirt.py", line 585, in createLinux
if ret is None:raise libvirtError(''virDomainCreateLinux()
failed'', conn=self)
libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err
''Device 0 (vkbd) could not be connected. Hotplug scripts not
working.'')
--
This message posted from opensolaris.org
Charles Hedrick wrote:> I''m unable to create a centos domU on Opensolaris 2009.6. I had no > problem following the instructions to make Solaris a dom0. The same > process worked just fine with the GUI virtual machine manager under > OpenSUSE 11.1. For a number of reasons I''d prefer to use Opensolaris > as my Dom0, but not if it going to be a battle to get everything to > work. Is Xen actually a production-quality system on Opensolaris?If your looking for production level support, see.. http://www.sun.com/service/opensolaris/ The bits in 2009.06 (3.1.4) do not support a VNC based para-virtualized graphics backend. The following should work for you.. virt-install --paravirt --name centos --ram 2038 ---nographics --os-type=linux --os-variant=rhel5 --network bridge --file /rpool/vms/centos --file-size=20 --location http://heidelberg.rutgers.edu/MYDVD/ A vnc para-virtualized frambuffer is support in our new bits They are based on 3.3.2-rc1 and are scheduled to be putback in b118. i.e. the following just worked for me. virt-install -n centos5.3 -r 800 -m XX:XX:XX:XX:XX:XX --vnc --noautoconsole -p -l http://heidelberg.rutgers.edu/MYDVD/ --disk path=/static/192.168.0.71/0/iqn.1986-03.com.sun:02:e772af32-5152-63fc-d833-cbd6eff121bb,driver=phy,subdriver=iscsi MRJ> with virtual machine manager > machine name: centos > paravirtualized > initial memory 1024 MB > Maximum memory 1024 MB > Virtual CPUs: 1 > > installation source http://.../MYDVD > which is the centos installation dvd > > disk image: /rpool/vms/centosx > disk size: 9120 MB > > network: shared physical device e1000g0 > > Unable to complete install ''libvirt.libvirtError virDomainCreateLinux() failed POST operation failed: (xend.err "Error creating domain: (2, ''Invalid kernel'', ''xc_dom_parse_elf_kernel: ELF image has no shstrtab\\n'')") > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/create.py", line 699, in do_install > dom = guest.start_install(False, meter = meter) > File "/export/builds/xvm_111a///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 923, in start_install > File "/export/builds/xvm_111a///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 944, in _do_install > File "libvirt.py", line 585, in createLinux > if ret is None:raise libvirtError(''virDomainCreateLinux() failed'', conn=self) > libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err "Error creating domain: (2, ''Invalid kernel'', ''xc_dom_parse_elf_kernel: ELF image has no shstrtab\\n'')") > > > attempt at manual creation: > > virt-install --paravirt --name centos --ram 2038 --vnc --os-type=linux --os-variant=rhel5 --network bridge --file /rpool/vms/centos --file-size=20 --location http://heidelberg.rutgers.edu/MYDVD/ > > Starting install... > Retrieving file .treeinfo 100% |=========================| 417 B 00:00 > Retrieving file .treeinfo 100% |=========================| 417 B 00:00 > Retrieving file .treeinfo 100% |=========================| 417 B 00:00 > Retrieving file vmlinuz.. 100% |=========================| 1.9 MB 00:00 > Retrieving file initrd.im 100% |=========================| 6.3 MB 00:00 > > virDomainCreateLinux() failed POST operation failed: (xend.err ''Device 0 (vkbd) could not be connected. Hotplug scripts not working.'') > Domain installation may not have been > successful. If it was, you can restart your domain > by running ''virsh start centos''; otherwise, please > restart your installation. > Fri, 12 Jun 2009 19:54:56 ERROR virDomainCreateLinux() failed POST operation failed: (xend.err ''Device 0 (vkbd) could not be connected. Hotplug scripts not working.'') > Traceback (most recent call last): > File "/usr/bin/virt-install", line 511, in ? > main() > File "/usr/bin/virt-install", line 471, in main > dom = guest.start_install(conscb,progresscb) > File "/export/builds/xvm_111a///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 923, in start_install > File "/export/builds/xvm_111a///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 944, in _do_install > File "libvirt.py", line 585, in createLinux > if ret is None:raise libvirtError(''virDomainCreateLinux() failed'', conn=self) > libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err ''Device 0 (vkbd) could not be connected. Hotplug scripts not working.'')
I got it to come up by removing the vnc option from the command line tool. I still have a problem, but I think it will be clearer to post that separately. -- This message posted from opensolaris.org
Thanks very much for this response. Is it practical for me to update just the xen components? I''m not averse to test releases on some systems, but I''d prefer to stick with a release (2009.6 in this case) on this particular system if I can. -- This message posted from opensolaris.org
Charles Hedrick wrote:> Thanks very much for this response. Is it practical for me to update just> the xen components? I''m not averse to test releases on some systems, but > I''d prefer to stick with a release (2009.6 in this case) on this particular system if I can. No, you need an updated kernel too. One thing you can do is to use beadm(1M) to create one or more alternate boot environments (BE). This way you can keep 2009.06 but also experiment with the newer bits in the dev tree. NOTE: the dev tree is still at build 111 (b111), but this should change shortly. There are various ways to do this... This is what I usually do to ensure that the stock bits remained absolutely unchanged. What we''ll do it to create a tree of cloned disk images.. Create a backup up os2009.06 in case you mess something up. Then, create a branch for the development release. You may have to update some packages to be able to upgrade to newer releases, so we''ll do that in the branch. beadm create os2009.06-backup beadm create dev-branch beadm activate dev-branch reboot One you''ve rebooted, re-target (the dev-branch) from the release repo to the development repo. Then upgrade the pkg package. beadm list pkg set-authority -O http://pkg.opensolaris.org/dev opensolaris.org pkg install SUNWipkg Now lets create a build specific BE. NOTE: b116 doesn''t exist in the repo as of today, but should shortly. ("pkg search entire" for a list of builds). From the dev-branch, create a b116 BE. beadm create snv116 beadm mount snv116 /mnt pkg -R /mnt refresh pkg -R /mnt install entire@0.5.11-0.116 bootadm update-archive -R /mnt beadm umount snv116 beadm activate snv116 reboot MRJ