On 06-12-16 23:39, Даниил Ландау wrote:
I had a very similar problem a couple of days ago.
I solved it by using unique vlan numbers for each nic/vnic pair in the qemu
arguments, i.e.:
/usr/bin/qemu-system-x86_64 \
-name "$(basename $NAME)" \
-boot cd \
-enable-kvm \
I had a very similar problem a couple of days ago.
I solved it by using unique vlan numbers for each nic/vnic pair in the qemu
arguments, i.e.:
/usr/bin/qemu-system-x86_64 \
-name "$(basename $NAME)" \
-boot cd \
-enable-kvm \
-vnc 0.0.0.0:$VNC \
-smp 2 \
> On Dec 5, 2016, at 10:54 AM, Willems Dirk wrote:
>
> Did you already receive any news about the KVM issue by Joyent?
I have not. Given it's getting toward the end of the year, I'm not sure if I
will, either.
> Also a second question :
>
> Which hardware you
On 2016-11-28 16:40, Dan McDonald wrote:
>> On Nov 25, 2016, at 7:49 AM, Willems Dirk wrote:
>>
>>> Hello,
>>>
>>> First of all Thank you for this wonderful OS.
>>>
>>> I'm using it for Home virtualization and have the same server also running
>>> on my Work for testing
> On Nov 25, 2016, at 7:49 AM, Willems Dirk wrote:
>
>> Hello,
>>
>> First of all Thank you for this wonderful OS.
>>
>> I'm using it for Home virtualization and have the same server also running
>> on my Work for testing purpose and want to use it for Production
Hello,
First of all Thank you for this wonderful OS.
I'm using it for Home virtualization and have the same server also running on
my Work for testing purpose and want to use it for Production servers by my
clients.
But I've a small problem.
I'm trying to add a second nic to the KVM image but