Hello,
I can't seem to boot from my disk when using Virtio. When using IDE in the same drive it boots fine. This is WinXP VM and I already have the drivers installed and working fine (I was happily using Virtio disks). SeaBIOS just says "Boot failed: could not read the boot disk". I have boot order setup right, with Virtio disk set to boot first. Can you please suggest a solution? Thank you.
My setup is as follows.
/usr/bin/kvm -id 100 -chardev socket,id=monitor,path=/var/run/qemu-server/100.mon,server,nowait -mon chardev=monitor,mode=readline -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -usbdevice tablet -name XP -smp sockets=1,cores=2 -nodefaults -boot menu=on -vga cirrus -localtime -rtc-td-hack -k en-us -drive file=/var/lib/vz/images/100/vm-100-disk-1.raw,boot=on,if=none,id=drive-virtio0,aio=native,cache=none -device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100 -m 3072 -netdev type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,vhost=on -device virtio-net-pci,mac=82:05:BF:3F:20:CE,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300
pve-manager: 2.0-38 (pve-manager/2.0/af81df02)
running kernel: 2.6.32-7-pve
proxmox-ve-2.6.32: 2.0-60
pve-kernel-2.6.32-6-pve: 2.6.32-55
pve-kernel-2.6.32-7-pve: 2.6.32-60
lvm2: 2.02.88-2pve1
clvm: 2.02.88-2pve1
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-1
pve-cluster: 1.0-23
qemu-server: 2.0-25
pve-firmware: 1.0-15
libpve-common-perl: 1.0-17
libpve-access-control: 1.0-17
libpve-storage-perl: 2.0-12
vncterm: 1.0-2
vzctl: 3.0.30-2pve1
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-5
ksm-control-daemon: 1.1-1
SeaBIOS is version 0.5.1-3 (In console it shows version 0.5.1-20100616_222654-volta )
I can't seem to boot from my disk when using Virtio. When using IDE in the same drive it boots fine. This is WinXP VM and I already have the drivers installed and working fine (I was happily using Virtio disks). SeaBIOS just says "Boot failed: could not read the boot disk". I have boot order setup right, with Virtio disk set to boot first. Can you please suggest a solution? Thank you.
My setup is as follows.
/usr/bin/kvm -id 100 -chardev socket,id=monitor,path=/var/run/qemu-server/100.mon,server,nowait -mon chardev=monitor,mode=readline -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -usbdevice tablet -name XP -smp sockets=1,cores=2 -nodefaults -boot menu=on -vga cirrus -localtime -rtc-td-hack -k en-us -drive file=/var/lib/vz/images/100/vm-100-disk-1.raw,boot=on,if=none,id=drive-virtio0,aio=native,cache=none -device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100 -m 3072 -netdev type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,vhost=on -device virtio-net-pci,mac=82:05:BF:3F:20:CE,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300
pve-manager: 2.0-38 (pve-manager/2.0/af81df02)
running kernel: 2.6.32-7-pve
proxmox-ve-2.6.32: 2.0-60
pve-kernel-2.6.32-6-pve: 2.6.32-55
pve-kernel-2.6.32-7-pve: 2.6.32-60
lvm2: 2.02.88-2pve1
clvm: 2.02.88-2pve1
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-1
pve-cluster: 1.0-23
qemu-server: 2.0-25
pve-firmware: 1.0-15
libpve-common-perl: 1.0-17
libpve-access-control: 1.0-17
libpve-storage-perl: 2.0-12
vncterm: 1.0-2
vzctl: 3.0.30-2pve1
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-5
ksm-control-daemon: 1.1-1
SeaBIOS is version 0.5.1-3 (In console it shows version 0.5.1-20100616_222654-volta )