[one-users] error : virDomainDefParseXML:8303 : unknown OS type hvm

Gerry O'Brien gerry at scss.tcd.ie
Wed Feb 6 04:31:20 PST 2013


Hello Jamie,

   The 'virsh capabilities' reports did indeed highlight a difference. 
The failing hosts had no guest capabilities, the reason being that, for 
some unknown reason, the virtualization capability in the BIOS was 
turned off.

   Everything is working fine now.

             Thank you,
                 Gerry


  On 06/02/2013 10:59, Jaime Melis wrote:
> Hi,
>
> does virsh capabilites report something different in those two hosts
> compared with the rest?
>
> cheers,
> Jaime
>
>
> On Wed, Feb 6, 2013 at 11:54 AM, Gerry O'Brien <gerry at scss.tcd.ie> wrote:
>
>> Hello Jaime,
>>
>>      Below is the domain information for a VM that runs on all my hosts
>> except two specific one. All hosts are identical PXE boot images except for
>> some /var directories & files (which I have double checked to make sure the
>> permissions are identical). I can live migrate the VM around all my hosts
>> except the two where is fails with the above error message. It to me looks
>> like there is some additional information that is stored in OpenNebula
>> outside the two failing hosts, possible where '<type
>> arch='x86_64'>hvm</type>' is defined? Any ideas?
>>
>>          Regards,
>>              Gerry
>>
>>
>>
>>
>> <domain type='kvm' xmlns:qemu='http://libvirt.**
>> org/schemas/domain/qemu/1.0 <http://libvirt.org/schemas/domain/qemu/1.0>'>
>>          <name>one-3461</name>
>>          <cputune>
>>                  <shares>4096</shares>
>>          </cputune>
>>          <memory>4194304</memory>
>>          <os>
>>                  <type arch='x86_64'>hvm</type>
>>                  <boot dev='hd'/>
>>          </os>
>>          <devices>
>>                  <emulator>/usr/bin/kvm</**emulator>
>>                  <disk type='file' device='disk'>
>>                          <source file='/var/lib/one//**
>> datastores/0/3461/disk.0'/>
>>                          <target dev='hda'/>
>>                          <driver name='qemu' type='qcow2' cache='none'/>
>>                  </disk>
>>                  <interface type='bridge'>
>>                          <source bridge='br61'/>
>>                          <mac address='02:00:0a:3d:01:0d'/>
>>                  </interface>
>>                  <graphics type='vnc' listen='0.0.0.0' port='9361'/>
>>          </devices>
>>          <features>
>>                  <acpi/>
>>          </features>
>> </domain>
>>
>> On 29/01/2013 10:12, Jaime Melis wrote:
>>
>>> Hi,
>>>
>>> this looks like a libvirt bug. Do you have access still to the domain
>>> files? can you paste here one that works and one that doesn't?
>>>
>>> Also, can you try and start a failed domain manually (by doing virsh
>>> create
>>> deployment.0)?
>>>
>>> Maybe adding a lock mechanism in OpenNebula's vmm/kvm driver would help.
>>> Let me know if you want help with that.
>>>
>>> cheers,
>>> Jaime
>>>
>>> On Tue, Jan 22, 2013 at 5:53 PM, Gerry O'Brien <gerry at scss.tcd.ie> wrote:
>>>
>>>   error : virDomainDefParseXML:8303 : unknown OS type hvm
>>>
>>>
>>>
>>>
>> --
>> Gerry O'Brien
>>
>> Systems Manager
>> School of Computer Science and Statistics
>> Trinity College Dublin
>> Dublin 2
>> IRELAND
>>
>> 00 353 1 896 1341
>>
>>
>


-- 
Gerry O'Brien

Systems Manager
School of Computer Science and Statistics
Trinity College Dublin
Dublin 2
IRELAND

00 353 1 896 1341




More information about the Users mailing list