Just a heads-up: A Xen package with XSAs through 163 is on its way
through the build system. I'll send an announcement when I've tagged
it as ready to be propagated to the mirrors.
As with the last XSA update, it will depend on having manually updated
to the new Virt SIG repository layout. If
Not sure if this actually made it to the list the first time.
Here is the SERIAL output (bottom of message after your questions). Googling
the error indicates it's something people ran into a few years back but was
supposedly fixed. Any ideas?
I can verify that if I REMOVE the second
On Tue, Dec 8, 2015 at 12:23 PM, George Dunlap wrote:
> Just a heads-up: A Xen package with XSAs through 163 is on its way
> through the build system. I'll send an announcement when I've tagged
> it as ready to be propagated to the mirrors.
>
> As with the last XSA update, it
I would stop the VM, edit its definition file (that's an XML file) and then
start it up. But be careful: After you edit the XML file, you need to
execute a command so KVM re-reads that file. I forgot that command, but you
can look it up on Google.
On Dec 9, 2015 7:52 AM, "Howard Leadmon"
On 09.12.2015 00:39, NightLightHosts Admin wrote:
> On Tue, Dec 8, 2015 at 5:26 PM, Dennis Jacobfeuerborn
> wrote:
>> Hi,
>> today we ran into a strange problem: When performing a regular Windows
>> 2008r2 update apparently among other things the following was installed:
>>
On Tue, Dec 8, 2015 at 5:26 PM, Dennis Jacobfeuerborn
wrote:
> Hi,
> today we ran into a strange problem: When performing a regular Windows
> 2008r2 update apparently among other things the following was installed:
> "SUSE - Storage Controller - SUSE Block Driver for
Maybe my google-fu is failing me, but I have spent the past couple hours
looking at how to add a vnet? Device to my KVM host running CentOS 6, and
for the life of me I can't get this going.
>From all my research if I want to add a device I should just do 'brctl addif
br1 vnet14' if I