[kernel-xen] Hot plugs error with latest scripts

[Steven Spencer]

On 09/19/2013 05:07 PM, Glenn Enright wrote:
>
>
> On 09/20/2013 04:46 AM, Steven Spencer wrote:
>> On 09/19/2013 09:24 AM, Steven Spencer wrote:
>>> All,
>>>
>>> I've run into this while creating a vm using the latest scripts on a
>>> brand new system. I can find this problem going back many versions, but
>>> not a really excellent answer. You people all seem to have the gold, so
>>> maybe you can help.
>>>
>>> Error: Device 0 (vif) could not be connected. Hotplug scripts not
>>> working.
>>>
>>> System:
>>>
>>> OS = CentOS 6.4 X86_64
>>> Xen = kernel-xen-3.11.1-1.el6xen.x86_64
>>>
>>> First time using a standalone script, so this may be the issue:
>>>
>>> name = "vm_test"
>>> memory = 2048
>>> vcpus = 2
>>> disk = [ 'phy:/virtual/vm_test.img,xvda,w' ]
>>> on_poweroff = 'destroy'
>>> on_reboot   = 'restart'
>>> on_crash    = 'restart'
>>> vif = [ "mac=00:16:36:35:35:97,bridge=br0,script=vif-bridge" ]
>>> kernel="/usr/lib/xen/boot/pv-grub-x86_64.gz"
>>> extra="(hd0)/boot/grub/grub.conf"
>>>
>>> I'll continue to look for the answer, but if someone has run into this
>>> in the recent past and has an answer, I'd appreciate it.
>>>
>>> Thanks,
>>
>> It had been a 48 hours or so since the install of the OS, so I rebooted
>> and tried again. Now I'm getting this when trying to create using the
>> config:
>>
>> Error: Device 51712 (vbd) could not be connected.
>>
>> It says that the block device does not exist, but I've verified that it
>> does exist.
>>
>> Thanks,
>
> You may want to check the params file to make sure that has everything
> correct.
>
> The vif line should probably not have the script= bit. For the disk, phy
> is for physical devices only, such as lvm, you probably need to use file
> or similar.
> _______________________________________________
> kernel-xen mailing list
> kernel-xen at lists.wireless.org.au
> https://lists.wireless.org.au/mailman/listinfo/kernel-xen
>
>

Well this is a physical location, and I got a little further using 
tap:aio: instead of phy, which starts the DomU, but now I have to figure 
out how to install the OS. Essentially, I now get this in the console of 
the running vm:


backend at /local/domain/0/backend/tap/2/51712

What is the best method for installing the OS from this point? I know 
this is a kernel list, so If I'm barking up the wrong tree, just tell me 
to buzz off.


-- 
-- 
Steven G. Spencer, Network Administrator
KSC Corporate - The Kelly Supply Family of Companies
Office 308-382-8764 Ext. 231
Mobile 402-765-8010 - PLEASE NOTE MOBILE NUMBER CHANGE!