Just the output of one of the viridian enabled windows hvm machines:
Florian
virsh dumpxml titan
<domain type=''xen'' id=''40''>
<name>titan</name>
<uuid>cedb6201-82d6-3c96-4da3-e0bfad6a7501</uuid>
<memory>2097152</memory>
<currentMemory>2097152</currentMemory>
<vcpu>2</vcpu>
<os>
<type>hvm</type>
<loader>/usr/lib/xen/boot/hvmloader</loader>
<boot dev=''hd''/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset=''localtime''/>
<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/dsk/c0t600A0B800049E902000009294ACD08D6d0p0''/>
<target dev=''hda'' bus=''ide''/>
</disk>
<interface type=''bridge''>
<mac address=''00:16:3e:00:00:01''/>
<source bridge=''e1000g3''/>
<script path=''/usr/lib/xen/scripts/vif-vnic''/>
<target dev=''vif40.0''/>
</interface>
<serial type=''pty''>
<source path=''/dev/pts/4''/>
<target port=''0''/>
</serial>
<console type=''pty''
tty=''/dev/pts/4''>
<source path=''/dev/pts/4''/>
<target port=''0''/>
</console>
<input type=''tablet'' bus=''usb''/>
<input type=''mouse'' bus=''ps2''/>
<graphics type=''vnc'' port=''5900''
autoport=''yes'' keymap=''de''/>
</devices>
</domain>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Hi Florian, On 10/10/2009 11:40 AM, Florian Manschwetus wrote:> Just the output of one of the viridian enabled windows hvm machines:Right. The way it works today is that viridian in enabled if you create a hvm guest with the guest os type set to windows. It''s not exposed to libvirt, etc... Is this a problem for you? MRJ
Am 13.10.2009 14:52, schrieb Mark Johnson:> > Hi Florian, > > On 10/10/2009 11:40 AM, Florian Manschwetus wrote: >> Just the output of one of the viridian enabled windows hvm machines: > > Right. The way it works today is that viridian in enabled > if you create a hvm guest with the guest os type set to windows. > It''s not exposed to libvirt, etc... > > Is this a problem for you? > > > > > MRJ >No if this behavior is guarantied, then it is ok. Florian