Hi,
I'm in the progress to migrate a custom fedora-based proxyVM to a debian 9
template,
because debian's longer support cycles.
On my fedora proxyVM I simply disabled
qubes-network and
qubes-firewall
to be in full control of the firewall rules and forwarding.
When I disable these services on
> The data is stored in the private.img file in that folder.
>
> You can either create a new qube, and then attach the file:
> qvm-block -A dom0:/var/lib/qubes/appvms/oldname /private.img
> then mount /dev/xvdi in , and extract the data from
> /mnt/home/user
> OR: mount the private.img file in
Hello,
it looks like I got hit by a severe problem that prevents me from starting an
appvm
I searched the bugtracker and it looks like:
https://github.com/QubesOS/qubes-issues/issues/2054
I also renamed a VM and it no longer starts.
The folder under
/var/lib/qubes/appvms/oldname
is still
Marek Marczykowski-Górecki:
> On Tue, Apr 18, 2017 at 10:54:00AM +0000, Joonas Lehtonen wrote:
>
>
>> Joonas Lehtonen:
>>> Hi,
>>>
>>> just a quick notice about todays kernel update.
>>>
>>> After upgrading, the new kernel 4.4.55
Joonas Lehtonen:
> Hi,
>
> do I need to worry about that warning? (VMs work fine)
> How can I fix it?
This was related to the recent dom0 kernel update for VMs and fixed with:
qvm-prefs -s kernel default
--
You received this message because you are subscribed to the Google Gr
Hi,
just a quick notice about todays kernel update.
After upgrading, the new kernel 4.4.55 became the new default for all
VMs that previously used the default kernel, but
VMs would no longer boot because they claim that an old kernel the one
that got removed during the upgrade (4.4.11?) is no
Reg Tiangha:
> On 04/17/2017 03:45 PM, Joonas Lehtonen wrote:
>> Hi,
>>
>> I need debian's kernel because the Qubes kernel does not provide the
>> needed network driver.
>>
>> I'm following the steps here to install the in-VM kernel, instead of t
Hi,
I need debian's kernel because the Qubes kernel does not provide the
needed network driver.
I'm following the steps here to install the in-VM kernel, instead of the
one provided by dom0:
https://www.qubes-os.org/doc/managing-vm-kernel/
The debian 9 template boots fine with pvgrub but
https://nvd.nist.gov/vuln/detail/CVE-2016-10229
> udp.c in the Linux kernel before 4.5 allows remote attackers to
> execute arbitrary code via UDP traffic [...]
fixed in [1] (2015-12-30)
It never affected Fedora according to:
https://bugzilla.redhat.com/show_bug.cgi?id=1439740#c2
> This fix was
>> Once your MAC address is randomized you might also want to prevent the
>> disclosure of your netvm's hostname to the network, since "sys-net"
>> might be a unique hostname (that links all your random MAC addresses and
>> the fact that you likely use qubes).
>
>> To prevent the hostname leak
Hi,
if you setup MAC randomization via network manager in a debian 9
template as described here:
https://www.qubes-os.org/doc/anonymizing-your-mac-address/
you still leak your hostname.
Once your MAC address is randomized you might also want to prevent the
disclosure of your netvm's hostname to
Hi,
before trying it:
Is it still maintained? (working with Qubes 3.2)
If so: There are a few formatting errors in the readme that make it hard
to read
https://github.com/Rudd-O/qubes-network-server/blob/master/README.md
thanks,
Joonas
--
You received this message because you are subscribed
Hi,
just in case others are having similar problems:
I'm running Qubes 3.2.
I created a fresh debian 9 by upgrading from debian 8.
Today the terminal in debian 9 started crashing (closing).
In the logs I saw:
U2MFN_GET_MFN_FOR_PAG: get_user_pages failed, ret=0x2
(or similar -
Are there any optimizations planed?
whonix-ws-dvm takes >50 seconds to start
fedora-24-dvm takes <10 seconds to start
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
thank you unman
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to
Hi,
I'd like to use the WiFi adapter in my laptop in hotspot mode.
Target setup:
wired-netvm <->proxyvm <-> hotspotVM (has the wifi device assigned)
(hotspotVM acts as an access point to other devices)
Creating a NetVM with gets the WiFi adapter assigned and using
NetworkManager to create a
cezg...@gmail.com:
> My guess is lack of time and funding. Qubes definitely could need
> better funding. The Qubes team are doing a great job, but they might
> be limited on what they can manage to get done because there are so
> many things on the to-do list.
>
> Maybe this will change with
Hi,
whonix-gw apparently uses tor 0.2.8.10, the latest 0.2.8.x version being
0.2.8.12 (released 2016-12-19).
Why is it not updated?
I guess there is very little risk in upgrading from 0.2.8.10 to 0.2.8.12.
I'm using a default whonix-gw template with
deb http://deb.whonix.org jessie main
>From
When I look at whonix-ws-dvm "initial memory" it says: ~2800MB
>>>
I changed that to 1000MB and everything works again.
>>>
>>> Why that high?
>
>> since its preset value was over 2800 I didn't want to reduce it to much
>> but I just found out that something changes that value. (I did
Andrew David Wong:
> I don't understand. Isn't the target TemplateVM shut down when
> qvm-create-default-dvm is called? How could it be using any memory
> while it's shut down?
This is not about the initial memory of the used templateVM (in this
case whonix-ws) but about whonix-ws-dvm. (qubes
>> I haven't encountered this before, but it sounds like the Tor Browser
>> update might've pushed you over the default 2 GB size limit. Maybe try
>> increasing the size of your DVM template?
>
> Storing savefile in /dev/shm (tmpfs - stored in RAM only) is an
> optimization to load it faster.
Hi,
when trying to recreate the dvm after the latest torbrowser update I get:
qvm-create-default-dvm whonix-ws
[...]
DVM savefile created successfully.
cp: error writing '/dev/shm/qubes/current-savefile': No space left on device
And DVM starting fails after that obviously.
Do I have to
Marek Marczykowski-Górecki:
> So, expect Fedora 24 template being supported in R3.1 soon too :)
Thank you!
Looking forward to the announcement.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving
Hi,
since Qubes 3.1 is supported until 2017-03-29
according to
https://www.qubes-os.org/doc/supported-versions/
does that mean we will see a Fedora 24 template for R3.1 before Fedora
23 reaches EOL?
thanks,
Joonas
--
You received this message because you are subscribed to the Google Groups
Richard:
> I'm trying to upgrade my Qubes 3.1.17 to 3.2 I've followed the steps
> outlined here: https://www.qubes-os.org/doc/upgrade-to-r3.2/ However, when I
> run...
>
>sudo qubes-dom0-update --releasever=3.2 qubes-release
>
> I receive:
> Nothing to do
>
I'm also
>> I'm not sure if it worth it. There is not much such announcements. On
>> the other hand, this may be exactly the reason for having a separate
>> mailing list for this.
I would also love to see a QSB-announce mailing (especially because
qubes-users is quite active, and only subscribing to
26 matches
Mail list logo
