public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Federico Fissore <federico.fissore@assist-si.it>
To: kvm <kvm@vger.kernel.org>
Subject: Re: boot=on option fails on win 2k/xp double boot
Date: Sun, 10 May 2009 10:38:18 +0200	[thread overview]
Message-ID: <4A06927A.1050306@assist-si.it> (raw)
In-Reply-To: <20090510052108.GC18554@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1020 bytes --]

Gleb Natapov, il 10/05/2009 07:21, ha scritto:
> On Sat, May 09, 2009 at 07:53:50PM +0200, Federico Fissore wrote:
>> I've a windows (virtual) box with windows xp originally installed and a  
>> windows 2k lately installed
>>
> Are they both installed on the same disk?


yes they are

> 
>> 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?
>>
> 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).
> 

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


[-- Attachment #1.2: nord_recuperi.xml --]
[-- Type: text/xml, Size: 1181 bytes --]

<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>

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3298 bytes --]

  reply	other threads:[~2009-05-10  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-09 17:53 boot=on option fails on win 2k/xp double boot Federico Fissore
2009-05-10  5:21 ` Gleb Natapov
2009-05-10  8:38   ` Federico Fissore [this message]
2009-05-10  8:51     ` Gleb Natapov
2009-05-11  9:20       ` Federico Fissore
2009-05-11  9:26         ` Gleb Natapov
2009-05-12  9:47           ` Federico Fissore

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A06927A.1050306@assist-si.it \
    --to=federico.fissore@assist-si.it \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox