[CentOS-virt] Centos virsh - add a physical device

Yes, you are able to add a CDROM device to your guest.

You can add either a physical drive or an ISO image. Are you using
virt-manager or just config files at the command line?

Tait

Hi,

I using only a comman line, my centos server have only text console
without a X server. I used a virsh.

For at ll

Can you post the config file for the guest?

This is a guest config file with xml and native format:

cat win2khvm.xml
<domain type='xen'
id='50'>

<name>win2k8-hvm</name>

<uuid>c53ac13f-d32f-9934-8c0b-a8728fb52f19</uuid>
<memory>1048576</memory>
<currentMemory>1048576</currentMemory>
<vcpu>1</vcpu>
<os>
<type>hvm</type>
<loader>/usr/lib/xen/boot/hvmloader</loader>
<boot dev='hd'/>
</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/lib/xen/bin/qemu-dm</emulator>
<disk type='block' device='disk'>
<driver name='phy'/>
<source dev='/dev/vol1/win2k8'/>
<target dev='hda' bus='ide'/>
</disk>
<disk type='block' device='cdrom'>
<driver name='phy'/>
<source dev='/dev/cdrom'/>
<target dev='hdc' bus='ide'/>
<readonly/>
</disk>
<interface type='bridge'>
<mac address='00:16:36:2a:e4:15'/>
<source bridge='eth0'/>
<script path='/etc/xen/scripts/vif-bridge'/>
<target dev='vif50.0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/2'/>
<target port='0'/>
</serial>
<console type='pty' tty='/dev/pts/2'>
<source path='/dev/pts/2'/>
<target port='0'/>
</console>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='5900' autoport='yes' keymap='en-us'/>
</devices>
</domain>


Native config:

cat win2k8.cfg
name = "win2k8-hvm"
uuid = "c53ac13f-d32f-9934-8c0b-a8728fb52f19"
maxmem = 1024
memory = 1024
vcpus = 1
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "c"
pae = 1
acpi = 1
apic = 1
localtime = 0
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
device_model = "/usr/lib/xen/bin/qemu-dm"
vfb = [ "type=vnc,vncunused=1,keymap=en-us" ]
disk = [ "phy:/dev/vol1/win2k8,hda,w", "phy:/dev/cdrom,hdc:cdrom,r" ]
vif = [
"mac�:16:36:2a:e4:15,bridge=eth0,script=vif-bridge,vifname=vif50.0" ]
parallel = "none"
serial = "pty"

If you want it to boot from anything in the CDROM device, change this to
read:

boot = "dc"
Alright, if I am not mistaken your system already has a CDROM setup. It
is pointing to the physical interface /dev/cdrom. I may be confusing
your question, but did you want to add another one?

If the current one isn't working you will have to figure out what the
CDROM device name is (/dev/sr0 is also an option) but make sure you have
modified the boot= line as I did above.

You should also be able to add an ISO image to act as the CDROM (all on
one line):

disk [ "phy:/dev/vol1/win2k8,hda,w","file:/path/to/file.iso,hdc:cdrom,r"]
Tait

I'm in the middle of a (re-)install on a domU and looking for quick
replies as too which GPLPV to use on a Windows 2008 Server install.

Windows 32bit
Xen/Centos 64bit (x86_64)

The question is regarding whether the driver to load into Windows is for
"itself" (32bit) or the underlying hypervisor (x86_64) as in:

====
There is now one download per platform/architecture, named as follows:
* gplpv_<chk/fre>_<platform>_<arch>_<version>.msi
* chk is a 'checked' build which contains debug info (please use
these if you want any assistance in fixing bugs)
* fre is a 'free' build which contains no debug info
* platform is 'wxp' for XP, 'wnet' for 2003, and 'wlh' for Vista/2008
* arch is 'x86' for 32 bit and 'AMD64' for 64 bits
====

Is the architecture ('<arch>') x86 (for the Windows domU 32bit
architecture) or x86_64 (for the arch version of Xen running)?

I'm having a gray moment.

It happens.

The arch should be for the domU as it has to install drivers in the domU
only, not dom0.

domU architecture, so in this case 32-bit. I'm using gplpv on quite a
few Server 2003 32-bit domUs running on 64-bit hardware & 64-bit
Xen/CentOS-dom0.

Eric

An HTML attachment was scrubbed...
URL: http://lists.centos.org/pipermail/centos-virt/attachments/20090930/df894508/attachment.html

An HTML attachment was scrubbed...
URL: http://lists.centos.org/pipermail/centos-virt/attachments/20090930/31e0f6d9/attachment.html