Re: [EXT] [qubes-users] How to edit Qubes R4.0.3 ISO image file in Windows 10 system

[Data Eight]

Hello Qubes Google Group Members (who are gave their suggenstions to my 
post):
Thanks all for your help and support regarding editing Qubes ISO image.

I referred the UEFI Troubleshooting web page and installed the QUBES OS in 
my Dell Inspiron and started to learn to work with QUBES.
Thanks once again. 

The exact problem I have is system get freezed when the system get reboot 
after successful QUBES OS installation. So, as per UEFI troubleshooting 
instruction for UEFI system, I have included some kernal line changes in 
xen.cfg file using vi editor, before selecting reboot after Qubes install.

The procedure I followed for this modification is as follows:
1. dont select reboot after successful installation of Qubes OS
2. press *ctrl+alt+f2*
3. type: *vi /mnt/sysimage/boot/efi/EFI/qubes/xen.cfg*
4. remove the following from the first line: *smt=off *and insert 
*efi=attr=uc*
5. then enter the following: *:wq*
6. press ctrl+alt+f6
7. select reboot.

Thats it. Now the black screen problem what I have faced was gone. I posted 
what I followed to resolve this problem. The above procedure will be 
helpful for someone. The windows 10 word in the help requested post, is 
actually not relevant to be used to ask suggession.  So sorry for it.

Thanks once again Group Users who are responded.
  

On Monday, December 21, 2020 at 5:02:38 AM UTC+5:30 Ulrich Windl wrote:

> On 12/14/20 7:42 PM, Data Eight wrote:
> > I am trying to install "Qubes-R4.0.3-x86-64 OS" on Windows 10 UEFI 
> > system. Using Rufus created bootable media (DD image option selected). 
> > The installation is done (till the message that qubes successfully 
> > installed and ready to go) but after first reboot, the black screen not 
> > proceed further.
>
> If you ever messed with grub2's boot menu, I could suggest to remove the 
> "quiet" option. So there should be some messages when booting, and maybe 
> sone message is the last one, so you may get a clue...
>
> > 
> > I found to add two lines (bootnoexit=1; mapbs=1) in each kernel section 
> > within bootx64.cfg  file within EFI folder.
> > 
> > But it is not working in Windows 10. Since I am a New user to Qubes OS, 
> > I request help in this issue (Can't logging to Qubes).
>
> What Do you mean with "in Windows 10"?: Run as VM in Windows 10?
>
> > 
> > Thanks in advance for your help.
> > 
> > -- 
> > 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...@googlegroups.com 
> > .
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/qubes-users/CALdk6vJ1-4ZNAYZ-viJfKyiHdBwpXiM4uF-hLKXsb3Ygwh%2BBtw%40mail.gmail.com
>  
> > <
> https://groups.google.com/d/msgid/qubes-users/CALdk6vJ1-4ZNAYZ-viJfKyiHdBwpXiM4uF-hLKXsb3Ygwh%2BBtw%40mail.gmail.com?utm_medium=email&utm_source=footer
> >.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9e39bd90-be0d-476c-b81b-eb8601292048n%40googlegroups.com.

Re: [qubes-users] Qubes Manager Feature Requests: Connect to not-running NetVM, restart NetVM with connected machines, force-restart a NetVM

[donoban]

Hi,

On 2/15/21 12:44 PM, r.wiesb...@web.de wrote:
> Hello fellow Qubes users,
> 
> I have 3 feature requests today regarding Qubes Manager:
> 
> 1) Connect to not-running NetVM
> If a not-running NetVM is chosen there should not be an error message
> but a choice between "Start NetVM" and "Abort"

This is already done in R4.1 version.

> 2) restart netVM with connected machines
> Sometimes NetVMs have issues that are easily solved by a restart.
> Nastily Qubes prevents restarting the netVM if VMs are connected. What
> should optionally happen is either that the connected VMs are
> disconnected, the NetVM is restarted and the VMs are reconnected (that
> is what I do manually whenever this is needed) or alternatively that all
> connected VMs are restarted as well.

Respect this there is a "Cascade shutdown" that will power off all the
connected VM's in recursive mode. I understand that is not what you
mean, you want a option for restart this VM without touching any others...

I understand that you find it helpful for some kind of hardware problem
(sleep / wake up?) but it seems more a hack than a real solution.

> 3) force-reboot a VM
> Users can kill a VM, but this way the user has to wait until the VM was
> terminated and then start the machine again (kill + start). It would be
> useful to have a single option for both tasks. That happens to me almost
> daily with the USB-VM.

Uhm more than a force-reboot option, ideally the restart option should
trigger a timeout and if it expires ask you if you want to kill it or
keep waiting (same that shutdown option). Is it not the current behavior?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/dae1c199-095a-a380-33ea-49785a310b4b%40riseup.net.


OpenPGP_signature
Description: OpenPGP digital signature

[qubes-users] Qubes Manager Feature Requests: Connect to not-running NetVM, restart NetVM with connected machines, force-restart a NetVM

[r . wiesbach]

Hello fellow Qubes users,

I have 3 feature requests today regarding Qubes Manager:

1) Connect to not-running NetVM
If a not-running NetVM is chosen there should not be an error message
but a choice between "Start NetVM" and "Abort"

2) restart netVM with connected machines
Sometimes NetVMs have issues that are easily solved by a restart.
Nastily Qubes prevents restarting the netVM if VMs are connected. What
should optionally happen is either that the connected VMs are
disconnected, the NetVM is restarted and the VMs are reconnected (that
is what I do manually whenever this is needed) or alternatively that all
connected VMs are restarted as well.

3) force-reboot a VM
Users can kill a VM, but this way the user has to wait until the VM was
terminated and then start the machine again (kill + start). It would be
useful to have a single option for both tasks. That happens to me almost
daily with the USB-VM.

Thank you.

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d51d00cb-5013-0a69-bcd9-0677378ec04f%40web.de.