xen discuss - Sep 2008 - XEN b98 problems getting installed, shutdown virtual machine to run

hi,

Just moved to b98 from b95. Xen and virtual machine manager(VMM) are not working
to go for me.
I can install a new machine via VMM OK, The problems start to come up if i try
to start it after install. The Run button will not work on VMM. If I go into
virsh I get the error message below.
The new machines do not get an ID. That may have something to do with it.

***********************************************************************************
virsh # reboot winxp01
error: Failed to reboot domain winxp01

virsh # resume winxp01
error: Failed to resume domain winxp01

virsh # list
 Id Name                 State
----------------------------------
  0 Domain-0             running
  - carl                 shut off
  - winxp01              shut off

virsh # start carl
libvir: Xen Daemon error : POST operation failed: (xend.err ''Device
5632 (vbd) could not be connected. Backend device not found.'')
error: Failed to start domain carl

virsh # 

************************************************************************************

Here is the error message from a console on a newly created machine. Hit the run
button and this is the error message.

***********************************************************************************
Unable to start virtual machine ''libvirt.libvirtError virDomainCreate()
failed POST operation failed: (xend.err ''Device 5632 (vbd) could not be
connected. Backend device not found.'')
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/console.py", line 349, in
control_vm_run
    self.vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 361, in
startup
    self.vm.create()
  File "libvirt.py", line 240, in create
    if ret == -1: raise libvirtError (''virDomainCreate()
failed'', dom=self)
libvirtError: virDomainCreate() failed POST operation failed: (xend.err
''Device 5632 (vbd) could not be connected. Backend device not
found.'')
''
*************************************************************************************

On build b95 i have no problems what so ever. The system hardware is exaclty the
same. System settup is exactly the same. I used the same ISO to install the
virtul machines.

The work around. To get a shutdown machine running.
Install the new machine via VMM. Use a simple file as hard drive.

Machine unstartable and in shutdown state.
>From VMM delete the machine.
Create a new machine with the same name as the one you deleted / the one you
want to start up.
Go through the install again, use the same*** file you used for the hard drive
before
*** thats the important bit! dont miss that bit out.

You may want to use an ISO image that will auto boot the first HDD ater a delay,
but i dont think that is nessasery.

Now the HDD of your vitual machine should boot up, and way you go! 

Am no expert, so following my instructions could be a bit risky ;)
--
This message posted from opensolaris.org

> hi,
> 
> Just moved to b98 from b95. Xen and virtual machine
> manager(VMM) are not working to go for me.
> I can install a new machine via VMM OK, The problems
> start to come up if i try to start it after install.
> The Run button will not work on VMM. If I go into
> virsh I get the error message below. 
> The new machines do not get an ID. That may have
> something to do with it.
I''ve just installed B98 . VMM doesn''t have any "Run"
button.
Right mouse click on corresponding entry to VMs list opens menu, where is option
"Run",
been  selected it starts SNV98 PVM with no problems.
**************
Old schema
***************
# xm start Solaris98PV
# xm console Solaris98PV
also works OK.
> 
> ******************************************************
> *****************************
> virsh # reboot winxp01
> error: Failed to reboot domain winxp01
> 
> virsh # resume winxp01
> error: Failed to resume domain winxp01
> 
> virsh # list
>  Id Name                 State
> ---------------------------------
>   0 Domain-0             running
> - carl                 shut off
>   - winxp01              shut off
> virsh # start carl
> libvir: Xen Daemon error : POST operation failed:
> (xend.err ''Device 5632 (vbd) could not be connected.
> Backend device not found.'')
> error: Failed to start domain carl
> 
> virsh # 
> 
> ******************************************************
> ******************************
> 
> Here is the error message from a console on a newly
> created machine. Hit the run button and this is the
> error message.
> 
> ******************************************************
> *****************************
> Unable to start virtual machine ''libvirt.libvirtError
> virDomainCreate() failed POST operation failed:
> (xend.err ''Device 5632 (vbd) could not be connected.
> Backend device not found.'')
> Traceback (most recent call last):
> File
> "/usr/share/virt-manager/virtManager/console.py",
>  line 349, in control_vm_run
>    self.vm.startup()
> ile "/usr/share/virt-manager/virtManager/domain.py",
> line 361, in startup
>     self.vm.create()
> le "libvirt.py", line 240, in create
> if ret == -1: raise libvirtError
>  (''virDomainCreate() failed'', dom=self)
> ibvirtError: virDomainCreate() failed POST operation
> failed: (xend.err ''Device 5632 (vbd) could not be
> connected. Backend device not found.'')
> ''
> ******************************************************
> *******************************
> 
> On build b95 i have no problems what so ever. The
> system hardware is exaclty the same. System settup is
> exactly the same. I used the same ISO to install the
> virtul machines.
> 
> The work around. To get a shutdown machine running.
> Install the new machine via VMM. Use a simple file as
> hard drive.
> 
> Machine unstartable and in shutdown state.
> From VMM delete the machine.
> 
> Create a new machine with the same name as the one
> you deleted / the one you want to start up.
> Go through the install again, use the same*** file
> you used for the hard drive before 
> *** thats the important bit! dont miss that bit out.
> 
> You may want to use an ISO image that will auto boot
> the first HDD ater a delay, but i dont think that is
> nessasery.
> 
> Now the HDD of your vitual machine should boot up,
> and way you go! 
> 
> Am no expert, so following my instructions could be a
> bit risky ;)
--
This message posted from opensolaris.org

