THANK YOU! THAT WORKED!
emike
Ryan Scott wrote:
> 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
>
>
>> bash-3.2# xm start Solaris97HVM
>> 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
>>
>> --- On Mon, 9/15/08, Boris Derzhavets <[EMAIL PROTECTED]> wrote:
>> From: Boris Derzhavets <[EMAIL PROTECTED]>
>> Subject: Re: [xen-discuss] b98 hvm problem
>> To: [email protected], "E. Mike Durbin" <[EMAIL PROTECTED]>
>> Date: Monday, September 15, 2008, 1:08 PM
>>
>> I would replace
>> --nographics \
>>
>> by
>>
>> --vnc \
>>
>> in virt-install command lines
>>
>> --- On Mon, 9/15/08, Boris Derzhavets <[EMAIL PROTECTED]> wrote:
>> From: Boris Derzhavets <[EMAIL PROTECTED]>
>> Subject: Re: [xen-discuss] b98 hvm problem
>> To: [email protected], "E. Mike Durbin" <[EMAIL PROTECTED]>
>> Date: Monday, September 15, 2008, 1:02 PM
>>
>> On instance bfu'ed from 97
>> => 98 along with xvm upgraded to 98 build
>> i was able to start :-
>> virt-install -n Solaris97HVM --hvm -r 2048 --vnc -f
>> /dev/zvol/dsk/snvtank/disk1 \
>>
>>> -l /export/home/isos/snv97.iso
>>>
>> Starting install...
>> Creating domain... 0 B 00:04
>>
>> VNC Viewer Free Edition 4.1.2 for X - built Jul 1 2008 15:57:39
>> Copyright (C) 2002-2005 RealVNC Ltd.
>> See http://www.realvnc.com for information on VNC.
>>
>> Default nic for xend has been defined:-
>> svccfg -s xvm/xend setprop config/default-nic="rge0"
>> svcadm refresh
>> xvm/xend
>> svcadm restart xvm/xend
>>
>>
>> --- On Mon, 9/15/08, E. Mike Durbin <[EMAIL PROTECTED]> wrote:
>> From: E. Mike Durbin <[EMAIL PROTECTED]>
>> Subject: [xen-discuss] b98 hvm problem
>> To: [email protected]
>> Date: Monday, September 15, 2008, 11:53 AM
>>
>> I have a couple of machines now loaded with b98.
>>
>> I can't install a hvm guest!
>>
>> I tried:
>>
>> ---------------------------------------------------------------------------------
>> #!/bin/sh
>> ISO=/home/emike/xvm/ISOs/en_win_srv_2003_r2_enterprise_x64_with_sp2_cd1_X13-06188.iso
>> set -x
>>
>> virt-install \
>> --hvm \
>> -n win2k3zvol \
>> -f /dev/zvol/dsk/rpool/clients/win2k3 \
>> -c ${ISO} \
>> --nographics \
>> --os-type=windows \
>> --os-variant=win2k3 \
>> -r
>>
>> 1024
>> ---------------------------------------------------------------------------------
>>
>> and I get:
>>
>> ---------------------------------------------------------------------------------
>> # sh win2003zvol.sh
>> + virt-install --hvm -n win2k3zvol -f /dev/zvol/dsk/rpool/clients/win2k3
>> -c
>> /home/emike/xvm/ISOs/en_win_srv_2003_r2_enterprise_x64_with_sp2_cd1_X13-06188.iso
>>
>> --nographics --os-type=windows --os-variant=win2k3 -r 1024
>>
>>
>> Starting install...
>> virDomainCreateLinux() 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 win2k3zvol'; otherwise, please
>> restart your installation.
>> Mon, 15 Sep 2008 10:36:25 ERROR virDomainCreateLinux() 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 471, in main
>> dom = guest.start_install(conscb,progresscb)
>> File
>> "/export/builds/xvm_98///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
>>
>> line 889, in start_install
>> File
>> "/export/builds/xvm_98///proto/install/usr/lib/python2.4/site-packages/virtinst/Guest.py",
>>
>> line 910, 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 5632 (vbd) could not be connected. Backend device not
>> found.')
>> ---------------------------------------------------------------------------------
>>
>> I
>>
>> tried:
>>
>> ---------------------------------------------------------------------------------
>> #!/bin/sh
>> ISO=/home/emike/xvm/ISOs/solarisdvd-s10u6-b7.iso
>> set -x
>>
>> virt-install \
>> --hvm \
>> -n s10u6 \
>> -f /dev/zvol/dsk/rpool/clients/s10u6 \
>> -c ${ISO} \
>> --nographics \
>> --os-type=solaris \
>> --os-variant=solaris10 \
>> -r 1024
>> ---------------------------------------------------------------------------------
>>
>> and I get
>>
>> ---------------------------------------------------------------------------------
>> Starting install...
>> Creating domain... 0
>> B 00:01
>> ---------------------------------------------------------------------------------
>>
>> And it just sits there for hours doing nothing.
>>
>> # virsh list
>>
>> Id Name State
>> ---------------------------------------
>> 0 Domain-0
>>
>> Running
>> 2 s10u6 Running
>>
>> Any ideas? Is 98 broken?
>>
>> I can install Nevada 98 as a PV guest, no problem.
>>
>> emike
>> _______________________________________________
>> xen-discuss mailing list
>> [email protected]
>>
>>
>>
>> _______________________________________________
>> xen-discuss mailing list
>> [email protected]
>>
>>
>> _______________________________________________
>> xen-discuss mailing list
>> [email protected]
>>
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> xen-discuss mailing list
>> [email protected]
>>
>
> _______________________________________________
> xen-discuss mailing list
> [email protected]
>
_______________________________________________
xen-discuss mailing list
[email protected]
