Re: virtio issues

Re: virtio issues

[aragonx]

> Just checking,  after you edit the xml, did you redefine your xml
to
> take effect ?
> 
> virsh define
/path/to/domainxml
> 
> /kashyap

Honestly I
created the storage with the GUI.  The client was always off when I
did so.  Do you still think I need to use the define?

---
Will Y.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: virtio issues

[Kashyap Chamarthy]

On Wed, Aug 24, 2011 at 9:04 AM,  <aragonx@dcsnow.com> wrote:
>
>
> Hello all,
>
> I have just started working with KVM and
> virtualization in general.  I have setup a client using Suse 9.3 x64
> as the base and Fedora 15 x64 as the host.  The kernel in the client
> has been upgraded to a custom 2.6.28.4 build.
>
> Everything seems
> to be working fine but I wanted to get some more disk performance so I'm
> trying to get virtio running.  I don't care too much about the disk
> the base OS is running on but I have a drive that I'm trying to add that I
> want to use the virtio for.  I can add the drive using IDE or SCSI
> drivers and it works fine (just slower had hoped).  If, however, I
> switch to virtio, it doesn't show up in the client.
>
> If I used
> edit from virsh, I see:

Just checking,  after you edit the xml, did you redefine your xml to
take effect ?

virsh define /path/to/domainxml

/kashyap

>
> <domain type='kvm'>
>
> <name>MC1DB</name>
>
> <uuid>f57c6236-2595-57ca-595b-aaaef4de87ea</uuid>
>
> <memory>7680000</memory>
>
> <currentMemory>7680000</currentMemory>
>
> <vcpu>4</vcpu>
>   <os>
>
> <type arch='x86_64'
> machine='pc-0.14'>hvm</type>
>
> <boot
> dev='hd'/>
>
> <bootmenu
> enable='no'/>
>   </os>
>
> <features>
>     <acpi/>
>     <apic/>
>     <pae/>
>   </features>
>   <clock offset='utc'/>
>   <on_poweroff>destroy</on_poweroff>
>
> <on_reboot>restart</on_reboot>
>
> <on_crash>restart</on_crash>
>   <devices>
>     <emulator>/usr/bin/qemu-kvm</emulator>
>     <disk type='file' device='disk'>
>       <driver name='qemu' type='raw'/>
>       <source file='/img/mc1db.img'/>
>       <target dev='hda' bus='ide'/>
>       <address type='drive'
> controller='0'
> bus='0' unit='0'/>
>
> </disk>
>     <disk type='block'
> device='cdrom'>
>       <driver
> name='qemu' type='raw'/>
>
> <source
> dev='/dev/sr0'/>
>
> <target
> dev='hdc' bus='ide'/>
>
> <readonly/>
>       <address
> type='drive'
> controller='0'
> bus='1' unit='0'/>
>
> </disk>
>     <disk
> type='block'
> device='disk'>
>
> <driver
> name='qemu' type='raw'/>
>
> <source dev='/dev/sda1'/>
>
> <target dev='vda' bus='virtio'/>
>
> <address type='pci'
> domain='0x0000'
> bus='0x00' slot='0x07'
> function='0x0'/>
>
> </disk>
>
> <controller type='ide'
> index='0'>
>       <address type='pci'
> domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
>     </controller>
>
> <controller type='scsi' index='0'>
>       <address type='pci' domain='0x0000'
> bus='0x00' slot='0x06' function='0x0'/>
>
> </controller>
>     <interface
> type='network'>
>       <mac
> address='52:54:00:fc:de:e0'/>
>
> <source network='default'/>
>
> <address type='pci' domain='0x0000' bus='0x00' slot='0x03'
> function='0x0'/>
>     </interface>
>     <serial type='pty'>
>       <target port='0'/>
>     </serial>
>
> <console
> type='pty'>
>
> <target
> type='serial' port='0'/>
>
> </console>
>     <input type='mouse'
> bus='ps2'/>
>     <graphics type='vnc'
> port='-1'
> autoport='yes'/>
>     <sound
> model='ich6'>
>       <address
> type='pci' domain='0x0000'
> bus='0x00' slot='0x04'
> function='0x0'/>
>
> </sound>
>     <video>
>
> <model type='cirrus' vram='9216'
> heads='1'/>
>       <address type='pci'
> domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
>     </video>
>
> <memballoon
> model='virtio'>
>
> <address
> type='pci'
> domain='0x0000' bus='0x00' slot='0x05'
> function='0x0'/>
>     </memballoon>
>
> </devices>
> </domain>
>
>
> Can someone tell
> me what I'm doing wrong?  I'm stumped.  And would it make a
> difference if I use virtio for the base disk also?
>
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

