[PATCH] xen: do not set NX bit when making initial pagetables readonly
by Ian Campbell
__supported_pte_mask has not been correctly configured at this point
and Xen prevents us from using the NX bit if the hardware does not
support it. Some BIOSes seem to offer the option to disable NX.
Signed-off-by: Ian Campbell <ian.campbell(a)citrix.com>
Cc: Mark McLoughlin <markmc(a)redhat.com>
Cc: Jon Swanson <jswanson(a)valuecommerce.co.jp>
Cc: fedora-virt(a)redhat.com
Cc: Jeremy Fitzhardinge <jeremy(a)goop.org>
Cc: Ingo Molnar <mingo(a)elte.hu>
---
arch/x86/xen/enlighten.c | 24 +++++++++++++-----------
1 files changed, 13 insertions(+), 11 deletions(-)
diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
index bea2152..e705bdf 100644
--- a/arch/x86/xen/enlighten.c
+++ b/arch/x86/xen/enlighten.c
@@ -53,6 +53,8 @@
#include "mmu.h"
#include "multicalls.h"
+#define _KERNPG_TABLE_RO __pgprot(_KERNPG_TABLE & ~_PAGE_RW)
+
EXPORT_SYMBOL_GPL(hypercall_page);
DEFINE_PER_CPU(struct vcpu_info *, xen_vcpu);
@@ -1487,9 +1489,9 @@ static __init void xen_map_identity_early(pmd_t *pmd, unsigned long max_pfn)
}
for (pteidx = 0; pteidx < ident_pte; pteidx += PTRS_PER_PTE)
- set_page_prot(&level1_ident_pgt[pteidx], PAGE_KERNEL_RO);
+ set_page_prot(&level1_ident_pgt[pteidx], _KERNPG_TABLE_RO);
- set_page_prot(pmd, PAGE_KERNEL_RO);
+ set_page_prot(pmd, _KERNPG_TABLE_RO);
}
#ifdef CONFIG_X86_64
@@ -1543,12 +1545,12 @@ static __init pgd_t *xen_setup_kernel_pagetable(pgd_t *pgd,
xen_map_identity_early(level2_ident_pgt, max_pfn);
/* Make pagetable pieces RO */
- set_page_prot(init_level4_pgt, PAGE_KERNEL_RO);
- set_page_prot(level3_ident_pgt, PAGE_KERNEL_RO);
- set_page_prot(level3_kernel_pgt, PAGE_KERNEL_RO);
- set_page_prot(level3_user_vsyscall, PAGE_KERNEL_RO);
- set_page_prot(level2_kernel_pgt, PAGE_KERNEL_RO);
- set_page_prot(level2_fixmap_pgt, PAGE_KERNEL_RO);
+ set_page_prot(init_level4_pgt, _KERNPG_TABLE_RO);
+ set_page_prot(level3_ident_pgt, _KERNPG_TABLE_RO);
+ set_page_prot(level3_kernel_pgt, _KERNPG_TABLE_RO);
+ set_page_prot(level3_user_vsyscall, _KERNPG_TABLE_RO);
+ set_page_prot(level2_kernel_pgt, _KERNPG_TABLE_RO);
+ set_page_prot(level2_fixmap_pgt, _KERNPG_TABLE_RO);
/* Pin down new L4 */
pin_pagetable_pfn(MMUEXT_PIN_L4_TABLE,
@@ -1597,9 +1599,9 @@ static __init pgd_t *xen_setup_kernel_pagetable(pgd_t *pgd,
set_pgd(&swapper_pg_dir[KERNEL_PGD_BOUNDARY],
__pgd(__pa(level2_kernel_pgt) | _PAGE_PRESENT));
- set_page_prot(level2_kernel_pgt, PAGE_KERNEL_RO);
- set_page_prot(swapper_pg_dir, PAGE_KERNEL_RO);
- set_page_prot(empty_zero_page, PAGE_KERNEL_RO);
+ set_page_prot(level2_kernel_pgt, _KERNPG_TABLE_RO);
+ set_page_prot(swapper_pg_dir, _KERNPG_TABLE_RO);
+ set_page_prot(empty_zero_page, _KERNPG_TABLE_RO);
pin_pagetable_pfn(MMUEXT_UNPIN_TABLE, PFN_DOWN(__pa(pgd)));
--
1.5.6.5
14 years, 3 months
F11 features
by Mark McLoughlin
Hey,
We're a bit behind on writing up descriptions for the virt features
coming in F11, but here's the first two pages:
https://fedoraproject.org/wiki/Features/VirtVNCAuth
Define a mapping of SASL authentication into the VNC protocol, and
implement it for QEMU and GTK-VNC, providing strongly authenticated,
securely encrypted remote access of virtual guest consoles.
https://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment
Assign PCI devices from your KVM host machine to guest virtual
machines. A common example is assigning a network card to a guest.
Please jump in with comments, testing, wiki edits, etc.
Cheers,
Mark.
14 years, 4 months
Fedora virt status
by Mark McLoughlin
2009-03-03 Feature freeze (32 days)
2009-03-10 Beta Freeze (39 days)
2009-04-14 Final freeze (74 days)
Alpha Freeze, Take 2
====================
Cole released new versions of virt-manager and virtinst releases:
http://www.redhat.com/archives/fedora-virt/2009-January/msg00041.html
http://www.redhat.com/archives/fedora-virt/2009-January/msg00042.html
Unfortunately, no libvirt release, but more on that below.
The biggest virt issue that we would have liked to get resolved the alpha is
the infamous "unsynchronized TSC" issue which causes guests on certain hosts
to hang or crash:
https://bugzilla.redhat.com/475598
Juan Quintela is close to a fix suitable for sending upstream, but in the
meantime we've applied a temporary fix to disable KVM's paravirt clock on those
hosts. The current rawhide kernel has this fix and the upcoming 2.6.29 kernel
for F-10 will have it too.
On Monday, rel-eng met and decided to try for an alpha refresh using Tuesday's
rawhide. A number of issues were found including:
https://bugzilla.redhat.com/481716
rawhide anaconda traceback when installing KVM guest (yum-HEAD.patch)
This turned out to be a problem with yum and was quickly fixed. There also
were issues with latest yum that affected the tools for building the
release tree and these were fixed.
https://bugzilla.redhat.com/482907
f11alpha anaconda hanging when moving to timezone screen
Initially KVM was accussed, but evidence was produced and we were granted
a reprieve.
Right now, the fingers are pointing at a bizarre GtkCheckButton related
issue but no doubt the problem will turn out to be completely random.
Plenty of fun to be had here if anyone is interested in helping.
So, the alpha has definitely frozen now, but blockers are still being worked
on.
Fedora Weekly News
==================
A new issue of FWN was posted with some nice virt coverage:
http://fedoraproject.org/wiki/FWN/Issue160#Virtualization
Thanks to Dale Bewley.
Fedora 10 Kernel
================
Plans have changed, F10 is going to get 2.6.29:
https://www.redhat.com/archives/fedora-kernel-list/2009-January/msg00098....
Initial builds are available in Koji for testing.
libvirt
=======
Work in preparation for a new release has been ongoing all week. The release is
likely to happen this weekend.
Some highlights from the week:
- Lots and lots of fixes
- libvirt_proxy vulvnerability:
http://thread.gmane.org/gmane.comp.emulators.libvirt/11459
- qemu disk format support, including support for COW backing stores
- virtio GSO is now enabled for KVM guests where appropriate
PCI Device Assignment
=====================
https://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment
This came up for review by FESCo this week and received a very positive
reception - seven +1s. Lots of time was spent discussing, but most questions
seemed to be just FESCo member's personal interest in the feature rather than
any real concerns over whether it should be approved.
Kevin Fenzi (nirik) and Dennis Gilmore (dgilmore) both mentioned that they're
using TDM cards with Asterisk and would like to be able to move this service
into a KVM guest. Supporting these cards are on of the most common requests.
Some time was spent discussing exactly what PCI devices can be assigned. The
first requirement is VT-d and AMD IOMMU. PCIe devices should work well.
Multiple conventional PCI devices on the same bridge can't be assigned to
different guests. Graphics cards won't work for now.
Will Woods asked about VT-d support causing issues with some BIOSes. Fedora
disabled CONFIG_DMAR in May because of this issue but it has been re-enabled
recently again. The goal is to resolve any of these issues, perhaps through
blacklisting. Any users experiencing issues should try disabling DMAR with
intel_iommu=off and report to iommu(a)lists.linux-foundation.org if that fixes
their problem.
On the testing front, basic device assignment seems to be working. Assigning
an e1000e device to a guest using qemu-kvm directly from the command line works
fine. One issue is that rawhide was missing the pci-stub module:
https://bugzilla.redhat.com/482792
but that's now resolved. A more serious issue is "TX Unit Hang" problems when
trying to do an install using an assigned NIC. These warnings seems to be a
suggest that the NIC isn't being fully reset before being used.
CONFIG_DMAR
===========
Related to PCI device assignment are Intel VT-d issues that have been reported
recently.
Basically, on some machines - e.g. Lenovo x200, Dell Precision T5400 and Dell
Latitude E6400 - VT-d support is causing serious and, in one case, data loss.
Kyle Martin sensibly made intel_iommu=off the default in rawhide:
* Fri Jan 23 2009 Kyle McMartin <kyle(a)redhat.com>
- disable intel_iommu by default (enable with "intel_iommu=on")
and has sent his patch to do so upstream.
More details on the issue:
https://bugzilla.redhat.com/479996
http://bugzilla.kernel.org/show_bug.cgi?id=12578
https://lists.linux-foundation.org/pipermail/iommu/2009-January/001028.html
David Woodhouse has promised to dig into it next week. Bhavesh Davda and
Adar Dembo from VMware are both working on the issue too. Adar tried
DMA_API_DEBUG, but no driver issues were uncovered.
Disk Access Errors
==================
Dan Walsh and Cole have been looking into how to solve the issue of qemu
blowing up when it doesn't have access to disk images because e.g. it was
downloaded to a user's homedir and doesn't have the appropriate SELinux label.
One suggestion is to add a <code>qemuaccess</code> program which would be run
early on by virt-managerto check that qemu will have access. That way the
problem could be reported earlier to the user in a manner that is easier to
diagnose.
sVirt
=====
A new F11 feature page has been posted:
https://fedoraproject.org/wiki/SVirt_Mandatory_Access_Control
"sVirt integrates SELinux with the Fedora virtualization stack to allow
Mandatory Access Control (MAC) security be applied to guest virtual
machines. Amongst other things, this prevents a security bug in the
hypervisor from allowing guests to attack the host or one another."
James Morris is hacking away on adding this to libvirt. Dan Walsh is going to
handle making sure it works well for Fedora.
Fedora Package Updates
======================
A discussion around what a Fedora package update description should contain
generated a wide discussion around how package maintainers should handles
updates in general. Some guidelines have been proposed here:
https://fedoraproject.org/wiki/User:Markmc/Draft_package_update_guidelines
These guidelines are virt specific, but might interest virt package
maintainers.
pv_ops
======
Jeremy Fitzhardinge has posted some patches to reduce the overhead of enabling
paravirt_ops on bare-metal:
http://lkml.org/lkml/2009/1/28/438
"In testing, the net result was that the overhead dropped by about 75%"
Fedora's kernel has pv_ops enabled, of course, so this should prove a nice win.
bugs
====
DOOM-O-METER: 186 open bugs last week, 191 this week. Booo!
(Hmm, how do you drop needinfo bugs from bugzilla queries?)
Some interesting ones:
https://bugzilla.redhat.com/454415
dnsmasq --user=nobody broken on F9
-> fixed now
https://bugzilla.redhat.com/479622
libvirt should avoid creating virtual networks with the same bridge name
-> Edouard found that if he created multiple virtual networks in
virt-manager, they all had the same bridge name.
https://bugzilla.redhat.com/460649
libvirtd requires restart in order to detect KVM support
-> If you install KVM after libvirtd has started, KVM support won't be
available in virt-manager. Fixing this may involve libvirtd having
to be restarted, or libvirtd might re-poll periodically for KVM.
https://bugzilla.redhat.com/480779
https://bugzilla.redhat.com/483204
F10 kvm mmu bugs:
-> Some users reported KVM MMU issues. The wiley Glauber Costa noticed that
the kernels in question had an nVidia driver loaded at the time. Since
Linux developers can't do anything to fix closed source drivers, these
bugs will be closed unless they can be reproduced without the nVidia
driver.
https://bugzilla.redhat.com/480822
https://bugzilla.redhat.com/480850
virtio_net oops during rawhide guest install on rawhide host
-> These oopses in slab_alloc() are still a major issue.
14 years, 4 months
f10 x86_64 xen VM guests fail to boot on f8 host
by Jon Swanson
Hi,
I've posted this same problem on the fedora-xen list, and the fedora
forums. Sorry to anybody who is getting duplicates.
Additional log info is available at
http://forums.fedoraforum.org/showthread.php?p=1149972&posted=1#post1149
972
It is also formatted a lot better and may be easier to follow.
------------------------------------------------------------------
I have two machines running fresh installs of f8 with the xen. Kernel
and all software versions are the same on both.
Specifically:
[root@machineA boot]# uname -a
Linux machineA 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008
x86_64 x86_64 x86_64 GNU/Linux
[root@machineA boot]# virsh version
Compiled against library: libvir 0.4.4
Using library: libvir 0.4.4
Using API: Xen 3.0.1
Running hypervisor: Xen 3.1.0
------------------------------------------------------------------
And:
------------------------------------------------------------------
[root@machineB ~]# uname -a
Linux machineB 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008
x86_64 x86_64 x86_64 GNU/Linux
[root@machineB ~]# virsh version
Compiled against library: libvir 0.4.4
Using library: libvir 0.4.4
Using API: Xen 3.0.1
Running hypervisor: Xen 3.1.0
MachineA has two AMD Opteron 275s. MachineB has four Intel(R) Xeon(TM)
CPU 2.80GHz processors.
Both machines are as up to date as possible.
I can boot or create x86_64 f10 guests on MachineA with no trouble
whatsoever.
MachineB will not boot/create x86_64 f10 guests.
The configuration files are created in the same manner, but as soon as
Xen tries to unpause the newly created domain, it crashes pretty much
instantly.
------------------------------------------------------------------
/var/log/xen/xend.log relevant output:
[2009-01-16 14:45:32 4120] DEBUG (DevController:150) Waiting for devices
vtpm.
[2009-01-16 14:45:32 4120] INFO (XendDomain:1130) Domain f10testB (21)
unpaused.
[2009-01-16 14:45:32 4120] WARNING (XendDomainInfo:1203) Domain has
crashed: name=f10testB id=21.
[2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1802)
XendDomainInfo.destroy: domid=21
[2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1821)
XendDomainInfo.destroyDomain(21)
------------------------------------------------------------------
I've also tried moving a functional guest from MachineA to MachineB to
boot it there, with the same results. Guest will not boot on MachineB.
f8 64bit guests will boot on MachineB with no problems.
f10 32bit guests will boot on MachineB with no problems.
Only 64bit machines seem to be borked.
Mark on the fedora-xen list suggested running xenctx on the crashed
domain. Output is as follows:
------------------------------------------------------------------
xenctx output:
/usr/lib64/xen/bin/xenctx -s System.map-2.6.27.5-117.fc10.x86_64 46
rip: ffffffff8100b8a2 set_page_prot+0x6d
rsp: ffffffff81573f08
rax: ffffffea rbx: 000016e1 rcx: 00000055 rdx: 00000000
rsi: 800000014ffc6061 rdi: ffffffff816e1000 rbp: ffffffff81573f68
r8: 0000000f r9: ffffffff817eb450 r10: ffffffff817eb650 r11:
00000010
r12: ffffffff816e1000 r13: 800000014ffc6061 r14: 8000000000000161
r15: 00000016
cs: 0000e033 ds: 00000000 fs: 00000000 gs: 00000000
Stack:
0000000000000055 0000000000000010 ffffffff8100b8a2 000000010000e030
0000000000010082 ffffffff81573f48 000000000000e02b ffffffff8100b89e
0000000000000200 ffffffff816e4000 0000000000000800 0000000000002c00
ffffffff81573ff8 ffffffff815a3c60 0000000000002c00 0000000000000000
Code:
7b 4a 1d 00 4c 89 e7 4c 89 ee 31 d2 e8 22 d9 ff ff 85 c0 74 04 <0f> 0b
eb fe 5b 41 5c 41 5d 41 5e
Call Trace:
[<ffffffff8100b8a2>] set_page_prot+0x6d <--
[<ffffffff8100b8a2>] set_page_prot+0x6d
[<ffffffff8100b89e>] set_page_prot+0x69
[<ffffffff815a3c60>] xen_start_kernel+0x5dd
------------------------------------------------------------------
I also finally figured out you can look at the Xen dmesg, which includes
the following line:
(XEN) traps.c:405:d44 Unhandled invalid opcode fault/trap [#6] in domain
46 on VCPU 0 [ec=0000]
The domain does install so the following bug does not seem to be the
cause of the current issues:
http://fedoraproject.org/wiki/Bugs/F10Common#Installing_Fedora_10_DomU_o
n_Fedora_8_Dom0_Fails
Any information / help / insight as to why this is happening would be
very much appreciated. The machines are pretty similar, and since the
guests are paravirtualized it does not really make sense for the
processors to be the cause of the problem.
Thanks,
jon
14 years, 4 months
selinux /dev/net/tun
by James Hubbard
I have a windows xp guest working using qemu-kvm with "-net nic -net
user". I'm attempting to use bridging. I've created the br0 interface
and modified my eth0 file. Bridging seems to be working. I'm able to
access the machine from other places. When I try to start qemu-kvm
with these options "-net nic,macaddr=11:22:33:44:55:66 -net tap" I get
this error:
warning: could not configure /dev/net/tun: no virtual network emulation
Could not initialize device 'tap'
These errors are in /var/log/messages.
setroubleshoot: SELinux is preventing qemu-kvm (qemu_t) "read write"
to tun (virt_image_t). For complete SELinux messages. run sealert -l
2ca593ab-ec5f-407b-a6d5-291abc0b2e29
setroubleshoot: SELinux is preventing chcon (unconfined_t) "mac_admin"
unconfined_t. For complete SELinux messages. run sealert -l
94da622e-0446-455d-bd85-da5f9d486b7b
setroubleshoot: SELinux is preventing qemu-kvm (qemu_t) "net_admin"
qemu_t. For complete SELinux messages. run sealert -l
9ab69ab1-ce67-442f-a628-f1909914a52f
Any suggestions?
--
James Hubbard
14 years, 4 months
running Vista under KVM
by Wayne Feick
I've been trying to experiment with running Vista under KVM today, but
I'm running into a cryptic error message that doesn't mean much to me:
Unable to complete install '<class 'libvirt.libvirtError'> internal error QEMU quit during console startup
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/create.py", line 723, in do_install
dom = guest.start_install(False, meter = meter)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 732, in start_install
return self._do_install(consolecb, meter, removeOld, wait)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 767, in _do_install
self.domain = self.conn.createLinux(install_xml, 0)
File "/usr/lib64/python2.5/site-packages/libvirt.py", line 915, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: internal error QEMU quit during console startup
'
Here is what I did.
I made sure libvirtd was running, launched Applications -> System Tools
-> Virtual Machine Manager and walked my way through the wizard screens
until I get to the "Ready to begin installation" screen.
Summary
Virtualization method: Fully virtualized
Initial memory: 512 MB
Maximum memory: 512 MB
Virtual CPUs: 1
Install media
Operating System: Microsoft Windows Vista
Installation source: /home/waf/vista64.iso
Kiskstart source:
Storage
Disk image: /var/lib/libvirt/images/Vista-1.img
Disk size: 4000 MB
Network
Connection type: Virtual network
Target: default
MAC address: -
Sound
Enable Audio: True
When I select Finish, I get a popup window with the error message.
I have the right processor capabilities to virtualize. It's a Core 2
T7200 with the following flags:
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl
pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
I can't seem to find a good KVM quick start guide on fedoraproject.org.
Any pointers would be greatly appreciated.
Wayne.
14 years, 4 months
Re: virt-p2v
by Richard W.M. Jones
On Thu, Jan 22, 2009 at 10:34:22AM -0800, Brian Krusic wrote:
> I've used virt-p2v many times with great success.
>
> However I have an issue.
>
> I've always converted hosts having small disks of around 35G over to
> domUs but have an issue were my current host in need of being
> virtualized has a physical disk of 400G but its / partition is only 35G,
> the rest of the drive is unallocated/unpartitioned and therefore unused.
[...]
> I obviously don't want to migrate the entire 400G disk as it only has a
> 35G root partition (ext3, no LVMs in this case).
Oh dear, this is a problem :-(
The answer unfortunately is that virt-p2v currently doesn't support
this - we can only migrate whole block devices.
Unfortunately even compression doesn't help very much here. Even if
the disk is mainly zeroes, the gzip-based compression used doesn't
compress very well, so you'll still have a longish wait. You can try
selecting compression anyway to see if it helps.
It's on the long to-do list to fix this so that people can migrate
partial disks (including just subdirectories, and excluding
subdirectories).
BTW, if the disk doesn't use LVM, you will need to use version 0.9.9,
uploaded to the website a few days ago, because that fixes a bug
related to having the root partition not being on LVM.
Rich.
--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
Read my OCaml programming blog: http://camltastic.blogspot.com/
Fedora now supports 68 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
14 years, 4 months
How To Get Fedora 10 Guest To See USB Device?
by Robert L Cochran
Here is the xml I have for my Fedora 10 guest machine running in my
Fedora 10 host machine.
Question: if I plug a USB flash drive into the host, how do I make that
accessible (as in readable and writable) to the guest machine? Look at
the <hostdev... > ebtry I have coded below. I must be doing something
wrong because when I:
*plug the flash drive in to the host
*verify the drive is mounted on the host
*start the guest
the guest cannot see that flash drive. Is the xml formatted incorrectly?
Or do I have to do something in the guest? Or do I need to plug the
flash drive in after starting the guest?
<domain type='kvm'>
<name>fedora10x64</name>
<uuid>33e7e731-4e18-dd90-222e-b1df83a76cad</uuid>
<memory>2097152</memory>
<currentMemory>2097152</currentMemory>
<vcpu>1</vcpu>
<os>
<type arch='x86_64' machine='pc'>hvm</type>
<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/bin/qemu-kvm</emulator>
<disk type='file' device='disk'>
<source file='/var/lib/libvirt/images/fedora10x64.img'/>
<target dev='vda' bus='virtio'/>
</disk>
<interface type='bridge'>
<source bridge='br0'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target port='0'/>
</console>
<hostdev mode='subsystem' type='usb'>
<source>
<vendor id='0x067b'/>
<product id='0x2517'/>
</source>
</hostdev>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
<sound model='es1370'/>
</devices>
</domain>
------------------------------------------------------------------
Thanks much!
Bob Cochran
14 years, 4 months
[ANNOUNCE] New release virtinst 0.400.1
by Cole Robinson
I'm happy to announce a new virtinst release, version 0.4.1. The release
can be downloaded from:
http://virt-manager.org/download.html
The direct download link is:
http://virt-manager.org/download/sources/virtinst/virtinst-0.400.1.tar.gz
This release includes:
- Add virt-image -> vmx support to virt-convert, replacing virt-pack
(Joey Boggs)
- Add disk checksum support to virt-image (Joey Boggs)
- Enhanced URL install support: Debian Xen paravirt, Ubuntu kernel and
boot.iso, Mandriva kernel, and Solaris Xen Paravirt
(Guido Gunther, John Levon, Cole Robinson)
- Expanded test suite
- Numerous bug fixes, cleanups, and minor improvements
Thanks to everyone who has contributed to this release through testing,
bug reporting, submitting patches, and otherwise sending in feedback!
Thanks,
Cole
14 years, 4 months
[ANNOUNCE] New release virt-manager 0.6.1
by Cole Robinson
I'm happy to announce a new virt-manager release, version 0.6.1. The
release can be downloaded from:
http://virt-manager.org/download.html
The direct download link is:
http://virt-manager.org/download/sources/virt-manager/virt-manager-0.6.1....
This release includes:
- VM disk and network stats reporting (Guido Gunther)
- VM Migration support (Shigeki Sakamoto)
- Support for adding sound devices to an existing VM
- Enumerate host devices attached to an existing VM
- Allow specifying a device model when adding a network device to an
existing VM
- Combine the serial console view with the VM Details window
- Allow connection to multiple VM serial consoles
- Bug fixes and many minor improvements.
Thanks to everyone who has contributed to this release through testing,
bug reporting, submitting patches, and otherwise sending in feedback!
Thanks,
Cole
14 years, 4 months