doing a search for ( Device 5632 ), reveals more people with much the same
problem as my self.

# xm start winxp01
Error: Device 5632 (vbd) could not be connected. Backend device not found.
Usage: xm start <DomainName>

Start a Xend managed domain
  -p, --paused                   Do not unpause domain after starting it    
  -c, --console_autoconnect      Connect to the console after the domain    
                                 is created

Brian,
--
This message posted from opensolaris.org

Sorry, i forgot. You are running HVM DomU
View CR 6742735.
In particular,
>Boris Derzhavets wrote:
> Not much luck:-
>
> Guest installation complete... restarting guest.
> virDomainCreate() failed POST operation failed: (xend.err ''Device
5632 (vbd) could not be connected. Backend device not found.'')
> Domain installation may not have been
>  successful.  If it was, you can restart your domain
>  by running ''virsh start Solaris97HVM''; otherwise, please
>  restart your installation.
> Mon, 15 Sep 2008 17:45:12 ERROR    virDomainCreate() failed POST operation
failed: (xend.err ''Device 5632 (vbd) could not be connected. Backend
device not found.'')
> Traceback (most recent call last):
>   File "/usr/bin/virt-install", line 511, in ?
>     main()
>   File "/usr/bin/virt-install", line 497, in main
>     dom.create()
>   File "libvirt.py", line 240, in create
>     if ret == -1: raise libvirtError (''virDomainCreate()
failed'', dom=self)
> libvirtError: virDomainCreate() failed POST operation failed: (xend.err
''Device 5632 (vbd) could not be connected. Backend device not
found.'')

This is bug 6742735, which was fixed last week (the fix will appear in
snv_99).  You can manually apply the fix to
/usr/lib/xen/scripts/vbd-default:

@@ -49,7 +49,7 @@
          if [ ! -b "${file}" ]; then
              err "\"${file}\" is not a valid block device."
"${domain}" "${path}"
          fi
-    elif [ -z "$file}" ];then
+    elif [ -z "${file}" ];then
          #
          # For example, an empty HVM CD-ROM device might not have
          # a file attached.


-Ryan
--
This message posted from opensolaris.org

Having CR 6742735 applied , i''ve got Windows HVM been managed fine via
VMM on build 98.
--
This message posted from opensolaris.org

hi,

dbaxps, thanks for your help.
--
This message posted from opensolaris.org

SNV_98 bfu''ed SNV_99 OK 
based on tar.bz2 archive at http://dlc.sun.com/osol/on/downloads/b99/

Reboot into XVM (98) kernel:-

# vi  $HOME/.hgrc
[extensions]
hgext.mq[diff]
git=True


#  /usr/sfw/bin/wget http://dlc.sun.com/osol/on/downloads/b99/xvm-src.tar.bz2
# bunzip2 < xvm-src.tar.bz2 | tar xf -

EMAIL=bderzhavets@yahoo.com
XVM_WS=`pwd`
SOLARIS_BUILD_TOOLS=/opt
LD_OPTIONS=-L/lib
export EMAIL XVM_WS SOLARIS_BUILD_TOOLS LD_OPTIONS

# sunos.hg/bin/build-all nondebug
        10 packages have been compiled  successfully

# svcadm disable xvm/domains xvm/console xvm/xend xvm/store

# pkgrm SUNWvirtinst SUNWurlgrabber SUNWlibvirt SUNWlibvirtr SUNWxvmh \ 
   SUNWxvmhvm SUNWxvmu SUNWxvmr SUNWxvmdomu  SUNWxvmdomr 

  10 packages removed

# pkgadd -d packages-nondebug SUNWxvmdomr SUNWxvmdomu SUNWxvmr SUNWxvmu
SUNWxvmhvm \
  SUNWxvmh SUNWlibvirt SUNWlibvirtr SUNWurlgrabber SUNWvirtinst

 10 packages installed

# svcadm enable xvm/store xvm/xend xvm/console xvm/domains

# reboot

All xvm services enabled OK.
Failure to load into new xVM kernel (99) . System hangs ( and panics) when
loading new xen.gz.

On Fri, Sep 26, 2008 at 06:23:22AM -0700, Boris Derzhavets
wrote:
> Failure to load into new xVM kernel (99) . System hangs ( and panics) when
loading new xen.gz.
nv99 is DOA for Xen on Intel. The fix is in nv100.

Could you,please, explain what for DOA stands.
--
This message posted from opensolaris.org

On Fri, Sep 26, 2008 at 07:02:57AM -0700, Boris Derzhavets
wrote:
> Could you,please, explain what for DOA stands.
Sorry. "Dead on Arrival". It doesn''t work, is known broken.