virtio issues

[aragonx]

Hello all,

I have just started working with KVM and
virtualization in general.  I have setup a client using Suse 9.3 x64
as the base and Fedora 15 x64 as the host.  The kernel in the client
has been upgraded to a custom 2.6.28.4 build.

Everything seems
to be working fine but I wanted to get some more disk performance so I'm
trying to get virtio running.  I don't care too much about the disk
the base OS is running on but I have a drive that I'm trying to add that I
want to use the virtio for.  I can add the drive using IDE or SCSI
drivers and it works fine (just slower had hoped).  If, however, I
switch to virtio, it doesn't show up in the client.

If I used
edit from virsh, I see:

<domain type='kvm'>
 
<name>MC1DB</name>
 
<uuid>f57c6236-2595-57ca-595b-aaaef4de87ea</uuid>
 
<memory>7680000</memory>
 
<currentMemory>7680000</currentMemory>
 
<vcpu>4</vcpu>
  <os>
   
<type arch='x86_64'
machine='pc-0.14'>hvm</type>
   
<boot
dev='hd'/>
   
<bootmenu
enable='no'/>
  </os>
 
<features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
 
<on_reboot>restart</on_reboot>
 
<on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/img/mc1db.img'/>
      <target dev='hda' bus='ide'/>
      <address type='drive'
controller='0'
bus='0' unit='0'/>
   
</disk>
    <disk type='block'
device='cdrom'>
      <driver
name='qemu' type='raw'/>
     
<source
dev='/dev/sr0'/>
     
<target
dev='hdc' bus='ide'/>
     
<readonly/>
      <address
type='drive'
controller='0'
bus='1' unit='0'/>
   
</disk>
    <disk
type='block'
device='disk'>
     
<driver
name='qemu' type='raw'/>
     
<source dev='/dev/sda1'/>
     
<target dev='vda' bus='virtio'/>
     
<address type='pci'
domain='0x0000'
bus='0x00' slot='0x07'
function='0x0'/>
   
</disk>
   
<controller type='ide'
index='0'>
      <address type='pci'
domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
   
<controller type='scsi' index='0'>
      <address type='pci' domain='0x0000'
bus='0x00' slot='0x06' function='0x0'/>
   
</controller>
    <interface
type='network'>
      <mac
address='52:54:00:fc:de:e0'/>
     
<source network='default'/>
     
<address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
   
<console
type='pty'>
     
<target
type='serial' port='0'/>
   
</console>
    <input type='mouse'
bus='ps2'/>
    <graphics type='vnc'
port='-1'
autoport='yes'/>
    <sound
model='ich6'>
      <address
type='pci' domain='0x0000'
bus='0x00' slot='0x04'
function='0x0'/>
   
</sound>
    <video>
     
<model type='cirrus' vram='9216'
heads='1'/>
      <address type='pci'
domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
   
<memballoon
model='virtio'>
     
<address
type='pci'
domain='0x0000' bus='0x00' slot='0x05'
function='0x0'/>
    </memballoon>
 
</devices>
</domain>


Can someone tell
me what I'm doing wrong?  I'm stumped.  And would it make a
difference if I use virtio for the base disk also?




-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.