Tried that as well, but this has to be something that gets set at the OS level
and loaded, as if you look at dmesg output, you can see all the vnet?? nodes as
the OS comes online.So the question is, what is virt-install doing that
creates the needed vnet interface that is part of the bridge.
This is pretty epic if true.
I'm installing some Fail 2008r2 now to check.
Is your hypervisor running CentOS 6 or 7?
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Dennis Jacobfeuerborn"
> To: "Discussion about the virtualization on
You most definitely do not need to destroy and re-create a VM just to
add a 2nd network interface.
I don't think those vnet interfaces got created by the host OS. I
believe those are created by KVM (or libvirt) when you start a VM. I
could be wrong though. But I just checked on my CentOS 6 K
Confirmed! :-(
Installing the SUSE Network and Storage drivers from the Optional Updates
renders the OS unbootable.
http://img.nux.ro/xR4-Screenshot.png
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Nux!"
> To: "Discussion about
On Tue, Dec 8, 2015 at 4:17 PM, President wrote:
> 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. An
How do you decide what MAC address to use for that VM interface? As I just
tried to change the MAC to some other value close, like I made
'52:54:00:34:e1:21' into say '52:54:00:34:e1:32', and when I try and load it
in, I get the following:
error: XML error: Attempted double use of PCI Address
The MAC address you gave is fine. I use random MAC addresses just like
you did.
Your PCI bus address also has to be unique within a given VM. I'm sorry,
I forgot to mention that. Look at my configuration example I sent. These
are emulated (virtual) network cards attached to the emulated (virtu
BTW, adding a 2nd virtual nic to a guest can also be done with command
line tools (I just googled this for you) :
https://kashyapc.fedorapeople.org/virt/add-network-card-in-guest.txt
( It came up as 1st result when I searched for: virsh add network
interface to existing guest )
But if you look
Op 09-12-15 om 01:00 schreef Dennis Jacobfeuerborn:
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 follow
On 09.12.2015 13:47, Patrick Bervoets wrote:
>
>
> Op 09-12-15 om 01:00 schreef Dennis Jacobfeuerborn:
>> 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 re
That is exactly what I was looking for, and worked perfectly, and will now
be added to my notes on working with VM's. I figured it was a matter of me
just not using the right search words in google, but damn if I could find
that page, and I tried.
Using the info on that page, I added an int
Op 09-12-15 om 14:23 schreef Dennis Jacobfeuerborn:
Yes, this is a CentOS 6 Host using regular libvirt based virtualization. The
Suse driver is apparently an optional update that gets delivered using the
regular Microsoft update mechanism. It's hard to believe that they didn't catch
a comple
It looks like no XSA-142 patch, which is "libxl fails to honour readonly flag
on disks with qemu-xen" has been applied to Xen4CentOS. I assume this
was on purpose?
If not, I can have someone try adding the original patch from
http://xenbits.xen.org/xsa/advisory-142.html and some variant of the c
13 matches
Mail list logo
