boot=on option fails on win 2k/xp double boot

I've a windows (virtual) box with windows xp originally installed and a windows 2k lately installed

If I run kvm from the command line for testing purposes everything is fine. If I run it with libvirt on the host, I does not boot, complaining with an I/O error

the problem arises since libvirt adds boot=on on the first disk

without that option, everything works fine

do you have any hint on this?

thanks

Are they both installed on the same disk?

libvirt should not add boot=on if interface type is IDE and if disk type is not IDE then boot is supported only from one disk (the one that has boot=on).

--
Gleb.

Gleb Natapov, il 10/05/2009 07:21, ha scritto:

yes they are

attached is the xml
the current non-working version uses disk images. but it fails the same way when using LVM volumes

other info: libvirt version is 0.4.6-10 and kvm is 72. these are what is currenntly available with debian lenny

<domain type='kvm'>
<name>nord_recuperi</name> <uuid>ac298be5-4c11-e7cd-4093-36c951445d3f</uuid> <memory>1048576</memory> <currentMemory>1048576</currentMemory> <vcpu>1</vcpu>
<os>

    <type arch='x86_64' machine='pc'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <pae/>
  </features>
  <clock offset='localtime'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/kvm</emulator>
    <disk type='file' device='disk'>
      <source file='/DATA/virtual.machines/nr/nr_c.qcow2'/>
      <target dev='hda' bus='ide'/>
    </disk>
    <disk type='file' device='disk'>
      <source file='/DATA/virtual.machines/nr/nr_e.qcow2'/>
      <target dev='hdb' bus='ide'/>
    </disk>
    <disk type='block' device='cdrom'>
      <source dev='/dev/cdrom'/>
      <target dev='hdc' bus='ide'/>
      <readonly/>
    </disk>
    <interface type='bridge'>
      <mac address='54:a4:7e:c0:0b:24'/>
      <source bridge='br2'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='5903' autoport='no' listen='192.168.46.20' keymap='it'/>

</devices>
</domain>

Can you please try non ancient version of KVM? kvm-85?

--
Gleb.

Gleb Natapov, il 10/05/2009 10:51, ha scritto:

unfortunately no, since that's the current stable version available with debian lenny :(

(btw, the latest available version is 84 on debian "experimental" !: not a version I would like to use on production)

I took it off libvirt and handled it manually with a startup script

thanks all the same

federico

May be you can test it not in production? On another machine. Or alternatively you can compile only userspace of kvm-84 and run it with kernel kvm modules available in lenny. Another option would be to run kvm-84 with -no-kvm flag.

--
Gleb.

Gleb Natapov, il 11/05/2009 11:26, ha scritto:

i've tried on my gentoo but I had some problems. I'll try asap with a fedora

btw the pure kvm support on debian lenny seems good, while libvirt & C. suck: I had a Centos 5.3 guest (asterisknow) and network performance degraded with time: after 12 hours the guest was unable to connect to VoIP phones. Running KVM directly (with plain old rc.local) solved the problem.

As said, the whole kvm stack on lenny is old and that maybe the problem.

Thanks for your help and time

Federico