> You havent looked at my other posts, I think.
> Have you checked the raw table? By default a netvm restricts traffic on
> a vif to the allocated IP: you need to remove that restriction.
>
> I made some notes on using an openBSD HVM as a netvm -
> https://github.com/unman/notes/blob/master/openBS
On Sat, Nov 24, 2018 at 02:41:07PM -0800, qubesuserma...@gmail.com wrote:
> On Thursday, November 22, 2018 at 7:35:38 PM UTC-5, unman wrote:
> > Attach Windows Vm to the new qube.
> > Attach your NIC to the Windows VM.
> > Now the WindowsVM has two network devices.
>
> Wow, I never thought that NI
On Thursday, November 22, 2018 at 7:35:38 PM UTC-5, unman wrote:
> Attach Windows Vm to the new qube.
> Attach your NIC to the Windows VM.
> Now the WindowsVM has two network devices.
Wow, I never thought that NIC can be attached to VM not on topmost, thanks for
the tip!
But, as I was setting up
On Friday, November 23, 2018 at 1:19:13 PM UTC-5, Sven Semmler wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 11/23/18 11:52 AM, Zrubi wrote:
> > I just wonder why would you do this?
>
> I suppose a Windows-only proprietary VPN client ... am I right?
>
> /Sven
Correct, good g
On Fri, Nov 23, 2018 at 06:52:32PM +0100, Zrubi wrote:
> > Is it just plain impossible for a WindowsVM to be a NetVM or I'm
> > missing something?
>
> I would not say impossible, but not working out of the box for sure.
> In practice: it would need a lot of development to make it work.
>
As I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/23/18 11:52 AM, Zrubi wrote:
> I just wonder why would you do this?
I suppose a Windows-only proprietary VPN client ... am I right?
/Sven
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAlv4RJgACgkQ2m4We49U
H7adyxAA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/21/18 5:47 PM, 'qubesusermarco' via qubes-users wrote:
> I have a Windows-7-VM assigned as some LinuxVM's netVM.
I just wonder why would you do this?
That would be big, bad, outdated and absolutely not designed for such
task...
> Is it just p
On Wed, Nov 21, 2018 at 04:47:33PM +, 'qubesusermarco' via qubes-users
wrote:
> I have a Windows-7-VM assigned as some LinuxVM's netVM. And I get the error
> below after some timeout when I try to start the appvm:
>
> ERROR: Start failed: internal error: libxenlight failed to create new doma
'qubesusermarco' via qubes-users wrote on 11/21/18 4:47 PM:
I have a Windows-7-VM assigned as some LinuxVM's netVM. And I get the error
below after some timeout when I try to start the appvm:
ERROR: Start failed: internal error: libxenlight failed to create new domain
'appVM_name'. See /var/lo
I have a Windows-7-VM assigned as some LinuxVM's netVM. And I get the error
below after some timeout when I try to start the appvm:
ERROR: Start failed: internal error: libxenlight failed to create new domain
'appVM_name'. See /var/log/libvirt/libxl/libxl-driver.log for details.
Here's the erro
10 matches
Mail list logo
