Oops ! 132 was tested OK Xen 3.4.3 Dom0 & pvops 2.6.31.6.
Via xml-profile for 132 DomU :-
<domain type='xen'>
<name>OSOL132</name>
<memory>2097152</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<bootloader>/usr/local/bin/pygrub</bootloader>
<os>
<type>linux</type>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<disk type='block' device='disk'>
<driver name='phy'/>
<source dev='/dev/sda7'/>
<target dev='xvda' bus='xen'/>
</disk>
<interface type='bridge'>
<mac address='00:16:3e:10:93:61'/>
<source bridge='eth0'/>
<script path='/etc/xen/scripts/vif-bridge'/>
<target dev='vif7.0'/>
</interface>
<console type='pty' tty='/dev/pts/2'>
<source path='/dev/pts/2'/>
<target port='0'/>
</console>
</devices>
</domain>
Now 132 gives the same issue as 134 (133) at Xen 4.0 Dom0 & pvops 2.6.32.11.
Via xml profile :
<domain type='xen'>
<name>OSOL132</name>
<memory>1048576</memory>
<currentMemory>1048576</currentMemory>
<vcpu>2</vcpu>
<bootloader></bootloader>
<os>
<type>linux</type>
<kernel>/home/boris/osol132/unix</kernel>
<initrd>/home/boris/osol132/boot_archive</initrd>
<cmdline>/platform/i86xpv/kernel/amd64/unix -B
zfs-bootfs=rpool/ROOT/opensolaris,bootpath=/xpvd/x...@51712:a</cmdline>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>destroy</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<disk type='block' device='disk'>
<driver name='phy'/>
<source dev='/dev/sda7'/>
<target dev='xvda' bus='xen'/>
</disk>
<interface type='bridge'>
<mac address='00:16:3e:4d:60:e3'/>
<source bridge='eth0'/>
<script path='/etc/xen/scripts/vif-bridge'/>
<target dev='vif8.0'/>
</interface>
<console type='pty' tty='/dev/pts/1'>
<source path='/dev/pts/1'/>
<target port='0'/>
</console>
</devices>
</domain>
Most probably the last XML definition causes the issue.
Pygrub at Xen 4.0 Linux Dom0 cannot define OSOL 132 PV DomU at all.
Backward compatibility is broken.
--
This message posted from opensolaris.org
_______________________________________________
xen-discuss mailing list
[email protected]
